X12 856 - NetSuite P2P

When an inbound 856 is received from the trading partner endpoint, Cloud monitor picks the file and ReceiveEDIEvent tries to find the matching inbound route. If found, the EDI message is translated to Netsuite Inbound Shipment XML and posted to Netsuite.
This section how to configure the integration to process the ASN 856 received from the Trading Partner and create the corresponding Standard Inbound Shipment in NetSuite.

How to Configure

1. Configure the Cloud Monitor: InboundEDIMN present in com.cleo.b2bcloud.core under the package com.cleo.b2bcloud.core.cloudMonitor has to be configured with trading partner endpoint setup in CIC and the ReceiveEDIEvent is already configured in the Cloud Monitor to process further. 
2. 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 (“accelerator-input.properties” file which is residing under “resources” folder). If there are changes, _TP_856v4010IR residing in the com.cleo._customer_.netsuite._tp_.inbound.n856.v4010 package should be modified as per the requirement.
3. 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_.netsuite._tp_.outbound.n997 package.

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.

1. • com.cleo._customer_.edi
   • com.cleo._customer_.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.n856
   • com.cleo.cic.connector.netsuite
2. Configure the Exit Points as follows:

   

3. In case of errors:
   • If the processing fails in any of the steps a ticket would be created and the same is visible in the cockpit message tile and the job with the Issue Flag.

     Below are the screenshots of the cockpit error tile and error job respectively.

     

     

     

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

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 already, and you want to use them then the same has to be updated in the Ruleset.
   • Look for the specific field mapping in the ruleset “_TP_856v4010RS” residing in com.cleo._customer_.netsuite._tp_.inbound.n856.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 to while creating the Inbound Shipment on NetSuite or add specific business logic while creating the Inbound Shipment on NetSuite.
   • The Inbound Shipment on NetSuite is currently created with the required data 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 IDS Template P2P X12 <> NetSuite Mapping Spec P2P present in the docs folder under the com.cleo._customer_.edinetsuite project. However, if you wish to add any additional fields then the ruleset _TP_856v4010RS needs to be updated as per the requirement.
   • Contact Cleo support if you need any assistance while adding additional rules.