You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to Generic Integration Framework to Support SFTP Interface.
Contents
Generic Integration Framework to Support SFTP Interface[edit]
The Secure File Transfer Protocol (SFTP) adapter will be built as an automated solution to load Masterdata once extracted from source of truth via SFTP. SFTP, a secure version of File Transfer Protocol (FTP), is a network protocol which facilitates file access, file transfer and file management over a Secure Shell (SSH) data stream.
Configuring SFTP Adapter to load Masterdata[edit]
The ICM support for generic integration provides the ability to synchronize ICM Masterdata tables using the input file from SFTP server. Through a technical configuration, you can specify the attributes to be used for this generic integration.
Create Masterdata Contract Type [edit]
To enable synchronization between ICM and SFTP, a Masterdata Contract Type should first be configured in ICM, with specific attributes for the integration.
To create a Masterdata Contract Type:
1. Click Create Contract Type sub menu from the Configuration tile. The Select Contract Type page opens.
2.Select Masterdata.
3. Click the Next button. The Create Contract Type Wizard page opens.
The Create Contract Type page has the following sections:
- Details: Enter the contract type name.
- Attributes: Select the Attributes for the Masterdata Contract Type.
- Display Preference: Select Attributes to be displayed in the Agreement Tile View.
- Team: Select the team.
- Verify: Verify the details in preview mode and click Create.
Client App Cross Reference[edit]
The Client App Cross Reference mapping maps ICM entities (for example, ICM attributes) to client app entities.
1. Navigate to the Create Masterdata page in ICM. This page contains the following tabs:
Masterdata Details
1. Select the Category from the drop-down. For example, Default.
2. Select the Masterdata Contract Type.
Note: In order to map ICM entities with entities in the file uploaded through SFTP, you must select Client App Cross Reference from the drop-down.
3. Click Next. The Attributes page opens.
Attributes
- Enter the relevant attribute values. For example, enter ICM Entity Name as ICMSupplierMaster and Client Entity Name as SupplierMaster. The Payload Type can be selected as CSV or Json.
- Select the Text Delimiter. Supported options are pipe, colon and comma.
- Select the Text Qualifier. Supported options are Single Quote, Double Quote, No Quote.
Note: The Client Name GenericIntegration must be selected. To create mapping using SFTP, select FileBased in the Integration Mode drop-down. The Transport Protocol can be FTP, SFTP, SSH or Blob.
4. Click Save to save the entity mapping.
Client App Entity Mapping [edit]
The Client App Entity Mapping maps ICM attributes (for example, attribute names used in Supplier Master) to attributes in the file uploaded through SFTP.
1. Navigate to theCreate Masterdata page in ICM. This page contains the following tabs:
Masterdata Details
1. Select the Category from the drop-down. For example, Default.
2.Select the Masterdata Contract Type.
Note: In order to map ICM attributes with attributes uploaded through SFTP, Client App Entity Mapping must be selected from the drop-down.
3. Click Next. The Attributes page opens.
Attributes
1. Enter the relevant attribute values. For example, enter ICM Entity Name as ICMSupplierMaster and Client Entity Name as SupplierMaster.
To create mapping using SFTP, select FileBased in the Integration Mode drop-down. The Client Name selected must be GenericIntegration.
In case of lookup and non-lookup attributes: The ICM Relationship Key should be set for lookup attributes and kept blank for non-lookup attributes. The Relationship Key framing should be <Master Contract Type Name> Double Underscore<ICM Attribute Name>. For example, in case of Supplier Master the ICM attribute name will be ICMSupplierCountry and the Masterdata Contract Type for this attribute will be ICMCountryMaster. Hence, relationship key will be ICMCountryMaster__ICMSupplierCountry.
2. Click Save to save the entity mapping.
Using SFTP Adapter to load/publish Masterdata[edit]
Download Payload[edit]
- Navigate to the Masterdata page in ICM.
- Click the View Record icon next to the Client App Cross Reference entity you have created. The Masterdata Details page opens.
- Click the Download Payload button. The template for the Masterdata will be downloaded to your local drive.
Note: The file format of the template will be according to the Payload Type selected in the attributes of the Client App Cross Reference entity.
- Open the downloaded CSV or Json file. This file will be used by third-party systems to push data to the SFTP adapter.
Publish Payload[edit]
Click Publish Payload. The empty payload will be published.
Note: For any subsequent Masterdata changes, the user needs to click Publish Payload button again to update the empty payload.
Using SFTP adapter to load/publish Masterdata [edit]
Download Payload [edit]
1. Navigate to the Masterdata page in ICM.
2. C'lick' the View Record icon next to the Client App Cross Reference entity you have created. The Masterdata Details page opens.
3. Click the Download Payload button. The template for the Masterdata will be downloaded to your local drive.
Note: The file format of the template will be according to the Payload Type selected in the attributes of the Client App Cross Reference entity.
4. Open the downloaded CSV file. This file will be used by third-party systems to push data to the SFTP adapter.
Publish Payload [edit]
Click Publish Payload. The empty payload will be published.
Note: For any subsequent Masterdata changes, the user needs to click Publish Payload button again to update the empty payload.
A notification is displayed once the Payload is published successfully.
Note: The user can create a subscription to the job status updates by using the standard in Notification Setting in the User Administration menu.
