I once read that “if you can’t explain simply that means you don’t understand well”. Organizational business processes are complex and putting them on a paper is generally an art than a science without standardized Business Process Modeling(BPM) standards.
Business process modeling (BPM), also called process modeling, is the illustration or representation of an organization’s activity or set of activities that will help the organization achieve its goals. In SAP implementations, it is a standard practice to map the current processes to create a baseline for future improvements. Often referred AS IS and then draw the TO BE (which if the future state).
The key reason to do is to simply reduce the communication gaps across all levels of the organizations. As simple mistakes, can be very costly as shown below.
If the business process is modeled correctly, then it would depict the activity, roles & responsibilities of each person/role (who starts it and who executes), input/output from each process step which would automatically reduce the communication gaps, improve efficiency and makes it easy to find opportunities for automation.
For S/4HANA, look no further than best practices where SAP provides such process diagrams. These can be used as starting point to understand the process, application/systems involved and roles that you need in the organization.
Process Diagrams in SAP S/4HANA Best Practices will jump start the discussion and keep all the stakeholders in the same page from business to IT.
They also come with BPMN so you can download any modify with BPMN supported tool. Here is how you can find them.
I took an integration scenario between S/4HANA Cloud and SAP Hybris Cloud for Customer for example purposes only. You take any best practice scope item, it usually comes with a very good business process diagram that should kick start your implementations and standardizes the enterprise knowledge like never before.
Best!!
Business process modeling (BPM), also called process modeling, is the illustration or representation of an organization’s activity or set of activities that will help the organization achieve its goals. In SAP implementations, it is a standard practice to map the current processes to create a baseline for future improvements. Often referred AS IS and then draw the TO BE (which if the future state).
The key reason to do is to simply reduce the communication gaps across all levels of the organizations. As simple mistakes, can be very costly as shown below.
NASA lost a $125 million Mars orbiter because one engineering team used metric units while another used English units…
If the business process is modeled correctly, then it would depict the activity, roles & responsibilities of each person/role (who starts it and who executes), input/output from each process step which would automatically reduce the communication gaps, improve efficiency and makes it easy to find opportunities for automation.
Process model should draw a balance between relationship and action, cognition and affect, message and medium.
Source: D. Te’eni, A cognitive-affective model of organizational communication for designing IT, MIS Quarterly 25 (2) (2001) 251–312.
For S/4HANA, look no further than best practices where SAP provides such process diagrams. These can be used as starting point to understand the process, application/systems involved and roles that you need in the organization.
Process Diagrams in SAP S/4HANA Best Practices will jump start the discussion and keep all the stakeholders in the same page from business to IT.
They also come with BPMN so you can download any modify with BPMN supported tool. Here is how you can find them.
SAP Best Practices Explorer https://rapid.sap.com/bp/
I took an integration scenario between S/4HANA Cloud and SAP Hybris Cloud for Customer for example purposes only. You take any best practice scope item, it usually comes with a very good business process diagram that should kick start your implementations and standardizes the enterprise knowledge like never before.
Best!!
- SAP Managed Tags:
7 Comments
