Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-AB (Application Component) Agency Business (Global Trade)⤷
MCWZ (Package) R/3 Application Development: LIS settlement
Basic Data
| Data Element | MC_ARLRKRGRLAL |
| Short Description | Key figure: No. of request lists (payment) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MCZAEHLER | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 9 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| 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 | No.ReqList |
| Medium | 15 | No. req. lists |
| Long | 20 | No. of request lists |
| Heading | 15 | No. req. lists |
Documentation
Definition
Number of payment request lists for single payment requests.
Use
Counter of payment request lists for single payment requests.
In the standard SAP R/3 this key figure is not updated in any information structure. Generally, no active updates are delivered for payment request lists.
If necessary, you have to create a field catalog first (compare application 02, key figure catalog ERDK). SAP recommends that you use SAP BW. The update would be made when the document is released to accounting, if necessary, provided an update rule has been created. The update group is 000030 (agency business) for event WA (payment request list).
Dependencies
The key figure is determined at document header level. An update in information structures with item characteristics does not generally make sense.
History
| Last changed by/on | SAP | 19980728 |
| SAP Release Created in |
