Hierarchy
BBPCRM (Software Component) BBPCRM⤷
LO-ADM (Application Component) Additionals Management⤷
WTAD (Package) IS-R: Additionals
Basic Data
| Data Element | ADDI_IDOCSUB |
| Short Description | Additionals IDoc: sub-system status update |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Sub. stat. |
| Medium | 16 | Sub-syst. status |
| Long | 25 | Sub-system IDoc status |
| Heading | 30 | Add. IDoc status in sub-system |
Documentation
Definition
Processing status of the additionals IDoc that is to be updated in your ERP system using a subsystem.
Use
Price tickets can be printed by a subsystem. The subsystem processes the additionals IDoc data and generates, for example, control commands for a ticket printer.
The subsystem can be triggered by an ALE layer. After having completed the activity, the subsysten can call the ChangeStatus method for business object 2106. By doing this, the processing status is logged in the ERP system by the subsystem.
You can then configure your system to update, or not update, the subsystem status. You have to flag the indicator to do this.
Notes
You can display the update status in the additionals monitor.
The IDoc number is assigned to the additionals document when the status is updated. This means that you can find your data more easily in the additionals monitor.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
