Microsoft Dynamics 365 Business Central Production Orders (Header-Level Guide)

Audience: production planners, manufacturing managers, shop-floor leaders, and BC admins. Focus: header-level only—no sub-pages, no button tours.



1) Overview: Production Order Statuses at a Glance

In Business Central, a production order’s Status shows its lifecycle stage. (People often call these “types.”)

  • Simulated → costing / what-if analysis. Prevalence: low (≈0–10%).

  • Planned → system-proposed supply from planning. Prevalence: high (≈40–70%).

  • Firm Planned → stabilized plan you intend to run. Prevalence: medium (≈15–40%).

  • Released → execution/WIP tracking. Prevalence: all active jobs.

  • Finished → closed/costed orders. (Detailed in Section 5 only.)

Per scope: Finished is not described in the initial type breakdown—see Section 4.

2) Detailed Descriptions by Status (excluding Finished)

A) Simulated

Business purpose: What-if costing and feasibility without committing the shop. Great for quotes, prototypes, and training.
Technical: Header state for cost calculation only—no WIP or ledger postings.
Config notes:

  • Item must be producible (Item → Replenishment System = Production Order).

  • Use certified Production BOM No. and Routing No. for meaningful simulated costs.

  • Costing Method on Item (Standard vs actual methods) influences interpretation.

Practical use:

  • Quote scenario: set Item No., Variant Code (if any), Quantity, Location Code, Due Date; calculate cost only.
    Real-world example: Compare laser vs waterjet by swapping Routing No. on the header to see unit cost deltas for a customer quote.

B) Planned

Business purpose: Supply proposals from planning to cover demand—suggestions, not promises.
Technical: Planning objects the system can reschedule or cancel. Promote to Firm Planned to freeze intent.
Config notes:

  • Driven by Item planning parameters: Reordering Policy, Safety Stock, Lead Times, Lot Multiples, etc.

  • Header carries Item No., Quantity, Location Code, Due/Ending Date (BOM/Routing can still be tweaked).

  • Action messages target Planned orders (increase/decrease/postpone/cancel).

Practical use:

  • Run planning weekly; review exceptions; adjust Quantity/Due Date; promote near-term orders to Firm Planned.
    Real-world example: Seasonal spike—planner consolidates close Due Dates and firms the next two weeks’ demand.

C) Firm Planned

Business purpose: A committed, stable plan that purchasing and capacity can act on confidently.
Technical: Firmed headers resist churn from planning runs. Staging area before execution.
Config notes:

  • Lock in Item No., Quantity, BOM No., Routing No., Location Code, Dates.

  • Certified BOM/Routing recommended before release.

  • Scheduling uses header Starting/Ending Date-Time against capacity calendars.

Practical use:

  • Firm after supplier confirmations and capacity checks; finalize dates to enable reservations and staging.
    Real-world example: Pilot of 500 units—planner pins Starting Date next Monday and Ending Date two weeks later; buyers stage critical parts.

D) Released

Business purpose: Execution mode—operators post consumption and output; managers track WIP and progress.
Technical: Enables material/capacity postings that form WIP and value entries.
Config notes:

  • Certified BOM/Routing unless intentionally running without routing.

  • Location Code (and Bin Code if mandatory) must be valid.

  • Posting Date required at posting time.

  • Flushing methods (from Item/Work/Machine Centers) govern backflush/manual consumption.

Practical use:

  • Release when material is staged and capacity ready; monitor WIP and dates for slippage.
    Real-world example: High-runner SKU: as output posts, managers watch WIP trends and ETA to Finished.

3) Status Change Process: What Happens and Who Cares

Typical path:

  • Simulated → Planned → Firm Planned → Released → Finished

  • Variations: Planned → Released (small shops), Released → Firm Planned (reopen for header corrections if allowed)

System effects:

  • To Firm Planned: Locks intent; schedules via Routing No. and header dates; planning respects it.

  • To Released: Enables material/capacity postings; WIP accounting begins.

  • To Finished: Stops execution; finalizes costs; clears WIP; posts variances.

Business implications & authorization:

  • Firm Planned: Triggers purchasing/staging commitments.

  • Released: Authorizes shop execution and WIP—often permission-gated or workflowed.

  • Finished: Finance often gates; ensure variances reviewed.

Prerequisites to move forward:

  • Certified BOM/Routing (unless intentionally no routing).

  • Valid Location/Bin and open Posting Date.

  • Realistic dates/quantities for capacity.

Config levers:

  • No. Series, permissions/workflows, posting setups, costing method.

4) Finished Production Orders (Dedicated Section)

Meaning:

  • Business: Closed job—no more activity; costs settled; inventory/G/L updated.

  • Technical: Final Value Entries posted to the produced item; WIP cleared; variances posted to designated G/L accounts.

Cost calculation in full:

A) Material costs

  • Standard cost items: Compare expected (BOM × standard) vs actual consumption; differences → Material Variance.

  • Actual methods (FIFO/Specific/Weighted Avg): Consumed components post at actual; produced item cost = actual materials + capacity + overhead; later adjusted by cost adjustment.

B) Capacity costs (machine & labor)

  • From Routing No. through work/machine center rates (Direct Unit Cost, Overhead Rate, Indirect Cost %).

  • Posted time/output → Capacity Ledger Entries → WIP → finished item cost.

C) Overhead allocation

  • Via work/machine center Overhead Rate and Indirect Cost %; both capitalize into WIP and finished cost.

D) Variances (typical buckets)

  • Material usage/substitution, setup/efficiency, manufacturing overhead, routing/operation, and quantity/yield variance.

E) Cost adjustment mechanisms

  • Adjust Cost – Item Entries recalculates/propagates actual costs (esp. FIFO/Specific chains).

  • Post Inventory Cost to G/L pushes inventory value to G/L (often scheduled).

  • Late invoices or retro changes re-roll costs and, if already sold, adjust COGS.

Cost flow to Inventory & G/L (simplified):

  1. Released: Material/capacity postings accumulate in WIP; outputs build inventory.

  2. Finished: WIP cleared into finished item inventory; variances posted to configured G/L.

  3. Adjust/Post: Period routines align Item Ledger/Value Entries with G/L; downstream COGS updated as needed.

Management reporting lens:

  • WIP balance/age, variance trends by item/work center/plant, unit cost vs standard, and absorption/throughput all depend on accurate header setup and certified BOM/Routing.

Final Good Practices

  • Treat Planned as a conversation, Firm Planned as a promise, Released as where money gets spent.

  • Keep BOMs/Routings certified and current—headers point to them.

  • Tune Item planning parameters to reality (lead times, order modifiers, safety) to avoid planning churn.

  • Schedule cost adjustment & G/L posting so finance reflects shop reality quickly.

Comments

Post a Comment

Popular posts from this blog

Understanding Database Indexes in Business Central (and How They Can Help You)

Image
When I first started working with Business Central, the word “indexes” felt too technical for me — like something only developers or database admins cared about. But then I discovered the Database Missing Indexes page . At first, I thought it listed all the indexes that exist in the database. Later, I realized it’s even more interesting: it actually shows the indexes that don’t exist yet, but SQL thinks should be there . That page became a game-changer for me in understanding why some reports and pages are slow, and how I can help point my team toward performance fixes. What Are Indexes, Anyway?  Indexes are like shortcuts. Imagine a giant cookbook with 1,000 recipes. If I want to find every recipe with “chicken,” I don’t flip through each page — I go to the index in the back. Databases work the same way. If I filter a table by Posting Date , an index lets the system jump straight to those rows instead of scanning everything. When no index exists for the filter, the system has to ...
Read more
Image
Dynamics 365 Business Central · Manufacturing · APICS/ASCM Business Central & APICS/ASCM for Manufacturers: A Practical, No‑Nonsense Guide for Consultants, IT Leaders, and Plant Managers By Grigorios Mavrogeorgis · Approx. 15–20 min read Who this is for Business Central consultants who need precise setup guidance. IT decision-makers evaluating ERP fit for manufacturing. Manufacturing managers who want to understand how BC will run their shop—today, not in theory. Table of contents APICS (now ASCM): What It Is and Why It Matters How Closely Business Central Aligns to APICS/ASCM The Three Primary Manufacturing Types—With Real Examples Configuring Business Central for Each Manufacturing Type JIT Manufacturing: Principles and Benefits Implementing JIT in Business Central: A Step‑by‑Step Blueprint End-to-End Configuration Recipes Practical Navigation & Setup Pointers Key Takeaways References 1) APICS (now ASCM): What It Is and Why It Matters APICS...
Read more
  Business Central Costing for Manufacturing — User Manual   Applies to: Microsoft Dynamics 365 Business Central (SaaS & On‑Prem). Screens and labels may vary slightly by version. The concepts are stable across recent versions. Suggested Blogger Labels: Business Central, Dynamics 365, Manufacturing, Costing, Standard Costing, FIFO, Average Costing, Work Centers, Machine Centers, WIP, Variances, Subcontracting, Month-end Close, Reporting 1) What this guide covers A practical, end‑to‑end playbook for setting up costing in Business Central (BC) for manufacturing and allocating costs to work centers and items. It includes: Costing concepts in BC (item costs, capacity costs, overheads, variances) Master data you need (Items, BOMs, Routings, Work/Machine Centers) The minimum viable setup for accurate costing How to allocate costs to work centers and roll them into item costs Posting flows, WIP, and G/L integration Day‑...
Read more