SAP ABAP Data Element ADDI_STATUS (Status of an additional)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
LO-ADM (Application Component) Additionals Management
⤷
WTAD (Package) IS-R: Additionals
⤷
⤷
Basic Data
| Data Element | ADDI_STATUS |
| Short Description | Status of an additional |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ADDI_STATUS | |
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | STATUS | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Status |
| Medium | 15 | Status, addit. |
| Long | 27 | Status of an additional |
| Heading | 11 | Status,add. |
Documentation
Definition
Status of an additional of a material.
Use The value of the status is displayed in the additionals monitor as a stop light.
The status has the following values:
- 0
The steps required for the associated follow-up actions were successfully completed. For example, an additionals IDoc was successfully generated as a result of a goods movement.
- 1
Some of the subsequent processing have been successfully completed. This value is set if, for example, a purchase order is generated for the follow-up action "Order additional", but only a partial delivery of the associated material has been received.
- 2
The individual processes have not been completed. The purchase order, for example, has still to be printed.
Notes
The values for this field is set internally by the program.
History
| Last changed by/on | SAP | 19990412 |
| SAP Release Created in |