Prerequisites for NetSuite <> X12 P2P

1. Create the required connector Projects in your workspace. Use naming conventions as noted in the Initial Setup for Accelerators and Boosters. This must be done prior to running the wizard setup steps.
2. The connector WSDL version year should be 2022 or above.
3. Configure the Cleoprovided Reference Table:
   
   • Deploy these Projects: com.cleo._customer_.booster.netsuite, com.cleo.b2bcloud.core and com.cleo.cic.connector.netsuite
   • Run this Business Process: CreatePartnerRefTableBPS 
   • To verify if the setup is complete, refer to the auditor logs. They will display starting step and completed step information. Any issues (such as driver issues or connection issues) are displayed in the auditor logs, in which case you must take necessary corrective action before running the BPS again.
   • If the process ends successfully, a table named partners will be visible in Cockpit. (In the integrations tab under the Reference tables section)
   • Add the Trading Partner Name and the corresponding Entity Internal ID (configured in NetSuite). For more information see Viewing and Editing Reference Tables in CIC Cockpit.
4. Configure the Item Reference Table:
   • Run the Business Process: CreateNetsuiteItemReferencesTableBPS 
   • To verify if the setup is complete, refer to the auditor logs. They will display starting step and completed step information. Any issues (such as driver issues or connection issues) are displayed in the auditor logs, in which case you must take necessary corrective action before running the BPS again.
   • If the process ends successfully, a table named NETSUITE_Item_References will be visible in Cockpit. (In the integrations tab under the Reference tables section).
   • Launch the Business Process ItemReferenceBPS to populate the table with all values from Netsuite.
   • Deploy these Projects:
     • com.cleo._customer_.booster.netsuite
     • com.cleo.b2bcloud.core
     • com.cleo.cic.connector.netsuite

Configure Staging Database

1. Deploy the following Projects:
   com.cleo._customer_.booster.netsuite
com.cleo.b2bcloud.core
com.cleo.cic.connector.netsuite
2. Run the Business Process CreateNetsuitePOReferenceTableBPS.bps.  Refer to Auditor logs to verify if the setup is complete.   Any issues (such as driver issues or connection issues, etc),are displayed in the logs; if this is the case you must take necessary corrective action before running the BP again.
3. Setup the Process Schedule LaunchNetsuitePOReferencePS.sched to run at the desired frequency. This scheduler object calls the LaunchPOReferenceBPS.bps periodically. By default, the schedule is set to run every 6 hours. Once the purchase orders are ready for confirmation or delivery, PO data is fetched from Netsuite using PO reference data saved search and updated in CIC staging table. This table is auto-cleared in every run of LaunchPOReferenceBPS.bps.
4. Otherwise, you can manually run the LaunchPOReferenceBPS.bps. This BP can be set to run at regular intervals. This process loads data from staged purchase orders and loads key PO reference information into a staging table, which is used by 855, 856, and 810 integration flows. In case the data is not already populated in the table through the scheduled LaunchPOReferenceBPS.bps, then the 855 and 856 process flow calls the LaunchPOReferenceBPS.bps explicitly to add relevant PO data in the table.   More details are described in the PO Reference Data Flow section of the 850 Outbound Flow. 

NetSuite Customizations

The Netsuite Customizations are bundled in a sandbox environment. Support must be requested to get this bundle shared to the customer’s instance by providing the Account Id. Refer to the steps to install the bundle in the Customer instance.

Internal IDs

The internal ids being used in the Saved Search Scripts will have to be modified as per the customer’s instance internal ids. Refert to this example of changing the internal id in the saved search script.

Global Variables

1. Configure B2BCloudAdminEmail (receiver) and B2BCloudHostEmail (sender) variables in com.cleo.b2bcloud.core.B2BCloudGV. These are resolved during failures and email is triggered.
2. NetsuiteVault- This variable contains the vault entry name assigned to the Netsuite connector.
3. The global variables have to be initialized with the internal id of the archival folder. The internal ids of the folders vary depending on the customer’s instance. For example: