Hierarchy
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ MCWZ (Package) R/3 Application Development: LIS settlement
Basic Data
Data Element | MC_BRTWPRD |
Short Description | Key fig: Gross value of payment (item) to 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 val.-item |
Long | 20 | Gross value (item) |
Heading | 21 | Gross value (item) |
Documentation
Definition
Gross value of single payment request at item level from customer-side pricing.
The value is taken from the condition subtotal 9 of the document conditions.
The prerequisite is that the payment type allows for customer-side pricing (see Customizing).
Use
The customer-side gross value is cumulated in this key figure.
In standard 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, if necessary, 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 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, single payment requests do not always have a purchasing organization (Customizing payment type).
A sales organization, on the other hand, has a statistics currency for grouping the update over several company codes when the local currencies differ. Single payment requests do not, however, always have a sales organization (Customizing payment type).
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 system determines the key figure at document item level. An update in the information structures with header and item characteristics is possible. Note also the key figure "Gross value of payment request (customer)". This is determined at document item level. Updating this key figure improves performance.
History
Last changed by/on | SAP | 19980505 |
SAP Release Created in |