Documentation
LunoLake EDI
EDI inside Microsoft Dynamics 365 Finance and Supply Chain Management. Orders, confirmations, despatch advices and invoices are exchanged with your trading partners from the records you already post, and every document is visible on the order it belongs to.
This is the manual for the people who set it up and the people who extend it. It says what the module does, what you have to tell it before it can do anything, what happens to each document from the moment a posting starts it, and how to add a document type of your own without touching a line of ours.
If you are new to it, read What LunoLake EDI is and then How a document travels. Those two pages are the whole shape of the thing in about ten minutes.
Getting started
What the module is, what happens to a document, and how to get it running.
Setting up
The records that have to exist before a document can be sent or received.
- Your organisationWho you are on the wire: the identifiers partners address you by.
- PartnersThe company at the other end, and the customer or vendor accounts it maps to.
- TransportsAS2, AS4 and SFTP: how documents actually leave and arrive.
- AgreementsWhat you have agreed to exchange with one partner, in each direction.
- ValidationRulesets, validation modes, and what happens when a document fails one.
- Several companiesOne partner trading with more than one of your legal entities.
The flows
Each business document, from the event that starts it to the record it leaves behind.
- Inbound orderA partner's order becomes a sales order, with the lines checked before it lands.
- Order confirmationConfirming a sales order sends the answer back.
- Despatch advicePosting a packing slip tells the partner what is on the way, down to the pallet.
- Invoice and credit noteThe invoice family: sales, project, free text, and the credit notes beside them.
- The purchase sideThe same four documents seen from the buying end.
- AcknowledgementsTwo layers of receipt, and what it means when one of them never comes.
- The posting gateValidation during posting, and the choice between warning and refusing.
Watching it run
Where to look when you want to know what happened, and where to look when it went wrong.
- The flow trackerEvery document a single order touched, on the order itself.
- The message logOne row per transmission, with the wire file behind it.
- Staging and compareWhere an inbound document waits, and what the comparison against your data says.
- OperationsThe workspace, the queue, and how to get a stuck document moving again.
Extending it
Your own document types and formats, in your own model, against a published surface.
- The extension modelHow the module finds code you wrote, and the three bases it looks for.
- Adding a document typeA worked example, from an empty model to a document on the wire.
- Handler referenceEvery method on the two document-type bases, what it decides, and its default.
- Acknowledgement handlersTeaching the module what a receipt looks like in your format.
- Electronic reportingThe configurations that turn records into a wire file and back.
- Testing an extensionProving your handler is found, and that it does what it says.
Reference
The lists, for looking something up.