Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PA-AS (Application Component) HR Administrative Services⤷
PAOC_ASR_CONTROLLER (Package) Controller
Basic Data
| Data Element | ASR_FORM_SCENARIO_VERSION |
| Short Description | Form Scenario Version |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ASR_FORM_SCENARIO_VERSION | |
| Data Type | NUMC | Character string with only digits |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| Value Table | T5ASRFSCNVER |
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 | Version |
| Medium | 20 | FormScenario Version |
| Long | 29 | Version |
| Heading | 35 | Form Scenario Version |
Documentation
Definition
Form scenarios are version dependent, meaning that the entire definition of a form scenario is made under a version number.
Use
When creating a form scenario, you must first create the version 0. If the form scenario is revised later on, then you can make these changes either in the existing version or you can create a new version with the next free number.
Dependencies
To use a form scenario in a process, you must also create an ISR scenario in parallel that is linked with the form scenario. The form scenario and the linked ISR scenario must have exactly the same version number.
If a version of a form scenario has already been used to perform a process, this version of the form scenario should not be changed retroactively. If changes are necessary, you should instead create a new version.
Example
History
| Last changed by/on | SAP | 20050520 |
| SAP Release Created in | 600 |
