1 of 52

Setup

Document Types

If a customer requires a new document type or additional fields to be added to an existing document type layout, this section will go through all the information required to do so.

In DocBits you will find the SETTINGS menu in the upper bar on the DASHBOARD.

If you are logged in to DocBits as an admin, you will find all fields of a document that can be extracted under the respective document type.

Open the menu for Document Types.

In the following overview you will find all standard document types available for you

Activate/Extraction Type

To the right of each document type, you will see Activate and Extraction Type sliders.

Activate: This document type is active in your DocBits environment.

Extraction Type: This slider allows you to enable or disable a set of predefined rules for the document type when it is processed by DocBits. By selecting the gear icon to the right of the slider, the following menu will appear.

To see which fields can be extracted, for example from an invoice, click on FIELDS for this document type.

Field Settings

Here you will find all the fields that can be extracted

You can also CREATE FIELDS like freight, postage or any field with an amount you want to extract from your invoices.

For each field you can check the boxes if they are:

REQUIRED: Here you can define if the field must contain a value to continue.
READ ONLY: Here you can define if a field can only be displayed but not edited.
HIDDEN: Here you can define whether a field should be hidden or displayed in the extraction view.
FORCE VALIDATION: Here you can define whether a field must always be validated manually, even if it has been read 100% by DocBits.
OCR and MATCH SCORE: Setting as described below, per field.
FORMULA: Creation of a formula per field.

If all settings are made and should be saved, please confirm this with the SAVE SETTINGS button at the bottom of the page, otherwise the settings will not be applied.

Recognition Settings

OCR

Here you can set the sensitivity of the OCR (Optical Character Recognition) function for all fields at once. This value determines the sensitivity with which a field is marked in red if it could not be extracted with 100% certainty (OCR related!).

Match Score

This is where you can set the sensitivity of the MATCH SCORE function for all fields at once. This value determines when a field is marked in red if DocBits has not extracted the field with 100% probability. In this case the field needs to be validated manually.

The button RESTORE DEFAULTS will set back both values to “50”.

Profile

Here you can define the profile that shall be used. Either Default or ZUGFeRD. In profile ZUGFeRD there are predefined fields that are mandatory for this type of invoice. If you do not explicitly use ZUGFeRD, please select “Default”.

EDI Data Transformation Process

Step 1: Structure Descriptor

Format: JSON
Purpose: This step involves defining the structure of the EDI data. It includes specifying segments such as SAC, N1, and PO1, and details the fields contained within each segment. For segments that contain nested structures, loops are defined to properly organize the data hierarchy.

{
  "SAC": {"fields": ["SAC", "DTM", "TX1", "TD5"]},
  "N1": {"fields": ["N1", "N2", "N3", "N4", "PER"]},
  "PO1": {
    "fields": ["PO1", "REF"],
    "loops": {
      "SAC": {"fields": ["SAC", "TX1", "DTM"]}
    }
  }
}

Step 2: Transformation Using XSLT

Format: XSLT
Purpose: This step involves transforming the structured JSON data into a structured XML format, specifically tailoring the output to meet the requirements for further processing or integration. This transformation helps in extracting precise information like acknowledgement types, order details, and conditional elements based on specific values.

<xsl:stylesheet version="1.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml" />
    <xsl:template match="/">
        <ORDER_CONFIRMATION>
            <ACKNOWLEDGEMENT_TYPE>
                <xsl:value-of select="//BAK/VALUE_2/text()" />
            </ACKNOWLEDGEMENT_TYPE>
            <ACKNOWLEDGEMENT_TYPE_DESCRIPTION>
                <xsl:choose>
                    <xsl:when test="//BAK/VALUE_2='AD'">With detail, no change</xsl:when>
                    <xsl:when test="//BAK/VALUE_2='AC'">With detail and change</xsl:when>
                    <xsl:otherwise>Unknown</xsl:otherwise>
                </xsl:choose>
            </ACKNOWLEDGEMENT_TYPE_DESCRIPTION>
            <!-- Additional fields and conditions are similarly transformed -->
        </ORDER_CONFIRMATION>
    </xsl:template>
</xsl:stylesheet>

Step 3: Preview (HTML Conversion)

Format: XSLT (outputting HTML)
Purpose: Converts the XML data from Step 2 into an HTML format for previewing the transformed data in a readable and visually appealing format. The HTML layout includes styles for presentation and structures data like purchase orders, supplier details, and order terms for easy viewing.

<xsl:stylesheet version="1.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="html" />
    <xsl:template match="/">
        <html lang="en">
            <head>
                <meta charset="UTF-8" />
                <meta name="viewport" content="width=device-width, initial-scale=1.0" />
                <title>Preview of Transformed EDI Data</title>
                <!-- Styles and head elements -->
            </head>
            <body>
                <div>
                    <!-- HTML structure mimicking an invoice or other document type, with data bindings from the transformed XML -->
                </div>
            </body>
        </html>
    </xsl:template>
</xsl:stylesheet>

Step 4: Extraction Paths

Format: JSON
Purpose: Specifies JSON paths for extracting key values from the XML data produced in Step 2. These paths are used to retrieve specific data points such as purchase orders and currency, which are crucial for downstream processing and integration into other systems.

{
  "fields": {
    "purchase_order": "//ORDER_CONFIRMATION/PURCHASE_ORDER/text()",
    "currency": "//ORDER_CONFIRMATION/CURRENCY/text()",
    ...
  },
  "tables": [
    {
      "name": "ORDER_CONFIRMATION_TABLE",
      "row_path": "//ORDER_CONFIRMATION/ORDER_LINES/ORDER_LINE",
      "columns": [
        {"name": "POSITION", "path": "POSITION/text()"},
        ...
      ]
    }
  ]
}

This updated sequence ensures a thorough process, transforming raw EDI data into structured, actionable information using JSON for data structuring, XSLT for transformation and HTML preview, followed by JSON paths for data extraction and integration.

Costruttore di Layout

Accesso al Layout Builder

Prima di tutto, assicurati che la funzione Layout Builder sia attivata. Questo può essere fatto navigando su Impostazioni → Elaborazione Documenti → Modulo → Tipo di Documento e assicurati che il cursore Layout Builder sia impostato su attivo come mostrato di seguito.

Dopo aver completato questa operazione, puoi accedere al Layout Builder tramite Impostazioni → Tipi di Documento. Una volta su questa pagina, puoi selezionare tra i vari tipi di documento che hai creato e selezionare "Modifica Layout" come mostrato di seguito

o se hai tipi di sottodocumento all'interno di un tipo di documento creato, puoi selezionare “Tipi di Sottodocumento” e selezionare “Modifica Layout” per il layout del sottodocumento che desideri modificare come mostrato di seguito.

Fondamenti del Layout Manager

Dopo aver seguito i passaggi precedenti, raggiungerai una pagina simile a quella mostrata di seguito.

Caricamento di un documento di esempio

Per caricare un documento nel layout builder, basta navigare a destra sullo schermo

Clicca sul pulsante “Carica Documenti” o trascina e rilascia il documento desiderato nell'area fornita

Gruppi

I gruppi possono essere creati selezionando l'icona seguente.

I gruppi ti permettono di creare diverse sezioni in un layout, rendendo più facile separare diversi gruppi di dati o informazioni per rendere un layout più facile da seguire. Puoi creare un titolo per ogni gruppo in modo che un utente possa sapere quali informazioni troverà in quel gruppo.

Elementi del Modulo

Questi sono un insieme di campi predefiniti che possono essere trascinati e rilasciati nel costruttore di layout e sono disponibili per te per creare il layout desiderato. Questi includono:

Testo – Questa è una casella di testo che crea un campo nel layout in cui è possibile inserire del testo una volta nella schermata di convalida.
Etichetta – Questo è un campo che può essere utilizzato per creare testo non modificabile, questo potrebbe essere utilizzato per creare sottotitoli o qualsiasi altro testo non modificabile desiderato quando si è nella schermata di convalida.
Checkbox – Questo crea un campo di tipo booleano che può essere selezionato o deselezionato.
Multi Checkbox – Questo funziona allo stesso modo della “Checkbox” ma può essere utilizzato quando l'utente sa che aggiungerà più caselle di controllo in una sezione.
Separatore Orizzontale – Questo crea una linea orizzontale nel layout che può essere utilizzata per separare le sezioni all'interno di un gruppo nel layout.
Tabella di Checkbox – Questo consente all'utente di creare una tabella di caselle di controllo composta da valori personalizzati degli assi x e y, ad esempio.

Pulsante – Questo crea un pulsante cliccabile nella schermata di convalida all'interno del layout che può essere impostato su una delle tre funzioni, tra cui: Esporta, Esporta con richiesta speciale o Rifiuta.
Tabelle Estratte - Questo ti consente di posizionare un'area nel layout del documento che illustra la tabella che viene estratta dal documento. Per informazioni clicca qui.
Pulsanti Fattura – Questo elemento ti consente di trascinare e rilasciare un insieme di pulsanti ottimizzati per le fatture. Quando sei nella schermata di convalida, selezionando il tipo di fattura (costo o acquisto) il PO Matching o la Contabilità Automatica scompariranno di conseguenza.

Campi del Codice QR – Questo elemento consente di trascinare e rilasciare un blocco che visualizzerà tutte le informazioni estratte da un documento quando è presente un codice QR.

Creazione di campi specifici per il documento

L'utente è in grado di creare i propri gruppi e campi personalizzati per un tipo di documento; questo può essere fatto sia durante la creazione originale di un tipo di documento, sia selezionando “Campi” nella pagina Tipi di Documento nelle Impostazioni.

Spazi vuoti

La regola del 100 percento

Per creare lo spazio sopra nel layout, è necessario utilizzare un "Label" dagli Elementi del Modulo in un modo speciale. Il motivo di ciò è che il Layout Manager opera secondo un sistema di 100 spazi per riga, in cui 1 spazio rappresenta 1 percento di una riga; questo significa che i campi possono occupare solo 100 spazi per riga come mostrato di seguito.

Questo significa che l'utente deve costruire il layout riga per riga secondo questa regola. Ad esempio, supponiamo che tu voglia aggiungere i campi “Nome” e “Data” nella stessa riga, ma desideri che il campo “Nome” sia più grande. Questo può essere fatto trascinando e rilasciando il campo “Testo” dal menu a discesa Elementi del Campo e denominando ciascun campo “Nome” e “Data” come mostrato.

Il problema ora esiste perché entrambi hanno la stessa dimensione di 33 (questa è la dimensione predefinita di tutti i campi trascinati e rilasciati), ma si desidera che il campo “Nome” sia più grande del campo “Data” e che entrambi i campi occupino l'intera riga nel layout. Pertanto, seguendo la regola del 100 percento, è possibile impostare i campi “Nome” e “Data” su qualsiasi combinazione di 100 che si desideri. Questo, ovviamente, dipende da quanto grande si desidera ciascun campo individuale, ma ai fini di questo esempio imposteremo il campo “Nome” su 70 e il campo “Data” su 30, i risultati sono:

Questa stessa regola si applica a tutti i campi nel Layout Builder.

Creare Spazi Vuoti

Ora che questa regola è stata spiegata, creare spazi vuoti avrà più senso. Come accennato in precedenza, per creare uno spazio vuoto devi utilizzare un “Label” dagli Elementi del Modulo.

Ad esempio, supponiamo che tu voglia creare uno spazio vuoto tra questi due campi.

Il primo passo è trascinare e rilasciare un “Label” tra questi due campi; una volta aggiunto, puoi fare clic sul campo “Label” che hai appena aggiunto e a sinistra ti verranno presentate le proprietà del campo. Ora, nello stesso modo in cui creeresti o cambieresti il nome di un campo come mostrato in precedenza, rimuoverai qualsiasi nome dalla proprietà “Label” in questo modo

Il risultato di questo sarà quindi

Ora c'è uno spazio tra i due campi. Questo spazio può essere esteso o accorciato secondo la regola del 100 percento discussa in precedenza, e con queste funzioni puoi creare qualsiasi layout desiderato.

Origin Layouts

DocBits excels in adapting document layouts according to their geographical origins while standardizing elements like currency formats based on user browser settings. Let’s explore how you can leverage the Layout Builder to customize layouts for different origins, such as the U.S. and Germany.

Understanding Origin-Based Customization

Currency and Format Standardization: Regardless of the original document’s currency or format, DocBits converts these elements into a standardized ISO format on the server, in line with the user’s browser settings.
Geographical Layout Customization: The system allows customization of document layouts based on their geographical origin. This means you can define specific fields and formats for documents from different countries.

Example: U.S. vs. Germany Layouts

U.S. Layout: For a U.S. invoice, you might include fields for city tax, aligning with the common tax structure in the U.S.
Germany Layout: In contrast, a German invoice layout may omit the city tax field, as it’s not a standard charge in Germany.

Using the Layout Builder

Select Origin Layout: In the Layout Builder, choose the base layout corresponding to the document’s origin.
Customize Fields: Adapt the layout by adding or removing fields. For instance, include ‘City Tax’ for a U.S. layout.
Apply and Test: Once customized, apply the layout to your documents and test to ensure accuracy.

Tips for Effective Customization

Understand Regional Differences: Familiarize yourself with the tax and format nuances of different regions.
Consistent Updates: Regularly update your layouts to reflect any changes in regional regulations.
User Feedback: Utilize feedback from users in different regions to refine layouts further.

Regex Manager

This feature by DocBits gives you an alternative to model classification as it allows you to write searchable regular expressions for a document type for classification and other purposes.

Document Type: The Regex Manager allows you to write regular expressions and this regex will then be searched for in the document, if it finds a match to the regex of a defined document, it then classifies that document to the corresponding document type. For example, if you wrote a regular expression to find “Gutschrift”. If DocBits found this term in a document it would classify that document as a credit note.

Document Origin: This lets DocBits know the country of origin of a document through regular expressions. For example, if a regular expression for a Spanish document contains the term “Factura”. If DocBits searches a document and finds this term then it would know that the document is of Spanish origin and classify it as such.

Accessing the Regex Manager

To find this feature in DocBits, from your Dashboard, navigate to Settings → Global Settings → Document Types. Within each of the created document types, there is a “Regex” option.

Adding and Removing Regex

By clicking on “Regex” you will be taken to this menu, which displays the existing regex models that have been created as well as an “ADD” button for you to create new regex models.

Importing Master Data

Field Mappings

Below you will find the necessary field mappings for importing master data, from Infor, into DocBits.

Auto Accounting (LN)

ChartOfAccounts

{
    "ID": "//DataArea/ChartOfAccounts/IDs/ID",
    "NominalAccount": "//DataArea/ChartOfAccounts/BaseChartOfAccounts/GLNominalAccount",
    "AccountType": "//DataArea/ChartOfAccounts/BaseChartOfAccounts/AccountType",
    "Description": "//DataArea/ChartOfAccounts/BaseChartOfAccounts/Description",
    "DebitCreditFlag": "//DataArea/ChartOfAccounts/DebitCreditFlag",
    "UnitCode": "//DataArea/ChartOfAccounts/MemoUnit/UnitCode",
    "ClassificationCode1": "//DataArea/ChartOfAccounts/Classification/Codes/Code[@sequence='1']",
    "ClassificationCode2": "//DataArea/ChartOfAccounts/Classification/Codes/Code[@sequence='2']",
    "ClassificationCode3": "//DataArea/ChartOfAccounts/Classification/Codes/Code[@sequence='3']",
    "ClassificationCode4": "//DataArea/ChartOfAccounts/Classification/Codes/Code[@sequence='4']",
    "FlexDimensions": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/ID"
}

TotalFlexDimensions

{
    "ID": "//DataArea/CodeDefinition/DisplayID",
    "Description": "//DataArea/CodeDefinition/Description",
    "DimensionID": "//DataArea/CodeDefinition/ReportingSlot",
    "Name": "//DataArea/CodeDefinition/Name"
}

FinalFlexDimensions

{
    "ID": "//DataArea/CodeDefinition/ReportingSlot",
    "Name": "//DataArea/CodeDefinition/ListID"
}

Auto Accounting (M3)

ChartOfAccounts

{
    "ID": "//DataArea/ChartOfAccounts/IDs/ID",
    "NominalAccount": "//DataArea/ChartOfAccounts/BaseChartOfAccounts/GLNominalAccount",
    "AccountType": "//DataArea/ChartOfAccounts/BaseChartOfAccounts/AccountType",
    "Description": "//DataArea/ChartOfAccounts/BaseChartOfAccounts/Description",
    "DimensionProfile": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/ID",
    "Dimension1": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[0]/ListID",
    "Usage1": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[0]/Usage",
    "Dimension2": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[1]/ListID",
    "Usage2": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[1]/Usage",
    "Dimension3": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[2]/ListID",
    "Usage3": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[2]/Usage",
    "Dimension4": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[3]/ListID",
    "Usage4": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[3]/Usage",
    "Dimension5": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[4]/ListID",
    "Usage5": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[4]/Usage",
    "Dimension6": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[5]/ListID",
    "Usage6": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[5]/Usage",
    "Dimension7": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[6]/ListID",
    "Usage7": "//DataArea/ChartOfAccounts/DimensionProfileSet/DimensionProfile/DimensionUsage[6]/Usage"
}

FlexDimensions (CodeDefinition)

{
    "ID": "//DataArea/CodeDefinition/DocumentID/ID",
    "Dimension": "substring(//DataArea/CodeDefinition/CodeValue/@listID,21)",
    "ListID": "//DataArea/CodeDefinition/ListID",
    "CodeValue": "//DataArea/CodeDefinition/CodeValue",
    "Description": "//DataArea/CodeDefinition/Description"
}

Tax Code

Full

{
    "ID": "//DataArea/LnTaxCode/DocumentID/ID",
    "TaxCodeIDFull": "//DataArea/LnTaxCode/TaxCode",
    "CountryCode": "//DataArea/LnTaxCode/CountryCode",
    "TaxCodeFull": "//DataArea/LnTaxCode/DisplayID",
    "Description": "//DataArea/LnTaxCode/Description",
    "TaxType": "//DataArea/LnTaxCode/TaxTypeCode",
    "TaxRateFull": "number(concat('0',//DataArea/LnTaxCode/SingularRatesGroup/SingularRate[1]/RateNumeric))*100"
}

Reduced

{
    "ID": "//DataArea/LnTaxCode/DocumentID/ID",
    "TaxCodeIDReduced": "//DataArea/LnTaxCode/TaxCode",
    "CountryCode": "//DataArea/LnTaxCode/CountryCode",
    "TaxCodeReduced": "//DataArea/LnTaxCode/DisplayID",
    "Description": "//DataArea/LnTaxCode/Description",
    "TaxType": "//DataArea/LnTaxCode/TaxTypeCode",
    "TaxRateReduced": "number(concat('0',//DataArea/LnTaxCode/SingularRatesGroup/SingularRate[1]/RateNumeric))*100"
}

Free

{
    "ID": "//DataArea/LnTaxCode/DocumentID/ID",
    "TaxCodeIDFree": "//DataArea/LnTaxCode/TaxCode",
    "CountryCode": "//DataArea/LnTaxCode/CountryCode",
    "TaxCodeFree": "//DataArea/LnTaxCode/DisplayID",
    "Description": "//DataArea/LnTaxCode/Description",
    "TaxType": "//DataArea/LnTaxCode/TaxTypeCode",
    "TaxRateFree": "number(concat('0',//DataArea/LnTaxCode/SingularRatesGroup/SingularRate[2]/RateNumeric))*100"
}

LN

A guide to importing master data from INFOR LN.

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 at https://docbits.com/doc/field-mappings/.

Once you have completed the above steps, you will have successfully configured 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 at https://docbits.com/doc/field-mappings/.

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:

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 at https://docbits.com/doc/field-mappings/.

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.

Document

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 (M3)

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 is done you should see the three separate master data tables in your DocBits environment(s) under Master Data Lookup:

chartofaccounts
totalflexdimensions
finalflexdimensions

Suppliers and Purchase Orders

Connection Point

You will need to create the DocBits API connection point in order to create the data flow later.

First, in InforOS, navigate to ION Desk → Connect → Connection Points

Once here, you will need to create a new connection point.

Select API

Give the connection point a name and description that describes its nature and its environment. Under the Connection tab, import the service account you created for the environment you are working with.

Next, switch to the Documents tab. You will need to add the following BODs to the connection point.

Ack-SupplierInvoice

This BOD is used to signal on DocBits that an error has occurred within Infor. The configuration for these two BODs should look similar to the following (API Call Name changing for each)

Sync.PurchaseOrder

The configuration for this BOD should look similar to the following

Sync.ReceiveDelivery

The configuration for this BOD should look similar to the following

Once these BODs are configured, you can save the connection point by pressing the icon located right to the back button.

Data Flow

The data flow will look similar to the following

(The reason for multiple DocBits APIs is due to each connection representing a different environment meaning, depending on the amount of environments you have, your data flow could differ slightly)

For the purpose of this explanation we will use the example of having four separate environments.

LN

The start of the data flow consists of your LN application

DocBits API

Here you will add an application and select the DocBits API(s) you created earlier

Files

The configuration should look as follows

LN 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 Suppliers and Purchase Orders to arrive in DocBits.

PurchaseOrder

From the above menu, in the left menu tab, select Common → BOD-Messaging → Publish BODs → Publish Order Management Transactional Data

Select the PurchaseOrder tab and check the box.

Suppliers

From the LN homepage, in the left menu tab, navigate to Common → BOD-Messaging → Publish BODs → Publish Logistics Master Data

Select the PartyMaster tab and check the Supplier → Buy-from or SupplierPartyMaster box.

BOD Triggering

Once all the correct BODs have been checked for publication, select the Options tab.

The following options should be selected.

Once this is complete, press the PROCESS button and the BODs will be triggered. A message will appear on screen to notify you that the BODs have been triggered.

If done successfully, the Supplier and Purchase Order tables should now be available under Settings → Master Data Lookup.

Tax Codes

Create DocBits Connection Point(s)

Open ION Desk → Connect → Connection Points

You will need 4 connection points for this dataflow, 3 API connection points for the different tax code categories (full, reduced and free) and an Application connection point representing your LN company.

In order to create new connection points, select the “+ADD” button”

Select “API” at the bottom of the list of options

You will be taken to the following page

This is where you will enter all the details of the TaxCode connection point. For each of the three connection points you will be creating do the following

Enter a Name: TaxCodeFull, TaxCodeReduced, TaxCodeFree
Description: This can be the same as the Name or similar
Import a service account you created.

Switch to the “Documents” tab and select the PLUS icon to add the BOD we need, like below

Search for the BOD

Search for the BOD called “Sync.LnTaxCode”, click on it and press “OK” to add the BOD.

Move on to the ION API section. Under API Call Name you can use the name of the BOD, Sync.LnTaxCode

Press the “SELECT” button

Select the API you configured for the environment you are working with and search for the following API. Once you have selected it, press “OK”.

Next, switch to the Request Body tab.

Here is where there will be a slight change for each connection point, this is seen in the field mappings you will assign to each tax code as they differ slightly.

In the field_mappings row, under value, is where you will put the specific field mappings for the specific tax code connection point you are creating (full, reduced or free). These mappings are available at https://docbits.com/doc/field-mappings/.

The end result should look the same or similar to the image above. Once this is done, click the SAVE option located here.

Data Flow Configuration

Navigate to ION Desk → Connect → Data Flows

Click on “+ADD” and select document flow

Create the following data flow by dragging and dropping the components from the to menu

Application (LN)

Here is where you will select your LN company, the final result should look similar to the following