Modeling Process Variants of a Business Scenario 

The Business Scenario design environment in the Integration Builder does not permit the qualified representation of branching (AND, OR, XOR) or any other complex process modeling constructs.

·        When representing different process variants you must find an appropriate compromise between the clarity of the Business Scenario on the one hand, and the number of separately defined Business Scenarios on the other.

·        Note the following conventions:

¡        Any optional actions (and communication steps) must be included in the Business Scenario and documented explicitly as optional. It is then clear in the Business Scenario that these optional steps do not necessarily have to be executed.

¡        If there are various branches in the process logic (OR, XOR) and the branches are located in different application components, then both branches must be included in the Business Scenario and documented accordingly.

¡        If there are various branches in the process logic (OR, XOR) and the branches are located in the same application components, then you must decide if it is vital that the branches are modeled at all.

·        The Business Scenario design environment in the Integration Builder does not permit any explicit variant management. Therefore, it is recommend that you include the different variants in a Business Scenario wherever possible. However, if the Business Scenario becomes overly complicated as a result, or it ceases to be comprehensible, SAP recommends that you model the variant as a separate Business Scenario.