Integrate
Template H
Use this page to Create a Basic Template.
To access this page:
Field |
Description |
Category Processes |
Click to open the Process page to add, edit, and delete processes for the category. |
TEMPLATE NAME |
Displays the name of the template entered when the template was added. |
DESCRIPTION |
Displays a description of the template entered when the template was added. |
CONNECTION ID |
Displays the connection ID for the target system against which the template type will be created. The options in this list box are connections registered in Common. Refer to Establish a Connection to a Target System for more information. NOTE: The connections that display are based on the selection in the TYPE list box. For example, if the user selects the template type BODS Execution, the CONNECTION ID list box displays connections to Data Services repositories only. |
TYPE |
Displays the template type selected when the template was added. |
ACTIVATE/DEACTIVATE |
Click to activate the template. The button displays a green icon for active templates and a red icon for inactive templates. |
ACTIVE |
If enabled, the template is active. If disabled, the template is inactive. |
Report |
Click to open the Template report which displays the screens, fields and other data captured during template creation. |
L |
If enabled, the template contains loops. Looping can be enabled at the template level for BDC Script and GUI Script template types only. |
Processes |
Click to open the Template Processes page which lists the processes to which the template is assigned. |
Template V All Tabs
This page has the following tabs:
- General tab BDC Script Template Type
- Configuration tab BDC Script Template Type
- Documentation tab
- Copy tab
- General tab Custom Template Type
- Documentation tab
- Copy tab
- General tab BAPI/RFC Template Type
- Configuration tab BAPI/RFC Template Type
- General tab GUI Script Template Type
- Configuration tab GUI Script Template Type
- General tab Syniti Connect
- General tab: SAP Data Services Job Template Type
- General tab User Defined Template Types
- Configuration tab User Defined Template Type
General tab BDC Script Template Type
Use this page to Import a BDC Script from a File.
Field |
Description |
Basic Details |
|
Template Name |
Displays the name of the template entered when the template was added. |
Connection ID |
Displays the SAP connection ID for the system against which the BDC script was created. The options in this list box are connections registered in Common. Refer to Establish an SAP Connection in Common for more information. NOTE: The connections that display are based on the selection in the Type list box. For example, if the user selects the template type BODS Execution, the CONNECTION ID list box displays connections to Data Services repositories only. |
Type |
Displays the template type selected when the template was added in this case BDC Script . |
Transaction Code |
Displays the SAP transaction code used by the BDC script. |
Stored Credentials |
|
User Credentials |
Click to open the User Credentials page to add Login credentials for the current user to track that user’s updates posted to the target system related to requests based on this template. |
Credentials Detected |
If checked, the user name and password have been detected based on the user credentials setting. If unchecked, the credentials have not been detected and must be added for the request to post successfully. |
File Import |
|
File Name Upload a file/Download a file |
Click to Upload the SHDB recording file for import. Click Download to download the file that was uploaded. |
Import |
Click to import an uploaded SHDB recording file containing a BDC script. A file must first be uploaded before it can be imported. |
Configuration tab BDC Script Template Type
Field |
Description |
Template Configuration |
|
Enable Loop |
If enabled, the BDC script can be configured to use looping at the BDC Script Data level and BDC Script Data rows can be put into and taken out of loops. When processing a loop during posting, Integrate processes multiple child keys for one parent key. Looping also allows Integrate to post multiple headers with infinite details. Enable looping during template creation. |
BDC Screen |
Click to open the BDC Screen page to manage the screens and fields captured during the SHDB transaction used for creating the BDC script. |
Custom Fields |
Click to open the Custom Fields page to add custom fields to the BDC Script template. The count on this icon represents the number of custom fields that have been added to the template. |
Documentation tab
Field |
Description |
Template Documentation |
|
Notes |
Displays notes entered about the template. |
Report |
Click to open the Template report which displays the screens, fields and other data captured during template creation. |
Active |
If enabled, the template is active and can be added to a process but cannot be updated. If disabled, the template can be edited. |
Copy tab
Field |
Description |
New Template Settings |
|
Copy Template |
Click to open the Copy page to create a template based on a copy of the current template. |
Merge BDC Screens |
Click to open the Copy page to merge the BDC screens captured in the current template to another template in any category. NOTE: This button displays for BDC Script template types only. |
General tab Custom Template Type
Use this page to Integrate
Field |
Description |
Basic Details |
|
Template Name |
Displays the name of the template entered when the template was added. |
Connection ID |
A Connection ID cannot be selected for a Custom Template. |
Type |
Displays the template type selected when the template was added, in this case Custom. |
Custom Properties |
|
Assembly File |
Displays the full name of the .NET DLL file that is the wrapper for code that calls the external process. |
Type Full Name |
Displays the Type (class) name in the .NET DLL that aDisplays the long name for the Type (class). This is required for loading the code to call the external process. |
Documentation tab
Field |
Description |
Template Documentation |
|
Notes |
Displays notes entered about the template. |
Report |
Click to open the Template report which displays the screens, fields and other data captured during template creation. |
Active |
If enabled, the template is active and can be added to a process but cannot be updated. If disabled, the template can be edited. |
Copy tab
Field |
Description |
New Template Settings |
|
Copy Template |
Click to open the Copy page to create a template based on a copy of the current template. |
General tab BAPI/RFC Template Type
Use this page to Configure a BAPI Template and Configure an RFC Template.
Field |
Description |
Basic Details |
|
Template Name |
Displays the unique name of the template entered when the template was added. |
Connection ID |
Displays the SAP connection ID for the system which contains the BAPI/RFC. The options in this list box are connections registered in Common. Refer to Establish an SAP Connection in Common for more information. The connections that display are based on the selection in the Type list box. For example, if the user selects the template type BODS Execution, the CONNECTION ID list box displays connections to Data Services repositories only. |
Type |
Displays the template type selected when the template was added in this case BAPI/RFC . |
Function Name |
Displays the RFC/BAPI function that Integrate can call from SAP. This value is selected when the template is added. The functions are extracted from SAP using the SAP Connections page. |
Create BAPI Template |
Click to pull the definition of the Function Module listed in the Function Name field from SAP to complete the template. |
Stored Credentials |
|
User Credentials |
Click to open the User Credentials page to add Login credentials for the current user to track that user’s updates posted to the target system related to requests based on this template. |
Credentials Detected |
If enabled, the user name and password have been detected based on the user credentials setting. If disabled, the credentials have not been detected and must be added for the request to post successfully. |
General tab Syniti Connect
Use this page to Create a Syniti Connect Template.
Field |
Description |
Template Name |
Displays the unique name of the template. |
Connection ID |
Displays the name of the data source that contains the Boomi Process used by the Template. The options in this list box are connections registered in Common. |
Type |
Displays Syniti Connect. |
Boomi |
|
Boomi Process ID |
Displays the name of the Boomi Process used to post data. This is the default Process added with the data source, but can be updated to another Process as needed. |
General tab SAP Data Services Job Template Type
Use this page to Create a Template with the SAP Data Services Job Template Type.
Field |
Description |
Basic Details |
|
Template Name |
Displays the unique name of the template entered when the template was added. |
Connection ID |
Displays the connection ID for the target system for posting. The options in this list box are connections registered in Common. Refer to Establish a Connection to a Target System for more information. The connections that display are based on the selection in the Type list box. For example, if the user selects the template type SAP Data Services Job, the CONNECTION ID list box displays connections to Data Services repositories only. |
Type |
Displays the template type selected when the template was added, in this case SAP Data Services Job. |
File Structure |
|
Data Services Job Name |
Displays the data source job added to the process post record for processes based on the SAP Data Services Job template type. |
Configuration tab BAPI/RFC Template Type
Field |
Description |
BAPI/RFC Configuration |
|
BAPI/RFC Definition |
Click to open the BAPI/RFC Definition page to view the definitions and BAPI fields contained in each definition. NOTE: The template must be created for data to display on the page. NOTE: Refer to Extract RFC Functions for more information. |
General tab GUI Script Template Type
Use this page to configure a GUI Script template.
Field |
Description |
Basic Details |
|
Template Name |
Displays the unique name of the template entered when the template was added. |
Connection ID |
Displays the SAP connection ID for the system against which the GUI script was recorded. The options in this list box are connections registered in Common. Refer to Establish an SAP Connection in Common for more information. The connections that display are based on the selection in the Type list box. For example, if the user selects the template type BODS Execution, the CONNECTION ID list box displays connections to Data Services repositories only. |
Type |
Displays the template type selected when the template was added in this case, GUI Script . |
Transaction Code |
Displays the SAP transaction code used by the GUI script in recording. |
Stored Credentials |
|
User Credentials |
Click to open the User Credentials page to add Login credentials for the current user to track that user’s updates posted to the target system related to requests based on this template. |
Credentials Detected |
If enabled, the user name and password have been detected based on the user credentials setting. If disabled, the credentials have not been detected and must be added for the request to post successfully. |
Configuration tab GUI Script Template Type
Field |
Description |
Template Configuration |
|
Enable Loop |
If enabled, the GUI script can be configured to use looping at the GUI Script Data level and GUI Script Data rows can be put into and taken out of loops. When processing a loop during posting, Integrate processes multiple child keys for one parent key. Looping also allows Integrate to post multiple headers with infinite details. Enable looping during template creation or after recording. |
GUI Script Data |
Click to open the GUI Script Data page to edit and delete the fields captured during the GUI script recording. |
General tab User Defined Template Types
Use this page to Create a Fixed Width or Delimited Template and Configure an XML Template.
Field |
Description |
Basic Details |
|
Template Name |
Displays the unique name of the template entered when the template was added. |
Connection ID |
Displays the SAP connection ID for the system that can use data in the user defined file after it is created and transferred to an FTP server. The options in this list box are connections registered in Common. Refer to Establish an SAP Connection in Common for more information. The connections that display are based on the selection in the Type list box. For example, if the user selects the template type BODS Execution, the CONNECTION ID list box displays connections to Data Services repositories only. |
Type |
Displays the template type selected when the template was added in this case User Defined . |
File Structure |
|
User Defined Template Type |
Displays the template type. Values are Delimited, FixedWidth and XML. |
Define |
Click to open the Structure page to add, edit and delete structures for the User Defined template. When adding a template, this button displays after a value is selected in the User Defined Template Type list box and the template is saved. |
Stored Credentials |
|
User Credentials |
Click to open the User Credentials page to add Login credentials for the current user to track that user’s updates posted to the target system related to requests based on this template. |
Credentials Detected |
If enabled, the user name and password have been detected based on the user credentials setting. If disabled, the credentials have not been detected and must be added for the request to post successfully. |
Configuration tab User Defined Template Type
Use this page to Create a Fixed Width or Delimited Template and Configure an XML Template.
Field |
Description |
File Configuration |
|
Delimiter |
Displays the character that separates the values in delimited files. Displays for a Delimited Template Type only. |
Fixed Width Pad Location |
Displays whether Integrate will pad the value in the field to its full length with spaces before or after the value for Fixed Width files. For XML files, this field should display [None]. |