SHORT VERSION:
Can you import a sales order, using the Item's InternalID, instead of the "Item (Req)" field - which is susceptible to changes in category hierarchy or item name??
LONG VERSION:
We currently import sales orders into NetSuite from a 3rd party system using a CSV file to hold the data.
We use a hierarchical item list - ie items can be sub-items of other items. (The parent items are only dummy items which we refer to as categories).
E.g. item list looks like:
CLOTHES
- MALE
- - T-SHIRTS
- - - SKU123 Red T-Shirt
When we import sales orders using the import assistant - the "Sales Order Items" area shows the field "Item (Req)" - which we use to identify the item. In this case, the item we want to import looks like this:
CLOTHES : MALE : T-SHIRTS : SKU Red T-Shirt
This all works ok.
BUT - if we change any part of the hierarchy, or item name, it breaks the import process.
E.g. if we change the category "MALE" to now be called "MENS", the import fails as it can't match the full item name.
To me, it doesn't make sense to map things on such a loosely controlled field. The import of items should be able to be done using the InternalID of the Item.
Ie - instead of mapping the imported item as
CLOTHES : MALE : T-SHIRTS : SKU Red T-Shirt
it should simply be the internalID of the item - e.g.
123456
That way when the hierarchy, or item name changes, you don't have to re-create the mapping/export from the 3rd party program.