SAP ABAP IMG Activity HRAS_HRASR00FSCN (Create Form Scenario)
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_HRASR00FSCN Create Form Scenario  
Transaction Code S_AEN_10001003   (empty) 
Created on 20050407    
Customizing Attributes HRAS_HRASR00FSCN   Create Form Scenario 
Customizing Activity HRAS_HRASR00FSCN   Create Form Scenario 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRAS_HRASR00FSCN    

In this IMG activity, you perform the following work steps:

  • Create form scenario
  • Create version
  • Define form fields
  • Define input helps
  • Assign back-end services
  • Assign form fields to back-end services
  • Define attachment types
  • Define scenario steps
  • Specify use of form fields in scenario steps
  • Specify attributes of attachment types
  • Specify additional information (links)
  • Define rules

For detailed information about the individual steps, see the relevant sections.

Create form scenario

A form scenario is the basis for a form-based process. In the form scenario, you define the basic set of form fields that can be used, configure the default values and value helps, and specify how the backend system is used to check the form data and make it persistent. In addition, you specify how attachments and link lists are used to provide additional information. The ISR scenario, on the other hand, is used to include the interactive form and create the layout. There is always a one-to-one relationship between the form scenario and the ISR scenario. You must define the relationship in the IMG activity Link ISR Scenario with Form Scenario.

Activities

  1. Choose New Entries.
  2. Enter the form scenario.
  3. Enter a name.
  4. Save your entries.

Create version

Form scenarios are version dependent, which means that there is at least one version of each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated scenarios. To be able to provide different forms for process variants, you create versions.

You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.

The form scenario and the (linked) ISR scenario are both version dependent. They must always have exactly the same version numbers. Note that the version number of the ISR scenario is generated and cannot be entered manually. When you create a new version in the form scenario, you therefore have to use the version number generated in the ISR scenario.

If you have already made extensive Customizing settings for the form scenario and want to create a new version based on the settings, you should use the IMG activity Manage Form Scenario.

Example

For the "Birth of a Child" process, you create a corresponding form scenario and ISR scenario named "Birth of a Child", each with the version 0. The form scenario version contains a form in which all relevant data regarding the birth of the child can be entered. Once the process has been used in a production system for some time, the form has to be changed to incorporate an additional field. In this case, you use the IMG activity Manage Form Scenarios to first create a new version of the form scenario and ISR scenario on the basis of the existing version. You then add the new field to the newly created version. You have to modify the process so that it uses the new version of the form scenario in the future.

Define form fields

In this step, you create all the fields that are relevant for the form scenario. This includes both the fields that appear on the form for the input or output of data and the fields that do not appear on the user interface and are used solely to transport data. If you no longer require a form field, you must delete it. Removing it from the form is not enough, since it will still be processed in the background.

Some form fields are mandatory and must always be defined. PERNR (personnel number) and EFFECTIVE_DATE (effective date) are examples of these mandatory form fields. Depending on the backend service used, there can be other mandatory form fields. For an overview of the mandatory fields for the back-end services provided in the standard system, "Personnel Administration Infotypes" and "Time Management Infotypes", see the relevant IMG activities:

You must 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

Form fields are generally linked to the fields of one or more back-end services (see the step "Assign form fields to 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 form fields that are not linked to a field of a back-end service, you have to enter the data element manually.

Form fields can be filled with default values. You specify for each form field whether it is to have a default value (default value type). For fields with default values, you can decide whether the default value is defined manually or determined using a back-end service. In this case, you enter the back-end service sequence number under which you have defined the back-end service in the form scenario.

For each form field, you enter whether or not there is to be a value help (value help type). You can either enter the possible values of the value help manually (see next section), or they can be determined using one or more back-end services.

You can also specify whether a collision check is to be performed for a form field.

On the user interface, the form is defined by the usage and positioning of controls (input fields, dropdown lists, radio buttons, and so on). The controls must be linked to the form fields so that the data entered in the user interface is stored in the form fields. For more information, see the online documentation for HR Administrative Services and choose Editing Interactive Forms in Adobe LiveCycle Designer.

Form fields can also be used as parameters in rules. Rules can be used in the definition of form scenarios to control whether a back-end service is accessed or whether a specific operation of this service is to be accessed.

Activities

  1. Choose Form Fields in the dialog structure.
  2. Choose New Entries.
  3. Create the mandatory fields PERNR and EFFECTIVE_DATE.
  4. Define all other form fields that you require for the form scenario.
  5. Save your entries.

Define value helps

In this step, you can define a manual value help for a field. Value helps can currently be displayed only as a dropdown list box. The dropdown list box contains all values that are valid for the input field, whereby the input can only be selected from this list of values. Each entry in the value help consists of a sequence number, the field value, and a field value text. The dropdown list box displays the text for the field value. When the entry is selected, however, the corresponding field value is entered in the field.

Requirements

If you want to define a manual value help for a form field, you must set Manual Value Help as the value help type for this form field in the Form Fields view.

Only value helps as dropdown list boxes are supported.

Activities

  1. Choose Input Help in the dialog structure.
  2. Choose New Entries.
  3. Enter a number.
  4. Enter the field value that is to be available in the input help for the form field.
  5. Enter a text for the field value.
  6. Repeat the steps for all other field values you want to be displayed in the input help. Enter a sequence number for each field value.
  7. Save your entries.

Assign back-end services

Back-end services provide the business logic that can be used in the form scenarios.

In this step, you specify which back-end services are used. To have data transferred to the back-end services, you link the form fields to the backend services. Back-end services are included using sequence numbers that identify them uniquely in the form scenario. You require the sequence number when defining default values and value helps. The number also specifies the sequential order in which the services are called at runtime.

Back-end services can also be assigned a Business Attributes

ASAP Roadmap ID 204   Establish Functions and Processes 
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_HRASR00FSCN 0 AEN0000011 HR Administrative Services 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
HRASR00FSCN C - View cluster SM34  
History
Last changed by/on SAP  20050407 
SAP Release Created in 600