1 of 12

Exporting to INFOR

Creating a BOD Mapping File

Download a BOD Mapping File and open it in your applicable file editor of choice to edit it. For this walkthrough, VSCode is used.

Editing Mapping File

Change the company to the correct one (SFV_AccountingEntityID) and edit location ID if needed.

Check the document code by going to the field settings of the document type you are trying to export (found in URL of field settings of document type in DocBits like below

Lastly, edit the SFV_LogicalID which can be found in INFOR ION DESK → Connect → Connection points and select the DocBits_Export or similar connection point and within that page you will find the Logical ID you need.

Create Logical ID (Connection Point)

If this Connection Point does not yet exist, you need to create one.

First, go to ION Desk → Connect → Connection Points and click on the “+ Add” button”

Then select the “IMS via API Gateway” option

You will be taken to the above screen where you must now fill in the necessary information, the name should be something like “DocBits_export” or similar.

For “ION API Client ID” you enter the same Client ID you obtained earlier for the ION Mapping File.

Then select the Document tab of the Connection Point creation menu and add the following documents by pressing the “+” sign, this will only become useful later.

Once you save this Connection Point you will obtain the Logical ID as shown below

Then insert this Logical ID into the appropriate section of the BOD Mapping File and save the file.

Upload File to DocBits

Drag and drop the file into your export configuration in DocBits. This is available at Settings → Export.

Erstellen einer IDM-Mapping-Datei

Erforderliche Felder für die IDM-Mapping-Datei

Beim Erstellen einer IDM-Mapping-Datei sind die folgenden Felder erforderlich:

Dokumenttypdefinition
- Stellen Sie sicher, dass der Dokumenttypcode in DocBits mit dem Namen übereinstimmt, der in der URL der Feldeinstellungen verwendet wird, ähnlich wie in der BOD-Mapping-Datei.
- Überprüfen Sie, ob der Dokumenttypname in IDM mit Ihrer Systemkonfiguration übereinstimmt. Zum Beispiel kann es in M3 M3_SupplierInvoice sein, während es in LN je nach Ihrer Einrichtung anders sein wird.
  - Eine Anleitung, wie man in IDM navigiert, finden Sie im Dokumentenmanager in IDM auf dieser Seite.

#Define Name of document
#Example: <DocBitsDocumentType>=<IDMDocumentType>
#INVOICE=LN_SupplierInvoice
INVOICE=M3_SupplierInvoice

Statische Werte
- Definieren Sie zunächst alle statischen Werte in einer einzigen Zeile mit dem Schlüssel Static_Values:
  Static_Values=FileNameSeparator,ACLString
- Weisen Sie dann jedem statischen Variablen Werte mit dem Präfix SV_ zu:
  SV_FileNameSeparator=_ SV_ACLString=Public

#Define mappings for the static values
#Example: Static_Values=<StaticVariableName>
Static_Values=FileNameSeparator,ACLString
#Example: SF_<StaticVariableName> = StaticValue
SV_FileNameSeparator=_
SV_ACLString=Public

ACL-Felddefinition

#Define ACL Field value
#Example: ACL_Fields= Concatenation of other defined fields that together should be a valid ACL in IDM
ACL_Fields=SV_ACLString

Suchbarer Name in IDM
- Der Suchbare PDF-Name wird der Dokumentname in IDM sein.

#Define Resource Mapping
#Example: Searchable_PDF_Name= Concatenation of other defined fields
Searchable_PDF_Name=IF_INVOICE_ID

Feldzuordnung

#Define index fields
#Example: Index_Fields=<IndexFieldIdFromIDM>:<type>
Index_Fields=INVOICE_ID:STRING,INVOICE_DATE:STRING,COMPANY:STRING,DIVISION:STRING,DIVISION_NO:STRING,CORRELATION_ID:STRING,SUPPLIER_ID:STRING,SUPPLIER_NAME:STRING
#Example: IF_<DocBitsFieldID> = <IDMAttributeId>
IF_INVOICE_ID=BOD_SupplierInvoiceID
IF_CORRELATION_ID=BOD_AlternateDocumentID_1
IF_INVOICE_DATE=M3_InvoiceDate
IF_COMPANY=M3_Company
IF_DIVISION=M3_Division
IF_DIVISION_NO=BOD_AccountingEntityID
IF_SUPPLIER_ID=BOD_RemitToPartyID
IF_SUPPLIER_NAME=BOD_SupplierPartyID

Beginnen Sie damit, alle verwendeten Indexfelder aufzulisten und die Feld-ID und den Typ anzugeben.

Index_Fields=INVOICE_ID:STRING,INVOICE_DATE:STRING,COMPANY:STRING,DIVISION:STRING,DIVISION_NO:STRING,CORRELATION_ID:STRING,SUPPLIER_ID:STRING,SUPPLIER_NAME:STRING

Jedes zugeordnete Feld folgt dem Format:
```
IF_<DocBitsFieldID> = <IDMAttributeId>
```
- Bestätigen Sie, dass IndexFieldFromDocBits = IDMAttributeID, um sicherzustellen, dass die Feldzuordnung in DocBits mit den Attributen in IDM (Dokumenttyp → Attribute) übereinstimmt. Eine Anleitung, wie man in IDM navigiert, finden Sie im Dokumentenmanager in IDM auf dieser Seite.

XML- und EDI-Dateiexport

Um die originale XML/EDI-Datei zusammen mit der generierten PDF zu exportieren, müssen Sie die IDM-Mapping-Datei in der Exportkonfiguration ändern. Aktualisieren Sie zunächst den Abschnitt Static_Values, indem Sie das Dateipräfix und die Erweiterung hinzufügen. Danach definieren Sie das tatsächliche Mapping, um die korrekte Exportkonfiguration sicherzustellen.

Wenn bereits ein Export für Rechnungen an IDM eingerichtet ist, sollte die generierte PDF bereits im Export enthalten sein. Wenn Sie die XML-Datei nicht benötigen, können Sie den nächsten Teil überspringen. Wenn Sie jedoch die XML-Datei benötigen, folgen Sie den folgenden Schritten.

Aktualisieren der statischen Werte:

Suchen Sie das Feld Static_Values und fügen Sie Folgendes hinzu:

,EDI_FILE_PREFIX,XML_FILE_PREFIX,PDF_FILE_PREFIX,PDF_FILE_EXTENSION,EDI_FILE_EXTENSION,XML_FILE_EXTENSION

Fügen Sie dann die folgenden Einträge unter SV_ACLString hinzu:

SV_EDI_FILE_PREFIX=EDI_810_
SV_XML_FILE_PREFIX=XML_810_
SV_PDF_FILE_PREFIX=INV_EDI_
SV_PDF_FILE_EXTENSION=.pdf
SV_EDI_FILE_EXTENSION=.xml
SV_XML_FILE_EXTENSION=.xml

Fügen Sie danach das tatsächliche Mapping hinzu und stellen Sie sicher, dass der Export-Dokumenttyp dem IDM-Dokumenttype entspricht.

XML-Mapping

Fügen Sie das folgende Mapping am Ende der Datei hinzu:

EMBEDDED_FILES_EXPORT = TRANSFORMED, XML
EFE_TRANSFORMED_SOURCE_NAME = Transformed.xml
EFE_TRANSFORMED_EXPORT_DOC_TYPE = M3_SupplierInvoice
EFE_TRANSFORMED_EXPORT_FILENAME = SV_XML_FILE_PREFIX+IF_INVOICE_ID+SV_XML_FILE_EXTENSION

EFE_XML_SOURCE_NAME = XML_DOCUMENT.xml
EFE_XML_EXPORT_DOC_TYPE = M3_SupplierInvoice
EFE_XML_EXPORT_FILENAME = SV_XML_FILE_PREFIX+IF_INVOICE_ID+SV_XML_FILE_EXTENSION

Hinweis: Stellen Sie sicher, dass export_doc_type auf den IDM-Rechnungstyp eingestellt ist. In diesem Beispiel ist es auf M3 eingestellt.

EDI-Mapping

Fügen Sie das folgende Mapping am Ende der Datei hinzu:

EMBEDDED_FILES_EXPORT = TRANSFORMED, EDI
EFE_TRANSFORMED_SOURCE_NAME = Transformed.xml
EFE_TRANSFORMED_EXPORT_DOC_TYPE = M3_SupplierInvoice
EFE_TRANSFORMED_EXPORT_FILENAME = SV_XML_FILE_PREFIX+IF_INVOICE_NUMBER+SV_XML_FILE_EXTENSION

EFE_EDI_SOURCE_NAME = EDI.edi
EFE_EDI_EXPORT_DOC_TYPE = M3_SupplierInvoice
EFE_EDI_EXPORT_FILENAME = SV_EDI_FILE_PREFIX+IF_INVOICE_NUMBER+SV_EDI_FILE_EXTENSION

Hinweis: Stellen Sie sicher, dass export_doc_type auf den IDM-Rechnungstyp eingestellt ist. In diesem Beispiel ist es auf M3 eingestellt.

Dokumentenmanager in Infor

Gehen Sie zum Dokumentenmanager und wählen Sie den Namen des aktuellen Dokumenttyps aus, den Sie exportieren möchten, z. B. Lieferantenrechnung.

Klicken Sie auf das obige Symbol und dann auf Verwaltung → Dokumenttyp und suchen Sie den Dokumenttyp, den Sie in der Liste benötigen.

Wie unten gezeigt, sehen Sie dann den Dokumenttypnamen, wie er in INFOR ist.

Stellen Sie sicher, dass dies so im IDM-Mapping-Datei angezeigt wird.

Datei in DocBits hochladen

Sobald die Datei vorbereitet ist, laden Sie sie in Ihre Exportkonfiguration in DocBits hoch. Dies ist unter Einstellungen → Export verfügbar.

Creating an ION API Endpoint

Infor Configuration

Once at the home screen, click on the burger menu and select ION API

After opening ION API, click on Available APIs in the left menu

Click on “+ADD” block

Then “+ Create New”

The information you insert should look like this

FYI: The description has multiple environments as this will be used for multiple environments and the icon and its color always remain the same.

Next, select the + at the bottom of the screen

This Target Endpoint URL can be found at doc2api.cloudintegration.eu

The information underneath this field should look as follows.

Once you have filled in this information, to the right of these fields there is a “Target Endpoint Security” field with a drop down. Select API Key from this drop down.

A table will then appear underneath this drop down, fill in the following information. The key value is specific to the customer and environment, it can be found within DocBits.

From the Dashboard → Settings → Integration → API Key

Copy and paste this into the Key Value field in InforOS

Once this is complete, press the following icon to save the configuration

You are not yet completely done with the configuration.

Go back into the API you just configured and enter the details like below

Go to the Documentation tab at the bottom and click on the +

Enter the following details:

Name = DocBits-”environment”
Type = Swagger
URL = go to doc2api.cloudintegration.eu, once on this page, open the following link

Copy the URL and use it for the URL field in InforOS

Save it once you have entered the information for all the fields. There should be a loading icon for a while but the end result should look like this

The same process would be used to create the endpoints for other environments.

FYI: If in the future you are struggling to find these endpoints, in ION API go to API Metadata and click on this icon to refresh the API metadata.

DocBits Export Settings

From the DocBits Dashboard of the required customer, go to Settings → Export, to add a new document type for export, do as follows:

Click on the “+ New” button

Select “Infor IDM + ION BOD”

You will then be taken to this menu where you need to give the new exportable document type a Title, select the document type from the dropdown and add all the necessary Mapping Files (ION, IDM and BOD).

Creating an ION API File

Obtaining existing/Creating new ION API File

This is created in INFOR ION API → Authorized Apps and an app like below should be shown

If not, then you need to create a new Authorized App. This can be done clicking the plus sign

Once you have entered the Name (DocBits_*Environment*) and Type (case specific) of the new Authorized App, you will be taken to a page where the Client ID and Secret have been generated automatically.

The information you fill in should be similar to what is shown above, it is important to enable the “Issue Refresh Tokens” slider at the bottom of the page.

Click “Download Credentials” to download the ION Mapping File.

Uploading the file to DocBits

Once you have downloaded the ION API file from Infor, you can upload it by going to Settings → Document Processing → Export like below

Export to M3 Mapping (API)

Sections

M3 export mapping file is divided in 5 sections and each section is further divided into 2 sections

Header
- Header Static Fields
- Header Fields
Tax Lines
- Tax Line Static Fields
- Tax Line Fields
Receipt Lines
- Receipt Line Static Fields
- Receipt Line Fields
Order Charge Lines (Additional Amounts)
- Order Charge Static Fields
- Order Charge Fields
Cost Lines
- Cost Line Static Fields
- Cost Line Fields

Adding and Removing Fields

Adding New Field:

First we need to add the M3 api field name to the relevant section’s fields list property (e.g. StaticFields, HeaderFields, InvoiceTaxFields)
Define the static value or document field name for the api field with appropriate prefix for the section
- Example 1: To define a static value of AAA for the M3 api field DIVI. First we added DIVI to StaticFields property. Then we add a line SF_DIVI = AAA as SF_ is the prefix for static fields
- Example2: To map header field IVDT (invoice data) to invoice_date field of DocBits. First we add IVDT to HeaderFields property. Then we add a line HF_IVDT = invoice_date as HF_ is the prefix for header fields

Removing Field:

Just remove the field from section’s field list property and remove the line defining value for the field.

Available M3 Api Fields:

Available M3 fields can be checked by opening appropriate screen in M3.

Similarly you can get field names for lines

Header:

Fields List Property: StaticFields

Section Fields Prefix: SF_

Available Fields: You can map any M3 api field with any static value

Header Fields

Fields List Property: HeaderFields

Section Fields Prefix: HF_

Available Fields: You can map any DocBits field to any M3 api field