Infor LN and M3 purchase to pay and order to cash: see where each order waits

What does Duaer read from Infor LN and M3?

Each purchase or sales order is a case, with the supplier or customer, the company, currency and amount. The steps are:

• Infor LN: purchase orders (tdpur400), receipts (tdpur406), invoices (tfacp200 and tfacp251), payments; sales orders (tdsls400), shipments (whinh430), invoices (cisli305), payments (tfacr200).
• Infor M3: purchase orders (MPHEAD), receipts (MITTRA type 25), invoices (FGINHE and FGINLI), payments (FPLEDG); customer orders (OOHEAD), deliveries (MHDISH), invoices (ODHEAD), payments (FSLEDG).
• An LN source reads one company; M3 reads every company (CONO).

How do you connect Infor LN and M3 to Duaer?

1. In Infor LN and M3's SQL Server database, create a read-only user with SELECT on the tables above.
2. If the database is only inside your network, start the Duaer on-premises data gateway (0.2.0 or later) there with tcp://database-host:port in ALLOWED_TARGETS; the credential's host and port must match it.
3. In Duaer, create a Microsoft SQL credential for this user.
4. As an owner or admin, open Data sources, select Add source, choose Infor LN and M3 under Purchase to pay or Order to cash, choose the credential, for LN enter the company number (such as 100); for M3 the schema is MVXJDTA unless you enter another, select Check connection and confirm.

How often does it read, and how much?

Each run reads the streams by change date, starting two weeks back; a step is never written twice. Queries only.

What are the limits?

• The tables, entities and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
• Infor CloudSuite offers no database and is not supported yet.
• LN's field names most need checking at the first real read.