Integrate

Configure a Process Based on a BAPI Template

This topic contains the following sections:

Configure BAPI Relationships

>Review the steps in the process.

Each loop in a process template based on a BAPI template must be linked to the Upload or Download loop through a relationship. The Auto Generate Database Objects feature creates these relationships, but they can also be edited.

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.

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: When Integrate generates relationships using the Auto Generate Database Objects feature, the Child Column Name does not have to link to the auto-generated Parent Column Name(ID) for Upload or Download tables. However, the parent and child loops must still be linked. Any column identified as a Header Key can be used as the Parent Column Name to link the detail records (or the child loops) to the header record (the parent loop). For example a Header Key column could be added to all upload and download tables for BAPI_MATERIAL_SAVEDATA that is populated with the Material Number.

To view relationships and configure them manually (if necessary):

  1. Click Relationships on the Page toolbar on the Process Template Loop page.

    NOTE If the Auto Generate Database Object feature was used, in the column on the left, Integrate mapped each child loop to the Upload parent loop. Below the plus icon for each loop name, the blue and orange bar indicates that the Child ID has been mapped to the Parent ID (in this case the Upload loop).

  2. Click Edit for an Upload relationship.

    View the field descriptions for the Process Template Loop View Relationships page.

    NOTE: The Parent Direction and Child Direction display Upload. The View Name for the Parent Upload is the view name generated for this loop by the Auto Generate Database Objects feature.  The View Name can be manually updated and saved on the Process Template Loop page. In this case, Integrate will update the View Name in the Parent Upload loop for the relationships.

  3. Select a column name from Parent Column Name list box to set a parent relationship if necessary.

    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. 

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

    NOTE: When Integrate generates the relationship automatically, it uses the value Parent ID 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.  

  5. Navigate back to the Relationship Mapping page.

    NOTE: In the column on the right, Integrate also mapped each child loop with download fields to the Download parent loop  Below the plus icon for each loop name, the blue and orange bar indicates that the Child ID has been mapped to the Parent ID (in this case the Download loop). Integrate also sets a relationship between the Parent Upload loop and Parent Download loop. The Download loops (those loop that contain download fields) map to the Parent Upload loop through the Parent Download loop.  This way, each record uploaded via the Primary Upload loop will have one or many corresponding records in the download tables.

  6. Click Edit for a Download relationship.

    View the field descriptions for the Process Template Loop View Relationships page.

    NOTE:: The Parent Direction displays Upload. The Child Direction displays Download.

  7. Select a column name from Parent Column Name list box to set a parent relationship if necessary.

    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. 

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

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.  

Configure BAPI Field Mappings

>Review the steps in the process.

Field Mappings can be performed by Integrate’s Auto Generate Database Object feature or can be configured manually.

Integrate’s Auto Generate Database Objects feature maps the fields for each process template loop. The MAPPING VALUE is identical to the TEMPLATE FIELD UNIQUE NAME.

When mapping fields for a process template based on a BAPI template, both Upload and Download field mappings are possible. Use filter buttons in the toolbar to quickly filter on All Fields, only Upload Fields, or only Download Fields. 

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 Loop page, 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 view field mappings and edit them manually if necessary:

  1. Click the Field Mappings icon for a loop.

  2. Click Upload Fields, Download Fields, or All Fields to apply a filter if necessary.

    NOTE: If no Upload fields exist, the Upload Fields button does not display. If no Download fields exist, the Download Fields button does not display.

  3. Click Edit for a field.

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

  4. Update the MAPPING VALUE or FIXED VALUE field.

    NOTE: Both fields cannot contain data for a Field Mapping.

  5. Click Save.