Sign in

865 Flow: Configuration and Testing

  • Updated

In D365, a search is performed to look for any unprocessed Sales Order Change records. If a record is found, it is parsed and the matching outbound route is searched. If there is a match, Sales Order Change Confirmation XML is translated to EDI 865 and sent to the trading partner.

This section explains how to configure the integration to retrieve Sales Order Change Confirmations and transform them into EDI X12 865 format for the Trading Partner.

How to Configure

  1. Configure Schedulers: LaunchSalesOrderChangeConfirmationPS.sched is scheduled to run once each hour. Adjust this frequency as required. Refer to Creating and Defining Process Schedules for details.
  2. Configure D365: If the Sales Order Change Confirmation is to be converted to EDI and then sent to the Trading partners from all the available sales orders in D365SCM, then the custom fields listed below must be configured with appropriate values.
    • SALESORDERHEADERV2ENTITY/CICSOURCE=CIC_EDI
    • SALESORDERHEADERV2ENTITY/CICSTATUS=Pending
    • SALESORDERHEADERV2ENTITY/CICORDERCHANGE=YES

    Only the Sales Order Confirmation records that have values matching CIC_EDI, Pending, and CICORDERCHANGE= YES will be searched for.

  3. Configure the Outbound Route: The Customer account id in the confirmation source payload is used to identify the Trading Partner to whom the Sales Order Change Ackowledgement is to be sent.

    The Customer account id is used to look up the Trading Partner name in the table, D365_SCM_Partners. If the Trading Partner name does not match the ‘tpname’ specified while creating the project using the Wizard, you must update the Outbound Route to reflect the matching name in _TP_865v4010OR present in the package, com.cleo._customer_.d365scm._tp_.outbound.n865.v4010.

  4. Configure the Enveloper: The X12 865 envelope details and the trading partner endpoint to which the X12 865 is to be sent should be configured in _TP_865v4010ENV residing in the trading partner project under the com.cleo._customer_.d365scm._tp_.outbound.n865.v4010 package. By default, the Customer name and the TP Name entered in the Wizard property file have been added to the sender id and receiver id, respectively. If there are any changes to the enveloping details, the _TP_865v4010ENV object must be updated.

How to Run the Flow

  1. Prior to running the flow, any Project that has been edited must be redeployed. This could include some or all of the following:

    • com.cleo._customer_.edi
    • com.cleo._customer_.edi.booster.d365scm
    • com.cleo._customer_.edid365scm
    • com.cleo._customer_.d365scm._tp_
    • com.cleo.b2bcloud.core
    • com.cleo.cic.connector.d365scm

    When the above projects are deployed to the server, dependent b2biaas and cockpit projects are also deployed automatically. If any of the projects are already deployed and have not been modified, they need not be deployed again.

  2. Run the flow either manually or automatically: 
    • Manually run the Business Process flow by launching LaunchSalesOrderChangeConfirmationBPS. See Starting Objects for information about 
    • Automatically run LaunchSalesOrderChangeConfirmationPS to kick off automatically based on the interval specified.
  3. Monitor the flow.

In Case of Errors

How to Customize

  1. Change how often to retrieve Sales Order Confirmation records from the D365SCM.

    The LaunchSalesOrderChangeConfirmationPS scheduler, residing in package com.cleo._customer_.d365scm._tp_.outbound.n865.v4010, is configured by default to retrieve Sales Orders Change Confirmations once each hour. Change the schedule to run more or less frequently as required. For details on defining a scheduler, see Creating and Defining Process Schedules.

  2. Add more details to the X12 865 from the D365 Invoice.

    The values mapped are documented in the Integration Design Specification Template present in com.cleo._customer_.edid365scm project under the docs folder. To add more fields, update the Ruleset _TP_865v4010RS present in com.cleo._customer_.d365scm._tp_.outbound.n865.v4010 package as required.

    Contact Cleo support if you need any assistance while adding additional rules.

  3. To modify the Sales Order Confirmation source schema, update DynamicsSCMSalesOrderChangeConfirmations.xsd located in the package, com.cleo._customer_.booster.d365scm/xsd. After the XSD has been updated, the SalesOrderConfirmationsOBJ.xml.objSchema located in com.cleo._customer_.booster.d365scm.salesOrderChangeConfirmations must be updated using the revised XSD. For details on updating XML schemas, see Creating XML Schemas.

Related articles

Comments

0 comments

Please sign in to leave a comment.