Location Metadata in Planning and Budgeting Sync
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 doesn't 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 to Planning and Budgeting
- Supported Metadata Saved Searches in Planning and Budgeting Sync
- Item Metadata in Planning and Budgeting Sync
- Vendor Metadata in Planning and Budgeting Sync
- Accounts Metadata in Planning and Budgeting Sync
- Class Metadata in Planning and Budgeting Sync
- Customer Metadata in Planning and Budgeting Sync
- Department Metadata in Planning and Budgeting Sync
- Project Metadata in Planning and Budgeting Sync
- Customer Project Metadata in Planning and Budgeting Sync
- Employee Metadata in Planning and Budgeting Sync
- Subsidiary Metadata in Planning and Budgeting Sync
- Custom Segment Metadata in Planning and Budgeting Sync
- Creating the Hierarchy of Metadata in Planning and Budgeting Sync
- Optimal Number of Metadata Records to Import to Planning and Budgeting
- Returning Metadata Hierarchy Based Only on Cloned Saved Search in Planning and Budgeting Sync
- Account Type Mapping in Planning and Budgeting Sync
- Item Type Mapping in Planning and Budgeting Sync