Configure and run the flows in NetSuite procure to pay: EDI for B2B Manager template

Built-in NetSuite export

Get purchase orders – This built-in template step gets new purchase orders from NetSuite.

You can configure the export settings if required.

Create an import to an EDI trading partner, or use an existing one based on your scenario

Post orders to import/destination app – Create an import using a trading partner, AS2, FTP, or VAN connection. To create the import, see also EDI flows.

Create an export from an EDI trading partner, or use an existing one based on your scenario

Get purchase order acknowledgments – Create an export using a trading partner, AS2 FTP, or VAN connection to get the purchase order acknowledgments. To create the export, see also EDI flows.

Add a transformation: You must add a script, EDI 855 to NS Purchase Order, to transform the exported data (EDI JSON) to canonical JSON format for the next step.

1. In the export, click the Actions (...) menu, then the Transformation option.

2. In the Define transformation page, at the top right corner select JavaScript.

3. Click the plus sign (+) next to the script settings to add a new script.

4. In the Create script page, enter a name for your script – for example, EDI 855 to NS Purchase Order. 

5. In the Edit content box, copy and paste this EDI 855 to NS Purchase Order script. Click Save.

6. In the Define transformation page, in Script, select the script you created above. 

7. Click Save. 

Built-in NetSuite import

Update purchase orders - This built-in template step updates purchase orders in NetSuite based on the purchase order acknowledgments from the EDI trading partner. The step includes a preMap hook and mappings that help to update the NetSuite purchase orders.

You can configure the import settings in NetSuite if required.

Create an export from an EDI trading partner, or use an existing one based on your scenario

Get advance shipment notices – Create an export using a trading partner, AS2 FTP, or VAN connection to get the purchase order acknowledgments. To create the export, see also EDI flows.

Add a transformation: You must add a script, EDI ASN 856 to NS Item Fulfilment, to transform the exported data (EDI JSON) to canonical JSON format for the next step.

1. On the export, click the Actions (...) menu, then click the Transformation () option.

2. In the Define transformation page, at the top right corner select JavaScript.

3. Click the plus sign (+) next to the script settings to add a new script.

4. In the Edit content box, copy and paste the EDI ASN 856 to NS Item Fulfilment script. Click Save.

5. In the Define transformation page, in Script, select the above script you created. 

6. Click Save. 

Add a Pre save page hook – You must create/add a PreSave page hook.

1. On the export, click the Pre save page hook () option.

2. In the Hooks page, the Scripts option is selected by default.

3. In Scripts, select the script that you had earlier created. That is, EDI ASN 856 to NS Item Fulfilment script.

4. Click Save.

Built-in NetSuite lookup

Lookup purchase orders - This built-in template step looks up NetSuite IDs with the status as Shipped in purchase orders. The step includes results mapping. The lookup data is then modified using the included post-response map hook.

You can configure the lookup settings if required.

Built-in NetSuite import

Create item fulfillment – This built-in template step creates item fulfillment in NetSuite for the shipped items. The step includes a pre-map hook and a mapping of the results.

You can configure the import settings if required.

Built-in NetSuite import

Update NetSuite item fulfillment – This built-in template step updates the item fulfillment with a transaction number. Based on the input filter, only records with a REF_CN or Reference Identification move to this step. The step includes mapping in which the reference identification is mapped to the package tracking number.

You can configure the import settings if required.

Create an export from an EDI trading partner, or use an existing one based on your scenario

Get invoice – Create an export using a trading partner, AS2 FTP, or VAN connection to get the EDI invoice. To create the export, see also EDI flows.

Add a transformation: You must add a script, EDI Invoice 810 to NS Vendor Bill, to transform the exported data (EDI JSON) to canonical JSON format for the next step.

Built-in NetSuite import

Create vendor bill – This built-in template step creates vendor bills to NetSuite for the EDI invoices. The step includes a mapping of the results.

You can configure the import settings if required.

Built-in integrator.io export

Listen for completed inbound flows – This built-in template step listens for completed inbound flows, based on the export step in which the listener is included and gets the 997 docs. For details, see Generate functional acknowledgment for an EDI X12 transaction

Create an import

Post functional acknowledgments – Create an import to send these 997 docs from the Celigo platform to the EDI trading partner. To create the import, see Generate functional acknowledgment for an EDI X12 transaction

Create an export

Get functional acknowledgments – Gets the 997 docs from the EDI trading partner. To create the export, see Reconcile functional acknowledgment for an EDI transaction

Built-in integrator.io import

Update transaction status in dashboard – This built-in template import step sends the 997 docs to the Celigo platform to reconcile them and updates the dashboard. For details, see Reconcile functional acknowledgment for an EDI transaction