SAP ABAP Data Element /SAPTRX/REQ_SET_NBR (Requirement Set Number)
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷ SCM-EM (Application Component) Event Management
⤷ /SAPTRX/ATIF (Package) Interface objects for Event Manager and Appl.Srv
⤷ SCM-EM (Application Component) Event Management
⤷ /SAPTRX/ATIF (Package) Interface objects for Event Manager and Appl.Srv
Basic Data
Data Element | /SAPTRX/REQ_SET_NBR |
Short Description | Requirement Set Number |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /SAPTRX/REQ_SET_NBR | |
Data Type | NUMC | Character string with only digits |
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 | Req. Set |
Medium | 15 | Req. Set No. |
Long | 25 | Requirement Set Number |
Heading | 10 | Req. Set |
Documentation
Definition
Used to group logically-related required expected events. Expected events should be assigned the same requirements set number if any one event in the group is required. For example, either delivery departure or proof of delivery.
When checking required predecessors, expected events in the same requirement set are not checked.
For example, you define an expected event set one (EES 1) with expected events one (EE1) and two (EE2) and an expected event set two (EES2) with expected events three (EE3) and four (EE4). When checking the predecessors and successors of expected events that have occurred, if EE4 occurs you can assume that EE1 has already occurred, since EE1 belongs to the predecessor set for expected events.
History
Last changed by/on | SAP | 20080415 |
SAP Release Created in | 46C |