Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

A Business Process solves a particular issue by transforming a defined business input into a defined and measurable business output via the execution of one or more Process Steps.
• Possible input can be any business relevant information. Having the same input and output, the sequence of Process Steps can vary, with each variation of the sequence being a Business Process Variant.
• A Business Process begins with a specific customer's need and ends with the fulfillment of that need.
• It is usually carried out within one organizational department or a group specialized in this tasks.
• It is defined independently of a specific Business Scenario and can therefore be used in different Business Scenarios.
• It is software independent.


It serves to achieve consistent granularity across the processes within a bid or project as well as across different SAP product lines and industries.

Business Processes defined with the guidelines below (see section "cut criteria") allow to integrate the process, functionality and service views as well as the data and organization views in one entity.  
Business Processes also structure projects and content in all different Application and Process Lifecycle Phases:

1. The structure is used to document the Business Processes
2. Lay the foundation for Project Engineering, Opportunity Management and Project Management
3. Structure organizational change management, development and requirements management. For proper requirements management it is key to understand which KPIs/ PPIs a Business Process is fulfilling. It is also necessary to define the KPIs/ PPIs for every Business process to clarify the value and benefits to be achieve.
4. Provide structure for Business Process monitoring
5. Are the foundation to decide how business requirement should be implemented with SAP standard software (customizing), with a partner product, with a development or whether the development could be realized with a SOA composition

Naming Conventions

Try to use gerund formulations expressing process character. Examples:

Otherwise, e.g. for existing business terms, use nominal formulations expressing process character. Example: Instead of "Managing Sales Orders" you could say "Sales Order Management" as well.

General guidelines

Do not use abbreviations, such as w/o (for without) or TPM (for Trade Promotion Management). They may not be transparent to the user, especially if the user is not a native speaker or not an expert in this specific subject.

72 characters is the maximum for any language. Consider leaving space for translation into other languages. Keep formulations straight to the point (telegram style).


Forecasting Maintenance, Managing Sales Orders

Cut Criteria

1. Business Process borders should be cut in a way to follow typical, industry organizational responsibilities in a company. If in a simulated company you hand over work from one specialized group / team / department to the next group we consider this as a border of a Business Process.  

When to create a new Business Process or only a new Business Process Variant? 
If you have two processing variants which create or update the same Business Objects they form Business Process Variants and not two separate Business Processes. This is also true if the processing variants share the same central Business Object and differ in separate additional Business Objects used.

Example: Paying with cash transfer and cheque both use a Business Object "payment". For paying with cheque there is an additional Business Object "outgoing cheque" needed. Both processing variants form two variants of the same Business Process.

Illustration in ARIS

  • No labels