Merchandise Hierarchy Node Import
NetSuite merchandise hierarchy nodes provide a way to group items in your merchandise hierarchy. You can use the Merchandise Hierarchy Nodes import to import new nodes to an existing merchandise hierarchy version. Before you can import hierarchy nodes, you must first create a hierarchy version and the required hierarchy levels. For more information regarding creating a merchandise hierarchy, see Creating a Merchandise Hierarchy.
To import merchandise hierarchy nodes, set the Import Type to Classification. In the Record Type list, select Merchandise Hierarchy Node.
For details about fields that can be mapped in the merchandise hierarchy node record, see the Records Browser’s merchandise hierarchy node reference page. You can use the field definitions here as a basis for creating your own CSV import template file. For information about working with the Records Browser, see Working with the SuiteScript Records Browser.
Review the following guidelines for Merchandise Hierarchy Node imports:
Supported Merchandise Hierarchy Node Sublist Data Imports
The Merchandise Hierarchy Node import supports the import of the following sublist data:
|
Sublist |
Notes |
|---|---|
|
Hierarchy Versions |
The Included in Version box on the Hierarchy Versions subtab indicates if the hierarchy node is assigned to a hierarchy version. You can assign a node to multiple versions. |
Using Import Assistant for Merchandise Hierarchy Node Mass Update
The following are typical use cases for importing merchandise hierarchy nodes:
-
Initial merchandise hierarchy setup
-
Adding new nodes to a merchandise hierarchy
-
Re-parenting existing nodes in a merchandise hierarchy
Merchandise Hierarchy Node Import Example
The following example shows how you might structure a file for importing merchandise hierarchy node data.
|
Name |
Description |
ExternalID |
VersionID |
LevelID |
p |
IsIncluded |
|---|---|---|---|---|---|---|
|
NORSO |
Company name |
100 |
1 |
1 |
|
T |
|
Women’s Wear |
Women’s apparel department |
101 |
1 |
2 |
100 |
T |
|
Tops |
Women’s upper body apparel |
102 |
1 |
3 |
101 |
T |
|
Bottoms |
Women’s lower body apparel |
103 |
1 |
3 |
101 |
T |
|
Shoes |
Women’s footwear |
104 |
1 |
3 |
101 |
T |
|
Jackets |
Women’s jackets |
105 |
1 |
4 |
102 |
T |
|
Shirts |
Women’s shirts |
106 |
1 |
4 |
102 |
T |
|
Pants |
Women’s pants |
107 |
1 |
4 |
103 |
T |
|
Skirts |
Women’s skirts |
108 |
1 |
4 |
103 |
T |
|
Boots |
Women’s boots |
109 |
1 |
4 |
104 |
T |
|
Sandals |
Women’s sandals |
110 |
1 |
4 |
104 |
T |
To establish the parent node of a node, enter the External ID for the parent node in the parentnodeID column. In the above example, the parent node for Women’s Wear is Norso. The External ID for NORSO is 100, so this is the value entered in the parentnodeID column for Women’s Wear.