top of page

What is BRD, FS, TS, BBP, AS-IS, TO-BE?

Updated: Mar 9

In the context of SAP implementation or software development projects, the terms BRD, FS, TS, BBP, AS IS, and TO-BE refer to various project documents and stages. Each of these documents plays a crucial role in defining and documenting the project requirements, scope, and objectives. Let's explain each of them:

  1. BRD (Business Requirements Document): The BRD is a document that outlines the business needs, requirements, and objectives of the project from a high-level perspective. It defines what the business wants to achieve through the project and serves as a foundation for the subsequent project documents.

  2. FS (Functional Specification): The FS is a detailed document that expands on the business requirements outlined in the BRD. It provides a comprehensive description of how the system or solution will fulfill these requirements from a functional perspective. The document may include information about data structures, user interfaces, process flows, business rules, and more.

  3. TS (Technical Specification): The TS is a document that builds on the FS and delves into the technical aspects of the project. It provides detailed information on how the system will be built or configured to meet the functional requirements. The TS is usually used by developers, technical consultants, and system administrators.

  4. BBP (Business Blueprint): The BBP is a critical document in SAP implementation projects. It bridges the gap between business requirements and system configuration. It maps the business processes, organizational structure, and requirements to specific SAP modules or functionalities. The BBP serves as a blueprint for the system configuration and customization.

  5. AS-IS: The AS IS represents the current state of the business processes and systems before the SAP implementation or project begins. It involves documenting existing processes, systems, pain points, and inefficiencies. The AS-IS analysis helps identify areas for improvement and informs the TO-BE state.

  6. TO-BE: The TO-BE represents the future or desired state of the business processes and systems after the SAP implementation or project is completed. It is based on the analysis of the AS-IS state and the defined business requirements. The TO-BE state describes how the business processes will operate with the new SAP solution in place.

These documents and terms are commonly used in SAP projects, and they help ensure that the project team, stakeholders, and consultants have a clear understanding of the project objectives, requirements, and deliverables. Each document serves a specific purpose in different phases of the project lifecycle.

For SAP Training Contact us at:

To Learn this Documentation concept book a slot

107 views0 comments

Recent Posts

See All

Who should take SAP FICO / S/4 HAN Finance training?

SAP FICO / S/4HANA Finance training is typically targeted towards individuals and professionals who have roles or aspirations in finance and accounting and want to work with SAP's Finance and Controll


Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page