Definition
In this substructure, you can analyze and document the process flow of your enterprise. The Business Processes substructure contains enterprise areas, which are broken down into scenarios, process groups, processes, and objects for which a wide range of additional information is available. You can use the Diagram Explorer to
display diagrams for structure items at various levels.Use
The customer input templates for the structure items in the Business Processes substructure allow you to document and analyze the main areas of importance for your enterprise in this area. The information you enter here is essential for drawing up your Business Blueprint. The customer input template for the Business Processes substructure is made up of the following sections:
Sections in the CI template for Business processes |
Content |
|
Construct a bulleted list of requirements and expectations for this structure item. This list should be specific to the customer and reflect their input. Critical points should be clearly visible. |
|
Describe in as much detail as possible how this structure item will be used in the customer’s enterprise. The most important business processes should be described in detail in this section. |
|
Describe the process flow in the EPC diagram. Include details of what happens at each event and process and how this affects downstream processes. |
|
Describe how the process flow in the customer's enterprise is displayed in the model. |
|
Address issues agreed in the workshop on the organizational structure of the SAP System. For example:
|
|
Describe the effect of this structure item on the customer’s enterprise structure. For example:
|
|
Describe improvements in the area of Business Processes which will result from implementation of SAP software. Be sure to include any impact on Business Drivers. By recording these improvements, benefits to the customer's enterprise become apparent. |
|
Detail any real or perceived gaps in functionality that have become evident through the business process review sessions. Enter "None apparent" if the customer’s requirements seem to have been fulfilled. |
|
Address any functional deficits, for example, in short-term solutions, user exits or ABAP. Look for the best high-level solution. If no solution is evident, the impact on the customer and the project must be clear, so that the team can decide how best to proceed. Enter "None apparent" if the customer’s requirements seem to have been fulfilled. |
|
Describe future or potential improvements, as well as issues to be clarified in a future SAP release or project phase. Any issues raised in the process review that are outside the current project scope should be recorded here. |
|
Describe issues of importance to the customer in relation to system configuration. Details are not required, but be sure to address any issues addressed during the review. |
|
Describe how the customer will manage security in this area. Don't cover the creation of authorizations in too much detail. Sensitize the team to the system functions and get the process owners to think about access to the system and its data. |
|
Enter any project-specific information that has not been covered in the sections above. |
You can find information on how to fill out the template under
Working with customer input templates.