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_BONBALF |
| Short Description | Key figure: Rebate basis (subtotal 7), vendor billing doc. |
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 | Reb.basis |
| Medium | 15 | Rebate basis |
| Long | 20 | Rebate basis |
| Heading | 21 | Rebate basis |
Documentation
Definition
Basic value from which the rebate (subsequent settlement) is calculated.
The value is derived from the condition subtotal 7 of the document conditions.
Use
In this key figure the condition subtotal 7 is cumulated from those vendor billing document items in which the subtotal is used. This is the case if the calculation schema for the vendor billing document uses the subtotal. Various calculation schemata can be used per billing document type, vendor and purchasing organization.
In the delivery status, this key figure is updated in the information structures S172 and S173 when the document is released to accounting. The update group is 000030 (agency business) for event WL (vendor billing document).
There is no connection between updates in the subsequent settlement. These are settled independently. Unlike subsequent settlement, this key figure is only updated once per item and not per condition record. The payment values (invoiced sales) should match.
Dependencies
Vendor billing documents can have various document currencies. The update is therefore made 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.
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 | 19970827 |
| SAP Release Created in |
