X12 855

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 Process Schedulers. The LaunchNetsuiteOrderAcknowledgementPS Scheduler is part of the com.cleo._customer_.booster.netsuite.orderAcknowledgement package.  Configure the specific time interval based on your specific requirements. By default, the process is set to run every hour.
2. Configure NetSuite.
   If the SalesOrder is supposed to be converted to EDI and then sent to the Trading partners from all available sales orders in NetSuite, then ensure that the custom field custbody_cleo_source_status contains the keyword PENDING_ in its value. Note:  Only Sales Orders in pendingFulfillment and canceled status will be searched for.
3. Configure the Outbound Route.
   The Entity - Internal ID is used to identify the Trading Partner to whom the Sales Order Acknowledgement is to be sent. The ID is used in the look-up against the table partners to find the Trading Partner name. If the Trading Partner name does not match the tpname while creating the project using Wizard, you must update the Outbound Route to reflect the matching name in _TP_855v4010OR (found in the com.cleo._customer_.netsuite._tp_.outbound.n855.v4010 package).
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.

Prerequisites - Folder Internal IDs and Names, Global Variables

After configuring the outbound 855 flow, the following prerequisites must be met before running.

• Folder Internal IDs. The Folder internal IDs being used in the Saved Search Scripts must be modified per the customer’s instance internal ID. The saved search script ID used for 855 is customscript_cleo_sch_855_oa_script.
• Folder name in saved document search. In addition to updating folder internal IDs, you must update the folder name under the criteria tab in the saved document search so that it points to the appropriate transaction folder name. The saved search ID used for 855 is customsearch_cleo_ss_855_getcsvfile.
• Configure Global Variables with Archive Folder Internal ID. Global Variables must be initialized with the internal ID of the archival folder as per the customer instance. For 855, update the Global Variable for AcknowledgementArchiveFolder.

Please see specific details for updating the NetSuite script for the steps noted above.

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_.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 Process Scheduler (found in the package,  com.cleo._customer_.netsuite.orderAcknowledgement) 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.