A search request is performed on NetSuite to look for any unprocessed invoice records. If the record is found, it will be parsed and the matching Outbound Route is searched. If the record is a match, then the NetSuite Invoice XML is translated to EDI 810 and sent to the trading partner.
This section explains the settings required to configure the integration between NetSuite to retrieve the Invoices and transform the same to EDI X12 810 format for the Trading Partner integration.
How to Configure the Flow
- Configure Schedulers: LaunchNetsuiteInvoicePS. This can be found in the
com.cleo._customer_.booster.netsuite.invoice
package. It is scheduled to run every 1 hour. Configure the specific time interval based on your specific requirements. - Configure NetSuite. If the Invoice is to be converted to EDI and then sent to the Trading partners from all the available invoices in the NetSuite, then the custom field custbody_cleo_source_status should contain the keyword
PENDING_
as its value. - Configure the Outbound Route. The Entity - Internal ID is used to identify the Trading Partner to whom the Invoice should be sent.
The internal 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 created when creating the project using the Wizard, update the Outbound Route to reflect the matching name in _TP_810v4010OR (found in thecom.cleo._customer_.netsuite._tp_.outbound.n810.v4010
package) - Configure the EDI Enveloper. The X12 810 envelope details and the trading partner endpoint to which the X12 810 has to be sent should be _TP_810v4010ENV (found in trading partner Project -
com.cleo._customer_.netsuite._tp_.outbound.n810.v4010
package). By default, the Customer name and the TP Name that is entered in the Wizard property file is added to the sender and receiver id respectively. If there are any changes to the enveloping details, the object must also be updated accordingly.
How to Run the Flow
- 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_.edi.accelerator.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
- Manually run the flow using LaunchNetsuiteInvoiceBPS. This can be found in the
com.cleo._customer_.booster.netsuite.invoice
package. (OR) Automatically run the flow using LaunchNetsuiteInvoiceBPS, which runs the flow based on the interval specified. - 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 Tile with error
Example of Cockpit Job with error
- For Outbound EDI validation use cases, see Validation Rules in the Transformation Settings object for Outbound EDI validation rules.
How to Customize
- Change the intervals of retrieving Sales Orders from NetSuite.
- The LaunchNetsuiteInvoicePS scheduler can be found in the
com.cleo._customer_.booster.netsuite.invoice
package and is currently configured to retrieve Sales Orders once each hour. Change the schedule to run more frequently or less frequently based on your requirements . See Creating and Defining Process Schedules for more information. - Add more details to the X12 810 from the NetSuite invoice. The values mapped are documented in the Integration Design Specification, which can be found in
com.cleo._customer_.edinetsuite
Project under the docs folder. However, if you wish to add any additional fields, then you must update the _TP_810v4010RS Ruleset, which can be found in the following package:com.cleo._customer_.netsuite._tp_.outbound.n810.v4010
.
Contact Cleo Support for assistance with adding Rules.
Comments
0 comments
Please sign in to leave a comment.