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 | VKKBI |
| Short Description | Sales conditions valid to |
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 | SP_VALID_TO | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Valid to |
| Medium | 15 | Valid to |
| Long | 20 | Valid to |
| Heading | 10 | Valid to |
Documentation
Definition
Date up to which sales conditions that are to be created in sales price calculation should be valid (validity end date).
Use
The validity end date is entered on the selection screen of the sales price calculation or set in the calling applications (integrated article maintenance, retail promotion). The validity end date can also be changed in the pricing table. When calling it from other applications, for example, from retail promotion, it may be the case that interactive changes cannot be made, as the validity of the conditions is determined in the calling application.
Sales conditions are flagged in the control for data backup by the application V.
Dependencies
You must also specify a date for the validity start date.
You can also set a different validity start date and a different validity end date for the purchase conditions when calling them using other applications.
History
| Last changed by/on | SAP | 19991110 |
| SAP Release Created in |
