Getting started
What LunoLake EDI is
A module inside your own Dynamics 365 that exchanges business documents with your trading partners, and a service that carries them. No middleware to learn, and no second place where the truth lives.
Most EDI for Dynamics 365 works by standing outside it. A separate platform holds the partner agreements, the mappings and the message history, and it talks to Dynamics through an integration. That arrangement works, and it leaves you with two systems that both believe they know the state of an order, an integration between them to keep healthy, and a support question that starts with finding out which of the two is wrong.
LunoLake EDI is a module in Dynamics 365 Finance and Supply Chain Management. Partners, agreements and message history are records in your own database, next to the customers and vendors they belong to. A despatch advice is produced from the packing slip you posted, not from a copy of it. When you want to know whether the invoice reached the customer, you look at the invoice.
What it covers
Four business documents, in both directions, in three wire formats. The same order can arrive from one partner as an EDIFACT ORDERS and from another as a UBL Order, and from there on it is a sales order like any other.
| Business document | EDIFACT | X12 | UBL |
|---|---|---|---|
| Order | ORDERS | 850 | Order |
| Order confirmation | ORDRSP | 855 | Order response |
| Despatch advice | DESADV | 856 | Despatch advice |
| Invoice | INVOIC | 810 | Invoice, credit note |
| Receipt for the envelope | CONTRL | 997 | Application response |
| Receipt for the document | APERAK | 997 | Application response |
The module ships no formats of its own. The four standard Danish UBL formats, sales and project invoices with a credit note for each, are Electronic Reporting configurations you import and bind; the module uses them as published, and they are not something to author.
Which part is yours and which part is ours
The module is yours. It runs in your environment, its data is your data, and you can read every line of what it did. Carrying the document to the partner is ours: the service takes what the module produced, speaks the transport the partner requires, and hands back what came the other way.
| Yours, in Dynamics 365 | Ours, as a service |
|---|---|
| Partners, agreements, identifiers | AS2, AS4 and SFTP connections |
| What a document contains | Certificates, and keeping them valid |
| When a document is sent | Delivery, retries and receipts |
| The order, the packing slip, the invoice | Network directories, where a network has one |
You do not configure the service, and this manual does not describe its insides. What it does describe is every point where it touches you: what leaves, what comes back, and what you see when something does not arrive.
What it looks like in use
Setting up a partner is a card in Dynamics, with the customer and vendor accounts it trades under, the identifiers it is known by, and one agreement per document per direction. After that, ordinary work does the sending. Confirm a sales order and a confirmation goes out. Post a packing slip and a despatch advice goes out. Post an invoice and an invoice goes out.
Inbound is the mirror of it. A partner order arrives, is checked against what you actually sell them, and becomes a sales order. What was compared, and what did not match, is kept.
Every document that an order touched shows up on the order itself, in the flow tracker, in the order it happened, with the state of each. That is usually the whole of a support question.
When it does not fit
Some partners ask for a document nobody else uses, or a format of their own. That is expected, and it is why the module has a published extension surface rather than a settings page with a text box. You add a document type in your own model, keyed to your own enum value, and the module finds it. It is a handler class and a couple of Electronic Reporting configurations, and it does not fork anything.
What you need before starting
- Dynamics 365 Finance and Supply Chain Management, with Electronic Reporting available.
- A trading partner who has told you what they send, in which format, over which transport.
- An identifier they address you by. In Denmark that is usually a GLN or a CVR number.
- A connection to the LunoLake service, which we set up with you.
Installing the module takes it from there.