Configure Reference Tables - D365 SCM

Configure the Cleo-provided Reference Table using the steps below.  See Viewing and Editing Reference Tables in CIC Cockpit for more information.

1. Run the CreateD365ScmPartnerRefTablesBPS.bps - located in package com.cleo._customer_.booster.d365scm.customer in project com.cleo._customer_.booster.d365scm.

   To verify that the setup has completed successfully, refer to the Auditor logs. These logs display the starting step and the completed step information. If there are issues (for example, driver or connection), they are displayed in Auditor logs info; the user must take necessary action, and then run this process again.

   When the process ends successfully, the table D365_SCM_Partners will be created in CIC Cockpit. Next, call com.cleo._customer_.booster.d365scm.customer.LaunchCustomersBPS.  This BP reads the customer payload (customer account id and warehouse id) from D365SCM and adds the data to the table as shown here.

   

2. Add a new row that includes Trading Partner Name, Trading Partner Id, Warehouse Trading Partner Name, and the corresponding customer account id that was assigned in D365 SCM. 

   

   • Trading Partner Name captures the partner name that identifies the partner.
   • Trading Partner ID captures the EDI X12 ID assigned to a partner. For example, an 850 X12 TP document would have a sender ID as the trading partner ID (located in ISA06). 
   • Customer Account ID is the D365 SCM-assigned ID for the customer entity record.
   • Warehouse ID is the unique warehouse ID that can be allocated only to one customer account ID
   • Warehouse name is the name of the 3PL warehouse trading partner that is related to the buyer/ retailer trading partner entity.
3. Run the CreateDataManagementTablesBPS.bps located in the package com.cleo._customer_.booster.d365scm.reference.tables in project com.cleo._customer_.booster.d365scm.

   To verify if the setup is complete, refer to the auditor logs. These logs would display the starting step and the completed step information. If there are issues (ex: driver or connection), then they are displayed in auditor logs info; the user must take necessary action, and then run this process again.

   Once the process ends successfully, the table named D365_SCM_DataManagement is displayed in the CIC Cockpit (Integrations tab/Reference tables section).

4. Add a new row that includes Definition Group ID, Description, and Direction for each doc type. 

   

   

   The Doctype column represents the message document type for the integration flows, for example, Invoice, ASN, and so on.  Add Doctype values as follows: SOConfirmation for 855, Invoice for 810, SalesOrder for 850, Inventory for 846 and “Customer’ for customer Entity V3, WarehouseShippingOrder for 940, GroceryOrder for 875, GroceryInvoice for 880, PaymentOrder for 820, OrderStatusReport for 870, PaymentOrder for 820, and SOChangeConfirmation for 865, and CrediDebitAdjustment for 812.

   DefinitionGroupId and Description represent the data project names and descriptions configured for O2C documents (850, 856, 855, 810, 846, and Customer, 940, 875, 880, 820, 870, 865, and 812 in D365 SCM. This is documented in X12 O2C With D365 SCM Accelerator, which can be found in the docs folder within the com.cleo._customer_.edid365scm project.

5. Run CreateDataManagementImportTablesBPS.bps (located in the package com.cleo._customer_.booster.d365scm.reference.tables in the project com.cleo._customer_.booster.d365scm).

   To verify if the setup is complete, refer to the auditor logs. If there are issues (ex: driver or connection), then they are displayed in auditor logs info; the user must take necessary action, and then run this process again.

   If the process ends successfully, the D365_SCM_DataManagement_Import table will be visible in the Cockpit (Integrations tab<Reference tables) and a new row will be added that includes FileName, ManifestFile, and PackageHeaderFile for each doc type.

   

   Note: Please reference the Data Management Import Configuration document for details on filename, manifest, and packageHeaderFile for different document types.