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_BRTRDRLBU |
| Short Description | Key figure: Final amount of posting list (payment to cust.) |
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 PL |
| Medium | 15 | Finl amt of PL |
| Long | 20 | Final amt post. list |
| Heading | 23 | Final amt of post. list |
Documentation
Definition
Final amount of posting list from single payment requests
Use
In this key figure the final amount is cumulated from posting lists for single payment requests.
The system takes the value of the condition subtotal 9 from the document conditions and cumulates it over the items.
Posting lists are used to post customer-side postings from single payment requests separately.
In standard SAP R/3 this key figure is not updated in any information structure. In general, no active updates are delivered for posting 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 take place 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 WB (posting list).
Dependencies
Posting 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, posting 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 local currencies differ. Posting lists, however, do not always have a sales organization (Customizing).
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 posting lists contain cumulated data from single payment requests.
History
| Last changed by/on | SAP | 19980728 |
| SAP Release Created in |
