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