Complete Journal
After the import mappings have been transferred or created and these have been mapped in the import paths to the files to be imported, the data can be transferred to the EDI Journal of COSMO EDI for checking and revision. After the plausibility check has been completed and the data is correct, the partner data is transferred from the EDI Journal to the Microsoft Dynamics 365 Business Central documents.
The EDI Journals page is accessed using the Tell Me feature. Choose the 
icon, enter EDI Journals, and then select the related link.
Double-click the journal to which you want to transfer the partner data. Only the partner data that matches the Transaction Type field is transferred to the selected journal. In the example, only the partner data of the ORDERS_IMP – Import Orders transaction.
To import the current partner data, select Home > Create Proposal in the EDI journal.
Confirm the window that opens with OK to start importing any existing partner data of the ORDERS_IMP transaction type into the current STD journal.
Import Data into a Specific Journal
All lines of the import paths with the same transaction code are always checked for the existence of new partner data and, if data is found, all data is transferred to the current journal.
There is an exception if an EDI Journal has been stored in the import paths. In the example below, the specific INTERCOMP journal was stored in the import paths for the intercompany orders. The import was called using the STD EDI journal.
Only the data from the import paths for which either no journal name or the current journal name is stored are transferred to the STD EDI journal. This means that only the first line, but not the second line, can be used for the current transfer.
This also means that if the import is called up from the INTERCOMP EDI journal, the files would be taken over from both lines, because no journal is stored in the first line. The following figure shows the correct setup for this case.
In this case the first line would only be transferred to the INTERCOMP journal and the second line only to the STD journal.
Result of Importing Partner Data
The result of importing existing partner data will be the completed journal into which the partner data has been transferred.
Because we assume that we have not yet carried out any further setups in COSMO EDI, such as the creation and setup of EDI partners, the EDI Journal shown below as an example shows for each line that there are errors for the transferred partner data, which must be corrected before the data can be transferred to the Microsoft Dynamics 365 Business Central documents.
The setup of COSMO EDI to correct errors in the journal will be discussed in more detail when the processing of the individual transaction types is explained.
If, however, an error should occur during conversion when importing partner data, e.g. because the file could not be imported correctly and the import mapping generates an error, note that COSMO EDI renames the imported file. Provided that partner data to be imported was found, the following cases can be distinguished after the import:
| Conversion to in-house format successful? | Partner data transferred without errors? | Results / Actions |
Transfer to Dynamics 365 Business Central docs successful? |
|---|---|---|---|
| No | No | Each file to be imported is named with the date (yyyymmdd), the time (hhmmsshhh) and the extension _processing. This ensures that the file is not processed twice when another user attempts to import the data. Because the file could not be transferred into the in-house format without errors, the file remains in the import directory under the new name. A line is still displayed in the journal. However, it contains error messages that indicate that the conversion was not successful. Apart from that, there is no detailed data for this line. | No |
| Yes | No | The data is displayed in the journal and can be checked and corrected here. However, a Yes in the Errors existing field prevents the data from being posted and transferred to the Microsoft Dynamics 365 Business Central documents. The name of the imported file is extended by the time of processing and the file is moved to the backup directory. | No |
| Yes | Yes | The data is displayed in the journal and can be transferred to the Microsoft Dynamics 365 Business Central documents by posting. The name of the imported file is extended by the time of processing and the file is moved to the archive directory. | Yes |
Protocols of the Import
The EDI Protocols page is accessed using the Tell Me feature. Choose the icon, enter EDI Protocols, and then select the related link, or from the EDI Journal page, choose Journal > Protocol to open the EDI Protocols page.
The posting of the imported data is logged here. Double-clicking a line opens the protocol.
General data is displayed in the header of the protocol and document-specific data in the lines.
General FastTab
The fields of this FastTab are described in the following table.
| Field | Description |
|---|---|
| No. | Here a consecutive number is automatically assigned for unique logging. |
| Transaction Type | The logged transaction is displayed here. |
| Transaction Type Description | The description of the logged transaction is displayed here. |
| Partner No. | The partner of the logged transaction is displayed here. |
| Test Indicator | Specifies whether the transfer of data was marked as a test. |
| Comment | The logged remark of the transaction is displayed here. |
| Error Existing | This displays whether there were any errors when the transaction was posted. Under certain circumstances, it is also possible to post incorrect lines of a journal. To be able to check this later, this field and the errors are also logged. |
| Warning Existing | This displays whether warnings existed at the time the transaction was posted. It is also possible to post with existing warnings, but the warnings are still logged. |
| Confirmation Existing | If confirmations were available for the transaction, this is indicated by Yes in the field. |
| User ID | The user ID of the employee who posted the transaction is displayed here. |
| Processing Date | Processing date of transaction |
| Processing Time | Processing time of transaction |
Lines FastTab
The fields of this FastTab are described in the following table.
| Field | Description |
|---|---|
| Line No. | Here a consecutive number is automatically assigned for unique logging. |
| Document Type | The document type affected by the data import is displayed here. For example, if you have imported a sales order, Sales Order will appear here. |
| Document No. | The document number affected by the data import is displayed here. For example, if you have imported a sales order, the number of the sales order in Microsoft Dynamics 365 Business Central that was created or updated is displayed here. |
| Document Sub-No. | An additional document number is entered in this field. This can be the used journal name, for example, when transferring the remittance advice (transaction: REMADV_EXP). In this case, the used template is transferred to the Document No. field. When importing delivery requests (transaction: DELFOR_IMP), the customer's blanket order number is saved in the Document Sub-No. field. In this transaction, the Document No. field then contains the Microsoft Dynamics 365 Business Central blanket order number. |
| External Document No. | The invoice number assigned by the vendor is entered in this field, for example, when importing purchase invoices (transaction: INVOIC_IMP). In this transaction, the purchase invoice number generated in Microsoft Dynamics 365 Business Central is then entered in the Document No. field. |
| Document Archive No. | When transferring delivery requests (transaction: DELFOR_IMP) with the COSMO Automotive module, a delivery request archive with the imported data is created in addition to the creation of a protocol. This archive is then used to evaluate changes between the last and current delivery request. |
| Document Modification Type | Here it is displayed whether it is one of the following document changes: - New - The transferred document was regenerated. - Change - The transferred document has changed an existing one (for example, DELFOR - Delivery Request). - Deletion - The transferred document should be deleted (for example, ORDCHG_IMP – Sales Order). |
| Comment | The logged comment of the document is displayed here. |
| Protocol No. Confirmation | The number of the EDI Protocol with which the current protocol was confirmed is displayed here. For example, if you send sales invoices to a customer with COSMO EDI and the customer sends you a confirmation of receipt of the sales invoices using the APERAK_IMP transaction, then COSMO EDI creates its own protocol for processing the confirmation and links it to the protocol that belongs to the sending of the sales invoices by storing the protocol number of the confirmation in the protocol of the sales invoices in this field. |
| Status Acknowledgment | If the transferred document was confirmed, the status of the confirmation for this document is displayed here. The options are: - Correct - The transferred document was confirmed as correct. - Incorrect - The transferred document was confirmed as incorrect. |
| Partner Reference Type Acknowledgment | There are two options in this field if there is a confirmation for the current protocol line: - Data exchange - This option is set if the confirmation status refers not only to the current document but to the complete data transfer. In this case it is possible, for example, that a complete data transfer is confirmed or rejected. - Message - This option is set when the confirmation status refers only to the current document. In this case, it is possible that not the complete data transfer, but only one document within the data transfer was rejected. |
| Partner Reference No. Acknowledgment | The reference number of the partner that belongs to the confirmation of the protocol line is stored here. |
| Partner Status Acknowledgment | If the protocol line belongs to a confirmation of the partner, the status of the confirmation for the document is displayed here. The options are: - Correct - The document for the protocol line was confirmed as correct. - Incorrect - The document for the protocol line was confirmed as incorrect. |
| File Path | The name and path of the imported file are displayed here. |
| Warning existing | This displays whether warnings existed at the time the transaction was posted. It is also possible to post with existing warnings, but the warnings are still logged. |
| Error existing | This displays whether there were any errors when the transaction was posted. Under certain circumstances, it is also possible to post incorrect lines of a journal. To be able to check this later, this field and the errors are also logged. |
Feedback
Submit feedback for this page.