Business Process Repository (BPR)

Contains a set of SAP best practices, and references to Transactions, Data, and user information and documentation. It is organized by industry, then departmental or functional focus. The BPR is used to seed the Business Blueprint projects with Business Scenarios.

Business Blueprint (a.k.a. Blueprint)

Business requirements for process implementation. The structure for accessing best practices for SAP Transactions related to industry processes, and for the business users to guide IT implementation.

Business Blueprint Project (a.k.a. Project)

A specific project within the Business Blueprint. Contains the hierarchical 'Structure' or process landscape—made up of Scenarios (Level 1), Processes (Level 2), and Process Steps (Level 3) —that is used to organize Transactions, Master Data, and Organizational Units, and refer to End User Roles and Logical Components.

Scenario (a.k.a. Business Scenario)

Level 1 of the blueprint project process hierarchy; a top-level process. For example, the Procurement to Payment processes. Processes (Level 2) are contained within the Scenario.

Process (a.k.a. Business Process)

Level 2 of the blueprint project process hierarchy; underneath (a subprocess of) a Business Scenario. For example, Processing Purchase Requisitions. Process Steps (Level 3) are contained within the Processes.

Process Step

Level 3 of the blueprint project process hierarchy, and the lowest (atomic) level of process structure. For example, Act on a Purchase Requisition. Typically associated with Transactions

Transaction

A program or application. Transactions may be programs executing something in the background, or be used as screens with User Interface (UI); such as a screen to enter your business expenses into an expense report. Typically associated with Process Steps, and can be associated with Scenarios and Processes.

Master Data

Data fields that are used by the Transactions. These are only related to Blueprint Projects and Scenarios, and not Processes or Process Steps. Can be added to (referenced by) the Blueprint project from the BPR.

End User Role

User, Job, or Role that will be using the process. Added to (referenced by) the project from the SAP HR model into the Blueprint project. Frequently includes people involved in end user testing, and those trained on, SAP implementation and changes.

Organizational Unit

Organization in the business that are accountable for the costs of processes, defined at a Project or Scenario level. Can be added to (referenced by) the Blueprint project from the BPR.

Logical Component

The component that must be loaded on the SAP system in order to provide certain functionality. For example: the Customer Relationship Management (CRM) system resource. Logical Components are defined per project. Process Steps and Transactions are supported by Logical Components, and the Logical Component must be the same for related Process Steps and Transactions.

Documentation

Includes General Documentation, loaded from the BPR, typically containing explanation of processes, and Project Documentation specific to the Blueprint project.