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_NEW_CONDRECORD |
| Short Description | Indicator "Execute New Cost Estimate for Old Conditions" |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | NewCostEst |
| Medium | 15 | New Cost Estim. |
| Long | 20 | New cost estimate |
| Heading | 10 | NewCostEst |
Documentation
Definition
Indicator for the report for subsequent structuring ofpricing documents directly from sales price conditions (RWVKPIC3 and RWVKPIC4). The indicator means that a new price calculation is to be carried out for "old" condition records, for which the validity start falls before a defined key date. The new price calculation also means that a new condition record is created.
Use
Purchase-side and sales-side price determination is carried out in subsequent structuring of the pricing document, as it is in sales price calculation. The validity start of the condition used as a basis is used as the price determination date for these price determinations. With conditions that have a validity start in the past, there is the danger that the price determinations carried out will not be based on the current conditions. In this sense, the condition is "old". When using the pricing worklist in this respect, there is a particular danger that the correct document indexes will no longer be created for the subsequently generated pricing documents.
You can therefore define a key date for a new price calculation. The conditions that have a validity start before this key date then count as old. The system suggests the current date as the key date.
Dependencies
If you have selected a key date that lies in the past, the system uses the current date as the price determination date for the new price calculation that leads to the creation of a new condition record. If the key date lies in the future, it is also used as the price determination date for the new price calculation.
The system creates a second, separate pricing document for the new calculations with new condition records.
Example
You start the report for subsequent pricing document creation on 01.05.2002. You completed annual negotiations with your vendor on 31.03. Pruchasing conditions have not changed since then. You use the pricing worklist. In this case, you set the indicator for the new price calculation with the key date 01.04.2002. There are two pricing document items (in different pricing documents) for conditions for sales prices with a validity start before 01.04.2002. The first pricing document item refers to the original condition. The validity end is the day before the current date. The second pricing document item belongs to the new price calculation that is carried out with the price determination date 01.05.2002. The sales price is copied from the condition and remains completely unchanged.
History
| Last changed by/on | SAP | 20020124 |
| SAP Release Created in | 470 |
