Hierarchy
⤷
⤷
Basic Data
| Data Element | J_7LV1MLFKZ |
| Short Description | Indicator: Save Article Quantity Flow at Vendor Level |
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 | Vendor |
| Medium | 15 | For Vendor |
| Long | 30 | Article Quantity for Vendor |
| Heading | 2 | Ve |
Documentation
Definition
If this indicator and the indicator for saving the quantity flow at article level are set, the quantity flow at article and vendor level is saved in a separate document.
This indicator is active for following document categories:
E Final settlement
J Annual prepaid declaration
P Periodical declaration
Use
Later use with new recycling partner regulations and for the explosion of the settlement volume at individual article and end vendor level.
Dependencies
A high volume of data is possible. The expected number of records corresponds roughly with that of the master data of articles that must be recycled and the vendor master data; data (if more than a thousand records) is already temporarily saved during the declaration run before the document is saved. The temporary records of a terminated incomplete declaration must be reorganized.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |