Hierarchy
⤷
⤷
Basic Data
| Data Element | WUF_PRED_TRANS_ORDER |
| Short Description | Predecessor Transformation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WUF_ORDER | |
| Data Type | NUMC | Character string with only digits |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 | Predecess. |
| Medium | 15 | Predecessor |
| Long | 25 | PredecessorTransformation |
| Heading | 10 | Predecess. |
Documentation
Definition
Contains the definition of a sequence of transformations.
Use
To define a sequence of transformations, you assign a predecessor to a transformation. The system performs a transformation that has a predecessor only if the predecessor transformation was unsuccessful, meaning that the return parameter "e_ok" was equal to ' '. The system processes all transformations in the order specified in "Sequence of the Transformation Call-Up". This means that it does not make sense for a transformation to refer to a predecessor with a higher sequence. The system only checks (for every transformation with a predecessor) whether the predecessor was performed with a positive result.
Dependencies
Example
You can determine a material in several ways from given input data. The system implements every determination method in a separate method. The methods are specified in a sequence that corresponds to their hierarchy, whereby each method refers to its respective predecessor.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |