SAP ABAP Data Element PRIVALIDITY (Price Catalog Inbound Start of Validity Period)
Hierarchy
☛
EA-RETAIL (Software Component) SAP Enterprise Extension Retail
⤷
SD-EDI (Application Component) Electronic Data Interchange
⤷
VPRI (Package) Application Development R/3 Retail/CP EDI messages
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
SD-EDI (Application Component) Electronic Data Interchange⤷
VPRI (Package) Application Development R/3 Retail/CP EDI messages
Basic Data
| Data Element | PRIVALIDITY |
| Short Description | Price Catalog Inbound Start of Validity Period |
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 | VALIDITY_BASE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Valid from |
| Medium | 15 | Validity |
| Long | 20 | Validity Date |
| Heading | 4 | VDat |
Documentation
Definition
Date from which the detailed changes are valid.
Use
The date permits different information statuses in a catalog.
Dependencies
The date cannot be processed further in the SAP system.
In the application, you can make settings specifying that only the current status and all future statuses, or all transferred statuses (complete history) can be displayed and processed in the catalog.
History
| Last changed by/on | SAP | 20060313 |
| SAP Release Created in |
