Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WBON (Package) WWS: Bonus
Basic Data
Data Element | KALBO |
Short Description | Settlement schema (subsequent settlement) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | KALSM | |
Data Type | CHAR | Character String |
Length | 6 | |
Decimal Places | 0 | |
Output Length | 6 | |
Value Table | T683 |
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 | Schema |
Medium | 15 | Sett. schema |
Long | 20 | Settlement schema |
Heading | 9 | Schema |
Documentation
Definition
Calculation schema in Purchasing that is used for price determination when creating settlement documents in subsequent settlement.
Use
The schema is used to determine
- the account key, for determining the accounts to be posted
- the tax calculated on the income.
Some of the settlement schemas may only be of use if account determination is to be carried out in a different way, or a different type of tax calculation is to be set via the condition technique.
The first line of a settlement schema can contain the statistical condition type "SBCB", to increase the legibility of the document conditions.
The condition types to be settled are then entered in the following lines.
After the condition types to be settled, condition type "S000" must be entered. This condition type is used for billing for settlement amounts from interim and partial settlement.
The aforementioned condition types are fixed in the document condition for settlement documents in the settlement program. Only taxes (condition classes D and G) are determined from price determination when settlement documents are created. Any other condition types cannot be entered and are therefore ignored.
Dependencies
For vendor rebate arrangements (rebate arrangement partner), the schema can be determined in the first step via the vendor schema group and the purchasing organization schema group (same assignment as for calculation schemas for general price determination).
If no schema is assigned, the settlement schema of the arrangement type is used in the second step.
For customer rebate arrangements, the arrangement schema must only be maintained in the arrangement type. This is sufficient, as account determination in sales allowes account determination dependent on a customer.
History
Last changed by/on | SAP | 19980514 |
SAP Release Created in |