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 |
| Short Description | Form Scenario |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ASR_FORM_SCENARIO | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | T5ASRFSCN |
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 | Scenario |
| Medium | 15 | Form Scenario |
| Long | 25 | Form Scenario |
| Heading | 35 | Form Scenario |
Documentation
Definition
Constitutes the basis for a form-based process. A process can be based on one or more form scenarios.
Use
Form scenarios are assigned to process steps when a process is defined. A form scenario can be used in several process steps.
A form scenario basically defines a set of form fields. These fields are relevant for the assigned process step, that is, they can be entered by the processor of the process step, are used for output, or are processed in the background. The fields are linked to so-called backend services. The backend services define how the fields are processed in the backend system, that is, from the business logic.
Other attributes can also be defined for the fields, such as value helps or default values.
A form scenario also defines which attachment types are supported and what additional information (using links) can be displayed.
Dependencies
Form scenarios are version dependent. In other words, the entire definition of a form scenario is based on a version. Each form scenario must start with the version 0.
The fields of a form scenario can be divided into scenario steps. By assigning scenario steps to process steps, you can control which fields are relevant for each of the process steps. Each form scenario must have at least one scenario step.
To use a form scenario in a process, you must 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. The ISR scenario is used essentially to define the user interface. The layout of the form is defined here and it is specified which fields are displayed on the form. Note that the use of fields on the user interface is not a criterion for the general relevance of the fields. In principle, all fields are relevant that were defined in the form scenario. Fields that are not displayed on the user interface are still processed in the background.
Example
History
| Last changed by/on | SAP | 20060208 |
| SAP Release Created in | 600 |
