Integrations / ERP / Oracle NetSuite
Does NetSuite Have Finite Capacity Scheduling? Native Options and SkyPlanner APS
Oracle NetSuite schedules production with infinite capacity unless you add the Advanced Manufacturing SuiteApp. Oracle’s own docs say infinite capacity scheduling “doesn’t account for current work center capacity or resource use.” Advanced Manufacturing adds a Finite Scheduling run that releases work orders in a sequence the planner sets.
In that run, the planner sets the release sequence and reruns the release when things change. Plants that want the schedule computed run SkyPlanner APS beside NetSuite for:
- a computed sequence for every machine, person and tool
- sequence-dependent changeovers, shared tools and several operators per job
- material timing in the plan
- a schedule that replans itself when the shop floor changes
How NetSuite schedules production, step by step
1. Work centers and work calendars
A NetSuite work center is not a machine record. It is a static Group (Lists > Relationships > Groups, Oracle) with the Manufacturing Work Center box checked. On the Manufacturing Work Center Settings subtab the group carries Machine Resources, Labor Resources and Work Calendar. The resource counts default to 0 and the calendar defaults to Default Work Calendar.
In standard manufacturing, capacity is a machine count, a headcount and a calendar per work center. Individual assets come in with the Advanced Manufacturing Work Bench (step 5).
2. Manufacturing Routing
The Manufacturing Routing record (REST: manufacturingRouting) lists the steps for an assembly. Each step has an Operation Sequence, Operation Name, Manufacturing Work Center, Setup Time, Run Rate and lag settings (Auto-calculate Lag, Lag Type, Lag Amount, Lag Unit). Setup Time is minutes per order, Run Rate is minutes per unit, and NetSuite uses both with the work calendar to place each step in time. When a work order uses a routing, NetSuite creates Manufacturing Operation Task records (REST: manufacturingOperationTask), one per step.
3. Forward or backward scheduling
Each work order is scheduled with one of two methods. Forward Scheduling: you set the Production Start Date and NetSuite calculates the end date. Backward Scheduling: you set the Production End Date and NetSuite works back to a start date from the routing and the work center calendar. To set the method on work orders, you first need the preference Generate Work Orders in Supply Planning.
Both methods are infinite capacity scheduling. Oracle states plainly that “NetSuite uses infinite capacity scheduling to schedule work” and that the strategy “can result in resource overloads.” Each work order is timed against its routing and calendar as if it had the work center to itself. Ten work orders due on Friday can all land on the same work center on Thursday. Oracle also warns that a backward-scheduled start date “may be a date in the past, prior to the current date.”
4. Supply Planning and Rough-Cut Capacity Planning
Demand Planning, Supply Planning and the Master Production Schedule decide what to make and when it is needed. Capacity checks come in two forms:
- Rough-Cut Capacity Planning (RCCP) in standard manufacturing (Transactions > Manufacturing > Capacity Planning). It compares work center capacity with the planned time on work orders and planned work orders, for “a mid- to long-term view,” and flags overloads and underloads.
- Rough Cut Capacity Planning (RCP) in Advanced Manufacturing (Advanced Manufacturing > Capacity Planning > Capacity Planning > Create Plan). It reports work center percentage use over a planning period and lets you build what-if scenarios.
Both are capacity reports. Neither moves a single operation.
5. Advanced Manufacturing: Work Bench and assets
The Advanced Manufacturing SuiteApp extends each routing step into a Manufacturing Work Bench record. That is where you define assets, lag times, labor requirements, work instructions, material usage and planned times. The Work Bench operation sequence, operation name and work center must match the NetSuite routing.
6. Finite Scheduling: sequence and release
This is the finite part. The planner opens Advanced Manufacturing > Finite Scheduling > Release Work Orders and works through the screen:
- Set display filters: Location, Production Class, Horizon Start (must be a Monday) and Horizon End, Planned Orders, Released Orders.
- Choose the Schedule Date, Schedule Method (Forward or Backward) and how Child Work Orders are handled.
- Tick WO Release on each work order in the order it should be released. The Sequence field fills in and can be edited.
- Click Sort Demand, optionally Preview Schedule, then Release Work Orders.
On release, NetSuite resets the operation start and end dates to the finite schedule. By default each operation goes onto a single asset, picked by earliest availability. The planner can define concurrency so an operation runs on several assets at once.
Oracle says Advanced Manufacturing finite scheduling “optimizes work center throughput” and “considers the facility’s current and future capacity.” It adds: “Planners can influence both the work order sequence and the number of assets that a work order can use at one time.” Those are the two levers.
What Oracle documents, and what it leaves to the planner
- Standard manufacturing is infinite. Without Advanced Manufacturing, overloads show up on the shop floor, not in the plan. (Oracle)
- The sequence is the planner’s. Oracle: “work orders must be released in sequence after they are created.” The planner ticks WO Release or edits the Sequence field, and Oracle names the work order sequence as a planner lever. (Oracle)
- Short horizons recommended. Oracle’s advice for processing time: “keep horizon periods as short as possible. Generally less than one week.” In practice, Finite Scheduling becomes a weekly release rhythm. (Oracle)
- Rescheduling is a new release. “The planner can review existing commitments to capacity and re-schedule them when necessary.” The Released Orders filter is there “to reschedule released work orders,” and the planner runs the release again. (same source)
- Planned work orders are only partly covered. “Planned status work orders don’t support full or end-to-end scheduling, even when Auto-Scheduling is enabled.” (Oracle)
- No routing, no finite schedule. “Work orders not associated with a NetSuite routing should not be scheduled.” (Oracle)
- Concurrency has a ceiling. “The number of concurrent assets shouldn’t exceed the number of assets assigned to the manufacturing work bench operation sequence.” (Oracle)
- Setup is a routing value. Setup Time on the routing step is minutes per order, the same whatever ran before on that work center. (Oracle)
- Every routing change is made twice. Each routing step needs its own Work Bench record with a matching sequence number, operation name and work center, so a routing change is repeated in the Work Bench. (Oracle)
In practice: a release rhythm the planner drives, a sequence built from the planner’s experience, and a new release run whenever a machine stops or a rush order arrives.
When NetSuite’s native scheduling is enough
NetSuite’s own tools are enough when:
- You run few resources with low mix. One or two bottlenecks, stable routings and repeat products. Infinite scheduling, Rough-Cut Capacity Planning and a planner who checks the load by eye will hold.
- You already run Advanced Manufacturing and the shop is simple. One asset per operation, short routings, a weekly rhythm and a planner who is happy to set the sequence by hand. Finite Scheduling covers that.
- You make to stock with long lead times. If Supply Planning drives purchasing and capacity only needs a rough-cut check, a detailed operation schedule adds little.
Once mix grows, rush orders arrive mid-week or operators become the constraint, the signs below appear.
When you need a finite capacity scheduler
You have outgrown the native tools when several of these are true:
- The weekly release sequence is wrong by Tuesday, and the planner rebuilds it several times a week.
- Delivery dates come from lead times, and sales keeps promising dates the shop cannot hit.
- Changeover time depends on which product ran before, and the right sequence would save hours each week.
- Jobs wait for a tool, a fixture or a material that the schedule did not know about, or two machines need the same tool at once.
- Some jobs need two or three operators at the same time, and the plan does not show who is free.
- Operators, shifts and absences decide real capacity, not the Labor Resources count on a work center group.
- You do not run Advanced Manufacturing and do not want to add it only for scheduling.
What to look for
- Finite capacity per resource, with shifts, people, leave and overtime, not just per work center group.
- Automatic sequencing against due dates and priorities, so the order is computed, not ticked by hand.
- Sequence-dependent changeovers: a changeover time per product pair, in each direction, used to pick the sequence.
- Tools as finite resources, so one tool is never planned on two workstations at once.
- Several operators per job and alternative machines and personnel when the primary resource is out.
- Material checks at each operation’s planned start, covering stock on hand and material still on order.
- Continuous rescheduling when work finishes late, a machine stops or an order changes.
- A visual timeline planners can edit, and shop floor feedback the schedule reacts to.
- A NetSuite integration path that fits 2026 and later. From 2026.1, Oracle says new integrations should be built on REST web services with OAuth 2.0. No new SOAP or TBA integrations can be built from 2027.1, and all SOAP endpoints are disabled in 2028.2. Bulk reads go through SuiteQL (
POST /services/rest/query/v1/suiteql, up to 100,000 results per query). - A short trial with your own data before anyone writes integration code.
Where SkyPlanner fits
SkyPlanner APS is a cloud finite capacity scheduler that runs beside NetSuite. NetSuite keeps items, BOMs, purchasing, inventory and finance. SkyPlanner computes the sequence and the replanning that Finite Scheduling leaves to the planner, for every workstation, person and tool.
Measured against the checklist above:
- Sequence computed, not ticked. The Arcturus engine builds the finite capacity schedule in seconds from due dates, priorities, customer priority and your rules. Planners adjust it on an interactive Gantt timeline.
- A rolling plan, not a weekly release. Autopilot reschedules automatically when production changes. Locks and priorities stay in your control.
- Changeovers by sequence. The setting time matrix holds asymmetric changeover times between products (blue to red 30 minutes, red to blue 60), and the engine picks the order with least setup. Setup and teardown times apply per job.
- Tools, people and alternatives. Tools are finite shared resources: a tool in use on one workstation is not scheduled on another at the same time. Several operators can be assigned to one job at once. When the primary machine or person is unavailable, the engine considers the alternatives. Workstation groups and efficiencies are part of the model.
- Material in the plan. Every operation is checked against stock and incoming purchase orders: ordered material counts as available on the PO delivery date.
- No Work Bench to mirror. SkyPlanner keeps its own process steps, so you do not need Advanced Manufacturing or a Work Bench record per routing step.
- Shop floor feedback in the same tool. Operators see their queue and log work on phone or tablet with Mobile Confirmations, Production Timer and Quick Log Mode.
Choose SkyPlanner when your planner rebuilds the release sequence several times a week.
Choose SkyPlanner when changeovers depend on the product sequence, or a shared tool or a three-person crew decides what can run.
Choose SkyPlanner when material arrives on purchase orders the plan has to wait for.
Choose SkyPlanner when you do not want to add Advanced Manufacturing only for scheduling.
UTU Oy, a switchboard and switchgear manufacturer in Ulvila, Finland, schedules production with SkyPlanner on top of Oracle NetSuite. Its ERP consulting firm presented three scheduling options, and UTU chose SkyPlanner for flexibility and modularity. UTU went live in September 2025, with SkyPlanner integrated with NetSuite and UTU’s payroll system.
SkyPlanner integrates with NetSuite in both directions. Work orders, routings, work centers, items and purchase orders come in. Planned operation dates, progress and logged hours go back, and webhooks push schedule changes as they happen.
No two NetSuite accounts are set up alike. The SkyPlanner team configures the integration to your routings, work centers and custom fields during onboarding and supports it after go-live. Your NetSuite partner or your developers can also build on SkyPlanner’s documented REST API (API reference, SkyPlanner docs) with just an API key.
Start with CSV exports from NetSuite in the 30-day free trial (up to 20 workstations, no credit card), and see your own finite schedule before any integration project. After that, pricing starts from 199 € per month with 5 workstations included, billed monthly, cancel any time. The integration is quoted up front for your process and needs, together with your plan, so you see the full cost before you start. Implementation is normally completed within weeks after onboarding starts, so you schedule live in weeks rather than after a long project.
See SkyPlanner APS for NetSuite for the overview, and the NetSuite integration guide for the technical build.
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.
98%delivery reliability, up from about 50%
“SkyPlanner plays a decisive role in maintaining our delivery reliability.”
Hannu Lahtinen, Managing Director
KJH-Comp · Sheet-metal mechanics and contract manufacturing
Delivery reliability rose from around 50% to as high as 98%, and scheduling now needs one supervisor instead of two.
FAQ
Does NetSuite have a scheduling tool?
Yes. Standard NetSuite schedules work orders forward or backward from the Manufacturing Routing and work center calendars, with infinite capacity. The Advanced Manufacturing SuiteApp adds Finite Scheduling, where the planner sequences and releases work orders against asset availability.
What is the difference between finite and infinite scheduling in NetSuite?
Infinite scheduling times each work order from its routing and calendar and ignores what else is loaded on the work center. Finite Scheduling in Advanced Manufacturing places work orders on available assets in the sequence the planner releases them, with Oracle recommending horizons generally under a week.
Does NetSuite have rough-cut capacity planning?
Yes, in two places. Standard manufacturing has Rough-Cut Capacity Planning under Transactions > Manufacturing > Capacity Planning, and Advanced Manufacturing has its own RCP plans. Both report load against capacity per work center. Neither builds an operation schedule.
Do I need Advanced Manufacturing to use SkyPlanner APS with NetSuite?
No. SkyPlanner does the finite scheduling itself, so the work orders, routings and work centers from standard NetSuite are enough input.
Can SkyPlanner handle sequence-dependent changeovers and shared tools?
Yes. The setting time matrix sets a changeover time for every product pair in each direction, and the engine picks the order with least setup. Tools are finite resources, so a tool in use on one workstation is not planned on another at the same time. Jobs can need several operators at once, and the engine uses alternative machines or personnel when the primary resource is out.