Initial Setup Steps

These steps are required before using the D365 X12 Accelerator.

Configure Reference tables

Configure the Cleo-provided Reference Table using the steps below. Refer to Viewing and Editing Reference Tables in CIC Cockpit for additional details.
Run the CreateD365BCPartnerRefTableBPS.bps. This can be found in com.cleo._customer_.booster.d365bc.reference.tables (package) in com.cleo._customer_.booster.d365bc (project).
Refer to the Auditor logs in the CIC Studio to verify setup has been completed successfully. These logs display step details. If there are errors or issues (driver or connection issues for example), they will be displayed in the logs; the user would take corrective action, and then run this process again.

When the setup process ends successfully, a new table (D365_BC_Partners) is created in the CIC Cockpit. Note: You must next manually add the trading partner's ID and name for the corresponding customer records (see below). Significance of the columns:

The trading partner name captures the partner name with which the partner would be identified.
The trading partner ID captures the EDI X12 ID assigned to a partner. For example, an 850 X12 TP document's Sender ID would be the trading partner id (located in ISA06).
The Sell to Customer ID is the ID assigned by MS Dynamics for the customer entity record.

Follow these steps to configure the Cleo-provided staging database.

Deploy the com.cleo.cic.util project.
Run com.cleo.cic.util.processes.CreateStagingDataV2TableBPS to create the required table. To verify if the setup is complete, refer to your Auditor logs, which will display both starting and completed step information. Errors or issues (e.g. driver, connection issues) will be noted in the logs. If this occurs, then corrective action should be taken before running the process again.

Configuration to certain Global Variables is required.

D365BCVault:- This variable contains the vault entry name assigned to the D365BC connector.
SleepInterval: This variable contains the sleep time ( in milliseconds ). This timer is used to retry certain APIs that are throttled.
companyName: This variable should store the company name of the organization tied to the sales order transactions.
HttpErrorCodesToBeIgnoredForTicketCreation: This is used to identify HTTP error codes that need to be flagged as ‘successful job flows’ in the Cockpit. If not mentioned here, the error codes would be flagged as failed jobs in the cockpit. In case a D365 BC API request is throttled (i.e with HTTP 429 Too Many Requests error ), the execution waits as per the time period configured in the SleepInterval global variable and the API request is made again. Since we have a retry logic for throttled requests implemented in the accelerator, these jobs need not be marked as failures, and hence this global variable is configured with the default value of throttling error code (429).
B2BCloudGV: Configure the B2BCloudAdminEmail (receiver) and B2BCloudHostEmail (sender) variables in com.cleo.b2bcloud.core.B2BCloudGV. These are resolved during failures; email notifications will be triggered.