Table 4 Comparison of the process... | Emerald Publishing

Table 4

Comparison of the process discovery before and after the demand realization

Before demand realization (business process changed)	After demand realization (business process changed)	Finding
The SAP automatically created a workflow (task) to indicate a new document, the task TAK agreement was created manually by the user. In case of forgetting to create the task, it leads to a long process duration Please see appendix table A, Figure A1 for more details	The DMS system was enhanced to identify the type of document, therefore the tasks TAK agreement was created automatically and process duration was improved significantly Please see appendix table A, Figure A2 for more details	(1) New DMS/scan is followed by TAK agreement
After the creation of a workflow (task) TAK agreement, an update flag indicated changes for the external partner systems Please see appendix table A, Figure A3 for more details	The automatic creation of the task leads to an early and reliable update of external providers Please see appendix table A, Figure A4 for more details	(2) Task TAK agreement is followed by Update EPC stat
When the user received the workflow that a TAK agreement was active for a specific claim, the user updated the memo field and the reserve of a claim Please see appendix table A, Figure A5 for more details	The full process can be automated, since the payments and total expenses indication in a document can lead to automatic processing Please see appendix table A, Figure A6 for more details	(3) Manual memo “TAK” is followed by a reserve change
The process expert identified the need of additional involvement of architecture, DMS (document services) and external party providers as there was an interface to these systems Please see appendix table A, Figure A7 for more details	The increased awareness of all teams lead to better decision-making and improved teamwork on changing this process. The early involvement of the responsible teams lead to a better alignment in development, testing and release of the change Please see appendix table A, Figure A8 for more details	(4) New claim DMS/scan is followed by task TAK agreement
In the old process, the identification of a TAK agreement happened after the closure of a subclaim (and the claim was already closed) Please see appendix table A, Figure A9 for more details	The change of the process lead to a more reliable and efficient processing, since the TAK process is identified very early Please see appendix table A, Figure A10 for more details	(5) Subclaim closed is sometimes followed by TAK document

Before demand realization (business process changed)	After demand realization (business process changed)	Finding
The SAP automatically created a workflow (task) to indicate a new document, the task TAK agreement was created manually by the user. In case of forgetting to create the task, it leads to a long process durationPlease see appendix table A, Figure A1 for more details	The DMS system was enhanced to identify the type of document, therefore the tasks TAK agreement was created automatically and process duration was improved significantlyPlease see appendix table A, Figure A2 for more details	(1) New DMS/scan is followed by TAK agreement
After the creation of a workflow (task) TAK agreement, an update flag indicated changes for the external partner systemsPlease see appendix table A, Figure A3 for more details	The automatic creation of the task leads to an early and reliable update of external providersPlease see appendix table A, Figure A4 for more details	(2) Task TAK agreement is followed by Update EPC stat
When the user received the workflow that a TAK agreement was active for a specific claim, the user updated the memo field and the reserve of a claimPlease see appendix table A, Figure A5 for more details	The full process can be automated, since the payments and total expenses indication in a document can lead to automatic processingPlease see appendix table A, Figure A6 for more details	(3) Manual memo “TAK” is followed by a reserve change
The process expert identified the need of additional involvement of architecture, DMS (document services) and external party providers as there was an interface to these systemsPlease see appendix table A, Figure A7 for more details	The increased awareness of all teams lead to better decision-making and improved teamwork on changing this process. The early involvement of the responsible teams lead to a better alignment in development, testing and release of the changePlease see appendix table A, Figure A8 for more details	(4) New claim DMS/scan is followed by task TAK agreement
In the old process, the identification of a TAK agreement happened after the closure of a subclaim (and the claim was already closed)Please see appendix table A, Figure A9 for more details	The change of the process lead to a more reliable and efficient processing, since the TAK process is identified very earlyPlease see appendix table A, Figure A10 for more details	(5) Subclaim closed is sometimes followed by TAK document

Source(s): Created by authors