...
Navigate to Marketplace and select Integration Templates
Select the Import CSV from FTP to Pricefx option:
Click on the Deploy button.
From the drop-down list select your IntegrationManager instance. Click on the Deploy button.
The import wizard will now begin:
| Info |
|---|
NOTE: When using Integration Templates option, it will display all IM connections that are of a specific type and that type is called “pricefx”. It will present these in a drop-down list and if it doesn’t exist then this step will fail. |
6 . Click on the drop-down list for Pricefx connections:
...
| Info |
|---|
Only by selecting a partition connection can the deployment process continue. |
7. Update the Name to CSV Import-Product Cost Import Transaction CSV from FTP to Pricefx, then click Next button.
8. Choose the SFTP Connection for the Customer URL path from the list:
...
We need to update the Directory Path to reflect the relative location where the CSV file for our Product Extension table transactions data will be located, it should appear as shown below:
...
10. Click Next button.
11. Next, the Data Upload and Mapping panel will appear. On this panel we need to drag and drop our CSV file for the upload:
...
12. Drag and drop CustomerMasterTransaction.csv onto the page.
13. The default parsing will appear for the first three rows:
...
14. Next, we need to select the Entity Type of Customer Data Source:
...
15. Next, we need to select the name of our Transaction data source:
...
16. Now we need to perform the data mapping to link our CSV columns to Product Master in our partition:
...
| Info |
|---|
The mapping process within the integration template will attempt to map the CSV columns to master table metadata attribute values. If it can’t find a match, then it will leave the Output column blank. |
NOTE: The Customer Id and Customer Name are considered mandatory fields. If the partition is empty and contains definition of Customer Master as “out-of-the-box”, then no automatic mapping is created.
16. You will notice that some of the CSV columns are automatically mapped to our Customer master table (all of the names that are singular are already done). Thus, we need to map the remainder:
...
17. Next, we will assign the remaining CSV columns to attribute(s) column(s) in our Customer Master:
Customer Group to attribute1(“CustomerGroup”)
Customer Type to attribute2(“CustomerType”)
Product Category to attribute3(“ProductCategory”)
Customer Class to attribute3(“CustomerClass”)
Sub-Region to attribute12(“SubRegion”)
18. The next mapping is for Last Update, we don’t need this mapping so you can delete it using the trashcan icon for this mapping.
...
19. The last two column mappings (User Group Edit and User Group View) are not needed and the mappings can be deleted.
| Info |
|---|
IMPORTANT: Since the CSV columns actually match the attribute names in our transaction data source all of the mapping is completely automatically. |
16. There is only one column mapping that has not been performed, if you scroll down and find the Last Update Date:
...
17. We don’t need this mapping, so we can delete this row in the column mapping by clicking on the trash can for that row:
...
20. Click Continue button.
The data mapping and loading of the Customer master will now be accomplished:
...