Hierarchy
⤷ 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_VALIDFROM_KEYDATE |
Short Description | Pricing: Key Date for "Old" Conditions in Document Structure |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Key Date |
Medium | 15 | Conds Key Date |
Long | 20 | Old Conds Key Date |
Heading | 10 | Key Date |
Documentation
Definition
Key date for identifying "old" sales price conditions in the report for subsequent structuring of pricing documents directly from conditions. Conditions with a validity start before this key date are counted here as "old".
Use
The key date is used in connection with the higher-level indicator Execute new cost estimate for old conditions. During structuring of the pricing documents, price determinations for conditions with a validity start before the key date are carried out with a more recent price determination date than the validity start for the condition.
Dependencies
If the higher-level indicator "Execute new cost estimate for old conditions" is not set, the key date is irrelevant.
Example
You can set either today's date, a date in the past, or a date in the future as the key date. The choice of the key date depends on the purpose of subsequent pricing document structuring. If the emphasis is on using the pricing worklist function, you must take into account the validity of the purchasing conditions when selecting the key date. A key date in the future could, for example, be the next day for a POS download, if you are no longer interested in a pricing document for "old" conditions (see indicator "No pricing document for old conditions"). In this case, you would also select the minimum validity date to be the same as the key date.
History
Last changed by/on | SAP | 20020124 |
SAP Release Created in | 470 |