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_BRTWRRD |
| Short Description | Key figure: Gross value of payment request (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 | Gross val. |
| Medium | 15 | Gross value |
| Long | 20 | Gross value customer |
| Heading | 21 | Gross value customer |
Documentation
Definition
Gross value of single payment request at header level from customer-side pricing.
The value is taken from the condition subtotal 9 of the customer-side document conditions and added up over the items, provided the payment type allows for customer-side pricing.
Use
In this key figure the customer-side gross value is cumulated.
In standard SAP R/3 this key figure is not updated in any information structure. 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, provided an update rule has been created. The update group is 000030 (agency business) for event WZ (single payment request).
Dependencies
Single payment requests 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 also the key figure "Key figure: Gross value of payment request customer (item)". This is determined at item level but the update is more performance intensive.
History
| Last changed by/on | SAP | 19980728 |
| SAP Release Created in |
