Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-XIF (Application Component) External Interface Business Transaction⤷
CRMEDI_ORDER_R3 (Package) Data Objects for Order Idocs from R/3
Basic Data
| Data Element | ADDI_IDOC |
| Short Description | Indicator which refers to separate additionals IDoc |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | Add. IDoc |
| Medium | 15 | Addit. IDoc |
| Long | 20 | Additionals IDoc |
| Heading | 17 | Additionals IDoc |
Documentation
Definition
Indicates that a separate IDoc is to be transferred containing the data of an additional.
Use
This indicator is used in purchase orders. A vendor receiving an order copy or the IDoc ORDERS can see from the indicator that the sold-to party for this item will generate a further IDoc for the additional and transfer the IDoc to the vendor.
Example
A vendor receives an order for men's shirts. The order is for the shirts and also for ticketing the shirts. If this indicator is set, the vendor knows that the customer will send him an additionals IDoc with the most up-to-date data at the appropriate time.
The data on the additional is transferred separately, as there can be a long period between the order data and the delivery date of a material. The retail prices may change in the meantime. To avoid the tickets having to be generated twice or the price marked twice, the data is sent as late as possible to the vendor.
History
| Last changed by/on | SAP | 20020828 |
| SAP Release Created in |
