HCM Processes and Forms (Technical Overview) 

Use

Architecture

The component is made up of the following architectural elements:

●     Process

The process groups together the following elements: ISR scenario, form scenario, and workflow template. A process can include one or more form scenarios.

For more information, see Process.

●     ISR Scenario

The ISR scenario is used to select the form and to define the form layout. It is part of the cross-application Internal Service Request function.

For more information, see ISR Scenario.

●     Form scenario

The form scenario answers the following questions regarding the following properties:

○     Which fields are used in a form?

○     How are these fields linked with the infotype fields in the backend system?

○     Which scenario steps exist?

○     Which types of attachments can be uploaded?

○     Which services are used?

The services determine the logic used to process form fields in the backend system. The following types of service are available:

■      PA Service (enables Personnel Administration infotypes to be created, changed, and deleted)

■      PT Service (enables Time Management infotypes to be created, changed, and deleted)

■      Generic Services Framework

The standard system includes the generic service S_MGR_POSITIONS (Positions in Manager’s Area of Responsibility), for example. You can use this service to ensure that a manager is offered only those jobs for selection in the Positions form field that belong to his or her area of responsibility.

Each form scenario has exactly one ISR scenario.

For more information, see Form Scenario.

●     Workflow template

You use a workflow template to define the process flow, define agent determination, and to control the form application in a process.

For each process there is a workflow template that defines the process flow.

For more information, see Business Workflow for HCM Processes and Forms.

●     Process Object

The process object represents the persistence layer of runtime data that results from the execution of a form-based process.

The system creates a process object if the user triggers the process in the start application. The system saves the following data and elements in this process object:

○     Data that a user entered in the form (for each process step)

○     Attachments that a user included in the process while the process was being executed

The process object is created and the data is saved using the Case Management component.

For more information, see Process Object.

●     Start Application

The start application enables processes to be started. Depending on the portal role, the start application can be structured differently. It displays the processes to be executed and the steps required to start a process (for example, displaying the Employee Selection function on the user interface of the start application).

For more information, see Start Application.

●     Form Application

The form application enables forms to be called in different scenario steps that are modeled in the workflow template.

For more information, see Form Application.

●     Digital Personnel File (DPF)

You can use the DPF together with HCM Processes and Forms. If you integrate the personnel file, the system automatically saves any forms and attachments in the employee's Digital Personnel File that are created when the process is executed.

The permanent saving of processes is fulfilled using the process object; however, the DPF provides an optional enhancement to the HCM Processes and Forms functions.

Integration

HCM Processes and Forms uses the following components and their technologies:

●     Internal Service Request (ISR)

The ISR Framework (including Interactive Forms based on Adobe software / Adobe Document Services) provides the technical basis for defining an ISR scenario and defining the graphical layout of the forms.

●     HR Master Data (PA-PA) and Data from Time Management (PA-PT)

The fields of forms in HCM Processes and Forms can be linked with the fields in Personnel Administration (PA) infotypes or Time Management (PT) infotypes. When the process is executed, the system updates the data in the infotypes with the entries made in the form fields.

●     SAP Business Workflow

SAP Business Workflow provides the technical basis for modeling the process steps that depict the process flow after the process is started.

In the workflow, you specify the following information for the individual process steps:

○     The order of the individual process steps

○     The functions that are provided to the users in the form application

○     The users that are to execute a process step

○     How and where the data is to be saved

●     SAP Enterprise Portal

The portal provides all users integrated in a process with the iViews needed to execute the process on the user interface:

○     Start Application

The start application enables the user to start processes.

○     Universal Worklist (UWL)

The UWL provides the work items with which the user can call the forms for which he or she is the intended agent.

●     Manager Self-Service (MSS)

The manager obtains access to the HCM Processes and Forms functions intended for him or her using the Manager Self-Service.

●     Employee Self-Service (ESS)

The employee obtains access to the HCM Processes and Forms functions intended for him or her using the Employee Self-Service.

●     Records and Case Management

Records and Case Management provides the following underlying technology:

○     Storage of process instances (for more information, see Process Object)

○     The interface and data storage for the Digital Personnel File (DPF) and the process documents (forms and attachments) stored there.