X12 855 - NetSuite P2P

When an inbound 855 is received from the trading partner endpoint, the Cloud Monitor picks the file and ReceiveEDIEvent tries to find the matching inbound route. If the matching inbound route is found, the  855 EDI message is translated to the email body and an email is sent out to the vendor’s mail ID. 855 data is not inserted in Netsuite.

This section explains how to configure the integration to process Order Acknowledgement 855 and create the corresponding email. 

If customers do not want to receive an email for Acknowledged 855s, for example, BAK02= AC (Acknowledge - With Detail and Change), then ruleset _TP_855v4010RS.ruleset can be modified so that when BAK02 = AC, the environment flag is set to ‘No’.

In Inbound855RouteBPS.bps Route BPS, read the flag value. If flag value = ‘NO’ then skip the ‘Send Email task’.

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 global variable: By default, the email is being sent to the Purchase Order creator’s mail address. If the customer wants the mail to be sent to another mail Id, they can do so by providing the other mail Id in the global variable Email_Id_855. The global variable is set to dummy@cleo.com by default.

   

   

3. 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 in the resources folder). If there are changes, _TP_855v4010IR residing in the package com.cleo._customer_.netsuite._tp_.inbound.n855.v4010 should be modified as required.
4. 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 the package com.cleo._customer_.netsuite._tp_.outbound.n997.

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.n855
   • com.cleo.cic.connector.netsuite

   If any of the projects are already deployed and are not modified, they need not be deployed again.

2. Configure the Exit Points as shown below.

   

3. Configure Email_id: The Email_Id_855 global variable will be present in the Admin Console > Global Variables tab. The email global variable has a dummy value by default. 
4. Ensure that the Cloud Monitor com.cleo.b2bcloud.core.cloudMonitor.InboundEDIMN is started. Go to Admin Console -> Resource Monitors.

How to monitor the flow

1. Monitor the flow using the following:
   • Auditor log entries. See Using the CIC Studio Auditor for more information.
   • Message Tiles
   • Jobs
   • Dashboard > Charts
2. In case of errors
   • If the processing fails in any of the steps a ticket is 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.