Hierarchy
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ MCWZ (Package) R/3 Application Development: LIS settlement
Basic Data
Data Element | MC_BRTRGRL |
Short Description | Key Fig.: Final Amt of Remuneration List, Payment: Customer |
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 | Fnl Amt RL |
Medium | 15 | Final Amount RL |
Long | 20 | Final Amount RL |
Heading | 23 | Final Amount Remun.List |
Documentation
Definition
Final amount of remuneration list, single payment request
The system takes the value of the condition subtotal 9 from the vendor-side document conditions.
Use
In this key figure the final amount is cumulated from remuneration lists for single payment requests. Remuneration lists are used to post certain conditions separately (remuneration list conditions).
In standard SAP R/3 this key figure is updated in information structure S170 when the document is released to accounting. The update group is 000030 (agency business) for event WD (remuneration list single payment request).
Dependencies
Remuneration lists can have various document currencies. The update is therefore intended 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 you use company codes with different local currencies.
Unlike a sales organization, a purchasing organization does not have a statistics currency to group the update over several company codes when the local currencies differ. Furthermore, single payment requests do not always have a purchasing organization (Customizing payment type).
On the other hand, a sales organization has a statistics currency for grouping the update over several company codes when local currencies differ. Single payment requests, however, do not always have a sales organization (Customizing payment type).
An update in the standard currency of the client (table T000) could also be considered for company codes with different local currencies, but would have to be implemented individually in the customer project.
The system determines the key figure at document header level. An update in the information structures with item characteristics does not generally make sense. Note that remuneration list items contain cumulated data from single payment request items.
History
Last changed by/on | SAP | 19991129 |
SAP Release Created in |