Configure a Process Based on a GUI Script Template

This topic contains the following sections:

Configure GUI Script Field Mappings

>Review the steps in the process.

The field mappings for process template loops can be created automatically using the Auto Generated Database Object feature. In this case, the MAPPING VALUE field and the TEMPLATE FIELD UNIQUE NAME field will have identical values. Refer to Generate Database Objects Automatically for more information.

Once the process template loop is configured, configure the field mappings for each loop level

When a template is added to a process, Integrate automatically creates loop levels based on the template. Each loop level of the template has a view mapped to it which contains the data to post for the corresponding template loop level for the process.

A process template loop field mapping provides the link between a field on a template and a column in a view. Each field on the template can be mapped to a view, be assigned a fixed value or be ignored.

Once a view is registered to the process template loop, Integrate compares the column in that view with the field names in the process template loop and automatically maps them if possible. If the fields in the view are named with valid SAP fields names, Integrate completes the mapping automatically based on the fields in the recording.

Synchronous templates also allow mappings to be tied to Return Values. Refer to Post Data Using Transaction Stringing for more information.

NOTE: Template Process Loop Field Mappings cannot be edited if the process is active.

NOTE: Field mappings automatically update to reflect a change in a process template loop’s view. For example, a user creates a process and selects a view name in the View Name list box on the Process page’s Vertical View on the General tab. When the process is saved, Integrate automatically maps the fields according to this view on the Process Template Loop Field Mappings page. If the user then updates the view name in the VIEW NAME list box on the Process Template Looppage, the Field Mappings are reset to reflect the columns in the updated view. If the process was created using the Auto Generate Database Object feature, updates to the VIEW NAME on the Process Template Loop page are also reflected in the field mappings on the Process Template Loop Field Mappings page.

To configure field mapping manually for a GUI Script process template:

  1. Select Categories from Navigation pane.
  2. Click the Processes icon for the category.
  3. Click the Templates icon for the process.

  4. Click the Loops icon for the process template.

    NOTE: The number displays the number of loops.

  5. Click Fields Mappings for a loop level on the Process Template Loops page.

  6. Click Edit.

    View the field descriptions for the Process Template Loop Field Mappings page.

  7. Locate a TEMPLATE FIELD UNIQUE NAME to configure.
    Either:

    Select a value from Mapping Value list box.

    NOTE: This value is a column in the database view.

    OR

    Enter a value in FIXED VALUE field.

    NOTE: A fixed value is a hard coded value sent during each posting process. It is read from the registration and not from the database. 

    NOTE:To ignore a field during a post, leave both MAPPING VALUE and FIXED VALUE fields blank.

    NOTE: If a mapping value is set but the value in the database is NULL, then Integrate will not include the field in the posting.

  8. Click Save.

Configure GUI Script Relationships

>Review the steps in the process.

A process based on a looped template must have links assigned to the view for different loops. These links are called relationships and are used to map values in parent views to values in child views.

Relationships between loops can be established manually, or Integrate can automatically determine relationships using the Auto Generate Database Objects feature.  Refer to Generate Database Objects Automatically for more information.

For each unique value in the Parent Column Name, Integrate will look for matching values in the Child Column Name and process each of the child rows through the post process.

NOTE: Each loop must have a View Name and Primary Key Column Name before a relationship can be added to the loop.

NOTE: If the VIEW NAME for a process template’s first loop is updated on the Process Template Loop page, Integrate updates relationships involving that loop with the new view name. Integrate updates relationships whether or not the process was created using the Auto Generate Database Objects feature.

NOTE: A process cannot be activated if the process is based on a GUI Script template with loops and no relationships have been established between the loops.

To add a relationship manually:

  1. Click Categories from Navigation pane.
  2. Click the Processes icon for a category.
  3. Click the Loops icon for a process based on a GUI Script template with multiple loops.

  4. Click Relationships on Page toolbar.

    View the field descriptions for the Relationship Mapping page.

    NOTE: Each loop level must be linked to another loop as either a parent or a child in a relationship.  The first loop in the process template and the parent of all other loops in the process template displays at the top of list on the Relationship Mapping page, and is called Upload.

  5. Click the + icon below a loop level.

    NOTE: This action allows the user to create a parent child relationship between the loop level above the + icon and the loop level that is above it in the hierarchy (the parent loop called Upload). For example, The Relationship Mapping page displays the Upload loop. Underneath Upload, Loop 1.1 and Loop 1.2 display. Clicking the plus icon beneath Loop 1.1 displays the Process Template Loop View Relationships page, where the user selects the column name for the parent Upload loop and the column name of the child Loop 1.1. This column name will link these loops together.

  6. Select a column name from Parent Column Name list box to set the parent relationship.

    NOTE: When Integrate generates the relationship automatically, it uses the value ID for the Parent Column Name. If the user manually sets a column as the Parent Column Name, this column must contain a unique value that can be mapped to a column in the child loop.  

  7. Select a column name from Child Column Name list box to set the child relationship.

    NOTE: When Integrate generates the relationship automatically, it uses the value ParentID for the Child Column Name. If the user sets a column as the Child Column Name, this column must contain a unique value that can be mapped to the Parent Column Name in the parent loop.  

  8. Click Save.

To edit a relationship on the Relationship Mapping page to accommodate changes in tables an d views:

  1. Click Edit beneath the plus icon for a loop.
  2. Select an option from Parent Column Name list box.
  3. Select an option from Child Column Name list box.
  4. Click Save.