Lanham EDI is designed from the start to work in a tightly cooperative manner with the Lanham E-Ship and E-Receive extension and takes a dependency on it. This makes our unique process of creating ASNs (Advanced Ship Notices) immediate and accurate.
Lanham EDI is built inside Microsoft Dynamics 365 Business Central so it takes advantage of all your business data in your ERP system and keeps all of your important information securely inside that system until it is transported to your trading partner.
Your familiar Dynamics 365 Business Central user interface makes Lanham EDI easy and intuitive to use.
Microsoft Dynamics NAV has evolved into Microsoft Dynamics 365 Business Central, supporting private and public cloud environments as well as traditional on-premises environments. Please be sure to review the product capabilities for your exact NAV/Business Central version by scrolling down this page or clicking the Traditional Application box below.
In today’s world EDI is often a requirement to get new business or to start a relationship with a new trading partner. It is intended to automate business transactions and remove as much of the cost in trading as possible.
With the objective of efficiency, why send EDI out for processing when EDI can be organized and transacted from right inside your business system? Purchase orders are sent automatically, and invoices are generated automatically. All EDI documents are transacted where they belong in your business system – orders with sales orders and invoices with invoices.
And everything is easily recognized in your D365 Business Central user interface. You can use Business Central drill-down to see the business detail you need. There is no need to learn a new system or new user interface.
Lanham EDI is job queue-enabled to automatically schedule the document receiving and sending processes, so you can manage by exception, based on alerts found in the user’s role center. Lanham EDI is seamless and beyond simple.
EDI documents and standards are constantly changing; therefore, we are constantly updating the Lanham EDI capabilities. If you have a question concerning new requirements or a specific document, please reach out to us with your questions so that we can assist you with the updated information: email@example.com.
EDI Standard is the base engine for Lanham EDI. It resides natively inside Microsoft Dynamics 365 Business Central and houses the EDI translator, cross reference engine and mapping tool.
This feature provides document translation inside the business system, a single mapping process between the EDI documents and the database and cross references, all within your consistent Business Central user interface. Users can drill-down from either a Business Central document or an EDI document to view the related transaction detail; and have a logical place for EDI archives.
The EDI trace window, part of EDI Standard, shows all transactions that were created by and associated with incoming documents such as 850 purchase orders. The user can then drill down to view any document or associated EDI transaction bi-directionally.
EDI Standard offers general cross-references for both inbound and outbound data such as:
This feature supports EDI sales and purchasing documents. The following outbound documents are supported in this feature: 810, 843, 850, Std 855, 856 (non-3PL), 857, 875, 880, 894, 940 (sales), 943 (purchase), and 997. Inbound documents include: 810, 840, 850, 856, 857, 861, 875, 880, 944 (purchase), Std 945 (sales) and 997.
This Lanham EDI feature, EDI Extended Purchasing Document Handling, provides the ability to map advanced purchasing EDI documents such as Return Orders and Payment Advices. The following outbound documents are currently supported: 180 and 820. Inbound Documents supported include – 180, 210, and 812.
This feature enables the user to map advanced 3PL documents where the inbound EDI file creates E-Ship packages and Bills of Lading in order to send an outbound 856 or Advanced Ship Notice (ASN). This feature also supports inbound 856 or 945 documents from the 3PL or third-party logistics fulfillment center.
This Lanham EDI feature provides the ability to map advanced purchasing EDI documents such as Return Orders and Payment Advices. The following documents are currently supported: Outbound Documents – 180 and 820; and Inbound Documents – 180, 210, and 812.
The Lanham EDI feature, Extended Documents Handling 2, provides the ability to map advanced EDI documents such as Transfer Orders and Remittance Advices. The following outbound documents are supported in this feature: 211, 867, 940, and 943 (Transfer Order or Transfer Shipment). This feature also supports the following inbound documents: 820, 867, 945, and 944 (Transfer Order or Update Transfer Order).
This feature provides shipment planning, rating and printed Bills of Lading.
When using Lanham EDI, the BOL feature is enhanced to provide package detail capture to build accurate EDI Advanced Ship Notices (ASNs) during the shipping process. ASNs are automatically sent to the EDI trade partner at the time of shipping to avoid any penalties surrounding not receiving ASNs prior to receiving the actual product shipment.
This feature is dependent upon E-Ship and E-Receive BOL and so does require that your D365 Business Central system also be registered for E-Ship and E-Receive Packing and BOL in addition to Lanham EDI BOL/ASN to support EDI Advance Ship Notice (ASN) creation.
Lanham EDI provides you several implementation options:
When exploring your EDI Total Cost of Ownership (TCO), you’ll also want to consider the Lanham Value Added Network (VAN) which offers some of the lowest rates in the industry.