Auto Accounting

Prerequisites

  • Functioning LN to DocBits dataflow
  • Correctly configured DocBits environment

Infor Configuration

ION Desk

In Infor, open the ION Desk application. In the left tab, go to Connect → Connection Points

 

This is where you will create the two connection points needed to import your data from LN that is required for Auto Accounting.

Click on “+ADD” to create a new connection point, select the API option like below

You will need to configure two separate API connection points, namely:

  • ChartOfAccounts
  • FinalFlexDimensions

ChartOfAccounts

The connection tab for your ChartOfAccounts connection point should look similar to what is illustrated below. Give the connection point an appropriate name and description, as well as import the Service Account you created.

You will need to add two BODs in this section for this connection point. These being Sync.ChartOfAccounts and Sync.CodeDefinition, to add these BODs do the following:

Sync.ChartOfAccounts

  • Click on the PLUS (+) icon
  • Select “Send to API”
  • Search for the Sync.ChartOfAccounts BOD
  • Switch to the ION API tab, copy the API name and search for the API Call by pressing the SELECT button
  • At product, select the API Endpoint that you created for the environment you are working with, which you created in ION API. Search for the following API call, select the API call and press OK.
  • Next, switch the Request Body tab
  • Here is where you will configure the field mapping for this BOD, your configuration should look like the following. The field mappings are available here.

Once you have completed the above steps, you will have succesfully congifured the Sync.ChartOfAccounts BOD. Click on the PLUS icon to add the next  and final BOD.

Sync.CodeDefinition (TotalFlexDimensions)

The connection tab for your CodeDefinition connection point should look similar to what is illustrated below. Give the connection point an appropriate name and description, as well as import the Service Account you created.

  • Select “Send to API”
  • Search for the Sync.CodeDefinition BOD
  • Switch to the ION API tab, copy the API name and search for the API Call by pressing the SELECT button
  • Next, switch the Request Body tab
  • Here is where you will configure the field mapping for this BOD, your configuration should look like the following. The field mappings are available here.

Once you have completed the above steps, you will have successfully configured the Sync.CodeDefinition BOD for the TotalFlexDimensions master data table.

FinalFlexDimensions

The connection tab for your FinalFlexDimensions connection point should look similar to what is illustrated below. Give the connection point an appropriate name and description, as well as import the Service Account you created.

You will need to add one BOD in this section for this connection point. This being the Sync.CodeDefinition, to add this BOD do the following:

The connection tab for your CodeDefinition connection point should look similar to what is illustrated below. Give the connection point an appropriate name and description, as well as import the Service Account you created.

  • Select “Send to API”
  • Search for the Sync.CodeDefinition BOD
  • Switch to the ION API tab, copy the API name and search for the API Call by pressing the SELECT button
  • Next, switch the Request Body tab
  • Here is where you will configure the field mapping for this BOD, your configuration should look like the following. The field mappings are available here.

Once you have completed the above steps, you will have successfully configured the Sync.CodeDefinition BOD for the FinalFlexDimensions master data table.

Data Flows

You will need to configure two separate data flows for Auto Accounting:

  • ChartOfAccounts
  • FinalFlexDimensions

ChartOfAccounts

An overview of this data flow looks as shown below (the amount of DocBits API connection points at the end depends on the amount of different environments you are configuring).

LN Company

The configuration for this connection point depends on the LN company which contains the master data you wish to import into DocBits, yours should look similar to what is shown below.

Documents

The following documents need to be added to the data flow:

  • Sync.ChartOfAccounts
  • Sync.CodeDefinition

DocBits (ChartOfAccounts)

This is where you add the ChartOfAccounts API connection point which you created earlier, the configuration for this should look similar to this

FinalFlexDimensions

An overview of this data flow looks as shown below (the amount of DocBits API connection points at the end depends on the amount of different environments you are configuring).

LN Company

The configuration for this connection point depends on the LN company which contains the master data you wish to import into DocBits, yours should look similar to what is shown below.

Document

The following document needs to be added to the data flow:

  • Sync.CodeDefinition

DocBits (FlexDimensions)

This is where you add the FinalFlexDimensions API connection point which you created earlier, the configuration for this should look similar to this

BOD Triggering

Once all the above is completed, you will need to navigate to Infor LN and trigger the BODs in order for the various master data you need for Auto Accounting to arrive in DocBits.

From the above menu, in the left menu tab, select Common → BOD-Messaging → Publish BODs → Publish Financial Master Data. From the following menu you will find the FlexDimensions and ChartOfAccounts BODs to publish.

Select the following BODs to publish by simply checking each box, no other changes need to be made as we want to publish all of these BODs so that the master data is complete in DocBits.

Once both of the above BODs are selected, navigate to the Options tab

Once on the Option menu, select the following options and select PROCESS to publish the BODs.

Once this si done you should see the three seaparate master data tables in your DocBits environment(s):

  • chartofaccounts
  • totalflexdimensions
  • finalflexdimensions

 

This is located under Master Data Validation

Table of Contents