1. Data Management
  2. Connectivity Studio
  3. Activities

Set up document - Ledger journal
Application task

Use a Ledger journal document to import data into the ledger journals.

Compared to the D365 FO document, the Ledger journal document focuses only on the ledger journals. It has ledger-journal-specific properties and behavior.
Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
  • No records are required for the journal header. Also, no mapping is required in the related message.
  • Only set up records for the journal line tables. All lines in the same import message run are added to the created header. For the records, use tables that are related to the defined journal name. For example, the LedgerJournalTrans table.
The journal name, as defined in the document header properties, defines which ledger journal is applicable. Examples of supported ledger journals are:
  • General journal
  • Invoice journal
On journal creation, the voucher settings of the journal name are considered. If a transaction date is available, the voucher is set.


Standard procedure

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:

  • Application: Use the Application field to define the applicable application.
  • Document type: Use the Document type field to define the applicable document type.
5. In the Project field, enter or select a value.
6. Define the applicable application for the document. For a Ledger 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. In the Document types field, select '0'.
8. Sub-task: Set properties.
  8.1 Expand the Properties section.
  8.2 To improve performance when processing a lot of records, you can use paging. For paging, the records are split over several threads which run these records in parallel batch tasks.
Define the number of records to be processed by one batch task.
  In the Query page size field, enter a number.
 

Note: You can use this calculation to define the number to be entered: Query page size = Total number of records / Number of available threads.
  8.3 On export, if you start the message run manually, you can have the standard D365 FO query page shown before the message is run. You can use this query page to define more-detailed ranges.
  Select Yes in the Prompt field.
 

Note: If the message is run in batch, the standard D365 FO query page is not shown and an error is logged.
  8.4 On import to D365 FO, time validations can be applicable.
By default, the time validation is applied. Which means, this field is set to No. As a result, each import of an instance to which time validation applies, results in a new instance.
If this field is set to Yes, no time validation is applied, and the existing instance is updated.
  Select Yes in the Disable time validation field.
  8.5 You can define the applicable journal name for each company in the ledger journal mapping. However, if no ledger journal mapping exists for a company, the default ledger journal name is applied.
Enter the default ledger journal name that defines the desired journal type for the companies without a ledger journal mapping.
Based on the document type and journal name, the journal header is created.
  In the Default ledger journal field, enter or select a value.
 

Note:

  • You can only select journal names that are related to the ledger journal.
  • If a ledger journal mapping exists for the current company, the applicable ledger journal name is shown in the Ledger journal field.
  8.6 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 a Ledger journal document, the standard handler class is 'BisDocumentLedgerJournal'. This handler class imports ledger-related data into ledger journals. For example: ledger allocations or customer payments. It creates the journal header and links the lines to the created header.
You can use a customized handler class. To do so, extend a standard handler class.
  In the Handler field, enter or select a value.
 

Note: If you use EDI, you can also use this handler class: BisEdiDocumentLedgerJournalChangeCompany. This handler class imports data into the ledger journals. On import, it switches to the company as defined in the EDI history and imports the ledger data into that company.
10. Sub-task: Set up ledger journal mapping.
  10.1 On the Action Pane, click Design.
  10.2 Several companies can exist in your D365 FO environment. Ledger journal names are defined per company and can be different per company.
You can define the applicable ledger journal name for each company in the ledger journal mapping.
  Click Ledger journal mapping.
 

Note: If no ledger journal mapping exists for a company, the default ledger journal name is applied. You can define the default ledger journal name on the document header.
  10.3 Click New.
  10.4 Enter the company for which you want to define the ledger journal name.
  In the Company accounts ID field, enter or select a value.
  10.5 Enter the ledger journal name that defines the desired journal type for the company.
Based on the document type and journal name, the journal header is created.
  In the Ledger journal field, enter or select a value.
 

Note: You can only select journal names that are related to the ledger journal.
  10.6 Close the page.
11. Close the page.

Notes

For vendor invoices, you can import the details as well in the VendInvoiceInfo table. You can add this table to the document records.

Related to Notes

Set up journal document

 		 

See also

Provide feedback