M3
Example Export M3
General Overview
The export to Infor M3 involves transferring invoice-related data from Docbits into Infor M3 in a structured manner. The data is organized into headers, tax lines, receipt lines, and cost lines. Each section includes static fields that remain constant across transactions and dynamic fields that vary based on the invoice or transaction details.
Field Mappings
Header Fields
HF_SUNO
supplier_id
Supplier identifier
HF_IVDT
invoice_date
Invoice date
HF_SINO
invoice_id
Invoice identifier
HF_SPYN
supplier_id
Supplier identifier
HF_CUCD
currency
Currency used in the invoice
HF_CUAM
total_amount
Total amount
HF_VTAM
total_tax_amount
Total tax amount
HF_ACDT
accounting_date
Accounting Date
HF_SERS
invoice_sub_type
Invoice sub type
HF_FTCO
supplier_country_code
Supplier country code
HF_PUNO
purchase_order
Purchase order
HF_TXAP
tax_country_1
Tax country
HF_CORI
correlation_id
Correlation identifier
HF_PAIN
sqr_field_esr_reference
Field Reference
HF_TCHG
additional_amount
Additional amount
HF_CDC1
negative_amount
Negative amount
HF_APCD
authorised_user
Authorised user
HF_TEPY
payment_terms
Payment terms
HF_PYME
payment_method
Payment method
HF_BKID
bank_id
Bank identifier
HF_GEOC
geo_code
Geo code
HF_TECD
discount_term
Discount term
HF_TXAP
tax_applicable
Tax applicable
HF_TXIN
tax_included
Tax included
Tax Line Fields
ITF_VTCD
TF_tax_code
Tax code
ITF_VTA1
TF_tax_amount
Tax amount
ITF_VTP1
TF_tax_rate
Tax rate
ITF_CLAM
TF_gross_amount
Gross amount
ITF_DIVI
company_id
Company identifier
ITF_TTXA
TF_amount
Amount
ITF_TAXC
TF_tax_code
Tax code
ITF_GEOC
TF_geo_code
Geo code
Order Header Extra Charges Fields
OrderExtraChargeFields
NLAM
NLAM
OECF_NLAM
TF_amount
Amount
Receipt Line Fields
IRF_IVQA
TF_quantity
Invoiced quantity
IRF_PUUN
TF_unit
Unit number
IRF_PUNO
TF_purchase_order
Purchase order number
IRF_PNLI
TF_line_number
Order line number
IRF_ITNO
TF_item_number
Item number
IRF_POPN
TF_item_number
Item number
IRF_SUDO
TF_packing_slip
Packing slip
IRF_NEPR
TF_net_unit_price
Net unit price
IRF_GRPR
TF_gross_unit_price
Gross unit price
IRF_PPUN
TF_unit_code_price
Unit code price
IRF_NLAM
TF_net_amount
Net amount
IRF_GLAM
TF_gross_amount
Gross amount
IRF_TCHG
TF_charges
Charges
IRF_CDC1
TF_discount
Discount
IRF_PNLS
TF_sub_line_number
Sub line number
IRF_REPN
TF_receipt_number
Receipt number
IRF_DIVI
company_id
Company identifier
IRF_IVCW
TF_catch_weight
Catch weight
IRF_PUCD
TF_unit_price_per
Unit price per
Order Line Charges Fields
OLCF_GRPR
TF_unit_price
Unit price
OLCF_CHGT
TF_voucher_text
Voucher text
OLCF_CEID
TF_costing_element
Costing element
OLCF_PUNO
TF_purchase_order
Purchase order
OLCF_PNLI
TF_line_number
Line number
OLCF_ITNO
TF_item_number
Item number
OLCF_CDSE
TF_charge_sequence
Charge sequence
OLCF_PNLS
TF_sub_line_number
Sub line number
OLCF_REPN
TF_receipt_number
Receipt number
OLCF_IVQA
TF_quantity
Quantity
OLCF_SUDO
TF_packing_slip
Packing slip
Order Charge Line Fields
OCF_NLAM
TF_amount
Amount
OCF_CEID
TF_costing_element
Costing element
OCF_CDSE
TF_charge_sequence
Charge sequence
Cost Line Fields
ICF_NLAM
TF_amount
Amount in the transaction
ICF_VTXT
TF_voucher_text
Voucher text
ICF_AIT1
TF_ledger_account
Ledger account
ICF_AIT2
TF_dimension_2
Dimension 2
ICF_AIT3
TF_dimension_3
Dimension 3
ICF_AIT4
supplier_id
Supplier identifier
ICF_AIT5
TF_dimension_5
Dimension 5
ICF_AIT6
TF_dimension_6
Dimension 6
ICF_AIT7
TF_dimension_7
Dimension 7
ICF_AO01
TF_accounting_object_1
Accounting object 1
ICF_AO02
TF_accounting_object_2
Accounting object 2
ICF_AO03
TF_accounting_object_3
Accounting object 3
ICF_AO04
TF_accounting_object_4
Accounting object 4
ICF_AO05
TF_accounting_object_5
Accounting object 5
ICF_AO06
TF_accounting_object_6
Accounting object 6
ICF_AO07
TF_accounting_object_7
Accounting object 7
Debit Note Header Fields
DN_HF_SUNO
supplier_id
Supplier identifier
DN_HF_IVDT
invoice_date
Invoice date
DN_HF_SINO
invoice_id
Invoice identifier
DN_HF_SPYN
supplier_id
Supplier identifier
DN_HF_CUCD
currency
Currency
DN_HF_CUAM
total_net_amount_us
Total net amount us
DN_HF_VTAM
total_tax_amount
Total tax amount
DN_HF_ACDT
invoice_date
Invoice_date
DN_HF_SERS
invoice_sub_type
Invoice sub type
DN_HF_FTCO
supplier_country_code
Supplier country code
DN_HF_TXAP
tax_country_1
Tax country
DN_HF_CORI
correlation_id
Correlation identifier
DN_HF_PAIN
sqr_field_esr_reference
Sqr field esr reference
DN_HF_TCHG
additional_amount
Additional amount
DN_HF_CDC1
negative_amount
Negative amount
DN_HF_APCD
buyer_id
Buyer identifier
DN_HF_TEPY
payment_terms
Payment terms
DN_HF_PYME
payment_method
Payment Method
DN_HF_BKID
bank_id
Bank identifier
DN_HF_GEOC
geo_code
Geo Code
Debit Note Cost Line Fields
DebitNoteInvoiceCostFields
NLAM,AIT5
NLAM,AIT5
DNCF_NLAM
TF_amount
Amount
DNCF_AIT5
purchase_order
Purchase Order
Debit Note Receipt Line Fields
DNRF_IVQA
TF_quantity
Quantity
DNRF_PUUN
TF_unit
Unit
DNRF_PUNO
TF_purchase_order
Purchase order
DNRF_PNLI
TF_line_number
Line number
DNRF_ITNO
TF_item_number
Item number
DNRF_POPN
TF_item_number
Item number
DNRF_SUDO
TF_packing_slip
Packing slip
DNRF_NEPR
TF_net_unit_price
Net unit price
DNRF_GRPR
TF_gross_unit_price
Gross unit price
DNRF_PPUN
TF_unit_code_price
Unit code price
DNRF_NLAM
TF_net_amount
Net amount
DNRF_GLAM
TF_gross_amount
Gross amount
DNRF_TCHG
TF_charges
Charges
DNRF_CDC1
TF_discount
Discount
Credit Note Header
CN_HF_SUNO
supplier_id
Supplier identifier
CN_HF_IVDT
invoice_date
Invoice date
CN_HF_SINO
invoice_id
Invoice identifier
CN_HF_SPYN
supplier_id
Supplier identifier
CN_HF_CUCD
currency
Currency
CN_HF_CUAM
total_net_amount_us
Total net amount us
CN_HF_VTAM
total_tax_amount
Total tax amount
CN_HF_ACDT
invoice_date
Invoice date
CN_HF_SERS
invoice_sub_type
Invoice sub type
CN_HF_FTCO
supplier_country_code
Supplier country code
CN_HF_TXAP
tax_country_1
Tax country
CN_HF_CORI
correlation_id
Correlation identifier
CN_HF_PAIN
sqr_field_esr_reference
Sqr field esr reference
CN_HF_TCHG
additional_amount
Additional amount
CN_HF_CDC1
negative_amount
Negative amount
CN_HF_APCD
buyer_id
Buyer identifier
CN_HF_TEPY
payment_terms
Payment terms
CN_HF_PYME
payment_method
Payment method
CN_HF_BKID
bank_id
Bank identifier
CN_HF_GEOC
geo_code
Geo code
Credit Note Cost Line Fields
CreditNoteInvoiceCostFields
NLAM,AIT5
NLAM, AIT5
CNCF_NLAM
TF_amount
Amount
CNCF_AIT5
purchase_order
Purchase order
Credit Note Receipt Line Fields
CNRF_IVQA
TF_quantity
Quantity
CNRF_PUUN
TF_unit
Unit
CNRF_PUNO
TF_purchase_order
Purchase order
CNRF_PNLI
TF_line_number
Line number
CNRF_ITNO
TF_item_number
Item number
CNRF_POPN
TF_item_number
Item number
CNRF_SUDO
TF_packing_slip
Packing slip
CNRF_NEPR
TF_net_unit_price
Net unit price
CNRF_GRPR
TF_gross_unit_price
Gross unit price
CNRF_PPUN
TF_unit_code_price
Unit code price
CNRF_NLAM
TF_net_amount
Net amount
CNRF_GLAM
TF_gross_amount
Gross amount
CNRF_TCHG
TF_charges
Charges
CNRF_CDC1
TF_discount
Discount
Static Fields
In addition to the dynamic mappings, there are several static fields used for each type of line, which are predefined as follows:
Header Static Fields:
StaticFields=DIVI,IBTP,BSCD,IMCD,APCD,CRTP,CONO,PVLD
SF_DIVI=RFP
SF_IBTP=20
SF_CONO=001
SF_BSCD=DE
SF_IMCD=0
SF_APCD=MHIDALGO
SF_CRTP=1
SF_PVLD=1
Tax Line Static Fields:
InvoiceTaxStaticFields=RDTP,DIVI,VTCD,CONO,TAXT
IT_SF_RDTP=3
IT_SF_DIVI=RFP
IT_SF_CONO=001
IT_SF_TAXT=2
Order Header Extra Charge Static Static Fields:
OrderExtraChargeStaticFields=RDTP,DIVI,CONO,CDSE,CEID
OEC_SF_RDTP=2
OEC_SF_DIVI=RFP
OEC_SF_CONO=001
OEC_SF_CEID=INVPD
OEC_SF_CDSE=99
Receipt Line Static Fields:
InvoiceReceiptStaticFields=RDTP,DIVI,SERS,RELP,VTCD,CONO
IR_SF_RDTP=1
IR_SF_DIVI=RFP
IR_SF_RELP=1
IR_SF_VTCD=52
IR_SF_CONO=001
Order Line Charge Static Fields:
OrderLineChargeStaticFields=RDTP,DIVI,CONO
OLC_SF_RDTP=5
OLC_SF_DIVI=RFP
OLC_SF_CONO=001
Order Charge Line Static Fields:
OrderChargeStaticFields=RDTP,DIVI,CONO
OC_SF_RDTP=2
OC_SF_DIVI=RFP
OC_SF_CONO=001
Cost Line Static Fields:
InvoiceCostStaticFields=RDTP,DIVI,CONO
IC_SF_RDTP=8
IC_SF_DIVI=RFP
IC_SF_CONO=001
Debit Note Header Static Fields:
DNStaticFields=DIVI,IBTP,BSCD,IMCD,TEPY,PYME,APCD,CRTP,CONO
DN_SF_DIVI=RFP
DN_SF_IBTP=20
DN_SF_CONO=001
DN_SF_BSCD=DE
DN_SF_IMCD=0
DN_SF_TEPY=N00
DN_SF_PYME=CSH
DN_SF_APCD=MHIDALGO
DN_SF_CRTP=1
DN_SF_BKID=DJ1
Debit Note Cost Line Static Fields:
DebitNoteCostStaticFields=RDTP,DIVI,CONO,AIT1,AIT2,AIT3,AIT4,AIT5,AIT6,AIT7
DNC_SF_RDTP=8
DNC_SF_DIVI=RFP
DNC_SF_CONO=001
DNC_SF_AIT1=20216
DNC_SF_AIT3=100
DNC_SF_AIT6=INVDN
DNC_SF_AIT7=PP20230
Debit Note Receipt Line Static Fields
DebitNoteReceiptStaticFields=RDTP,DIVI,SERS,RELP,VTCD,CONO
DNR_SF_RDTP=1
DNR_SF_DIVI=RFP
DNR_SF_RELP=1
DNR_SF_VTCD=52
DNR_SF_CONO=001
Credit Note Header Static Fields:
CNStaticFields=DIVI,IBTP,BSCD,IMCD,TEPY,PYME,APCD,CRTP,CONO
CN_SF_DIVI=RFP
CN_SF_IBTP=20
CN_SF_CONO=001
CN_SF_BSCD=DE
CN_SF_IMCD=0
CN_SF_TEPY=N00
CN_SF_PYME=CSH
CN_SF_APCD=MHIDALGO
CN_SF_CRTP=1
CN_SF_BKID=DJ1
Credit Note Cost Line Static Fields:
CreditNoteCostStaticFields=RDTP,DIVI,CONO,AIT1,AIT2,AIT3,AIT4,AIT5,AIT6,AIT7
CNC_SF_RDTP=8
CNC_SF_DIVI=RFP
CNC_SF_CONO=001
CNC_SF_AIT1=20216
CNC_SF_AIT3=100
CNC_SF_AIT6=INVDN
CNC_SF_AIT7=PP20230
Credit Note Receipt Line Static Fields:
CreditNoteReceiptStaticFields=RDTP,DIVI,SERS,RELP,VTCD,CONO
CNR_SF_RDTP=1
CNR_SF_DIVI=RFP
CNR_SF_RELP=1
CNR_SF_VTCD=52
CNR_SF_CONO=001
Full Example
Handling Charges with Infor M3
Overview
This document provides detailed information on how DocBits integrates with Infor M3 to handle charges associated with invoices and purchase orders (PO). It includes scenarios for external charges and the expected solutions.
Charge Handling Scenarios
1
External Charges Not on PO but on Invoice (Accepted)
External charges appear on the invoice but are not listed on the PO. These charges are accepted.
Charges will be posted against Accounting Rule PP20-228 based on the cost element sent by DocBits.
2
External Charges Not on PO but on Invoice (Not Accepted)
External charges appear on the invoice but are not listed on the PO. These charges are not accepted or approved.
The total invoice value is recorded with a header charge for non-approved charges. Additionally, a debit note is created for these charges.
3
External Charges on Invoice Greater or Lesser than PO (Within Tolerance)
External charges on the invoice are greater or lesser than those on the PO but within the accepted tolerance.
Extra charges are posted against Accounting Rule PP20-228 based on the cost element sent by DocBits.
4
External Charges on Invoice Greater than PO (Outside Tolerance, Not Approved)
External charges on the invoice are greater than those on the PO and outside the accepted tolerance, and they are not approved.
The invoice is recorded with the total invoice amount. An additional non-approved charge is added as a header charge, and a debit note is created for this additional charge.
5
External Charges on Invoice Greater than PO (Outside Tolerance, Approved in DocBits)
External charges on the invoice are greater than those on the PO and outside the accepted tolerance, and they are approved in DocBits.
Extra charges are posted against PP20-228. Two options considered:<br>- If APS900 tolerance > DocBits, extra charges automatically posted.<br>- If APS900 tolerance = DocBits, extra charges posted with new charge elements not on PO.
6
External Charges on Invoice Lesser than PO (Outside Tolerance, Not Approved)
External charges on the invoice are lesser than those on the PO and outside the accepted tolerance, and they are not approved.
The invoice is posted as unapproved in APS110. The AP team adjusts the charges through the Invoice Control option in APS110, which calls APS360.
7
External Charges on PO and No Charge on Invoice
External charges are listed on the PO, but there are no charges on the invoice.
The invoice is posted as unapproved in APS110. The AP team adjusts the charges through the Invoice Control option in APS110, which calls APS360.
Example for Scenario 5
Line 1
$6000
$6000
Freight (E001)
$1000
$3000
Total
$7000
$9000
Tolerance of Freight: $100 approved automatically in M3 (APS900) and DocBits. Total invoice value of $9000 approved (with charges) manually.
APS451 (Invoice Line):
Line Type 1 (Invoice Line): $9000
Line Type 5 (Line Charge): $1000 (Element: E001 for Freight on PO $1000)
Line Type 5 (Line Charge): $2000 (Element: E101 for Freight on PO $0)
Important Fields and Values for Handling Charges in DocBits
Sequence Number
Unique identifier for each charge scenario
Costing Element ID
Identifier for the costing element
Costing Element Description
Description of the costing element
Charge Type
Typically, "External"
Charge Invoicing
Relevance needs to be determined
Distribution Method
Method used for distributing the charges
Gross Weight
Applicable if gross weight is available on the invoice
Volume
Applicable cases need to be defined
Net Amount
Applicable cases need to be defined
3rd Party Charge
Presence on the invoice and processing requirements
Invoice Charge Quantity
Clarification needed
Markup
Assumed to be the difference between charge and discount
Charge Category
Relevance needs to be defined
Costing Operator
Relevance needs to be defined
\
M3 Configuration
Prerequisites
You have created:
An ION API Endpoint
An ION API File
A BOD Mapping File
An IDM Mapping File
Import Mapping Files
Before you setup the dataflow, you need to import the mapping files into InforOS.
In ION Desk → Connect and open Mappings
Click on the Import icon
From here you need to select the various mapping files you will need which include: SyncCaptDoc_SyncSuppInv, SyncSupplierInvoice_LoadSupplierInvoice, and LoadSupplierInvoice_ProcessSupplierInvoice.
Once you have imported all the mappings files, make sure to approve each of them by clicking the tick icon within each of their squares on the Mapping dashboard.
DocBits to M3
The next step is to setup the Data Flow in ION Desk, navigate to the ION Desk application and select Data Flow → + ADD → Document Flow like below
You will then see this page, this is where you will build the flow of information from DocBits to M3
An M3 data flow will look similar to what is shown below (there are 3 DocBits applications and APIs due to it being used for 3 separate environments).
All parts of the chain are dragged and dropped from the top section
In the chain, DocBits and M3 are both Applications whereas in between them there are mappings that convert the data into a form that can be understood by the next section of the train and “map” the information so that it goes to where it is needed or meant too.
DocBits Application
Give it the appropriate name such as “DocBits” then select the plus sign and search for the connection point you created earlier such as DocBits_Export or similar and click on it.
To create this connection point, go to ION Desk → Connect → Connection Points
Click “+ Add”
Select “IMS via API Gateway” and fill in the following information
The ION API Client ID is in the ION API File you created at How to Create an ION API File, this can be found by the “ci” value.
Switch to the document tab, and add the Sync.CaptureDocument BOD to the DocBits connection point like below.
Then save the connection point by pressing the disk icon in the upper-left corner.
Navigate back to the Dataflow section of ION Desk to access your dataflow. Your DocBits application should look similar to what is shown below.
Mapping 1
The first mapping node should look as follows
Mapping 2
The second mapping node should look as follows
Mapping 3
The third mapping node should look as follows
M3 Application
There should already be a M3 or similarly named connection point created in INFOR so just like the DocBits Application you select it by clicking the “+” sign and it should look as follows
DocBits API
You will first need to create this API as a connection point which is done by:
ION Desk → Connect → Connection Points
Click “+ Add” and select API
The information you fill in should look like the following
Switch to the document tab and add the following configuration
Acknowledge.SupplierInvoice
The configuration for this BOD is as follows
Make sure you have selected the “Send to API” option in the above menu.
Lastly ensure that you alter the request body as well to look like this.
Repeat this process for the rest of the BODs, each configuration is shown below.
Sync.PurchaseOrder
The configuration for this BOD is as follows
Sync.RemitToPartyMaster
The configuration for this BOD is as follows
Sync.SupplierPartyMaster
The configuration for this BOD is as follows
BODs
The following configurations should look as follows:
First
Second
Third
Forth
Fifth
The last icon should be empty as it is not carrying any document or information.
Once you have added all necessary nodes to the data flow, press this button to activate the data flow (after saving the data flow by pressing the hard drive icon).