How-toSage X3Manufacturing / MRP / Scheduling

Sage X3 Production Planning, Scheduling and Tracking

Question
sage x3 production planning

Also searched as

  • sage x3 production scheduler
  • sage x3 production tracking
  • sage x3 mrp and work orders

Short answer

Sage X3 plans production from master data (items, BOMs, routings, work centers) through MRP or manual work orders, schedules operations against work center capacity, then records progress with production tracking. Setup quality in the BOM, routing and work center calendar decides whether the plan is believable.

Applies to: Sage X3 Manufacturing module, V7 onward; screen names and menu placement differ slightly by version and activity codes

Set up planning, scheduling and tracking

  1. 1Confirm the Manufacturing activity code is on for your folder, and that the items to be built are set as manufactured with a valid BOM and routing.
  2. 2Build work centers with capacity, efficiency and calendars; accuracy here drives scheduling.
  3. 3Define routings (operations, work center, setup and run times) and BOM components with scrap or yield where relevant.
  4. 4Set item-site planning parameters: lead times, lot sizing, safety stock and planning policy.
  5. 5Run MRP (or MPS for top-level items) to generate planned and firm work order suggestions.
  6. 6Firm the suggestions into work orders, then run the scheduler to place operations on the work center calendars and review the load.
  7. 7Issue components and record operation and output quantities through production tracking, so cost and stock update as work progresses.
  8. 8Review variances, close work orders and feed the results back into lead times and routing standards.

Planning: MPS, MRP and work orders

Sage X3 supports master production scheduling for finished goods and MRP that explodes requirements through BOMs and nets them against stock, orders and supply. MRP output is a set of suggestions: planned work orders and purchase suggestions that you firm into real documents.

Planning is only as accurate as lead times, lot sizes and stock accuracy. Many sites get poor MRP results not because of the engine but because routing times are guesses and inventory counts drift. Fix those before tuning planning parameters.

Scheduling

Scheduling places each work order operation on a work center timeline using routing times, work center capacity and calendars. The scheduler lets planners see load by work center, find bottlenecks, and reschedule when priorities change.

Decide on forward versus backward scheduling by business need: backward from a due date for make-to-order, forward from release for make-to-stock. Treat finite capacity as a refinement. Start with load visibility first, then add finite rules when data quality supports it.

Production tracking

Production tracking records what happened: components consumed, operations completed with time, and finished quantity received into stock. Choose the granularity deliberately. Tracking at work-order level is light but gives coarse cost data, while operation-level tracking with labor time gives better variance analysis at the price of more data entry.

Backflushing components at completion reduces shop floor effort but depends on accurate BOMs. Mixed models are common: backflush low-value hardware, issue expensive or serialized parts manually.

Try it here, free

Sage X3 Import Template Worksheet

Open full tool

An editable import tracker for Sage X3: which object, which import template, source file, records loaded, errors and owner, with error rates calculated.

Common pitfalls

  • !Running MRP on routing times and lead times nobody has validated.
  • !Letting inventory accuracy drift, which turns MRP suggestions into noise.
  • !Over-tracking at operation level when the shop floor will not enter the data.
  • !Ignoring work center calendars, so scheduled dates ignore shifts and holidays.
  • !Firming everything MRP suggests without a planner review.

How an ERP-grounded AI assistant handles this

Planners often ask questions like which work orders are late and why. A private AI layer such as ERPray can answer from live X3 data, showing the query, for example open work orders past due by work center, shortages by component and supplier lead time. It stays read-only, so scheduling changes remain with your planners.

Frequently asked questions

Does Sage X3 have finite capacity scheduling?

X3 includes scheduling against work center capacity and calendars, and you can review load by work center. How strict the finite behaviour is depends on version and configuration. Plan to validate it against your own routings, and consider advanced scheduling tools if you need complex sequencing.

What is the difference between MPS and MRP?

MPS plans top-level finished goods against forecasts and orders. MRP then explodes those requirements through the BOM to plan components and sub-assemblies. Many shops run MRP alone, using MPS only for items that need controlled, level-loaded schedules.

How do I track production on the shop floor in X3?

Use production tracking against work orders to record component usage, operation completion and finished output. For hands-on terminals, check whether your version offers a shop floor or mobile front end, or integrate a separate data collection tool.

Why does MRP suggest work orders for items we have in stock?

Usually because stock is allocated or reserved, safety stock is set, lead time offsets put demand earlier than expected, or on-hand differs from the system. Check item-site planning parameters, allocations and open demand before blaming the engine.

Related

How-to

How to Run a Physical Inventory Count in Sage X3

Sage X3 physical counts run through Stock > Counts: create a count session scoped to a site, category, or zone, generate the count sheet to freeze theoretical quantities, enter counted quantities, review the variance report, then validate to post stock and valuation adjustments. Blocking movements against the counted locations during the window keeps the variance meaningful.

How-to

Subcontracting in Sage X3: Setup, Flow, Packing and What MFGM Means

In Sage X3, subcontracting means an outside supplier performs one or more operations on your material. You flag the operation as subcontracted in the routing, the work order drives a purchase document to the subcontractor, components are sent, and the processed goods are received back into stock. MFGM is generally how people refer to the manufacturing module and its records, not a separate feature.

Error fix

Division by 0 Error in Sage X3: Find the Cause and Fix It

A division by 0 error in Sage X3 means a calculation divided by a field that was zero or empty at runtime. Typical sources are a zero unit-of-measure coefficient, a zero quantity or base quantity on a BOM or routing, a zero price or rate, or custom 4GL or report code that never guards the denominator. Find the script and line from the error, then fix the data or guard the calculation.

How-to

Sage X3 Developer Studio: What It Does and How to Track Versions and Release Notes

Sage X3 Developer Studio is the development environment for building and changing X3 solution code and web pages, working with the Adonix 4GL scripts and the Syracuse web layer. To track versions, read the release notes and compatibility guides that Sage publishes for each version and patch rather than relying on remembered dates.

How-to

Sage X3 API Documentation: REST (Syracuse), SOAP Web Services and Where to Find Docs

Sage X3 exposes data and business logic in two main ways: REST-style SData services through Syracuse, which read and write business objects as JSON or XML, and SOAP web services that publish X3 subprograms and objects. Official documentation is in Sage's online help and developer resources for your version.

How-to

Sage X3 Table Dictionary: How to Browse Tables and What PAYMENTD Holds

Sage X3 keeps its table definitions in a data dictionary you browse from the development area of the application. Tables are named in short uppercase codes, live in the folder's schema (often a schema named like the folder, such as SEED), and columns carry a numeric suffix like _0. PAYMENTD holds the line-level detail of payment entries, paired with a header table.

AI for ERP

AI for Sage X3, Grounded in Your Own Ledgers and Stock Data

Add AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.

AI for ERP

AI for Sage X3 in Food and Beverage: Lot Genealogy and Shelf-Life Answers From Your Own Data

Private AI on Sage X3 for food and beverage: lot genealogy, shelf-life, allergen and batch yield questions answered from live data, on-prem or private cloud.

Stuck on Sage X3?

Talk to engineers who work inside Sage X3 every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software