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_KZWI4RD |
| Short Description | Key figure: Condition subtotal 4, 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 | Subtotal 4 |
| Medium | 15 | Subtotal 4 |
| Long | 20 | Condition subtotal 4 |
| Heading | 21 | Condition subtotal 4 |
Documentation
Definition
Condition subtotal 4 for single payment request from customer-side pricing.
Use
In this key figure, the condition subtotal 4 is cumulated from the single payment request items in which the subtotal is used.
This is the case if customer-side pricing is intended (see Customizing payment type) and the calculation schema uses the subtotal. Various calculation schemata can be used, depending on the payment type and billing document type, as well as the vendor, customer and purchasing organization.
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, if necessary, 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. Therefore, the intention is to make the update 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).
On the other hand, a sales organization has a statistics currency for grouping the update over several company codes when the 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 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 item level. An update in the information structures with header and item characteristics is possible.
History
| Last changed by/on | SAP | 19980505 |
| SAP Release Created in |
