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_STAGE |
| Short Description | Scenario Step |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ASR_FORM_SCENARIO_STAGE | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | T5ASRFSCNSTG |
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 | Step |
| Medium | 15 | Scenario Step |
| Long | 20 | Scenario Step |
| Heading | 35 | Scenario Step |
Documentation
Definition
Defines a part status of a form scenario. A form scenario consists of any number of (greater than zero) scenario steps.
Use
You define scenario steps if the form configuration is not to be processed as a whole at the runtime of the process, in other words, when different parts of the form configuration are relevant depending on the process step involved.
Simply defining scenario steps does not have any effect. The scenario steps become functional when form fields are assigned to them. In this way, a scenario step represents a subset of the form fields that are relevant for this scenario step. As these form fields are linked with backend services, a scenario step also represents a subset of the fields and operations defined for the backend services.
A scenario step is assigned to a workflow step during the process definition. At runtime, only the backend services and operations belonging to the scenario step are executed.
A scenario step also defines which attachments can be added or displayed in the step and what additional information (using links) is provided.
Dependencies
Each form scenario must have at least one scenario step.
If you have not assigned any form fields to a scenario step, then it is implicitly understood that all form fields are assigned.
Scenario steps do not have an automatic effect on the user interface of the form. In other words, a field that is not assigned to a scenario step is not automatically hidden on the form. A modification of the user interface that is dependent on the scenario step must be programmed separately.
A standard form field exists with the name FORM_SCENARIO_STAGE. If you define this form field under this name and with the data element ASR_FORM_SCENARIO_STAGE, it is always filled with the current scenario step at the process runtime. You can use this standard form field in a rule, for example, to make the rule dependent on the scenario step, or you can use it to program a scenario step-dependent modification of the user interface.
Form fields are assigned to the scenario steps in the Customizing of the form scenario. This assignment is relevant at runtime, but is enhanced with a further mechanism: During the processing of the process, the form fields that were used in each step are documented internally for each step. Each form field that was used in a step is then automatically used in all subsequent steps as well. This additive approach means that the following fields are relevant in a scenario step i:
- All form fields that are assigned to the scenario step i in the Customizing of the form scenario
- All form fields that were relevant at runtime in the previous scenario step i-1
Example
History
| Last changed by/on | SAP | 20050705 |
| SAP Release Created in | 600 |
