Sign in
< Back to Top

X12 810 - D365 BC

A search is performed on D365BC to look for any unprocessed invoice records. If the record is found, it is parsed and the matching outbound route is searched. If there is a match, then the D365BC Invoice (JSON) is translated to an EDI 810, and then sent to the trading partner.

This section explains how to configure the integration to:

  • retrieve the Invoices
  • transform the Invoices to EDI X12 810 format 

How to Configure the Flow

  1. Configure the Process Scheduler: LaunchSalesInvoicePS is scheduled to run every 1 hour. See Creating and Defining Process Schedules for more information.
  2. Configure D365 BC: If the Invoice is to be converted to EDI and then sent to trading partners from all the available invoices in D365BC, then the custom field PostedSalesInvoice/CIC_Status must be configured with a Pending value.
  3. Configure the Outbound Route.
    1. The Sell to customer no mentioned in the shipment source payload identifies the trading partner to which the 810 is sent.
    2. The Sell to customer id is used in the look-up against the table D365_BC_Partners to find the trading partner name. If the name does not match the tpname (during project creation with the wizard), you must update the Outbound Route _TP_810v4010OR to reflect the matching name. This route is in the com.cleo._customer_.d365bc._tp_.outbound.n810.v4010 package.
  4. Configure the EDI Enveloper _TP_810v4010ENV. The X12 810 envelope details and trading partner endpoint to which the 810 is to be sent should be  TBy default, Customer name and the TP Name (as entered in the wizard property file) will have been added to the sender and receiver ID respectively. If there are any changes to the enveloping details, then the enveloper must be updated accordingly.  The object can be found in the com.cleo._customer_.d365bc._tp_.outbound.n810.v4010 package, as part of the trading partner project.

How to Run the Flow

  1. Before proceeding, ensure that the following Projects have been deployed. If any of these Projects are already deployed and remain unmodified, there is no need to redeploy them. Similarly, if any of these Projects were not checked out to your Workspace, they can be skipped from the deployment process.
  • com.cleo._customer_.edi
  • com.cleo._customer_.edi.booster.d365bc
  • com.cleo._customer_.edid365bc
  • com.cleo._customer_.d365bc._tp_
  • com.cleo.b2bcloud.core
  • com.cleo.b2biaas.clarify
  • com.cleo.cic.cockpit.core
  • com.cleo.cic.cockpit.core.n810
  • com.cleo.cic.cockpit.core.n812
  • com.cleo.cic.cockpit.core.n850
  • com.cleo.cic.cockpit.core.n855
  • com.cleo.cic.cockpit.core.n856
  • com.cleo.cic.cockpit.core.n846
  • com.cleo.cic.cockpit.core.n940
  • com.cleo.cic.cockpit.core.n945
  • com.cleo.cic.cockpit.core.n820
  • com.cleo.cic.cockpit.core.n875
  • com.cleo.cic.cockpit.core.n880
  • com.cleo.cic.cockpit.core.n860
  • com.cleo.cic.cockpit.core.n943
  • com.cleo.cic.cockpit.core.n944
  • com.cleo.cic.connector.d365bc

How to Customize the Flow

  1. Change the intervals at which Invoices are retrieved from D365SCM. The LaunchSalesOrderInvoicePS scheduler (in the com.cleo._customer_.d365bc._tp_.outbound.n810.v4010 package)  is currently configured to retrieve Invoices once every hour. Adjust per your requirements.
  2. Add more details from the D365BC Invoice to the X12 810. The values that are being mapped are documented in the Integration Design Specification in the com.cleo._customer_.edid365scm project under docs folder.

    Note: if additional fields are required, you must update the following Ruleset accordingly.

    TP_810v4010RS (from the D365bc Invoice) is in the com.cleo._customer_.d365bc._tp_.outbound.n810.v4010 package. 

    Contact Cleo Support for assistance.

Related articles

Comments

0 comments

Please sign in to leave a comment.