Integrations / ERP / Sage X3
Does Sage X3 Have Finite Capacity Scheduling? MRP, Loads, Finite Schedulers and SkyPlanner APS
Sage X3 has no finite capacity logic in its standard work order scheduling, and that is the gap SkyPlanner APS fills. X3 plans materials with MRP and dates work orders with Scheduling (FUNMAUTJ). Sage’s UK support team describes it as an infinite capacity scheduler: it schedules “each work order independently” and does not stagger orders for resource load.
Finite scheduling is a separate layer. Sage offers the on-premises Production Scheduler, or the generic Finite scheduler interface (GFS) to Sage X3 Web Scheduling or a third-party scheduler. Plants that need every machine, person and tool scheduled finitely run SkyPlanner APS beside X3.
How Sage X3 plans and schedules production, step by step
1. Work centers carry the capacity
Capacity lives on the work center (function GESMWS, table WORKSTATIO). The fields that matter for scheduling:
- Structure (TWD): the weekly structure, which assigns the shift pattern.
- No. of resources (WSTNBR): the number of resources an operation needs at the work center. Sage’s example is a labor work center that takes three people.
- % efficiency (EFF) and Shrinkage in % (SHR), which correct routing times.
- Work center type (WSTTYP): machine, labor or subcontracting.
- A Constraint check box, and a Replacement tab with its own Work center type (RPLWSTTYP) for alternate work centers, each with a priority.
- A capacity variation grid with start and end dates, a reason, a variation structure and a variation number of resources, for temporary shifts or downtime.
The Load tab splits load into Firm, Planned, MRP and MPS load, so a planner can see what is committed and what is still a suggestion.
2. MRP creates the suggestions
MRP (FUNMRP) balances supply and demand per reference date and storage site. It reads sales orders, work order materials, purchase orders, work orders, subcontract orders and transfers, then creates work order suggestions and purchase order suggestions. Suggestion type, Reorder quantity and Splitting on the product-site control the output.
Dates come from lead times. The end date of a suggested work order is the requirement date minus the quality control lead time. The start date is the end date minus the production lead time, or minus the routing time if the product is calculated from its routing. If that start falls before the processing date, X3 uses the processing date.
Capacity gets a single line in the MRP help: “An appropriate MRP setup is used, in parallel with the MRP process, to generate a workload.” (Sage X3 help, FUNMRP) A workload, not a capacity check.
3. Scheduling (FUNMAUTJ) dates the operations
Scheduling sequences each work order’s operations from its routing (GESROU), forward or backward depending on the requested dates on the work order. Operation start and end dates land on the work order operations (MFGOPE), and the Scheduling status on the header (MFGHEAD) moves to Scheduled.
Sage’s UK support team spells out the logic in its V12 scheduling guide: “The function schedules each work order independently.” And: “It does not delay or stagger work orders based on overall resource load.” (Sage Community Hub) Ten orders through one CNC cell all get their ideal dates, whatever the cell can run.
4. Loads shows the overload, the planner fixes it
Loads (CONSMWK) compares load with capacity per work center and period. Recalculate the loads (FUNMIWL, Manufacturing > Batch processes) rebuilds the load data. A red bar means the work center is over capacity in that period. The planner then reschedules or deschedules in the Planning workbench, moves operations to a free work center or staggers orders by hand.
X3 shows the problem. A person resolves it.
5. Finite scheduling is an add-on layer
Sage offers two routes, both switched on through activity codes:
- Production Scheduler (activity code POPS with Active selected, function FUNPSSCH). A planning tool that shows work order scheduling “in the form of a Gantt chart”. The separate Finite Capacity activity code activates finite capacity mode in the production scheduling functions. Work orders go in through Submit for scheduling.
- Generic Finite scheduler interface (activity code GFS). A generic interface developed by Sage that links cloud or on-premises X3 to Sage X3 Web Scheduling, Sage’s add-on scheduler, or to a web scheduler from an ISV. X3 drives it with Submit for scheduling, Resubmit for scheduling and Remove from scheduling (Manufacturing > Finite scheduler).
X3 also calculates an Earliest start date per operation from component availability (First Date of Material Availability, FDMA). It passes that date to Production Scheduler or a web scheduler as a constraint. Standard scheduling itself does not use it: the Work order help states that “The Sage X3 scheduling process does not consider component availability when determining operation start dates.”
Where Sage X3 stops
- Standard scheduling is infinite. Sage’s support guide says resolving overloads “would require finite capacity scheduling or manual adjustment”. (Sage Community Hub)
- Loads go stale. Add a shift or change a calendar and “existing load buckets won’t automatically adjust” until you run Recalculate the loads. By default the inquiry shows only scheduled orders; MRP suggestions appear only with inquiry code ALL. (same source)
- Production Scheduler is on-premises only. “Production Scheduler is only available for on-premises instances of Sage X3.” (Sage X3 help V12, POPS) The V11 page goes further: “Production Scheduler is not available for new Sage X3 installations.” (Sage X3 help V11)
- Production Scheduler has documented gaps. Sage lists these as not currently available (Sage X3 help, FUNPSSCH):
– optimization of setup times based on multiple item parameters and a setup matrix – links between production orders – multi-resource scheduling by synchronizing parallel operations – lists of usable resources with different production rates
- Work orders lock while optimized. A work order sent to Production Scheduler gets status Being optimized, and “You cannot modify the work order at these statuses.” It stays locked until it is removed from scheduling. (Sage X3 help, FUNPSMOPT)
- The GFS advanced interface wants one resource per operation. The help for No. of resources says: “You must set this field to 1 if you are using the generic Finite scheduler advanced interface.” The reason given: “Sage X3 Web Scheduling cannot optimize production times when multiple resources are assigned to a work center.” (Sage X3 help, GESMWS) An operation that needs a crew of three cannot say so to the scheduler.
When Sage X3’s native planning is enough
Many Sage X3 plants do not need a finite scheduler.
- Materials, not machines, set the pace. In make-to-stock or repetitive plants, the real risk is buying late. Clean BOMs, routings, lead times, lot sizing and safety stock in MRP solve most of the problem.
- Load visibility is enough. A weekly look at Loads and a few manual moves in the Planning workbench keep the plant on time.
- You already own Production Scheduler on-premises. For Gantt-based sequencing without setup matrices, order links or synchronized parallel operations, it does the job.
- You already run Web Scheduling with No. of resources set to 1 and the plan matches the shop floor.
Four ways to schedule production on Sage X3
- Planning boards inside the X3 client: the Planning workbench and Loads, or a drag-and-drop board on the X3 screens. They fit when load visibility and manual moves keep the plant on time.
- Sage’s own finite scheduling: Production Scheduler on-premises, or Sage X3 Web Scheduling through the GFS interface with No. of resources set to 1.
- Enterprise APS suites: large planning suites rolled out through a multi-month integrator project, for a plant with its own planning department.
- Cloud APS with shop-floor execution: SkyPlanner APS schedules every workstation, operator, tool and material in seconds, with operators on phone or tablet. It fits X3 manufacturers who want to be live in weeks.
When you need a finite capacity scheduler
- Loads is red most weeks and the Planning workbench has become a full-time job.
- Promised dates come from lead times, so sales and production disagree about what is realistic.
- Changeovers drive your throughput and standard X3 scheduling does not order jobs to reduce them.
- Jobs need several operators at once, or share tools and fixtures between machines.
- You run Sage X3 in the cloud, so on-premises Production Scheduler is not an option.
- Rush orders and breakdowns mean a manual rebuild of the plan, often in Excel.
- Operators need their own job queue, not a printed work order list.
What to look for
- Finite capacity per resource, shift and person, including absences and overtime.
- Sequence-dependent setups: a setting time matrix where A to B can take longer than B to A, and an engine that picks the least-setup order.
- Tools and crews as constraints: a shared tool booked on one machine at a time, and operations that need several operators at once.
- Material checks in the schedule, against inventory and open purchase orders with their expected delivery dates.
- Alternative machines and personnel and multi-level products handled by the engine, not by the planner.
- Replanning without a manual rerun when a work order is reported or a new order lands, instead of a separate scheduler pass.
- A clean ownership model with X3: which system owns dates, how locked work orders are handled, and what goes back (operation dates, status, tracking).
- A deployment that matches yours. Cloud X3 gives no direct file-system or database access, so the scheduler has to work through the GraphQL API, web services or hosted file transfer.
- Time to value: a test with your own data before any integration project.
Where SkyPlanner fits
SkyPlanner APS is a cloud finite capacity scheduler. On Sage X3 it closes each gap listed above:
- A schedule that stays current. The Arcturus AI engine builds a finite capacity schedule in seconds, and Autopilot reschedules automatically when production changes. No separate Recalculate the loads step, no overload left for a planner to fix by hand.
- Crews and alternatives without remodeling. Several operators can work one workstation at once, so a three-person operation stays one. Parallel machines are workstations in a group with their own efficiencies. The engine moves jobs to alternative machines or personnel when the primary one is unavailable, or splits a job across several.
- The setup matrix Production Scheduler lists as missing. A setting time matrix holds sequence-dependent changeover times between products (blue to red 30 min, red to blue 60 min), and the engine picks the order with the least setup. Setup and teardown times are modeled too.
- Tools as finite resources. A tool in use on one workstation is not scheduled on another at the same time.
- Material-driven scheduling. The engine simulates future inventory, so work is planned only when its materials are available. Ordered material counts as available on the PO delivery date, and stock updates when the PO is marked Delivered (purchase orders in the SkyPlanner docs).
- Priorities and locks you control. Job priority, completion-date prioritization, customer priority, Fast Track and Dynamic Priorities steer the engine. Running Time Lock and Bulldozer, which pushes downstream jobs, keep planners in control.
- Execution on the shop floor. Operators see their queue and log work on phone or tablet with Mobile Confirmations, Production Timer and Quick Log Mode.
- Cloud, whatever your X3 deployment. SkyPlanner runs the same for X3 in Sage’s cloud and on your own servers.
Choose SkyPlanner when you need finite scheduling on cloud X3 and Production Scheduler is not an option.
Choose SkyPlanner when operations need crews or alternative machines and you do not want to force No. of resources to 1.
Choose SkyPlanner when you want planning and operator time logging in one tool, with timelogs posted back to X3 as production tracking.
Choose SkyPlanner when you want finite scheduling live in weeks, not after a months-long APS project.
The Sage X3 integration
SkyPlanner integrates with Sage X3 in both directions. Work orders (MFGHEAD, MFGOPE), routings, work centers, calendars, stock and open purchase orders come from X3. Planned operation dates go back through the Work order web service (GESMFG), and logged hours post as Production tracking (GESMTK). SkyPlanner webhooks push each schedule change as it happens.
No two plants run X3 the same way, so the SkyPlanner team configures the integration to your setup and supports it after go-live. Your Sage X3 partner or in-house developers can also build on the documented SkyPlanner REST API (API reference). An API key is enough to start.
X3 stays your system for MRP, products, BOMs, routings, purchasing and stock.
Start with a CSV import in the 30-day free trial. Pricing starts from 199 € per month with 5 workstations included. The integration is quoted up front for your process and needs, together with your plan, so you see the full cost before you start.
See SkyPlanner APS for Sage X3, the Sage X3 integration guide for data mapping, features and pricing.
SkyPlanner reviews from manufacturers
2 hsaved every week
“SkyPlanner has taken our production planning from Excel spreadsheets to real-time production optimization.”
Kalle Kalliomäki, Supply Chain Specialist
UTU · Electrical switchboards and switchgear
Production planning saves 2 hours of working time every week, and a new work queue reaches the line in seconds.
+90%production efficiency
“Efficiency has gone up 90% in production.”
Abdul Rucyinga, Head of IT
Laboratory & Allied · Pharmaceutical manufacturing
Production efficiency is up 90%, and a three-month optimized plan across all workstations takes under 30 minutes.
6 monthsof free capacity visible to sales
“SkyPlanner creates the foundation and reliability for all production planning.”
Anu Järvinen, Production Manager
Fredman Operations · Food-safe packaging papers
Sales sees free capacity six months ahead, and schedule-change requests that took an hour or more are answered in seconds.
99.2%delivery reliability
“SkyPlanner has brought visibility to identifying bottlenecks and clarified production management.”
Toni Tuori, Production Manager
Piristeel · Roof safety and rainwater systems
Delivery reliability reached 99.2% this year, and scheduling saves up to four hours of working time per day.
FAQ
Is Sage X3 scheduling finite or infinite capacity?
Infinite in the standard product. Scheduling (FUNMAUTJ) dates each work order from its routing without staggering orders for resource load. Loads (CONSMWK) shows the overload and a planner resolves it by hand. Finite scheduling needs Production Scheduler or a scheduler connected through the GFS interface.
Can I still buy Sage X3 Production Scheduler?
Only for on-premises X3, according to the V12 help. The V11 help says it is not available for new installations, so your Sage partner can confirm what is sold today. For Sage X3 cloud, the generic Finite scheduler interface is the documented route.
What is the difference between Production Scheduler and Sage X3 Web Scheduling?
Production Scheduler is the built-in, on-premises Gantt scheduler activated with the POPS activity code. Web Scheduling is a separate Sage add-on that runs through the generic Finite scheduler interface (GFS), which works with cloud and on-premises X3. Web Scheduling 2023.3.4 added a GraphQL integration that requires Sage X3 2024 R1.
Does SkyPlanner APS work with Sage X3?
Yes. SkyPlanner integrates with Sage X3 in both directions, on cloud and on-premises X3. Work orders, routings and work centers flow in, and planned dates and production tracking flow back. Start the free trial with CSV exports; the SkyPlanner team configures the integration during onboarding.
Do I have to remodel my work centers for finite scheduling?
For the generic Finite scheduler advanced interface, yes. Sage requires No. of resources = 1 on each work center, so operations that need a crew lose that information. With SkyPlanner, no. Several operators can work one workstation at once, parallel machines become a workstation group, and your X3 work centers stay as they are.
Does Sage X3 sequence jobs to reduce changeovers?
Not in standard scheduling, and Production Scheduler lists setup-matrix optimization as not currently available. SkyPlanner’s setting time matrix stores changeover times for each product pair in both directions, and the engine orders the jobs with the least total setup.
