Location Metadata
Customers in NetSuite can use NSPB Location Planning Category values to group locations into different categories and create their own custom hierarchy. When you import Location metadata to your Planning and Budgeting, the NSPB Location Planning Category values are used to build the Location metadata hierarchy.
You can define the NSPB Location Planning Category on a location record.
The Location metadata hierarchy is built with the following logic:
-
If a location from NetSuite has a parent, the parent of the location is used in your Planning and Budgeting as the parent.
-
If a location from NetSuite does not have a parent, but has an NSPB Location Planning Category, the NSPB Location Planning Category is used in your Planning and Budgeting as the parent.
-
If a location from NetSuite has neither a parent nor an NSPB Location Planning Category, the top-level location is used in your Planning and Budgeting as the parent.
Related Topics
- Metadata Export in Planning and Budgeting Sync
- Supported Metadata Saved Searches in Planning and Budgeting Sync
- Item Metadata
- Vendor Metadata
- Accounts Metadata
- Class Metadata
- Customer Metadata
- Department Metadata
- Project Metadata
- Customer Project Metadata
- Employee Metadata
- Custom Segment Metadata
- Creating the Hierarchy of Metadata in Planning and Budgeting Sync
- Optimal Number of Metadata Records to Import
- Returning Metadata Hierarchy Based Only on Cloned Saved Search
- Account Type Mapping
- Item Type Mapping