SAP ABAP Data Element PVS_STTAG (Recipe Key Date)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
PLM-RM-REC (Application Component) Recipe
⤷
RMSRCPMSC (Package) RMS-RCP: Miscellaneous

⤷

⤷

Basic Data
Data Element | PVS_STTAG |
Short Description | Recipe Key Date |
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 | STT | |
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 | Key Date |
Long | 20 | Recipe Key Date |
Heading | 10 | Key Date |
Documentation
Definition
Date on which the recipe is edited
Use
You can either edit recipes on a key date or with a change number. Note the following for recipe editing with a key date:
- When you create a recipe, it is valid as of the key date.
- When you create a new change state for an existing recipe, you need a change number. You can generate the change number when you create the change state. It is then assigned the key date as its valid-from date.
- When you load a recipe, the system loads the change state that is valid on the key date. Changes apply to the entire validity period of the change state.
The current date is the default value for the key date. If you enter both a key date and a change number when you access a recipe, the dates of the change number apply.
Dependencies
Irrespective of whether you edit your recipes with or without a change number, the changes are logged in change documents.
Example
History
Last changed by/on | SAP | 20031212 |
SAP Release Created in | 46C |