SAP ABAP IMG Activity HRAS_CONFIGFORMSCEN (Configuration of Forms)
Hierarchy
☛ EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   ⤷ PA-AS (Application Component) HR Administrative Services
     ⤷ PAOC_ASR_PROCESS_MODELLING (Package) Modeling Processes
IMG Activity
ID HRAS_CONFIGFORMSCEN Configuration of Forms  
Transaction Code S_PEN_05000150   (empty) 
Created on 20050518    
Customizing Attributes HRAS_CONFIGFORMSCEN   Configuration of Forms 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRAS_CONFIGFORMSCEN    

Use

In this section, you make all the settings required to configure form scenarios and the corresponding ISR scenarios.

Together with ISR scenarios, form scenarios form the basis for HR processes. An HR process usually encompasses several roles (for example, a request is submitted by an employee, approved by a manager, and processed by an HR administrator) and results in a change in HR master data. Each role is integrated in the process by means of Interactive Forms based on Adobe Software. The interactive forms and the changes to the HR master data are configured by means of form scenarios. A process can be based on one or more form scenarios.

Form scenarios define the basic set of HR master data that can be changed when a process is executed. They define which HR master data fields are relevant in which process step, and which changes to the data are to be performed on the database. This is done through the integration and configuration of backend services. In addition to the standard services for processing Time Management data and Personnel Administration data, you can also create your own Generic Services and include them in the form scenario definition. In addition, form scenarios determine whether and in which steps the inclusion of attachments is supported. Additional information can also be provided by adding links.

While the form scenario is responsible for the configuration of access to the backend system, the ISR scenario is used to define the user interfaces. The ISR scenario specifies which form is used for display, and the layout of the form.

There is a one-to-one relationship between the form scenario, ISR scenario, and the interactive form. This means that exactly one ISR scenario is assigned to a form scenario, and an ISR scenario references exactly one form. If you want to use different forms in a process (for example, if you want different agents to be able to display or edit different data), you have to create a corresponding number of form scenarios. If you want data and attachments to be forwarded from one form scenario to the next, you also have to define the data transfer between the form scenarios.

In addition to defining form scenarios and ISR scenarios, you also have to perform additional steps to be able to implement an entire HR process:

  • You must define the process as a whole.
  • You must create a workflow template to specify the required processing steps and the agents who process them.
  • You must configure authorizations.
  • You must define the process group assignment so that the various roles (such as employee, manager, HR administrator) can execute the relevant steps of the process.

Form scenarios and ISR scenarios are therefore only part (albeit a significant part) of an entire process. Before starting to define form scenarios and ISR scenarios, you should therefore have developed an overall concept for the process you are creating.

If an ISR scenario or form scenario (with an existing version) has already been used in a productive process, you should not change the configuration. If you want to make changes to a process or an ISR scenario or form scenario, you should always create a new version, and only ever use that new version in the future. In this way, processes that have been started can be concluded with the old version and new processes can be started simultaneously with the new version.

If you want to create a new version of a form scenario on the basis of the current configuration, execute the IMG activity Manage Form Scenarios.

Note

SAP provides a range of sample processes and form scenarios to aid you. The Manage Form Scenarios IMG activity contains a tool that enables you to copy the sample form scenarios to the customer namespace. You can then edit and enhance the copied form scenarios to match your requirements.

Caution

The form scenarios and processes that are provided by SAP are to be used only as a model; they must never be used in a production system. SAP reserves the right to change, enhance, or delete the sample processes at any time. If you were to use the processes in a production system, this would cause serious inconsistencies and loss of data.

Technical Prerequisites

If you create a form scenario for which you use the standard service Personnel Administration Infotypes (SAP_PA), the Additional Actions (0302) infotype must be activated in your ERP system and the corresponding infotype records must be created for your employees.

To activate the Additional Actions infotype, you execute the Activation 'Additional Actions' step in the Customizing for Personnel Administration under Customizing Procedures -> Actions -> Set Up Personnel Action Types.

For more information about the technical settings of the component, see SAP Library under HR Administrative Services -> HCM Processes and Forms -> HCM Processes and Forms (Technical Overview).

Standard settings

Activities

Before you configure the form scenario in Customizing, you should check your company requirements and create a suitable concept that is as detailed as possible by including the following steps:

  • Determine which processes you want to be supported.
  • Determine the required workflow templates.

    For more information about SAP Business Workflow, see the documentation for SAP NetWeaver under Application Platform (SAP Web Application Server) -> Business Services -> SAP Business Workflow.

  • Specify the steps that must be performed to handle a process in its entirety.

    Example

    The Request Transfer process or form scenario requires the following steps:

    • Sending Manager
      • The sending manager requests the transfer of an employee assigned to him or her.
    • Receiving Manager
      • The receiving manager receives the transfer request and processes it.
    • Approval
      • The supervisor of the sending manager approves the employee transfer.
    • HR Administrator
      • The HR administrator completes the processing of the transfer, adding any missing data as required.
  • Specify which data is to be entered in the form.
  • Specify which fields must be included in the form for this purpose.
  • Specify which backend services are required to process these fields.
  • Specify which verification documents must be provided as attachments.

Note

The Implementation Guide activities are organized in such a way that a meaningful exemplary sequence is obtained if you work through the steps successively. At certain points, however, it is necessary to switch back and forth through the IMG activities.

Example

Business Attributes
ASAP Roadmap ID 103   Set up development systems 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRAS_CONFIGFORMSCEN 0 AEN0000011 HR Administrative Services 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050518 
SAP Release Created in 600