Import IDoc from FTP to Pricefx

This template fetches an IDoc file from an FTP location (configured during deployment) and loads its data to a selected Pricefx partition using a defined mapper. The file should contain IDoc in XML format.

Installation

Go to PlatformManager > Marketplace, find Import IDoc from FTP to Pricefx, select Deploy and then select a target integration instance and template version.

Configuration Steps

  1. Enter a name for the template deployment and select Pricefx connection (or create a new one).

  2. Choose the SFTP connection (or create a new one).

  3. In Integration Properties:

    • Pricefx object type – Select the type of Pricefx object that will be loaded. If you select Product/Customer Extension, you need to specify additional mapping in the mapper in the next step.

    • Use .done file

      • If Yes is chosen, there has to be an empty marker file with the “.done” suffix added along with the actual data file. For example, if there is a data file named idoc.xml, there has to be another file idoc.xml.done added. This would only be used if the data file is generated by other integrations.

      • If No is chosen, you only need to upload the data file, without any additional marker files. This would mostly be used when the customers will be uploading the file themselves.

    • Use configured business keys – Choose Yes if you want to define your own custom business keys to be used when uploading data to Pricefx.

    • Comma separated business keys – Put here a list of comma separated business keys that will be used when uploading data to Pricefx. This is only used if the option above is set to Yes.

    • IDoc file path on FTP server – Defines where the file is located at the FTP server. The path is relative to the root path from the FTP connection configuration.

  4. In the mapper step, define the mapping of input and output fields and decide whether empty values should be sent as an empty string or null value.
    If Product/Customer Extension was selected, the mapping should have these properties:
    Type – constant, Input – <extension actual name>, Output – "name"

 

PlatformManager version 1.75.0