SAP ABAP IMG Activity HRAS_QISRSCENARIO (Create ISR 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_QISRSCENARIO Create ISR Scenario  
Transaction Code S_AEN_10000611   (empty) 
Created on 20050316    
Customizing Attributes HRAS_QISRSCENARIO   Create ISR Scenario 
Customizing Activity HRAS_QISRSCENARIO   Create ISR Scenario 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRAS_QISRSCENARIO    

Use

In this IMG activity, you create an ISR scenario that has a one-to-one relationship with a form scenario. To be able to use a form scenario in a process, one ISR scenario must exist for each form scenario. The ISR scenario and the form scenario must be linked with each other. You make this setting in Customizing for HR Administrative Services in the IMG activity Link ISR Scenario with Form Scenario.

In the form scenario, you define primarily the basic set of form fields and their processing through the backend services. In the ISR scenario, you specify the definition of the user interface. You also specify which form is used for the display and how the layout of this interactive form is designed. You use interactive forms based on Adobe software to create and process the forms.

ISR scenarios and form scenarios are version dependent. The version numbers of the ISR scenario are assigned automatically. Note that a form scenario must have exactly the same version as the linked ISR scenario. For this reason, you should always create a new version in the ISR scenario first and then use the same version number when you create a version in the form scenario manually.

Note

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.

Note on ISR Customizing

In HR Administrative Services (Applikation H) ISR scenarios are only used to control the user interface in the form of interactive forms in a form-based process. In other applications however, a complete process is modelled using an ISR scenario. HR Administrative Services therefore uses only a small part of the functions available for ISR scenarios. The Customizing environment of ISR scenarios was therefore adjusted accordingly and all irrelevant elements have been hidden. The hidden elements are sometimes filled with standard values. These are:

  • Message type

    The Message type 5D is used. The Customizing of the delivered Message type 5D must exist in the current clients and cannot be changed.

  • Flow Logic BAdI

    The flow logic is provided using the Business Add-In from the ISR scenario SASR. The delivered ISR scenario SASR must exist in the current clients and cannot be changed.

  • Active Indicator

    The active indicator is set automatically. The active indicator is also set automatically for all newly created versions, in other words, all versions are active simultaneously. Which version is actually used is defined in the process configuration.

  • Validity Period

    The validity period is hidden and is not checked again.

  • Indcator Using Date Fields

    On the screen for entering additional data for the scenario (in ISR Customizing using a button), the indicator Using Date Fields is set automatically. This ensures that the date fields in the interactive form are displayed correctly.

The following parameters and functions are only available for display purposes:

  • Entry type

    Adobe PDF is always used as the entry type. Other entry types are not supported at the moment.

  • Characteristics

    It is no longer possible or necessary to maintain characteristics manually. By using the buttons you can compare the form fields of the linked to form scenarios and the characteristics automatically.

Requirements

Standard settings

Activities

The following describes how to create a new ISR scenario. If you have carried out steps 1 to 5, start at step 6.

To create a new ISR scenario, proceed as follows:

  1. Create the scenario.

    Please note the following naming convention:

    The scenario is an alphanumeric key of four characters. Scenarios that start with an S are reserved for SAP.

    1. Enter H as the application.
      2. The ISR scenario can be used in connection with a form scenario only if you use the application H. If you enter another application or leave the field empty, the form scenario, and therefore the process in which it is used, cannot run.
    2. Create a version for the scenario.
      3. The version is automatically created with the value 0. Each time you create another version, the system automatically increases this value.
    3. Save your entries.

  1. Process the necessary IMG activities to configure the backend services. The form fields in particular are then created that are required for the further configuration of the ISR scenario.
  2. Execute a comparison of the form fields:
    1. Select the ISR scenario and the version.
    2. Choose Characteristics and then Compare Form Fields.
      3. The system reads the form fields of the linked form scenario and automatically creates all required form fields (characteristics) in the ISR scenario.
    3. Save your data.

      The ISR scenario is then set up such that you can create or process the interactive form. If you enhance the form scenario at a later date and add new fields, you must then perform this comparison again. This is the only way to guarantee the consistency of the ISR scenario.

  3. Create the interactive form:
    1. Choose Version.
    2. Decide whether you want to edit an existing form or have the system generate a new form.
      3. Recommendation
      We recommend that you have the system generate the form. This is the only way to guarantee that the form adheres exactly to the definition of the ISR scenario or the underlying form scenario.
      You should also never use the same form in two different ISR scenarios as this can lead to problems when processing the form.
      Note
      Ensure that you create the form in the customer namespace. You can also generate the form without specifying a name. In this case, the name is automatically created using the template Z_ISR_FORM_<ISR-Szenario>, where <ISR-Szenario> is the name of the ISR scenario.
    3. Generate the form. The following options are available:

  • Create without Template
    • We recommend that you create the form without a template.
  • Create without Template from Existing Scenario
    • With this option all fields of the existing scenario are also transferred to the form. This, in turn, can lead to inconsistencies.
  • Generate with SAP Design
    • You should not use this option in HR Administrative Services as in this case the form is generated with an unnecessary large amount of fields and UI controls that cannot be used in this form and each one must be adapted separately.
  1. Enter the Package in which the form is to be created.
    2. Note
    Make sure that the form is a client-independent Workbench object and thus exists in all clients. In contrast, the ISR scenario and the form scenario are client-dependent. In addition to the form, a so-called interface is generated for which you must also specify a package. This interface is a technical necessity and contains all fields (characteristics) that are to be available in the form.

  1. Process the form with Adobe LiveCycle Designer.

    For more information, see the SAP Library under HR Administrative Services -> HCM Processes and Forms -> ISR Scenario -> Configurating the ISR Scenario -> Creation and Editing of an Interactive Form.

  2. Save and activate the form. Ensure that you also activate the generated interface.
  3. Complete the processing in Adobe LiveCycle Designer.

    A message may appear stating that not all form fields are defined as characteristics. Answer No each time the system asks you if characteristics are to be generated. Otherwise this can lead to inconsistencies in the ISR scenario.

    Note on editing of forms

    You have the following options to edit an existing form again:

    • You can edit the form by executing this IMG activity and choosing Change Adobe Form.
    • You can edit the form directly by using the Form Builder (transaction SFP). In this case, you enter the name of the form manually, choose Change, and then switch to the Layout tab page.

      However, if you have defined new form fields and compared the ISR scenario as described i

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_QISRSCENARIO 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
HRASR00FSCNISR C - View cluster SM34  
History
Last changed by/on SAP  20051018 
SAP Release Created in 600