Skip to Content
0
Former Member
Jan 24, 2013 at 04:48 AM

Business Scenario Design Guidelines

126 Views

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