Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WVKP (Package) IS-R: Sales pricing
Basic Data
| Data Element | W_SPC_POST_KSCHL |
| Short Description | Sales Price Calculation: Condition Type for Posting |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KSCHA | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | Cond. Type |
| Medium | 15 | Condition type |
| Long | 20 | Post Condition Type |
| Heading | 4 | CTyp |
Documentation
Definition
Condition type for posting prices or percentage values in sales price calculation.
Use
The condition type entered here can be either a main condition type (with its own access sequence) or a condition supplement. A condition supplement can only be saved if the corresponding main condition is saved at the same time.
For the posting to be unique, the user must also enter the application for the condition type.
Dependencies
In Customizing for retail pricing, the user can determine which prices and percentage values are to be saved by means of a data backup control for each list field and sales calculation schema.
Condition supplements have a special roll in posting the basic purchase price (list field "EKPGR"). In addition to the fixed Customizing settings, the purchase price calculation schema used and the condition record data of the basic purchse price defined in the sales price calculation can also be used as an origin.
For the actual posting, the dynamic checks in BAdI "SPC_POSTING_CONTROL" and manual changes in the item detail screen are also to be taken into account.
Example
History
| Last changed by/on | SAP | 20011218 |
| SAP Release Created in | 470 |
