The tables behind BOM Management

The model contains 17 tables. Operational Id fields are text identifiers; Users instead has a User reference and required Email. Preserve the source identities used to resolve every reference. Users.User is a self-reference, and People.User points to Users: reconcile account records in the appropriate platform identity context before resolving people.

Revision status, revision product and work order status are calculated context fields. Order status, order required date and resource status on work orders also provide parent context. Verify their actual values after loading references. Production Planner checks the selected BOM revision and customer order lines during the work-order handoff. Lot number is text on different records; reconcile it against the physical lot when comparing Batches, inventory balances and material issues.

1. Resolve the platform Users identities, including required Email and the self-reference, then prepare People.User and the agreed role permissions.
2. Load Items, Parties and Resources with reviewed codes, units and actual availability.
3. Load BOM revisions and resolve BOM components and BOM change requests to their parents and people. Review imported lifecycle states before enabling actions.
4. Load Orders and purchase orders, then their order lines and purchase lines. Reconcile line quantities against the real commitments.
5. Load inventory balances from the agreed stock source and reconcile location and lot values separately from historical issues.
6. Load work orders, then material issues, production logs and Batches. Preserve their source state and keep historical imports from being treated as new production actions.