Hierarchy
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ MCWZ (Package) R/3 Application Development: LIS settlement
Basic Data
Data Element | MC_NETRGRLAL |
Short Description | Key figure: Net value of request list (payment to vendor) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | WERTV9 | |
Data Type | CURR | Currency field, stored as DEC |
Length | 17 | |
Decimal Places | 2 | |
Output Length | 23 | |
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 | Net val.RL |
Medium | 15 | Net value of RL |
Long | 20 | Net value of RL |
Heading | 21 | Net value of req.list |
Documentation
Definition
Net value request list from single payment requests
Use
In this key figure, the net value is cumulated from request lists for single payment requests.
Request lists are used to post vendor-side postings from single payment requests separately.
In standard SAP R/3, this key figure is not updated in any information structure. Generally, no active updates are provided for 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, if necessary, after the document is released to accounting, provided an update rule has been created. The update group is 000030 (agency business) for event WA (request list).
Dependencies
Request lists can have various document currencies. The update is therefore made in the local currency of the company code.
In general, it only makes sense to update this key figure if the company code is a characteristic of the information structure. Otherwise, problems arise if company codes with different local currencies are used.
Unlike a sales organization, a purchasing organization does not have a statistics currency for grouping the update over several company codes when the local currencies differ. Furthermore, request lists do not always have a purchasing organization (Customizing).
On the other hand, a sales organization has a statistics currency for grouping the update over several company codes when the local currencies differ. Request lists, however, do not always have a sales organization (Customizing).
An update in the standard currency of the client (table T000) could be considered for company codes with different local currencies, but this would have to be implemented individually in the customer project.
The key figure is determined at document header level. An update in the information structures with item characteristics does not generally make sense. Note that request lists contain cumulated data from single payment requests.
History
Last changed by/on | SAP | 19980728 |
SAP Release Created in |