Business Process Mapping scenario: "Best Practice"

[Former Member]

Hi All,

Configuring the Business Process scenarios in Solution Manager 7.01 we identified different Business Processes (E.g.: P2P and Workforce Management) use the same process steps and transactions.

As we envisaged the risk of uncontrolled overlaps between the core business processes, we finalised two different options:

1. Map the BP scenarios and transactions in silos. This option will force us to repeat the same configuration in both business process/steps/transaction (E.g.: P2P and WM). The counter effect is the overload during the implementation phase as well as a major governance effort to guarantee the change in the different BPs will cascade in all the BP scenarios impacted.

2. Map the scenarios linking (cross-reference) the specific steps to the process/transaction whenever necessary. Potentially, this second approach will generate a suitable solution consistent with the BPMon scope.

Having told this my questions are:

a) is there any u201Cbest practiceu201D (or approach) you already used to mitigate the risk we envisage?

b) If option 2 is the preferred one, is there a configuration document to link the BPs?

Regards,

Giampaolo

[Former Member · Accepted solution]

Just a quick update as we recognized that transactions and Process Steps occur in several processes in the SolMan structure is unavoidable. Whenever we will configure a Process Step, we will use the u201CWhere usedu201D feature in SolMan to determine which other Processes are using configuration (IMG nodes), transactions and technical objects related to this Process Step.

[Former Member · Accepted solution]

Solved and solution published

Edited by: Giampaolo Lupi on Nov 3, 2011 11:10 AM