Hierarchy
BBPCRM (Software Component) BBPCRM⤷
LO-ADM (Application Component) Additionals Management⤷
WTAD (Package) IS-R: Additionals
Basic Data
| Data Element | ADDI_SKLRT |
| Short Description | Additionals: Class type for sender |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KLASSENART | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TCLA |
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 | Class type |
| Medium | 15 | Class type |
| Long | 20 | Class type |
| Heading | 3 | Ty. |
Documentation
Definition
Class type of the sender for which a follow-up action for additionals is to be triggered.
Use
Specify a class type and class if you want to restrict the number of plants where a follow-up action is triggered. You may want to do this in the case of two-step stock transfer between distribution centers, for instance, to prevent an additionals IDoc being generated every time goods are received at the second distribution center. An additional usually only has to be affixed once, in the first distribution center.
You must choose a valid combination of existing class type and class.
Notes
It is not essential to enter a class type and class. If, for example, an additionals IDoc is to be generated on the basis of the goods movement type, then this additionals IDoc will be generated for every plant that triggers this goods movement type if you leave the class type and class blank.
History
| Last changed by/on | SAP | 19970902 |
| SAP Release Created in |
