X12 820 - NetSuite O2C

When an inbound 820 is received from the customer (inbound endpoint), the cloud monitor picks up the file, and the ReceiveEDIEvent searches for the matching inbound route. If a match is found, the EDI message is translated to NetSuite Payment Order XML and posted to NetSuite.

This section explains how to configure the integration to process the Inbound Payment Order received from the Trading Partner and create the corresponding Standard Customer Payment on NetSuite.

How to Configure

1. Configure the Cloud Monitor: InboundEDIMN (located in the com.cleo.customer.edinetsuite.inbound Project under package com.cleo.customer.edinetsuite.inbound.InboundEDIMN.cloud.monitor must be configured with the trading partner Endpoint setup in CIC. The ReceiveEDIEvent is already configured in the Cloud Monitor to process further.
2. Configure the Inbound Route: The inbound route is setup with Sender ID as the trading partner name and Receiver ID as the customer name supplied in the Wizard properties file (accelerator-input.properties file residing under the resources folder). If there are changes, _TP_820v4010IR residing in com.cleo._customer_.netsuite._tp_.inbound.n820.v4010 package should be modified as required.
3. Configure the 997 Enveloper: The 997 envelope details and the trading partner Endpoint to which the 997 is to be sent should be configured in _TP_997ENV residing in the trading partner project under com.cleo._customer_.netsuite._tp_.outbound.n997 package.

How to Run 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.

1. • com.cleo._customer_.edi
   • com.cleo._customer_.edi.booster.netsuite
   • com.cleo._customer_.edinetsuite
   • com.cleo._customer_.netsuite._tp_
   • com.cleo.b2bcloud.core
   • com.cleo.b2biaas.clarify
   • com.cleo.cic.cockpit.core
   • com.cleo.cic.cockpit.core.n810
   • com.cleo.cic.cockpit.core.n850
   • com.cleo.cic.cockpit.core.n855
   • com.cleo.cic.cockpit.core.n856
   • com.cleo.cic.cockpit.core.n846
   • com.cleo.cic.cockpit.core.n940
   • com.cleo.cic.cockpit.core.n945
   • com.cleo.cic.cockpit.core.n944
   • com.cleo.cic.cockpit.core.n820
   • com.cleo.cic.connector.netsuite
2. Ensure that the cloud monitor com.cleo.b2bcloud.core.cloudMonitor.InboundEDIMN is started. Go to Admin Console > Resource Monitors.
3. Monitor the flow using:
   
   • Log Entries (Studio Auditor)
   • Message Tile View (Cockpit)
   • Jobs View (Cockpit)
   • Dashboard > Charts (Cockpit)  

   In case of errors:

   • If processing fails in any step, a ticket is generated and information is also visible in the Message Tile view and Job view in CIC Cockpit. 

     Example of Cockpit error message tiles

     

     Example of Cockpit error job

     

   • If the Trading Partner configuration is not found, a ticket is created and an optional email alert is generated.
   • If a file fails to process due to invalid EDI syntaxes, a ticket is created and a rejected 997 is sent to the trading partner. 
   • For Outbound EDI validation use cases, see Validation Rules in the Transformation Settings object.

How to Customize

1. Replace the custom fields in the ruleset with your own custom fields
   • If you have any custom fields in your NetSuite instance that you want to use, the Ruleset must be updated.
   • Look for the specific field mapping in the ruleset “_TP_820v4010RS” residing in com.cleo._customer_.netsuite._tp_.inbound.n250.v4010 package. The Cleo-specific custom field is mapped with custbody_cleo_<field id>. Change the same to reflect the corresponding field id.
2. Add more details while creating the Sales Order on NetSuite or add specific business logic while creating the sales order on NetSuite
   • The Sales order on NetSuite is currently created with the data required to process orders successfully. Cleo-defined custom fields have been used to map specific values from the EDI files. The values that are being mapped are documented in the LMS Template X12-NetSuite-Mapping-Spec.xlsx present in the docs folder under the com.cleo._customer_.edinetsuite project. However, if you want to add more fields, the ruleset _TP_820v4010RS must be updated as required.

Contact Cleo Support for assistance when adding Rules.