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_FIELDNAME |
| Short Description | Name of Form Field |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ASR_FIELDNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | T5ASRFSCNFLD |
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 | Field Name |
| Medium | 15 | Field Name |
| Long | 20 | Field Name |
| Heading | 30 | Field Name |
Documentation
Definition
Are used to enter and output data in a form scenario.
Use
Each form scenario consists of a quantity of form fields. Form fields are usually linked to backend services and thus ensure the connection to the business logic.
You must define a form field for each field that is to be displayed on the form (for entry or for output). The fields are displayed using so-called UI controls that are linked to the form fields. All form fields are processed at runtime. Form fields that are not linked to a UI control are processed in the background.
Depending on the backend service used, there is a set of mandatory form fields that must always be defined.
Dependencies
The type of each form field must be determined (using a data element). You can determine the types either by manually entering a data element or automatically if the form field is linked to a field for a backend service.
Form fields are generally linked to the fields for one or more backend services. In this way, the data saved in the form field is forwarded to the backend service where it can be processed.
Form fields can also be used as parameters of rules. Rules can be used in the definition of form scenarios to control whether a backend service is called or whether a specific operation of this service is to be called.
Form fields can be grouped together using scenario steps. By assigning scenario steps to process steps, you can control which form field is relevant in a particular process step.
Example
Mandatory fields that must always be defined are:
- PERNR - Personnel number
- EFFECTIVE_DATE - Effective date
There can also be other mandatory fields depending on the backend service used.
History
| Last changed by/on | SAP | 20050615 |
| SAP Release Created in | 600 |
