The sales Manager of an eCommerce manufacturer/supplier wants new purchase orders placed by the retailer to be synced to NetSuite. This is to ensure approval of the orders and pass along approved orders to downstream teams/departments for fulfillment and invoicing.
Generates the purchase orders (EDI transaction 850) from the trading partner source to NetSuite as sales orders. This is a batch flow that gets the purchase order transactions on a scheduled basis from the trading partner source. In integrator.io, the transaction is transformed from EDI JSON to NetSuite JSON using the source bubble.
The flow looks for the corresponding order in NetSuite that matches the purchase order ID. By default, the flow uses the purchase order ID, trading partner, and ISAID field details on the NetSuite sales order to store the purchase order ID and trading partner ID.
-
If an order is found in NetSuite, the flow ignores the purchase order and the ignore count is shown as 1 on the Flow Dashboard.
-
If the order is not found, the flow creates the sales order in NetSuite with the default status as “Pending Approval”. The success count is shown as 1 on the Flow Dashboard.
You can change the default status of the sales order to be created in NetSuite using the order status mapping.
Important
-
Customers and items must already be synced to NetSuite.
-
Map shipping and payment methods between source and NetSuite.
Export source: Trading partner source
Import destination: NetSuite
Built-in import: Post NetSuite sales orders (add) - adds or ignores to generate the sales orders to NetSuite.
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.
An Account Receivables (AR) analyst of an eCommerce manufacturer/supplier wants invoices created in NetSuite against successfully shipped orders to sync directly to the EDI Source system and notified of the payment and records are closed.
On a scheduled basis the flow gets the invoices from NetSuite since the last flow run. The flow creates an invoice (EDI transaction 810) in the trading partner source app. In NetSuite, on the invoice, the custom field Synced EDI Invoice must be checked for the flow to pick invoices.
Important
-
Sales orders must exist in NetSuite
-
Map shipping and payment methods between source and NetSuite
Export source: NetSuite
Import destination: Trading partner source
Built-in export: Get NetSuite invoices - get all invoices from NetSuite where the “Synced EDI NS invoice” field is unchecked.
As a Sales Manager/Warehouse Manager of a manufacturing company, I want to send the Purchase Order acknowledgments from NetSuite against the Purchase Orders created directly in the source system.
Generates the purchase order acknowledgments based on the NetSuite sales order status as purchase order acknowledgments (EDI transaction 855) to the trading partner source. This scheduled flow picks the sales orders created since the last flow run. If the Send Acknowledgment to EDI TP box is checked on the NetSuite sales order, the flow gets all the sales orders that are acknowledged and creates purchase order acknowledgments to the trading partner source app. The flow generates acknowledgments only for the orders that have the Send EDI acknowledgment box checked and the Sycned EDI acknowledgment box unchecked.
If a new purchase order change request is created for a sales order after the acknowledgment is sent, a new acknowledgment should be sent again for these orders with the updated details. If there is no acknowledgment sent before the purchase order change request, only one acknowledgment must be sent with the updated details. The flow sends the acknowledgment for an order with multiple line items. The flow syncs multiple acknowledgments for different orders in a single flow run.
Important
Sales order must exist in NetSuite
Export source: NetSuite
Import destination: Trading partner source
Built-in export: Get NetSuite sales order - gets all sales orders from NetSuite where the “Synced EDI NS acknowledgment” field is unchecked.
A Warehouse Manager of an eCommerce manufacturer/supplier wants shipped orders in NetSuite to sync directly to the trading partner source as the order fulfillment completion.
Generates the item fulfillment from NetSuite as advanced ship notice (EDI transaction 856) to the trading partner source. The scheduled flow gets the fulfillment records with the status as Shipped in NetSuite. The Synced EDI fulfillment field must be checked on the NetSuite item fulfillment. This is a once-exported scheduled flow. Before you generate the fulfillment, make sure to sync the sales order.
The supported items are:
-
Inventory Item
-
Simple items
-
Lot Numbered items
-
Serialized items
-
Bin
-
-
Matrix Items
If there are multiple fulfillments, the flow should not export until the whole order is fulfilled. The flow checks the once-used custom field on the item fulfillment record in NetSuite, once it's exported. You can uncheck the once field and should be able to export the fulfillment again when there is some error to a particular Ship Notice. The 856 Ship Notice created in Orderful contains all the details of the Shipment which has info regarding the Ship Date, Tracking Numbers, Ship Address, Ship Carrier, etc.
Export source: NetSuite
Import destination: Trading partner source
Built-in export: Get NetSuite item fulfillment - get item shipments from NetSuite where the “Synced EDI NS shipment” field is unchecked.
Built-in lookup: Get NetSuite item fulfillment packaging details - get packaging details for NetSuite item shipment.
Generates the functional acknowledgments in integrator.io and sends them to the trading partner source as functional acknowledgments (EDI transaction 997). A functional acknowledgment is generated on a successful run of the Purchase orders (850) to NetSuite sales orders (add) and Purchase order change requests (860) to NetSuite sales orders (update) flows.
Built in export: Get functional acknowledgments
Comments
0 comments
Article is closed for comments.