Hierarchy
BBPCRM (Software Component) BBPCRM⤷
LO-ADM (Application Component) Additionals Management⤷
WTAD (Package) IS-R: Additionals
Basic Data
| Data Element | ADDI_EVENT |
| Short Description | Event that triggers follow-up actions for additionals |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ADDI_EVENT | |
| 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 | Event |
| Medium | 15 | Event |
| Long | 20 | Event |
| Heading | 10 | Event |
Documentation
Definition
Event of an application which triggers a follow-up action for additionals.
Use
The event is used in Customizing for additionals to control follow-up actions.
Notes
The only event defined for application "Goods movement" is "Create". The change and delete functions for a goods movement are modeled in the system using movement types.
If, for example, you want to create an additionals IDoc for a goods receipt in the distribution center, you must create a detailed entry
in the control table for event "Create" in Customizing for the procedure.
Customizing entries for the events Change and Delete should be defined when changes to a purchae order or delivery should lead to new follow-up actions for additionals. If the quantity on-order of a material is changed, for example, the quantity of the additional will change. If you want a new additionals IDoc to be generated, you have to maintain an entry for the event Change as a requierment for the procedure for additionals.
History
| Last changed by/on | SAP | 19980325 |
| SAP Release Created in |
