Show TOC

 Overview: Data Processing in HCM Processes and Forms


Several components of the HCM Processes and Forms application are involved in processing the data. The following overview shows you how the individual components work together to check and save the data.


Link between form data and infotype fields in Customizing

In order for the system to be able to process the data in the application database of the infotypes, you must make the appropriate Customizing settings to link the fields that are included in the form application with the infotype fields of the application.

  • In Customizing, you enter for each form scenario the Personnel Administration and Time Management infotypes that are affected by operations such as Change, Create, and so on.

    You specify which field in the form scenario represents a specific field in the relevant infotype. In other words, you specify the relationships between form fields of the form application and the infotype fields.

  • When setting up the form scenario, you specify which fields in the form are relevant for which form scenario step, that is, which data is relevant in which step for checking or saving.

  • When setting up the workflow, you specify which form scenario step is executed for a specific workflow step.

For more detailed information, see the Implementation Guide for HR Administrative Services under Configuration of Forms/Processes and Business Workflow for HCM Processes and Forms .

Processing of data when executing a process
  • If a user uses the Check function in the form application or navigates to the Check and Send view, the system checks the plausibility of the values in the fields that were specified for the relevant form scenario step. This applies to the start application and all other process steps.

    • The backend layer for the form scenarios determines the relationships based on the data specified in Customizing for the form.

    • The backend layer calls the business logic of the application for the infotypes and checks the entered data depending on the operation that is to be executed (Change, Create, and so on).

  • If a user executes the Send function in the form application, the system saves all data changed, deleted, or created by the user in the form data container of the process object. This also happens when the start application is used and when executing individual process steps.

    The system performs an update of the infotypes only if it is specified in the workflow for a workflow step that the data is to be saved in the infotypes of the application database.

    Note Note

    If you have a process that consists solely of a start application, the data can be saved in the infotypes only if you created a workflow template with a workflow step with which the data is saved in the infotypes.

    A standard task, with which the data is automatically saved, is provided for this. An additional form scenario step in which the data is saved by the user is therefore not required. For an example, see the demo workflow template WS17900037.

    End of the note.

The following diagram provides an overview of how the components work together, as described above.