A business scenario is a series of business process steps. The importance of each business process step is most apparent in the business scenario context, for example, the "Delivery" business step differs greatly when used in the "Import" and "Export" business scenarios. One option for taking this differentiation into consideration is to create a new business process step for each contect. In the example detailed above, it is possible to define two new business process steps, one called "Export Delivery" and another called "Import Delivery". If this approach would be taken for all business process steps, a single business scenario could be used. Alternatively, it could also be possible to create two business scenarios, one called "Import" and one called "Export" and use a single business process step called "Delivery". From a technical perspective, the business scenario in the Trading Execution Workbench (TEW) part of the key for determining the subsequent action. Attributes "Step", "Session", "Previous step" and "Business scenario" clearly determine which action class is called. While "Step", "Session" and "Previous step" have to be entered in the TEW, the business scenario is determined automatically. BAdI "WB2_CALC_SCENARIO" is used to define the business scenario at item level. In the document data structures of the TEW, the business scenario is stored in the dynamic fields "SCENARIO_GT". This field is set using a enhancement class. The following enhancement classes are used to extract data from trading contracts:
All these enhancement classes read the business scenario data out of enhancement table "WBGT". For scenarios at header level, it is important to ensure that the processes have been designed to ensure that all items possess the same business scenario. If this is not the case, the enhancement classes listed above initialize the business scenario at header level. If a business scenario is not used, business scenario "00" with the following enhancement classes can be used: