Implementing Manufacturing and Materials Management: From Empty Plant to Costed Work Order · Module 7 · Items and the Item Model
Building item classes
Lesson 67 of 188 · 13 min
Open the item class hierarchy from Product Information Management. Create second-level classes per the design — purchased, manufactured, finished good — set inheritance and show attributes flowing down, configure which attributes are required per class, set item class security for one class, and show the resulting hierarchy. Inheritance is what keeps the hierarchy small. Define once at the top. Required attributes are a data quality control. Use them — but only for values that genuinely must be present at creation. Over-requiring at creation is how a data steward ends up typing placeholder values. Class security is how you separate engineering data from commercial data, which is one of the lab's acceptance criteria.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Manufacturing and Materials Management: From Empty Plant to Costed Work Order, with a certificate on completion and a fourteen-day refund window.
In this module: Module 7 · Items and the Item Model
- 1What we are building
- 2Why the item model is permanent
- 3The item object model
- 4Master versus organization attributes
- 5Designing the class hierarchy
- 6Item numbering
- 7Building item classes
- 8Item templates
- 9Creating items manually
- 10The attributes that matter most
- 11Assigning items to organizations
- 12Item statuses and lifecycle phases
- 13Importing items in bulk
- 14Data quality before migrationFree preview
- 15What breaks
- 16Lab briefing: the Halden item model
- 17Lab solution walkthrough