Business Scenario Design Guidelines

[Former Member]

I am hoping one of you experts will be able to help me with a fundamental Solution Manager question.

Many of the Solution Manager tools (BPMon, Solution Documentation, RBPD, Exception Mgmt etc) require that the Business Process Hierarchy is setup correctly. The documentation tells you to create a 3 level hierarchy, comprising of Business Scenario, Business Process and Process Steps.

I would like specific guidelines on how these are to be created. Should a process step exist in only one scenario or can it exist in multiple scenarios?

Consider the following Procurement Scenarios. If I create scenarios like below

• Procure to Pay for planned inventory items  – starting from MRP, Purchase Req, Purchase Order, Inbound Delivery, Goods Receipt, Invoice Receipt etc
• Procure to Pay for unplanned inventory items  – starting from Purchase Req, Purchase Order, Inbound Delivery, Goods Receipt, Invoice Receipt etc
• Procure to Pay for Catalog based consumables – starting from Shopping cart in SRM, Purchase Req, Purchase Order, Goods Receipt, Invoice Receipt etc
• Procure to Pay for Non Stock Items
• Procure to Pay for rush orders
• etc

Will this approach create problems in the future or if we use BPMon or RBPD? Or should we stick to just the one all-encompassing Procure to Pay which has all steps but only once?

From a business perspective, it makes sense to create different scenarios.  But I am perplexed as to how BPMon will figure out statistics for each scenario, unless there is a way of entering document type?  How have other people designed this?

Thanks in advance

Jayshree

[Former Member · Accepted solution]

Hi Jayashree,

A process step can exist in multiple scenarios in solution documentation/blueprints.

When we are talking about BPM , the standard procure to pay , order to cash scenarios are already available in the configuration. When you add them , it will pick the required monitoring contexts and capture the usage of the documents/orders etc.

Please visit the below site for more details:

https://websmp203.sap-ag.de/bpm - > Business process monitoring -> Media library

For solution documentation info -> Please visit http://service.sap.com/rkt-solman -> Solution Implementation section.

Thanks,

Jagadish.

[Former Member]

Hi,

this is the another challenge we faced in our documentation project, and later we concluded it all depends on how your business runs and the functionality which you required to use.

for pure documentation purpose, your functional guys comes forward and provide you the business process stes.

And best practise to go end to end business process flow ir respective of systems, means if you have global purchase and local purchase, may be the flow  would be same, systems involved might differ.either or the case create business process steps as same as your business flow. 

other related discussions here http://scn.sap.com/thread/3169612

Thanks,

Jansi