Class Metadata
Customers in NetSuite can use Class Planning Category values to group classes into different categories and create their own custom hierarchy. When you import Class metadata to your Planning and Budgeting, the Class Planning Category values are used to build the Class metadata hierarchy.
You can define the Class Planning Category on a class record.
The Class metadata hierarchy is built with the following logic:
-
If a class from NetSuite has a parent, the parent of the class is used in your Planning and Budgeting as the parent.
-
If a class from NetSuite does not have a parent, but has a Class Planning Category, the Class Planning Category is used in your Planning and Budgeting as the parent.
-
If a class from NetSuite has neither a parent nor a Class Planning Category, the top-level class 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
- Customer Metadata
- Department 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