1. | Click Connectivity studio Integration Design. |
2. | Click the Documents tab. |
3. | Click New. |
4. | Define a meaningful name for the document. Example: If the document is used for a sales integration, you can use names like 'Sales - Order' or 'Sales - Invoice'. |
  | In the Document field, type a value. |
  |
Note: Best practice: In the document name, do not use the: |
5. | In the Project field, enter or select a value. |
6. | Define the applicable application for the document. For a journal document, for example, select a 'D365 FO' application. |
  | In the Application field, enter or select a value. |
  |
Note: You can only select an application that is defined for the applicable project. You can define project applications on the Projects page. |
7. | Select one of the journal-related document types: - WMS journal - Report as finished journal - Production picking list - Project journal |
  | In the Document types field, select an option. |
8. | Sub-task: Set properties. |
8.1 | Expand the Properties section. |
8.2 | Enter the journal name that defines the desired journal type. Based on the document type and journal name, the journal header is created. |
  | In the Name field, enter or select a value. |
  |
Note: You can only select journal names that are related to the selected document type. |
8.3 | You can automatically post the journal when the import is finished. |
  | Select Yes in the Post journals field. |
  |
Note: When testing the document and message, you are advised to set this field to No. So, you can review the imported data before the journal is posted. |
9. | Sub-task: Set custom handler. |
9.1 | Expand the Custom section. |
9.2 | For each journal document type, a standard handler classes is available: - WMS journal: BisDocumentWMSJournal - Report as finished journal: BisDocumentProdParmReportFinish - Production picking list: BisDocumentProdPickList - Project journal: BisDocumentProjJournal These handle classes create the journal header and link the lines to the created header: - BisDocumentProdParmReportFinish: In the document, only add a ProdParmReportFinished record. - BisDocumentProjJournal: In the document, only add a ProjJournalTrans record. These handler classes, do not create the journal header automatically: - BisDocumentWMSJournal: In the document, add a WMSJournalTable record with a WMSJournalTrans record as a child record. - BisDocumentProdPickList: In the document, add a ProdJournalTable record, and as desired other records as child records. You can use a customized handler class. To do so, extend a standard handler class. |
  | In the Handler field, enter or select the desired handler class. |
10. | Close the page. |