Sign in
< Back to Top

EDI X12 Order-to-Cash <> D365 BC (Overview)

Also called the O2C cycle, Order-to-cash is how your business receives, processes, manages, and completes orders. It begins from the time an order takes place and includes each step of the delivery and payment process. In this case, D365 Business Central (BC) represents our backend.

This particular Accelerator contains prebuilt Schemas, Rulesets, Business Processes, and other resources used for development, deployment/execution, and testing. This includes mapping tools specific to several business flows as part of this Accelerator.  Finally, there are also resources necessary to display data in several Cockpit monitoring pages. 

Supported Business Flows

D365BCSupFlows.png

Features

Pre-built Integration Flows: Integration flows in CIC are provided to receive X12 850 (Purchase Order) from trading partners and create the corresponding Sales Order in D365 BC. Once the Order is confirmed,  the integration flow automatically retrieves details from D365 BC and creates the X12 855 (PO Acknowledgement). In case there is any change to the existing Sales Order, the trading partner sends out an X12 860 (Purchase Order Change) which in turn updates the existing sales order in D365 BC. Once the Shipment and Invoice are created for the Order in the D365 BC, this Accelerator has the project to retrieve the Shipment and Invoice records from the D365 BC which generates the respective outbound documents like X12 856 (ASN) and X12 810 (Invoice) document.

The integration flow also automatically retrieves item details from D365 BC and creates the X12 846 (Inventory Inquiry/Advice) for trading partners. The manufacturer (D365 BC) can instruct the warehouses or warehouses can instruct other warehouses to ship the items ordered, by automatically retrieving sales/transfer order details from D365 BC and creating outbound X12 940 (Warehouse Shipping Orders) for the warehouse or third-party logistics provider (3PL). The warehouse sends out X12 945 (Warehouse Shipping Advice) to D365 BC to let them know that a shipment has taken place and based on the Depositor number in EDI 945 the existing Sales/Transfer order is updated in D365 BC.
Integration flows in CIC are provided to receive X12 820 (Payment Order or Remittance Advice) from the trading partners and create the corresponding CashReceiptJournal in D365 BC. The Integration flow can also receive X12 875 (Grocery Order) from trading partners and create the corresponding Sales Order in D365 BC with the Grocery_Order flag as true. Once the Grocery Invoice is created for the Grocery Order in the D365 BC, the Accelerator has a project used to retrieve the Grocery Invoice records from the D365 BC which generates the outbound document,  such as the X12 880 (Grocery Products Invoice). When there is stock to be transferred, the manufacturer informs the warehouse/3PL about the items transfer information through the X12 943 (Warehouse Stock Transfer Shipment Advice) so that they are ready to receive the incoming stock from the customer/vendor/any other warehouse. Once the stock has been received by the warehouse/3PL, they generate X12 944 (Warehouse Stock Transfer Receipt Advice) as confirmation for the number of items received by the manufacturer, which will update the existing Warehouse Receipt in D365 BC.

All the flows will also have the respective X12 997 (Func Ack) flow and outbound EDI validations included.

Integration design Specification Template: The document which explains the business rules that are applied while creating the inbound and outbound documents.  The template helps in documenting any changes to the template integration as per your requirement.

Multiple Trading Partner Onboarding: The design lets you, onboard multiple Trading Partners, at once using the Wizard. 

Email notification for unknown trading partners: If the Inbound/Outbound payloads are received where no matching configurations are found, then an email notification will be generated.

EDI message validations:

  • Duplicate Inbound messages The Accelerator has the logic to handle any duplicate EDI data that is retrieved from the Trading partner. If need be, this can be turned per partner or per doctype.
  • Inbound/Outbound EDI Data validation: Accelerator is enabled to catch any invalid EDI syntaxes in both Inbound and Outbound flow. The execution will be stopped if there are any syntax errors. The settings can be changed to not stop execution as well. 

Error Handling and Ticket Creation: Accelerator ensures all the processing failures are logged as a ticket and marked as an Issue in the Cockpit.

Out-of-the-box Cockpit visibility: Accelerator is already enabled with the resources necessary to display data in several Cockpit monitoring pages.

  • The Message Details view provides the life cycle of an Order until the Invoice has been generated.
    D365BCTripV.png

  • The Accelerator also uses Dashboard charts to monitor various transactions. Below are charts for 850, 855, 856, 810, 846, 940, 945, 820, 875,880, 860, 943, and 044 documents.
    Details about the count of translated messages are also displayed.
    D365BcDashViews.png

Prerequisites

1. D365 Business Central ERP instances should be configured with certain customizations to D365BC entities and fields. The customization package should be deployed in the customer's D365 instance using the steps mentioned in Steps to install D365 BC Accelerator Package in Customer's D365 Instance.

2. Create the required connector projects in your workspace prior to running the wizard setup.
Always follow this naming convention for the connector name: com.cleo.cic.connector.d365bc

The connector should contain these entities: 

  • SalesOrder
  • SalesOrderSubform
  • PostedSalesShipment
  • PostedSalesShptSubform
  • UpdateSalesShipment
  • PostedSalesInvoice
  • PostedSalesInvoiceSubform
  • UpdateSalesInvoice
  • ItemCard
  • ItemReferences
  • Location Card
  • ShippingAgents
  • TransferOrder
  • TransferOrderSubform
  • CashReceiptJournal
  • PurchaseOrder
  • PurchaseOrderSubform
  • SalesReturnOrder
  • SalesReturnOrderSubform
  • WarehouseReceipt
  • WhseReceiptSubform

3. Create a Vault Entry with Manual authentication. This is needed to run a Web Service Consumer in the accelerator. The Vault Entry Alias name should be added in PostBatchAPIWSC in the package com.cleo._customer_.booster.d365bc.salesOrder.   Also, see creating a manual vault entry in 365 BC.

4. Import the Business Central certificates (available here) into the CIC Studio>Admin console>Keystore Manager.
D365 BC Cert1
D365 BC Cert2
D365 BC Cert3

5. Download the Accelerator using the template wizard.  See Initial Setup for Accelerators and Boosters.

6. The Item Number - Any Product ID field (PO107/PO109/PO111/PO113/PO115/PO117/PO119/PO121/PO123/PO125) (POC09/POC11/POC13/POC15/POC17/POC19/POC21/POC23/POC25) preceded by the Qualifier
VN / MG / VC / UP will be considered as an item number that is already present in D365 BC and mapped to the field SalesOrderSubform/No.  These items must have a Reserve method as either Optional or Always. (Example shown here)


D365BcPreReq.png

Note: For the EDI 943 and 944 integration flows, it is mandatory that the BC Auth Vault must be created by someone with the required BC Warehouse Employee Access.

What is not supported

  • This Accelerator currently supports X12 EDI Version 4010 only.
  • This Accelerator supports only those integrations for documents that have been processed in the CIC; it does not support non-CIC document integrations. For example, you cannot create an invoice, ASN, or confirmation record for an Order that was not processed by the CIC.

How to add a flow

If you wish to add a flow that is not part of this Accelerator, take these steps to add a flow(s) to your Project.  Note that the steps below are based on a specific example. Actual steps will be based on your specific requirements.

Adding an inbound flow:

The steps below use the example of adding an inbound 860 flow. 

  1. Create a package in the com.cleo._customer_.edi project. Name it com.cleo._customer_.edi.n860).
  2. Create an 860 EDI schema (make sure to use the correct version).
  3. Create a package in the project com.cleo._customer_.booster.d365bc. Name it com.cleo._customer_.booster.d365bc.salesOrderChangeRequest.
  4. Create a Business Process to call the required D365BC Business Process.
  5. Check out the com.cleo.cic.cockpit.core.n860 Project from the Cleo repository and add it to the dependencies referenced in the com.cleo._customer_.d365bc._tp_ project.
  6. Create a package in the com.cleo._customer_.edid365bc project. Name it com.cleo._customer_.edid365bc.inbound.n860.
  7. Create an inbound route BPS and configure it as required.
  8. Create a package in the com.cleo._customer_.d365bc._tp_ projectcom.cleo._customer_.d365bc._tp_.inbound.n860.v4010.
  9. Create an Inbound EDI Route and configure it accordingly.
  10. Create the transformation Ruleset per specific mapping requirements.
  11. Deploy all projects that have changed.
  12. Run and test the flow.

Adding an outbound flow:

The steps below use the example of adding an inbound 846 flow. 

  1. Create a package in the com.cleo._customer_.edi project. Name it com.cleo._customer_.edi.n846.
  2. Create an 846 EDI Schema (make sure to use the correct version).
  3. Create a package in the project com.cleo._customer_.edi.booster.d365bc. Name it com.cleo._customer_.edi.booster.d365bc.inventory.
  4. Create your Process Schedulers, Launcher Business Process, and DARS (Ruleset).
  5. Check out the com.cleo.cic.cockpit.core.n846 project from the Cleo repository and add it to the dependencies as referenced in the com.cleo._customer_.d365bc._tp_project.
  6. Create a package in the com.cleo._customer_.edid365bc project. Name it com.cleo._customer_.edid365bc.outbound.n846.
  7. Create an Outbound Route Business Process and configure it per your requirements. As a guide, you can refer to the Outbound810RouteBPS found in the com.cleo._customer_.edi.d365bc.customer.outbound.n810 package.
  8. Create a package in the com.cleo._customer_.d365bc._tp_project. Name it com.cleo._customer_.d365bc._tp_.outbound.n846.v4010.
  9. Create an Outbound EDI Route and configure it accordingly.
  10. Create the transformation Ruleset per your mapping requirements.
  11. Create and configure the EDI Enveloper.
  12. Deploy all projects that have changed.
  13. Run and test the flow.

Please contact Cleo Support for help on the above steps. 

Project Structure

Detailed documentation is provided on the project structure and object-level details that are in the Accelerator. Please refer to the X12 O2C With D365 BC Accelerator document provided in the com.cleo._customer_.edid365bc project under the Docs folder.

Please contact Cleo Support if you need assistance with project structure. 

Next Steps

There are several actions you may need to take that are described in these initial setup steps, which include the configuration of:

  • Reference Tables
  • Staging Database
  • Global Variables

Related articles

Comments

0 comments

Please sign in to leave a comment.