855 Flow: Configuration and Testing

A search request is performed on NetSuite to look for any unprocessed sales order records. If a record is found, it is parsed and the matching outbound route is searched. If there is a match, the NetSuite SalesOrder XML is translated to EDI 855 and sent to the trading partner.

This section explains how to configure the integration to retrieve Sales Orders and transform them to EDI X12 855 format for the Trading Partner.

How to Configure

1. Configure Schedulers. The LaunchNetsuiteOrderAcknowledgementPS Scheduler is part of the com.cleo._customer_.booster.netsuite.orderAcknowledgement.n855 package.  Configure the specific time interval based on your specific requirements. By default, the process is set to run every hour.
2. Configure the Outbound Route. The CustomerInternalId field is used to identify the Trading Partner to whom the OrderAcknowledgment records is to be sent.
3. Configure the Outbound Route. The Entity - Internal ID is used to identify the Trading Partner to whom the Sales Order Acknowledgement should be sent.
4. Configure the Enveloper. The X12 855 envelope details and the trading partner Endpoint to which the X12 855 is to be sent should be configured in _TP_855v4010ENV (found in trading partner project, com.cleo._customer_.netsuite._tp_.outbound.n855.v4010 package).  By default, the customer name and the tp name entered in the Wizard property file are added to the sender id and receiver id, respectively. If there are any changes to the enveloping details, _TP_855v4010ENV must also be updated accordingly.

How to Run Flow

1. Make sure the following Projects have been deployed. If any of these are already deployed and are not modified, they need not be deployed again.
   • 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.n810
   • com.cleo.cic.cockpit.core.n850
   • com.cleo.cic.cockpit.core.n855
   • com.cleo.cic.cockpit.core.n856
   • com.cleo.cic.connector.netsuite
2. Run the flow either manually or automatically: 
   • Manually run the flow using LaunchNetsuiteOrderAcknowledgementBPS in com.cleo._customer_.booster.netsuite.orderAcknowledgement package.  See Starting Objects for details.
   • Automatically run the flow using LaunchNetsuiteOrderAcknowledgementPS, which runs the flow based on the interval specified.
3. Monitor the flow using:
   • Log Entries (Studio Auditor)
   • Message View (Cockpit)
   • Jobs View (Cockpit)
   • Dashboard > Charts (Cockpit)  

• In case of errors, a ticket is generated and information is also visible in the Message and Job views in CIC Cockpit.
• Example of Cockpit error tile
  
• Example of Cockpit error job
  
•  
•  
• For Outbound EDI validation use cases, see Validation Rules in the Transformation Settings object for Outbound EDI validation rules.
•  

How to Customize

1. Change how often orders are retrieved from NetSuite.

   TheLaunchNetsuiteOrderAcknowledgementPS Scheduler (found in the package,  com.cleo._customer_.netsuite.orderAcknowledgement.n855) is configured by default to retrieve orders once every hour. You can change the schedule to run more or less frequently. See Creating and Defining Process Schedules for more info.

2. Add more details to the X12 855 from the NetSuite invoice.

   The values mapped are documented in the Integration Design Specification, which can be found in the com.cleo._customer_.edinetsuite project under the docs folder. However, if you wish to add fields, you must update the _TP_855v4010RS Ruleset in the package, com.cleo._customer_.netsuite._tp_.outbound.nRefactor855.v4010. 

Contact Cleo Support for assistance when adding Rules.