Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WBON (Package) WWS: Bonus
Basic Data
| Data Element | BOBAS |
| Short Description | Settlement basis (for purchasing documents only) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOBAS | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Set. basis |
| Medium | 15 | Settlement bas. |
| Long | 20 | Settlement basis |
| Heading | 9 | Set. bas. |
Documentation
Definition
Indicator for purchasing documents (purchase order, scheduling agreement) that determines that the final net invoice amount of the invoice verification document is to be used for updating the value of the business volume during business volume update at the time of invoice verification.
If the indicator is not set, the update of the business volume value uses the document conditions of the purchasing document.
Use
From the point of view of subsequent settlement, only the final net invoice amount can be updated, as no price determination is carried out when invoice verification documents are entered.
To still obtain a differentiated update of the business volume value, it is therefore possible to use the document conditions of the relevant purchasing document.
For vendor billing documents (invoices without reference to order) and settlement requests, the update of business volumes is always based on the document conditions.
Note
In order to update business volume from document conditions, you must enter '7' (transfer of values as per KOMP-BONBA) in the "Subtotal" column in the line of calculation schema that refers to the field "Reference step from" of the condition type in subsequent settlement. If necessary, you can also use any other subtotal.
As a result, the system identifies the relevant subtotal of the calculation schema as the basis, as long as this is not automatically determined from the scale or condition basis (i.e. value-based scale or condition basis) via the "Reference step from".
- The subtotal controls whether the condition values or subtotals (e.g. moving average price) are stored in the interim, and if so, in which fields.
- If the subtotals are not maintained correctly, a business volume update is not possible. You can check whether the subtotals are being used correctly by using report RWMBON20.
- If the same subtotal is used twice, the values involved are added together. This is not usually desirable.
- The basis for calculating provisions is different. This calculation is defined by the From-To reference step(s) in the calculation schema. As a rule, provisions should have the same base value. As a result, the From-reference step entries and subtotal entries should therefore refer to the same lines in the calculation schema.
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
