When importing errors, you may encounter an error message from NetSuite. These messages are reported directly from NetSuite and are not generated by FarApp. Here are the explanations behind common errors and how to resolve them:
ERROR: INVALID_KEY_OR_REF – Invalid item reference key …
- This error is reported because one of three reasons:
- There is no matching SKU in NetSuite – please make sure that there are matching SKUs in NetSuite for every item on the order.
- There is a duplicate SKU in NetSuite – FarApp (like many other systems) requires that there be a unique item in NetSuite for each SKU. If you have more than one item with the same SKU, then FarApp can’t identify which item to post the order against.
- The item is inactive in NetSuite – NetSuite doesn’t allow posting orders against inactive items. If you don’t want the item to be active, you’ll need to activate it in order to allow NetSuite to accept the order, and then deactivate the item again.
ERROR: USER_ERROR - Please configure the inventory detail for this line.
- "Inventory Details" are a set of fields in NetSuite that need to be populated on Sales Orders/Cash Sales when an item on an order is a Lot Controlled, Bin Controlled or Serialized item.
- This error usually indicates that you don't have the inventory detail configured for the item in NetSuite. Once you configure the inventory detail for the item in NetSuite, you should be able to import the order. NetSuite provides functionality for automatically populating the inventory detail on orders. We believe the two options available are to either have your Sales Order/Cash Sale form pre-populated with the inventory details you need, or to use a script to populate the inventory detail. You should consult NetSuite for either option.
- It is also possible that you do have the inventory details configured but that the lot/bin you are trying to use is out of inventory for the item on the order and you will need to replenish this stock for the order to post.
- If none of the solutions in the points above work for you, FarApp can select the first available lot/bin at given location, or a specific bin at a given location. This will apply to all your orders. If this solution will work for you, please open a ticket with us describing which solution you want to use and providing a sample order to work with as we create the mapping to accomplish this for you. Please note that if you require unique bins to be selected on each order, somehow the storefront will have to communicate which bin to select on the order, since otherwise FarApp would have no way of knowing which one to select. This would mean you need to communicate to the storefront which lot/bin a given item is in. We believe this is not possible for most storefronts.
ERROR: TRANS_UNBALNCD — Transaction was not in balance.
- This is an Avalara/NetSuite configuration issue. It appears to be a common problem that comes up when setting up Avalara to handle taxes in NetSuite.
- Please see this article that Avalara provides: https://help.avalara.com/kb/NetSuite_-_Knowledge_Base/Why_am_I_getting_%22Transaction_was_not_in_balance.%22_in_NetSuite%3F
ERROR: INVALID_KEY_OR_REF – Please enter a value for amount.
- Usually this issue appears when testing order sync when the connector has not been activated. Activating the connector usually fixes this error. Activating the connector does not start the billing cycle. Turning on Order, Fulfillment or either of the product sync options will start the billing cycle (buttons will appear to turn these options On/Off once the connector is activated).
ERROR: Invalid record type 
- We have found that this always is an error in a script on the NetSuite end. Please take a look at any scripts you might have running.
ERROR: UNEXPECTED_ERROR - An unexpected error occurred. Error ID:...
Anytime you see an UNEXPECTED_ERROR, it's an error code that NetSuite support can look up. Most of the errors of that sort that FarApp has seen are one of the following cases:
1) A NetSuite outage or bug.
2) A script in NetSuite that's erroring.
3) A bad mapping like a string for a record ref/select field (that requires a numeric or other type of value).
Since NetSuite upgraded a bunch of accounts to 2016.2 on 9/16/16 we have seen some customers with scripts that are not compatible with some changes made in 2016.2 so it's triggering an error. If you contact NetSuite support with the Error ID, they should be able to tell you where exactly the issue is.
An Order Wants You to Enter a Payment Method, But a Payment Method has Already Been Mapped
- This can occur if an order is posting to an existing customer in your NetSuite. Please check whether the existing customer record has a default credit card. If so, you will need to remove this so that the payment method FarApp is trying to send to your NetSuite can take effect.