Skip to main content

Production Order Creation Flow

Before creating an order, select the correct site and environment and verify order-creation access. Automatic scheduling additionally needs planning.manage. Use published material, BoM and routing definitions when your workflow derives operations and component requirements from master data.

The order form, supported imports and Konnie use shared creation services to resolve manufacturing requirements. Review the returned preview and saved result on whichever entry point you use.

1. Start With The Order Form​

When a user opens the create form, Ennea previews the next tenant order number, for example PO-2026-000001. The number comes from the tenant order-number sequence and is assigned again on creation so child orders and concurrent users stay consistent.

The user enters the normal order data:

  • material
  • planned start and end
  • quantity
  • priority
  • a planned lifecycle state for new work; status selection is available when editing
  • production-order custom fields

Custom fields live on the production order. They do not live on work centers, steps, or material lines.

2. Select A Material​

When a material is selected, the system looks up the material's default published BoM and default published routing.

The form then previews:

  • routing operations as production steps
  • BoM nodes as material lines
  • BoM or routing parameters as production-order custom fields
  • default custom-field values

If a material pointer is stale, the backend falls back to the published default BoM or routing and repairs the material reference.

3. Resolve Custom Fields And Parameters​

BoM and routing parameters are handled as production-order custom fields. This means the same value can be used for:

  • 150 percent BoM resolution
  • variant-aware routing resolution
  • order tables and search
  • reports
  • shop-floor views
  • Konnie questions and confirmations

Required fields are contextual. A field can be required at:

  • creation
  • release
  • start
  • completion

Only fields with matching requirement rules block the current action.

4. Create A Network Plan​

Before orders are written, the backend creates a production order network plan.

The plan contains:

  • the request
  • the resolved main order
  • the resolved order tree
  • BoM and routing snapshots
  • custom-field values
  • buy items
  • warnings and blocking issues

If the plan has blocking issues, creation stops and the UI or Konnie can ask for the missing values.

Konnie checks manufacturing setup for every material order in the network. A regular order needs operations, eligible work centers and configured durations. Missing setup blocks creation and import confirmation. Explicitly requested drafts can retain these gaps as warnings; Konnie must not silently change the request to a draft or remove the material to bypass them. Manual orders without a material remain supported and report setup warnings.

Konnie's order read returns manufacturingSetup with per-operation findings. configured describes the operation structure and timing only; it does not confirm available capacity, stock, release approval or customer acceptance. A saved order, the lifecycle status planned, or a fallback Production step does not prove manufacturing completeness. Published routing changes also do not retrofit existing orders: reconcile their outstanding operations separately and read them back before reporting completion.

5. Explode The BoM​

The creation request can use one of three explosion modes:

  • none: create only the main order
  • singleLevel: create child orders for the first BoM level
  • multiLevel: recursively create the full make-order network

Buy items remain material lines. Creating the network does not purchase them or reserve Warehouse stock.

Explosion includes safety limits for maximum depth, generated orders, generated nodes, buy items, and cycle detection.

6. Convert The Plan​

After validation, the plan is converted into real records:

  • main production order
  • child production orders, if exploded
  • production steps
  • splits
  • BoM lines
  • production order network aggregate

After creation, open the saved main order and check its number, quantity, steps, material lines and children. A preview number is provisional: simultaneous creation or component orders can affect the allocated number.

7. Continue Through Lifecycle Gates​

The order lifecycle is:

  • draft
  • planned
  • released
  • in_progress
  • completed
  • cancelled

When an order moves to released, in_progress, or completed, Ennea checks the matching required custom-field rules. Missing required values block that transition.

Dates and automatic scheduling​

Enter loading or delivery dates when your workflow has an agreed target. With automatic scheduling enabled, choose forward scheduling from the planned start or backward scheduling from loading/delivery. Backward creation derives the production dates instead of requiring you to guess them. Check published routing durations, eligible work centers and effective working time first. See Planning for deadline precedence and limits.

Confirm and recover​

For an exploded order, use the inline network preview and confirm the reviewed plan. Refresh the preview after changes to parameters, quantities or overrides. For an ordinary order, review the form and save. Fix displayed blocking issues rather than bypassing them by omitting the material or parameters.

If the response is uncertain, search for the saved order before submitting another create. If no published routing or BoM appears, ask the master-data owner to check publication, defaults and access. If variant resolution fails, check the required parameter values and selected variant. Creation does not automatically receive stock, buy missing items or start execution.

See order networks, customer-order intake and materials and BoMs.