Show TOC

Procedure documentation1.1 Configuring a Form Scenario and an ISR Scenario

 

A form scenario, together with the related ISR scenario, provides the basis of a form-based process and configures the interactive form.

In this lesson you will perform the following steps:

  • Create the form scenario ZTFS and ISR Scenario ZTFS with the relevant personnel and address fields that enable the employee to use a form to inform the system of their change of address

  • Define and configure fields from infotypes I0001 and I0006 (setting default values and input help) and define how the form data is processed in the back-end system

  • Generate automatically the accompanying ISR scenario

  • View the automatically generated form scenario step

  • Check the form consistency

  • Create the form for the form scenario.

Procedure

Create the Form Scenario and ISR Scenario with Design Time for Processes and Forms
  1. Open Design Time for Processes and Forms.

  2. In the object selection area, choose Form Scenario from the dropdown list.

  3. Enter a name for the new form scenario – ZTFS – and choose Enter.

  4. A dialog box appears. Choose Yes to create a new object.

  5. In the Create Form Scenario dialog box, enter the following information:

    • ISR Scenario: ZTFS

    • Form: Z_ISR_FORM_ZTFS

    • Backend Service: SAP_PA

    Note Note

    The Backend Service textbox should indicate which back-end service is being used in this form scenario. You may change the service by selecting from the dropdown list. You may also add further back-end services to the form scenario at a later stage.

    End of the note.
  6. Choose Continue to confirm your entries.

  7. A dialog box appears asking to create both a form (scenario) and an interface (ISR scenario). Choose Yes to create them both.

  8. In the Object Entry Directory dialog box, choose Save to create a local object.

Define and Configure the Relevant Form Scenario Fields

Define the form fields for form scenario ZTFS version 0. This includes the following fields:

  • Mandatory fields that you must always create (already provided by the system)

  • Display fields that give the user of the form information about the employee whose data the form changes, for example data that is part of a form header row

  • Specific form scenario fields for changing data

  1. In the object hierarchy area, double-click Fields.

    The object processing area displays the mandatory fields for your form scenario required by the back-end system. The fields displayed vary according to which back-end service you are using. Here we are using SAP-PA.

  2. Choose Service Fields to add more fields.

    The Transfer Service Fields window appears showing the back-end service in use and allowing you to select the infotype and infotype version. Choose the following settings. The system automatically displays the correct screen structure fields for the selected infotype:

    • Infotype: 1

    • Infotype Version: 99 (for International)

    • Operation: Change

    Note Note

    • Screen structure - This is used to display data on the user interface that is derived from the relevant database, but not saved in the database. The data can be input fields, output fields, or descriptive texts. You cannot make assignments to more than one screen structure. Each screen structure contains all infotype fields that are relevant for the user interface.

    • Version - At least one screen structure exists for each infotype. If the infotype is country-specific, more than one screen structure exists. Select the appropriate version for the country.

    • Operation - If you want to run the Create, Change, Delete, or Change without Delimiting operations on the InfoObjects, you must provide the data for the new data records to be created. You do this by assigning form fields to InfoObjects. Access to the InfoObjects is enabled by screen structures.

    End of the note.
  3. Choose Determine Fields to update the field list in the dialog box and select the fields from infotype I0001 in the following table. For each field:

    1. Scroll to the row with the appropriate Name or Service Fld.

    2. Select the corresponding Transfer column checkbox.

    3. Enter a Field Name using the values in the following table.

    Name

    Service Fld

    Field Name

    Default Value

    Employee/app Name

    ENAME

    I0001_EMPLOYEE_NAME

    SAP-PA service/Cur

    Personnel Area

    WERKS

    I0001_PERSA_TEXT

    SAP-PA service/Cur

    Position

    PLANS

    I0001_POSITION

    SAP-PA service/Cur

  4. Choose Continue to transfer the selected fields to your form scenario.

    The display area now shows the added form fields.

  5. Add the default values for infotype I0001 fields in the above table. For each field, proceed as follows:

    1. Double-click the Default Value cell.

    2. From the Change Default Value Determination dialog box, select the Origin of Default Value =SAP-PA radio button.

    3. In the Type of Default Value column, choose Cur(rent) from the dropdown list.

    4. Save your entries.

  6. Select the fields from infotype I0006 (Addresses). These are form scenario specific fields allowing the employee to change data.

    1. Choose the Service Fields button.

    2. Choose the following settings:

      • Infotype: I0006

      • Version: 99

      • Subtype: 1 (for permanent addresses)

      • Operations: Change

        Note Note

        The Operations text box defines how the form data is processed in the back-end system when the automatic save is executed. An operation must be selected if you want to modify the infotype record in the database. The SAP_PA back-end service enables data records of Personnel Administration infotypes to be created, changed, and deleted. The operation ‘change’ causes the back-end service to copy the last infotype record and override any data with the data from the form scenario

        End of the note.
    3. Choose Determine Fields to display the infotype I0006 fields.

  7. Select the Infotype I0006 fields in the following table. For each field, proceed as follows:

    1. Scroll to the appropriate Name or Service Fld.

    2. Select the corresponding Transfer column checkbox.

    3. Enter a Field Name using the values in the following table.

    Name

    Service Fld

    Field Name

    Default Value

    Street

    STRAS

    I0006_STREET

    <blank>

    Postal Code

    PSTLZ

    I0006_POST_CODE

    <blank>

    City

    ORT01

    I0006_CITY

    <blank>

    Country Key

    LAND1

    I0006_COUNTRY

    DE

  8. Choose Continue to transfer the selected fields to your form scenario. The display area now shows the added form fields.

  9. Add the default value for Country.

    1. Double-click the Default Value cell of the Country row.

    2. From the Change Default Value Determination dialog box, select the Origin of Default Value =Manually radio button. Enter DE.

    3. Save your entries.

  10. Choose Save on the main toolbar to save the form scenario and automatically generate the ISR Scenario. The system reads the form fields of the linked form scenario and automatically creates all required form fields (characteristics) in the ISR scenario. The form scenario and ISR Scenario are now synchronized. If you enhance the form scenario at a later date and add new fields, you must then synchronize again by saving the form scenario in the described way.

View the Automatically Generated Form Scenario Step
  1. In the object hierarchy area, double-click Scenario Steps. A default scenario step is visible.

  2. Add the following scenario steps under the existing default scenario step:

    Scenario Step

    Name

    FSS_1

    Request

    FSS_4

    Department Check

  3. Save your entries. Notice that your new scenario steps have the same column settings as the default scenario step.

  4. Delete the default scenario step.

  5. Save your entries.

Note Note

Scenario steps allow you to define specific Customizing for process steps. This Customizing affects the use of certain fields, the processing of attachments, and the availability of hyperlinks. For these settings to come into effect when the process is run, you must also define which scenario step to use in the appropriate workflow step. When defining the process, you define which scenario step is used to start the process under Creating a Process. A form scenario must have at least one scenario step. Only one form in your form scenario means that your form looks the same in all process steps. Note that all fields are assigned to this step automatically.

End of the note.
Check the Form Scenario Consistency

Check the following settings for the form scenario:

  • Definition of the form scenario

  • Definition of the linked ISR scenario

  • Definition of the back-end service used in the form scenario

  1. In the object hierarchy area, double-click your form scenario (the root of the hierarchy). The Check icon appears on the main toolbar.

  2. Choose Check.

  3. Process any error messages and warnings that are displayed in the Status Bar.

Note Note

The results of these checks are displayed in the status bar, providing information, error messages, or warnings. Incorrect settings should be corrected to enable the form scenario to run properly.

End of the note.
Create the Form for your Form Scenario
  1. In the object hierarchy area, double-click Form. The form, the ISR Scenario, and the interface were created when you created the form scenario at the beginning of this tutorial. When you save the form scenario, the ISR Scenario and the Interface are updated.

  2. Choose Change Form. The Adobe LiveCycle Designer Form Builder opens, ready for you to create your form.

Result

You have now created the form scenario, the form scenario steps, the ISR Scenario, and the interface as well as a form for entering the necessary data. You have checked that the form scenario is consistent and you are now ready to use the form scenario in a workflow step.