SAP ABAP IMG Activity HRAS_XI_QISRSCENARIO (Form Scenario for XI Message Type: 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_XI_QISRSCENARIO Form Scenario for XI Message Type: Create ISR Scenario  
Transaction Code S_PEN_05000341   (empty) 
Created on 20050609    
Customizing Attributes HRAS_XI_QISRSCENARIO   Form Scenario for XI Scenario: 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_XI_QISRSCENARIO    

Use

In this IMG activity, you create the ISR scenario that you want to use to set up the form scenario for the XI message type.

An ISR scenario has a 1:1 relationship to a form scenario. The ISR scenario and the form scenario must be linked to each other. You cannot link an ISR scenario to several form scenarios.

Whilst you define the basic quantity of the form fields in the form scenario, in the ISR scenario you define the user interface. You also define which form is used for display purposes and the layout of this form. You can use SAP Interactive Forms by Adobe to create and process the forms.

ISR scenarios are also version dependent as are form scenarios. 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. You should therefore always create a new version of the ISR scenario first and then when you create the version of the form scenario manually, assign the same version number.

Requirements

Standard settings

The SAP namespace comprises all ISR scenarios whose key starts with S. The key of customer-specific ISR scenarios must therefore start with a different character.

Activities

  1. Create the ISR scenario.

    1. Enter H as the application.
      2. The ISR scenario can be used in connection with a form scenario only if you enter a different 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.
    4. Save your entries.

  • Perform the IMG activity Create Form Scenario for XI Message Type.
  • Perform the IMG activity Link ISR Scenario with Form Scenario for XI Message Type.
  • Repeat this IMG activity (Form Scenario for XI message type: Create Create ISR Scenario).
  • 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.
    4. Save your data.

The ISR scenario is now in such a state that you can create or process it. If you enhance the form scenario at a later date and add new fields, you must carry out the comparison again. This is the only way to ensure that consistency is achieved between the form scenario and ISR scenario.

  • Create the interactive form.
    1. Choose Version.
    2. Decide whether you want to process an existing form or create a new one.
      3. Recommendation
      We recommend that you regenerate the form. This is the only way to ensure that the form is exactly the same as the definition of the ISR scenario or that of the basis form scenario.
      In addition, you should never use the same form in two different ISR scenarios as this could cause problems when processing the form.
      Note
      Make sure 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 generated automatically according to the template Z_ISR_FORM_<ISR Scenario>, whereby <ISR Scenario> is the name of the ISR scenario.
    3. Generate the form. You can choose between the following options for this: -- Create without template
      4. We recommend that you use this option.
      -- Create Using Template from Existing Scenario
      With this option, all fields of the existing scenarios are copied into the form. This can cause inconsistencies.
      -- Generate with SAP Design
      This option should not be used with HR Administrative Services. With this option, the form is generated with too many unnecessary fields and UI controls that you cannot use without additional adjustments.
    4. Specify the package in which the form should be created.
      5. Note
      Note that the form is a client-independent workbench object and therefore exists in all clients. The ISR scenario and the form scenario are client-dependent. In addition to the form, an interface is also generated for which you must also enter a package. This interface is technically necessary and contains fields (characteristics) that should be available in the form.

  1. Process the form using Adobe LiveCycle-Designer.

    For more information, see the SAP Library under HR Administrative Services -> HCM Processes and Forms -> ISR Scenario -> Configuration of ISR Scenario -> Creating and Processing Interactive Forms.

    Note

    Note that the form for a form scenario for the XI message type is only used for display. We therefore recommend that you only use the display UI controls in this form.

  2. Save and activate the form. Make sure that you also activate the generated interface.
  3. Finish the processing in Adobe LiveCycle Designer.

    A message may appear saying that not all form fields are defined as characteristics. Answer the question whether the characteristics should be generated with No. Otherwise inconsistencies may occur.

Note on Processing Forms

To process a form that was already created, you have the following options:

  • You can process the form by performing this IMG activity and choosing Change Adobe Form
  • You can process the form directly using the Form Builder (transaction SFP). In this case, enter the name of the form manually, choose Change and then the tabpage Layout.

If you have defined new form fields and have compared the ISR scenario as described in step 5, you should always call the Adobe LiveCycle Designer using IMG activity Form Scenario for XI Message Type: Create ISR Scenario. The system sees automatically that new fields exist and asks whether the interface of the form should be adjusted. Answer this question with Yes. When ending the Adobe LiveCycle Designers you must then make sure that you also activate the interface.

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional 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_XI_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  20060905 
SAP Release Created in 600