Show TOC

Function documentationDefinition of Form Fields

 

You use this function to create all form fields that are relevant for a form scenario.

This includes fields that appear on the form for the input or output of data, as well as fields that do not appear on the user interface and are used solely to transport data.

Some form fields are mandatory. Such mandatory form fields for processes that affect the HR master data are, for example, PERNR (personnel number) and EFFECTIVE_DATE (effective date). Depending on the back-end service used, there can be other mandatory form fields. For an overview of the mandatory fields for the back-end services provided with the standard system, see:

Settings for Back-End Service SAP_PA

Settings for Back-End Service SAP_PT

Settings for Back-End Service SAP_PD

Settings for Generic Services

Note Note

If you no longer need a form field, remove it from the form and delete it from the form scenario version. Otherwise this field is still processed in the back-end system.

End of the note.

Features

The definition of a form field comprises the following settings:

  • Field name

  • Name

  • Field attribute

    The field attribute determines the properties of a field.

    You can determine the field properties for each field that you use in an interactive form. You have many attributes available, such as Editable. This means that the field appears on the form and you can make entries in it.

    For form scenarios of type Adobe Form only: When processing the form layout, you must use the correct ISR control element for the form. The system checks whether this is the case, and displays the result of the check in the Form column.

  • Default value

    Form fields can be filled with default values. You specify for each form field whether it has a default value. For fields with default values, you can decide whether the default value is defined manually or determined using a back-end service. You can use a radio button to select the sequence number of the back-end service under which you defined it in the form scenario.

  • Input help

    For each form field, you specify whether there is an input help (type of input help) as follows:

    • Manually – You enter the possible values of the input help

    • Back-End Service – Possible values are determined using one or more back-end services.

    • Webdynpro Value Help – You select a Webdynpro component that will serve as the input help for the field during runtime.

    You can only choose one checkbox to specify the source of input help. If you choose more than one checkbox, an error is displayed.

  • Collision check

    Switching on the collision check for a form field means that suitable checks are made at the process runtime that ensure that the part of the back-end system linked with the form field remains unchanged.

  • Data binding

    You specify the type of each form field using a data element. You can do this in one of two ways:

    • Manually by entering a data element explicitly

    • Automatically by linking the form field to a back-end service field

    You usually link the form fields to the fields of one or more back-end services. In this way, the data saved in the form field is forwarded to the back-end service where it can be processed. For more information, see Configuration of Back-End Services.

    For form fields that are not linked to a field of a back-end service, you always have to enter the data element manually.

    Note Note

    You can use form fields as parameters in rules to control whether a back-end service is called or whether a specific operation of this service is called. For more information, see Definition of Rules.

    End of the note.

Activities