# Oracle Fusion Item Class Design Worksheet > Source: https://netray.co/tools/oracle-fusion-item-class-design-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Plan item classes, parent classes, attribute groups and templates before you configure Fusion Product Hub, then export the design to Excel. ## Category oracle ## Erp Oracle Fusion Cloud SCM ## Audience - Oracle Cloud consultant - PIM analyst - Item master data steward ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Item class **Key:** item_class **Type:** text #### Parent class **Key:** parent **Type:** text #### User item type **Key:** item_type **Type:** select **Options:** - Finished Good - Subassembly - Purchased Item - Raw Material - Phantom - Service #### Item number format **Key:** numbering **Type:** text #### Attribute group **Key:** attr_group **Type:** text #### Attributes in group **Key:** attr_count **Type:** number **Format:** integer #### Required attributes **Key:** required_attr **Type:** number **Format:** integer #### Item template **Key:** template **Type:** text #### Catalog category **Key:** catalog **Type:** text #### Required share **Key:** required_pct **Type:** number **Expr:** if(gt(attr_count,0), required_attr / attr_count * 100, 0) **Format:** percent **Rows:** **Item class:** Root Item **Item type:** Finished Good **Numbering:** Free text, max 30 **Attr group:** Common manufacturing **Attr count:** 12 **Required attr:** 4 **Template:** Make Item **Catalog:** Product Categories **Item class:** Machined Part **Parent:** Root Item **Item type:** Subassembly **Numbering:** MP-nnnnnn **Attr group:** Machining specs **Attr count:** 9 **Required attr:** 5 **Template:** Make Item **Catalog:** Machined **Item class:** Purchased Component **Parent:** Root Item **Item type:** Purchased Item **Numbering:** PC-nnnnnn **Attr group:** Supplier data **Attr count:** 8 **Required attr:** 3 **Template:** Buy Item **Catalog:** Purchased **Item class:** Raw Material **Parent:** Root Item **Item type:** Raw Material **Numbering:** RM-nnnnn **Attr group:** Material spec **Attr count:** 7 **Required attr:** 4 **Template:** Buy Item **Catalog:** Materials **Item class:** Service Item **Parent:** Root Item **Item type:** Service **Numbering:** SV-nnnn **Attr group:** Service terms **Attr count:** 5 **Required attr:** 2 **Template:** Service Item **Catalog:** Services **Totals:** #### Total attributes **Key:** attr_count **Agg:** sum **Format:** integer #### Total required attributes **Key:** required_attr **Agg:** sum **Format:** integer #### Item classes **Key:** item_class **Agg:** count **Format:** integer **Summary:** #### Overall required share **Key:** required_overall **Expr:** if(gt(sum_attr_count,0), sum_required_attr / sum_attr_count * 100, 0) **Format:** percent **Primary:** true **Description:** A very high share means item creation will be slow. A very low share means weak data quality. **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the worksheet **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is an item class in Oracle Fusion? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms oracle fusion item class, oracle fusion product hub item class design, oracle fusion item class hierarchy, oracle fusion item template, item master design worksheet, oracle pim item class attributes, oracle fusion item catalog category design, oracle cloud item class setup --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json