Hierarchy
EA-GLTRADE (Software Component) SAP Enterprise Extension Global Trade⤷
LO-GT-TEW (Application Component) Trading Execution Workbench⤷
WB2B_TEW (Package) Trading Execution Workbench
Basic Data
| Data Element | WB2_MASTER_STEP |
| Short Description | Main Step |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WB2_STEP | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | MasterStep |
| Medium | 15 | Master Step |
| Long | 20 | Main Step |
| Heading | 15 | Master Step |
Documentation
Definition
Each business process step can be assigned a different business process step as its master step. The business process step and master step must have the same document type. By assigning a master step to a business process step, you create a simple hierarchy that influences the selection of data and association management. If a business process step has a master step, associations are created for the master step, not the business process step.
If the same master step is assigned to several business process steps, step-independent selection of source documents is possible.
Example
Association:
A business process contains the steps "Prepare delivery" and "Close delivery". When the "Prepare delivery" step is generated, the R/3 delivery document is generated. When the "Close delivery" step is generated from the "Prepare delivery" step, the delivery document is changed and a goods issue is posted. In association management, this creates the problem that the business process step of the R/3 delivery document changes from "Prepare delivery" to "Close delivery". If associations were created for the business process step "Prepare delivery", these entries are incorrect after the changeover to "Close delivery". The business process entries in the association tables are not automatically adjusted if the business process step of a R/3 document changes. As a result, in these cases, you must use a master step. The same master step must be maintained for both business process steps, for example "Prepare delivery" or a more general "Delivery" step. As the associations are carried out using the master step, the association entries are still valid even after the business process step has changed from "Prepare delivery" to "Close delivery".
Selection:
Let us use business processes "A" and "B" as examples. Business process step "C" is assigned to business processes "A" and "B" as the master step. If the "Selection by master step" indicator is set for business process step "C", with preceding step "C", the TEW selects all documents with business process step "A" or "B".
History
| Last changed by/on | SAP | 20020125 |
| SAP Release Created in | 46C |
