2A. Item catalogue modelling, review and assembly BOMs
Model each item of supply with the correct commodity, usage, quantity and traceability controls, then independently approve the item and any assembly structure before operational use.
Purpose
Model each item of supply with the correct commodity, usage, quantity and traceability controls, then independently approve the item and any assembly structure before operational use.
Company Administrator, Materials Planner, different QA Head, Auditor
E2E-CAT-NUT-M8 bulk nut; E2E-CAT-BOLT-M8 batch bolt; E2E-CAT-SEAL-142 batch shelf-life material; E2E-CAT-BEARING-S serialized part; E2E-CAT-ACT-ASM serialized assembly; E2E-CAT-TW-120 calibrated tool; E2E-CAT-RIG-01 serialized asset.
Before you begin
- Flow 01 security and named-user separation are available
- Materials Planner has item write access
- A different QA Head has item approval access
- Only fictitious catalogue identities are used
Catalogue modelling concepts
A tenant-owned parent/child structure such as Fasteners › Nuts or Fasteners › Bolts. The category selects the typed specification template; it is not the tracking policy.
A read-only, clearance-filtered structure explorer that connects each visible category to its item identities, control contract, preferred BOM, reverse assembly usage, effectivity, supersession and approved alternates. It never creates or changes inventory.
A revisioned supply-chain role: raw material, semifinished, finished product, trading good, spare part or operating supply. New common data must have a selected type before submission/approval; untouched retained records are not silently reclassified. This role does not yet implement configurable SAP material-type quantity/value/view controls or nonstock/service processes.
Common composition/grouping fields, exact net/gross weight, volume and dimensions with active dimension-correct units. Measurements are per base unit; gross cannot be less than net. Changes require the existing item-revision approval workflow. Changing the base unit also requires explicit review of retained per-base-unit measurements.
Unique valid language tags, short names and optional descriptions. The canonical item name remains the fallback. Manual entry, governed Basic Material Data JSON import and revision evidence retain the same values.
The access-clearance level, separate from technical classes or category specifications. Historical definitions require sufficient clearance for both the current item and the stored snapshot.
What the identity is: PART, MATERIAL, ASSEMBLY, TOOL or ASSET. Nature is independent of whether the item is consumed, returned or repaired.
How the item is normally handled: CONSUMABLE, RETURNABLE or REPAIRABLE.
The single unit used for stock-ledger arithmetic and its allowed decimal places. Serialized identities require EA and whole quantities.
An item-specific alternate unit such as 1 BOX = 100 EA. Source documents retain the entered unit and factor while stock posts in the base unit.
NONE for untracked bulk, BATCH for lot-controlled quantity, SERIAL for one identity per whole EA, or BATCH_AND_SERIAL when both are mandatory.
A manufacturer, registered supplier, customer or legacy number linked to the controlled internal item, optionally with CAGE and revision.
Category-defined TEXT, NUMBER, BOOLEAN, DATE or ENUM values. Required fields and allowed options are enforced before approval.
New and materially edited records are non-operational DRAFTs. Submission records the maker; a different authorised user must approve or reject.
Open the exact historical definition from Catalogue Governance. The server verifies its checksum and scope before returning data; original physical values and descriptions are not replaced by current draft values.
An approved definition is never edited in place. Create next revision draft clones it under a human-confirmed unique code while Moduvio assigns the immutable UUID, sequence, checksum, actors and timestamps; the approved predecessor stays addressable until the new revision is independently approved and supersedes it for new use.
A versioned, independently released component structure with normalized quantities, optional scrap, references and optional lines. Direct and indirect cycles are rejected.
Add item is the one-record planner path and produces a DRAFT. Governed XLSX is the migration-administrator bulk path with mapping, row errors, DRY RUN and atomic COMMIT; imported records enter REVIEW_REQUIRED.
Both paths reject duplicate part numbers. XLSX is create-only and never overwrites an existing item; use audited Item Master Edit for updates, which reopens catalogue review.
Items and Opening Stock are separate executable sheets and summary counts. Delete the supplied Opening Stock example for item-only import; an item COMMIT alone creates no ledger or current-stock balance.
Procedure
- 1
Start in Catalogue map. Select Fasteners and confirm its Nuts and Bolts descendants appear; select an item and follow the visual category → identity → approval → BOM/lifecycle structure before creating or editing anything.
- 2
Confirm categories and specification templates before creating items. Use Fasteners › Nuts/Bolts for the sample hardware and the dedicated Materials, Assemblies, Tools and Assets categories for the remaining identities.
- 3
Create the sample items and assign nature, usage, base unit, precision and tracking independently. Demonstrate that a bolt can be BATCH controlled while a nut may be untracked bulk, and that a serialized repairable part is still a PART rather than an ASSET.
- 4
Add the BOX-to-EA conversion and manufacturer/supplier references to the hardware. Complete every required typed specification and set shelf life or calibration frequency only where applicable.
- 5
Submit each item revision. Confirm the submitter cannot approve it; use a different QA Head to approve valid records and reject one deliberately incomplete draft without making it operational.
- 6
From an approved sample choose Create next revision draft, enter revision B and confirm immutable A remains separately visible and operational during B review. Approve B as a different QA Head, then confirm A is SUPERSEDED rather than rewritten and that stock and traceability remain broken down by exact revision, with any unverifiable historical quantity labelled Legacy unpinned.
- 7
Create the serialized assembly BOM from approved components. Enter component quantities in base or valid alternate units, verify normalized quantities, then test self-release and cycle rejection before independent release.
- 8
For bulk migration, download the governed workbook and replace every supplied E2E row. Delete the Vendor and Opening Stock examples for an item-only run, rename one test header, inspect automatic mapping, correct it explicitly and revalidate.
- 9
Introduce one invalid JSON value and one duplicate part number in a disposable copy. Confirm each issue identifies Items, row and field and prevents DRY RUN; then correct the workbook.
- 10
Run database DRY RUN and prove the item and stock business-row counts did not change. After independent review, COMMIT and confirm the imported item is REVIEW_REQUIRED while its stock ledger and current balance remain empty.
- 11
Preview the committed part number again and confirm it is rejected as an existing item. Use audited Item Master Edit—not XLSX—for an intentional update and confirm catalogue review is reopened.
- 12
As Auditor, review the immutable prepare, submit, approve/reject and BOM events with actor, timestamp, revision and snapshot evidence.
Expected result
- The clearance-filtered Catalogue map shows category descendants, item controls, BOM components, reverse assembly usage and permitted lifecycle links without changing data
- Every sample archetype retains its independent nature, usage, category, unit and tracking controls
- Approved revision A and draft/rejected revision B remain immutable and simultaneously addressable; approving B supersedes A only for new selection
- Exact revision identity is retained through BOM, inbound, physical stock, reservation/issue and as-built evidence, and stock is separated by revision
- Legacy physical history without provable revision remains explicitly unpinned rather than being assigned to latest
- Batch, serial, shelf-life and calibration constraints fail closed at receipt or movement
- Pack conversions preserve entered and normalized quantities
- Required typed specifications and unique part references are enforced
- The maker cannot approve their item or release their BOM
- Direct and indirect BOM cycles are rejected
- Manual creation returns DRAFT; governed XLSX COMMIT returns REVIEW_REQUIRED
- Both paths reject duplicate part numbers and XLSX never performs a silent update
- DRY RUN changes no item or stock business rows
- Item-only COMMIT leaves stock ledger and current balance at zero