Oracle Fusion Item Class Design Worksheet
Item classes in Oracle Fusion Product Information Management decide which attributes an item carries, how it behaves and how easy it is to maintain. This worksheet lets you design the hierarchy on paper first so changes after go live stay small.
| Item class | Parent class | User item type | Item number format | Attribute group | Attributes in group | Required attributes | Item template | Catalog category | Required share | |
|---|---|---|---|---|---|---|---|---|---|---|
33.3% | ||||||||||
55.6% | ||||||||||
37.5% | ||||||||||
57.1% | ||||||||||
40% |
Template names and class names in the sample rows are placeholders for a discrete manufacturer. Replace them with your own design, and verify the available item types and templates in your pod.
Review your item master design
Optional: get a short expert review of your class hierarchy and attribute plan before you configure it.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List one row per item class and attribute group. Fill in the parent class, the item type, the numbering approach, the template that sets defaults and the catalog category that will classify items. The sheet calculates the required attribute share per row and overall. Review it with engineering, purchasing and finance together, because each group cares about different attributes and nobody likes the default answer when it is set by the loudest voice.
Principles for good item class design
Keep the hierarchy shallow. Child classes inherit attributes from parents, so put shared attributes high and specialized ones low. Split classes only when attributes or behavior truly differ, not to mirror a legacy numbering scheme. Separate item behavior, which templates control, from classification, which catalogs and categories control. Mixing them is the commonest source of rework.
- Shared attributes live in the parent class
- One purpose per attribute group
- Templates set operational defaults
- Catalog categories carry classification and reporting
Reading the required share
If every attribute is required, item creation becomes a bottleneck and users enter filler data. If almost none are, you lose the structure you built the classes for. A rough range of one quarter to one half required per group is a reasonable starting point for design discussion, not a rule. Use the share to find classes that deserve a second look.
Common mistakes
Do not design classes around the legacy system's categories without questioning them. Do not create a class for every product family before you know which attributes differ. Do not forget the migration impact: each class needs a mapping in your FBDI item loads, so a redesign after the first mock load costs real time. Freeze the design before data load rehearsal begins.
Frequently Asked Questions
What is an item class in Oracle Fusion?
An item class is a category of items in Product Information Management that defines which attribute groups and attributes apply, and can drive item creation behavior. Classes sit in a hierarchy, and children inherit from their parents.
How is an item class different from a catalog category?
Item classes control the structure and attributes of the item record. Catalog categories classify items for purposes such as purchasing, planning or reporting. An item has one class but can belong to categories in several catalogs.
How many item classes should we have?
As few as satisfy your attribute differences. Many successful designs have a modest number of classes with shared parents, rather than one class per product family. Add classes when attributes or behavior genuinely differ.
Can we change the item class design after go live?
Some changes are possible, but structural changes touch existing items, integrations and loads. Treat the design as a controlled decision and test any later change in a non-production pod with real data volumes first.
If you are cleaning a legacy item master before migration, Netray can help classify and de-duplicate part descriptions with private AI on your own infrastructure. This worksheet stands on its own.
Related Tools
Oracle Fusion FBDI Template Field Guide
Map every FBDI column to its source, rule and owner before you load. Editable worksheet that exports to Excel.
OracleOracle Fusion Role Provisioning Worksheet
Plan who gets which Fusion job role, with which data access, who approved it and whether it raises a segregation of duties concern.
OracleOracle Fusion Work Order Statuses Reference
Look up what each Oracle Fusion Manufacturing work order status means, what you can do in it, and which status usually comes next.
OracleOracle Fusion Supply Planning Checklist
Work through plan setup, data collection, item and sourcing attributes, plan runs and exception review for Fusion Supply Planning.
More Oracle tools
See all- Oracle Fusion BI Publisher Report Specification Template
- Oracle Fusion Quarterly Update Test Checklist
- Oracle Fusion Cloud SCM Fit Gap Worksheet
- Oracle Fusion Data Migration Mapping Worksheet
- Oracle Fusion Cutover Plan Worksheet
- Oracle Fusion Inventory Organization Design Worksheet
- Oracle Fusion SCM UAT Test Script Template
- Oracle Fusion SCM Implementation Statement of Work Template
- Oracle Fusion FBDI Load Time Estimator