Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-SOA-SMT (Application Component) Service Mapping Tool⤷
GMT_GENERAL (Package) Objects for All Packages Within GMT
Basic Data
| Data Element | SMT_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 | SMT_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 | Predecessor Transformatn |
| Heading | 10 | Predecess. |
Documentation
Definition
Contains the definition of a sequence of transformations.
Use
In order to define a sequence of transformations, you assign a predecessor to a transformation. A transformation that has a predecessor is only executed if the predecessor transformation was not successful, that is, if the return parameter was "e_ok" or ' '. The system processes all transformations in the sequence determined by the "Sequence of the Transformation Call-Up". Therefore, it is not logical for a transformation to refer to a predecessor with a higher sequence. The system checks for each transformation with a predecessor only if the predecessor has been executed with a positive result.
Dependencies
Example
There are multiple ways of determining a material from given input data. Each determination method is implemented in a separate method. The methods are specified in the sequence corresponding to the hierarchy, they refer to their relevant precessor.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
