Sign in

X12 880 - D365 SCM

  • Updated

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

This section explains the settings required to configure the integration between D365SCM to retrieve the Grocery Invoices and Transform the same to EDI X12 880 format for the Trading Partner integration.

How to Configure

  1. Configure Schedulers: LaunchSalesFroceryOrderInvoicePS 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 Grocery Invoice is supposed to be converted to EDI and then sent to the Trading partners from all the available invoices in D365SCM, then the custom fields mentioned below should be configured with appropriate values.
    • CICSTATUS=Pending
    • CICSOURCE=CIC_EDI
    • GroceryStatus= YES

    Grocery status flag set in 875 to YES during 875 processing. This flag is used to distinguish normal POs 850 from Grocery POs 875s). Grocery Invoices are filtered in SCM using CICGroceryStatus=YES and CICStatus =PENDING. After being processed, invoice status is updated to COMPLETED and status is updated to FAILED in case of failure. Grocery invoices are exported in Dynamics SCM with help of Data management framework APIs.

  3. Configure the Outbound Route: The Customer invoice account id mentioned in grocery invoice source payload is used to identify the Trading Partner to whom the 880 is supposed 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 Wizard, you must update the Outbound Route to reflect the matching name in _TP_880v4010OR present in com.cleo._customer_.d365scm._tp_.outbound.n880.v4010 package.

  4. Configure the Enveloper: The X12 880 envelope details and the trading partner endpoint to which the X12 880 is to be sent should be configured in _TP_880v4010ENV residing in the trading partner project under com.cleo._customer_.d365scm._tp_.outbound.n880.v4010 package. By default, the Customer name and the TP Name entered in the Wizard property file have been added to the sender and receiver id, respectively. If there are any changes to the enveloping details, the same object must be updated.
  5. Configure the Reference Table: Add the following details to the reference table -D365_SCM_DataManagement:

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.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.

  2. Run the flow either manually or automatically: 
    • Manually run the Business Process flow by launching LaunchSalesGroceryOrderInvoiceBPS. See Starting Objects.
    • Automatically run LaunchSalesGroceryOrderInvoicePS to kick off automatically based on the interval specified.
  3. Monitor the flow.
    • Log Entries (Studio Auditor)
    • Message Tiles (Cockpit)
    • Jobs (Cockpit)
    • Dashboard > Charts (Cockpit)

In Case of Errors

How to Customize

  1. Change the intervals for checking the status of Grocery Purchase Order imported to D365.

    The LaunchExecutionSummaryPS scheduler within com.cleo._customer_.booster.d365scm.executionSummary package is currently configured to check the status of Grocery Purchase Order imported to D365. Change the schedule to run less frequently if required. For details on defining a scheduler, see Creating and Defining Process Schedules.

    Note: A time interval of at least 15 minutes is recommended to fetch the execution summary status. The LaunchExecutionSummaryPS scheduler is set to run every 15 minutes with a start time of 12:00:00 AM.

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

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

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

  3. To modify the Invoice source schema, update Dynamics365Invoice.xsd located in com.cleo._customer_.booster.d365scm/xsd package. After the XSD has been updated, the InvoiceDocumentOBJ.xml.objSchema located in com.cleo._customer_.booster.d365scm.invoice 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.