820 Flow: Configuration and Testing

When an inbound 820 is received from the trading partner endpoint, the InboundAzureEV event is triggered and InboundPreprocessorBPS is executed. This BPS involves the event, ReceiveEDIEvent, that tries to find a matching inbound route. If a matching inbound route is found, the EDI message is translated to D365 Customer payment journal XML and posted to D365.

This section explains how to configure the integration to process the Payment Order received from the Trading Partner and create the corresponding Standard payment Order in D365.

How to Configure

1. Configure the inbound route: Inbound Route will be set up with Sender ID as Trading partner name and Receiver ID as the customer name that was supplied in the Wizard properties file (wizard-input.properties file which is residing under the resources folder). If there are changes, _TP_820v4010IR residing in the com.cleo._customer_.d365scm._tp_.inbound.n820.v4010 package must be modified as required.
2. Configure the 997 enveloper: The 997 envelope details and the trading partner endpoint to which the 997 has to be sent should be configured in _TP_997ENV residing in the trading partner project under com.cleo._customer_.d365scm._tp_.outbound.n997 package.

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. Configure the Exit Points as follows:

   

3. Configure the Data Flow: Add a new Data Flow with the required source Endpoint specified and "Transformation" selected as the target Endpoint. For the target Endpoint, select the event com.cleo._customer_.edid365scm.inbound.InboundAzureEV

   

4. Monitor the flow.
   • Log Entries (Studio Auditor)
   • Message Tiles (Cockpit)
   • Jobs (Cockpit)
   • Dashboard > Charts (Cockpit)

In case of errors

• A ticket is generated; information will also be visible in the Message and Job views in CIC Cockpit.

  

  

• If the Trading Partner configuration is not found, a ticket is created and also an optional email alert is generated.
• If the processing fails due to invalid EDI syntaxes, a ticket is created and rejected 997 is sent to the trading partner.

How to Customize

1. Change the intervals for checking the status of payment order imported to D365.

   The LaunchExecutionSummaryPS scheduler within com.cleo._customer_.booster.d365scm.executionSummary package is currently configured to check the status of payment 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 while creating the payment Order in D365 or add specific business logic while creating the payment order in D365.

   The payment order in D365 is currently created with the data required to process orders successfully. The values mapped are documented in the Integration design spec Template X12-D365SCM-Mapping-Spec.xlsx present in the docs folder under the com.cleo._customer_.edid365scm project. To add more fields, update the ruleset _TP_820v4010RS as required.

   This template file consists of regular fields used in payment orders. To add fields, the template file must be updated with the new fields and the mapping details in D365 must also be updated with additional records.

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

3. If the user wants to modify the payment order target schema, the corresponding XSD DynamicsSCMCustomerPaymentJournal.xsd located in com.cleo._customer_.booster.d365scm/xsd package must be updated. After the XSD has been updated, the CustomerPaymentJournalOBJ.xml.objSchema located in com.cleo._customer_.booster.d365scm.customerPaymentJournal must be updated using the revised XSD. For details on updating XML schemas, see Creating XML Schemas .