Import Partner Data
After you have imported or set up the EDI Import Mappings required to convert your partner data, you can make the necessary settings for importing the partner data.
Set up Import Paths
The data of your partner must be available as a file. This file must be stored in a directory accessible to COSMO EDI. Based on the file name or directory, COSMO EDI must be able to distinguish which transaction must be linked to the file and in which format the file is available.
To specify all directories where COSMO EDI will find the files to be imported from your partners, navigate to EDI Import Paths in COSMO EDI.
The EDI Import Paths page is accessed using the Tell Me feature. Choose the 
icon, enter EDI Import Paths, and then select the related link.
To set up a new import path, choose the New button. Some examples of how to set up the import paths are shown below.
The fields for setting up the data to be imported into the EDI Import Paths are described in the following table.
| Field | Description |
|---|---|
| Transaction Type | Enter the code of the transaction that you want to link to the file to be imported. If you select the drill-down arrow in the field, you get an overview of all possible transactions for importing partner data. These constant transactions were automatically created by the initialization run of COSMO EDI. |
| Type of Data Mapping | Specifies how data is mapped. The options are: - Inhouse (No Mapping) - The file already exists in the in-house format and does not need to be converted. This is the case, for example, if your partner also uses COSMO EDI or if the data is already delivered to you otherwise in in-house format, for example, when processing intercompany transactions. - Mapping - The file is in a different message format and must be converted to the in-house format. This is the default option. |
| Mapping Code | Enter the import mapping code if you need to convert your partner's data into the in-house format. The import mapping converts the partner data into the in-house format required for COSMO EDI. The import mapping selected here must match the transaction type you have defined. |
| File Transfer Code | Specifies the code associated with the file transfer service. |
| Path | Specifies the directory where the files to be imported can be found. This directory can also be located on a network drive. However, full rights to read, write and delete files are required. |
| File Name | Enter the name of the files to be read in the directory specified under Path. You can use the wild cards * and ?. Note that the files selected in this way must correspond to the transaction specified under transaction type and the message format entered in the mapping code, if applicable. |
| Archive Path | After the file has been imported by COSMO EDI without errors, the file will be moved to the directory specified here so that it will not be imported again during the next import. The file name of the imported file is extended by the date (yyyymmtt) and the time (hhmmsshhhh) to be unique. For example: The file Order0001.txt will be moved to the archive path on 18.07.2008 at 08.39:53,696 after the correct import and would then be named Order0001.txt20080718083953696. |
| Journal Name | If you want to transfer the data to be imported to a specific journal, select this posting sheet here. When importing the data, the application then places the data only in this journal. In the example above, for example, the intercompany invoices to be imported of transaction type INVOIC_IMP are only placed in the INTERCOMP journal. This means that you can determine the journal into which the imported data can be transferred, either for specific partners or for specific sales coordinators. |
In this example, a directory for importing orders (transaction: ORDERS_IMP) and for importing order changes (transaction: ORDCHG_IMP) has been defined. This became necessary because the file names for both orders and order changes are Order*.txt.
A differentiation of the files between orders and order changes would therefore not have been possible in one directory.
If the files of these different transactions were located in one directory, the import of the orders (transaction type: ORDERS_IMP) would, for example, also import the order changes (transaction: ORDCHG_IMP) and vice versa. This would inevitably cause an error message.
When you set up the import paths, make sure that the files found under File Name and Path match the transaction specified in the Transaction Type. Otherwise, you will receive an error message when you try to import the partner data later.
Assign Import Mappings to the Data to Be Imported
If you have set up the necessary import mappings for converting the partner data to the EDI in-house format, you must enter these in the import paths.
In this example, different mapping codes were assigned because the files to be imported have different message formats (EANCOM, SAP, TRADACOM). However, the files to be imported are all imported from the same directory C:\...\ORDER.
To ensure that the files to be imported are converted to the EDI in-house format with the appropriate import mapping, you must either ensure that the files are named accordingly as shown above or, that the files to be imported are stored in different directories depending on the message format.
When setting up the import paths, make sure that the files to be found under File Name and Path match the transaction specified under Transaction Type and that the format of the files matches the stored mapping code. Otherwise, you will receive an error message when you later try to import the partner data.
Actions
The actions on the EDI Import Paths page are described in the following table.
| Menu | Action | Description |
|---|---|---|
| Home | Test Connection | Allows users to test the connection to the server. |
| Open Inbox | Opens the EDI Inbox Messages page. | |
| Line | Controlling | Opens the EDI Import Path Controlling List in which you can manage the EDI Import Path Controllings. |
Feedback
Submit feedback for this page.