Configure and run flows in the Orderful – NetSuite integration template

Contents

• Overview: Understanding the Orderful – NetSuite integration template
• Install the Orderful – NetSuite integration template
•  Configure and run flows in the Orderful – NetSuite integration template
  • Orderful purchase orders (850) to NetSuite sales orders
  • Orderful purchase order change requests (860) to NetSuite sales orders
  • NetSuite item shipments to Orderful ship notices/manifests (856)
  • NetSuite invoices to Orderful invoices (810)

Additional record mapping is required to integrate the template’s exports and imports with your Orderful and NetSuite apps.

Note that all of your flows are disabled when first installed. After configuring the flows, you may enable them in your Flows dashboard or in Flow Builder with the Off/On toggle button. then run or schedule each flow.

Orderful purchase orders (850) to NetSuite sales orders

On a scheduled basis, this flow retrieves new Purchase Order transactions (transaction type 850) from Orderful and creates Sales Orders in NetSuite.

Flow details

• Export source: Orderful
• Import destination: NetSuite

• Built-in export: Get Orderful transactions (850 - Purchase orders) – get all transactions from Orderful that have been created since this flow last ran
  • preSavePage hook: Processing orderful transactions(850).js – avoid loops from the nested arrays and store required elements in a single loop
• Built-in import: Import NetSuite sales orders – add (or ignore) sales orders into NetSuite with purchaseordernumber as the lookup identifier
• Built-in import: Import Orderful transaction status – update transaction status into Orderful with id as the lookup identifier

Before you begin

1. Customers should be present in both Orderful and NetSuite.
2. Items should be the same in both Orderful and NetSuite.

Setup instructions

1. Configure static mapping for Shipping Method (InternalId) for your NetSuite configuration in Import NetSuite sales orders.
2. Configure hard-coded mapping for Items : Price Level (InternalId) and Items : Tax Code (InternalId) in Import NetSuite sales orders according to your business rules.
3. Configure dynamic mapping for Items : Item (InternalId) and Customer (InternalId) according to your business rules in Import NetSuite sales orders.
4. Configure hard-coded mapping for statusReason in Import Orderful transaction status according to your business rules.
5. Add Subsidiary mapping according to your business rules in Import NetSuite sales orders.

Field mappings: Import NetSuite sales orders

Field mappings: Import Orderful transaction status

Orderful purchase order change requests (860) to NetSuite sales orders

On a scheduled basis, this flow retrieves Purchase Order Change Request transactions (type 860) from Orderful and updates existing Sales Orders in NetSuite that are in a pending approval/fulfillment status.

Flow details

• Export source: Orderful
• Import destination: NetSuite

• Built-in export: Get Orderful transactions (860_PURCHASE_ORDER_CHANGE_REQUEST_BUYER_INITIATED) – get all transactions from Orderful that have been created since this flow last ran
  • preSavePage hook: Processing orderful purchase order change request (860).js – avoid loops from the nested arrays and store required elements in a single loop
• Built-in lookup: Get NetSuite sales order by purchase order number – get a sales order from NetSuite by purchase order number
• Built-in import: Import NetSuite sales orders – update sales orders into NetSuite with purchaseordernumber as the lookup identifier
• Built-in import: Import Orderful transaction status – update transaction status into Orderful with id as the lookup identifier

Before you begin

1. Purchase orders in Orderful and sales orders in NetSuite should be the same, already synced by running Orderful purchase orders (850) to NetSuite sales orders first.
2. Orderful purchase order numbers should be stored as a PO# in NetSuite sales orders.
3. Items should be the same in both Orderful and NetSuite.

Setup instructions

1. Configure hard-coded mapping for Items : Price Level (InternalId) and Items : Tax Code (InternalId) in Import NetSuite sales orders according to your business rules.
2. Configure dynamic mapping for Items : Item (InternalId) according to your business rules in Import NetSuite sales orders.
3. Configure hard-coded mapping for statusReason in Import Orderful transaction status.

Field mappings: Import NetSuite sales orders

Field mappings: Import Orderful transaction status

NetSuite item shipments to Orderful ship notices/manifests (856)

On a scheduled basis, this flow retrieves new item fulfillments from NetSuite and creates Ship Notice transactions (type EDI 856) in the Orderful platform.

Flow details

• Export source: NetSuite
• Import destination: Orderful

• Built-in export: Get NetSuite item shipments – get all item shipments from NetSuite that have been created since this flow last ran
  • preSavePage hook: Processing Orderful transactions (856).js – counts the number of items to add the numeric count sequentially for hierarchicalIDNumber in the items
• Built-in import: Import Orderful ship notices/manifests (856) – add ship notices/manifests into Orderful
• Built-in lookup: Get Orderful validation by transaction id (856) – get a validation from Orderful by transaction id
  • preSavePage hook: Processing orderful valid transactions (856).js – check whether the transaction is valid or invalid

Before you begin

1. Purchase orders in Orderful and sales orders in NetSuite should be the same, already synced by running Orderful purchase orders (850) to NetSuite sales orders first.
2. Orderful purchase order numbers should be stored as a PO# in NetSuite sales orders. 

Setup instructions

Configure hard-coded mapping for each of the following fields in Import Orderful ship notices/manifests (856), according to your business requirements:

• from:id
• to:id
• type:name
• stream
• N1_loop.partyIdentification.
  entityIdentifierCode
• packagingCode
• weightQualifier
• weight
• unitOrBasisForMeasurementCode
• identificationCode
• identificationCodeQualifier

• transportationMethodTypeCode
• dateTimeQualifier
• hierarchicalIDNumber
• hierarchicalLevelCode
• referenceIdentificationQualifier
• hierarchicalParentIDNumber
• marksAndNumbersQualifier
• numberOfUnitsShipped
• unitOrBasisForMeasurementCode
• productServiceIDQualifier
• hashTotal
• transactionSetPurposeCode

Customize the handlebars template

Follow the instructions below to modify the handlebars template for the Orderful HTTP request body:

1. In Flow Builder, click to edit Import Orderful ship notices/manifests (856).
2. In the Edit import panel, scroll down to the section How would you like the records imported.
3. Under Build HTTP request body, click Launch.
4. In the resulting editor, customize according to your requirements and preview the sample records.

HTTP request body: Import Orderful ship notices/manifests (856)

NetSuite invoices to Orderful invoices (810)

On a scheduled basis, this flow retrieves new invoices from NetSuite and creates Invoice transactions (type 810) in the Orderful platform. 

Flow details

• Export source: NetSuite
• Import destination: Orderful

• Built-in export: Get NetSuite invoices – get all invoices from NetSuite that have been created since this flow last ran
• Built-in import: Import Orderful transactions (810) – add transactions into Orderful
• Built-in lookup: Get Orderful validation by transaction id (810) – get a validation from Orderful by transaction id
  • preSavePage hook: Processing Orderful valid transactions (810).js – check whether the transaction is valid or invalid

Before you begin

1. Purchase orders in Orderful and sales orders in NetSuite should be the same, already synced by running Orderful purchase orders (850) to NetSuite sales orders first.
2. Orderful purchase order numbers should be stored as a PO# in NetSuite sales orders. 

Setup instructions

Configure hard-coded mapping for each of the following fields in Import Orderful transactions (810), according to your business requirements:

• from:id
• to:id
• type:name
• stream
• SAC_loop:servicePromotionAllowanceOrChargeInformation:
  servicePromotionAllowanceOrChargeCode
• SAC_loop:servicePromotionAllowanceOrChargeInformation:
  allowanceOrChargeIndicatorCode
• SAC_loop:servicePromotionAllowanceOrChargeInformation:
  unitOrBasisForMeasurementCode
• PID_loop:productItemDescription:itemDescriptionTypeCode
• baselineItemDataInvoice:unitOrBasisForMeasurementCode
• baselineItemDataInvoice:productServiceIDQualifier
• baselineItemDataInvoice:basisOfUnitPriceCode
• N1_loop.partyIdentification.entityIdentifierCode
• N1_loop:partyIdentification:entityIdentifierCode
• N1_loop:partyIdentification:identificationCode
• termsOfSaleDeferredTermsOfSale:percentOfInvoicePayable
• termsOfSaleDeferredTermsOfSale:termsBasisDateCode
• termsOfSaleDeferredTermsOfSale:deferredAmountDue
• termsOfSaleDeferredTermsOfSale:termsTypeCode
• referenceInformation:referenceIdentificationQualifier
• transactionSetHeader:transactionSetIdentifierCode
• carrierDetails:standardCarrierAlphaCode
• dateTimeReference:dateTimeQualifier

Customize the handlebars template

Follow the instructions below to modify the handlebars template for the Orderful HTTP request body:

1. In Flow Builder, click to edit Import Orderful transactions (810).
2. In the Edit import panel, scroll down to the section How would you like the records imported.
3. Under Build HTTP request body, click Launch.
4. In the resulting editor, customize according to your requirements and preview the sample records.

HTTP request body: Import Orderful transactions (810)