On a scheduled basis, the flow gets the purchase order change request transactions from the source and updates the sales order in NetSuite. The flow looks for the purchase order details from the purchase order ID, trading partner, and ISAID fields. The flow only updates the purchase order details on the NetSuite sales order and does not create any records.
- If an order is found in NetSuite with any other status, the flow fails the record and reports these records as errors in the integrator.io dashboard.
- If the order is not found, an error message is shown removes the transaction from the polling bucket, and reports the error count for that specific transaction in the dashboard.
- If one of the existing lines on the NetSuite sales order is not in the purchase order change request, the flow ignores the line as the EDI 860 only contains the updated details.
Note
For quantity changes, the purchase order change request contains the updated number and this is a replacement of the initial quantity provided as part of the purchase order and not an adjustment.
If you configure multiple sources, the flow syncs the purchase order change request from all sources to NetSuite
Important
- Sales orders must be already created in NetSuite.
- The respective items must exist in the trading partner source and NetSuite.
- The Send EDI Acknowledgement and Synced EDI Acknowledgement boxes must be unchecked on the Purchase orders (850) to NetSuite sales orders (add) flow. If the box is checked, the flow unchecks the Send EDI Acknowledgement and Synced EDI Acknowledgement boxes, so that this record is manually qualified for the next flow run (acknowledgment sync).
Export source: Trading partner source
Import destination: NetSuite
Built-in import: Post NetSuite sales orders (update) – updates the sales orders and generates to NetSuite.