SAP ABAP Data Element UPS_PREGEN (ALE Distribution Unit: Strategy for PredecessorDetermination)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-GTF-UPS (Application Component) Distribution Unit / Distribution Packet
⤷
U_P_S (Package) ALE Distribution Unit

⤷

⤷

Basic Data
Data Element | UPS_PREGEN |
Short Description | ALE Distribution Unit: Strategy for PredecessorDetermination |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | UPS_PREGEN | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | GenPredec. |
Medium | 20 | DeterminePredecessor |
Long | 30 | Determine Predecessor Units |
Heading | 10 | GenPredec. |
Documentation
Definition
Strategy for predecessor determination.
Several ALE distribution units (UPS) can contain interdependent data that needs to be serialized, or posted in the correct sequence.
Use
The following serialization strategies are available:
- ' ' : No serialization
- '1' : Determination by identical packet type
Any UPS of the same packet type that has already been sent is interpreted as a predecessor. Each of these must be posted in the target system before the current UPS can be posted.
- '2' : Determination by identical objects to be imported
Any UPS that contains one of the objects to be imported (that triggers distribution) is interpreted as a predecessor. Each of these must be posted in the target system before the current UPS can be posted.
Dependencies
Example
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 46C2 |