Does SAP S/4HANA Have Finite Capacity Scheduling? Capacity Leveling, PP/DS and SkyPlanner APS

S/4HANA has two layers of capacity planning. Most plants run only the first.

1. MRP and lead time scheduling

MRP Live (MD01N) creates planned orders. Lead time scheduling then dates their operations and creates capacity requirements from the work center formulas for setup, processing and teardown. It does not look at the load other orders already put on that work center. SAP Learning puts it plainly: “The operations are scheduled infinitely. The non-working times of the work centers are taken into account, but not the capacity requirements of other orders” (SAP Learning). The result is overloaded work centers.

2. Work center capacity master data

Capacity lives on the Work Center, not on the order. A work center can have several capacity categories (SAP’s example: 001 Machine and 002 Labor), each with formulas that turn routing standard values into capacity requirements. The Factory Calendar defines the workdays, time intervals override the standard available capacity, and capacity versions (standard, minimum, maximum) model alternative shift patterns.

3. Capacity evaluation

Planners compare requirements with available capacity in the Manage Work Center Capacity app. MRP controllers can also check it from the stock/requirements list. Evaluation shows the overloads but moves nothing.

4. Capacity leveling, by the planner

Leveling is where finite placement happens, and the planner drives it. SAP Learning: “In capacity leveling, operations are scheduled finitely. They are dispatched to periods with free capacity.” The tools:

Tool	What it does
Tabular planning table	Dispatches operations to periods with free capacity. SAP: “you cannot create a specific sequence for the dispatched operations within a period”
Capacity Scheduling Table (formerly Schedule Production)	Dispatches and deallocates bottleneck operations. “Only bottleneck operations that are assigned to a pacemaker work center are considered.” Other operations in the order are adjusted by midpoint scheduling
Capacity Scheduling Board	Graphical chart to dispatch, reschedule or deallocate individual bottleneck operations on pacemaker work centers

The classic Graphical Planning Table (CM21, CM22 and the rest of the CM* transactions) is compatibility scope. SAP Learning: “The use right for the Graphical Planning Table expires on Dec 31, 2025.” That date has passed. If your planners still work in the CM* transactions, the move to the Fiori apps is overdue.

5. Embedded PP/DS

PP/DS is SAP’s automated finite scheduler. It used to be part of SAP APO and has been embedded in S/4HANA on-premise since release 1610. SAP markets it as the step after MRP: “Move beyond classic MRP with SAP S/4HANA Manufacturing for planning and scheduling software” (SAP product page).

What it adds:

• Resources with a Finite Scheduling indicator: “You define whether a resource is finite or infinite in the scheduling parameters for the resource via the Finite Scheduling indicator” (SAP Help). The optimizer can override that per run: its optimization profile has an “Always Schedule as Finite” option that dispatches to resources with a finite capacity load (SAP Learning).
• Scheduling modes: Infinite scheduling, Searching for a slot, Adding an operation at the end, Inserting an operation, Inserting an operation and closing gaps, Squeezing in an operation.
• Heuristics and optimization runs that cut setup times, setup costs and delays.
• A setup matrix for sequence-dependent changeovers, min and max distances between operations, and alternative modes.
• Multi-level pegging, campaign and block planning, and alerts.
• The Production Scheduling Board (a Fiori Gantt) and the Monitor Capacity Utilization app.

Getting there takes work. You activate it in Customizing (Advanced Planning > Basic Settings > Activate Advanced Planning and Scheduling), run the HANA-integrated liveCache, and flag materials and work centers for advanced planning. Everything not flagged stays in classic MRP. The optimizer, per an SAP product expert’s blog, “needs to be additionally installed preferably in a separate hardware” (SAP Community). The same blog: “A dedicated license, Manufacturing for Planning and Scheduling is required if this switch is set to Active.”

S/4HANA alone covers the plant when:

• You have one bottleneck and long lead times. Planning runs show overloads weeks ahead, and a planner levels the pacemaker work center in the Capacity Scheduling Table once a week.
• Your demand is mostly MRP-driven and stable. Few rush orders, few changeovers that matter.
• You already license and staff PP/DS. Your planners work in the Production Scheduling Board every day, and every material and work center that matters is flagged for advanced planning.

SkyPlanner APS is a cloud AI scheduler that runs beside SAP S/4HANA and closes the gap between MRP and a finite plan. MRP stays in SAP, and SkyPlanner takes over the leveling your planners now do by hand:

• Finite on every resource, automatically. The Arcturus engine builds a finite capacity schedule in seconds from orders, priorities, constraints, capacities, materials and rules. Every workstation, shift and person is finite on every run, with no pacemaker limit and no optimization profile to tune.
• A sequence, not a period bucket. Planners see which job runs first on Tuesday on an interactive Gantt timeline, and the engine keeps the plan consistent when they drag a job.
• Material-driven. Every job is checked against stock and incoming purchase orders. Ordered material counts as available on the PO delivery date, and stock updates when the PO is marked Delivered, so an operation does not start before its components are there.
• Changeovers by sequence. A setting time matrix stores changeover times per product pair, and they can differ by direction (blue to red 30 minutes, red to blue 60). The engine uses it to choose the order with least setup, and the “Allow similarity” rule groups jobs that share a property such as a tool.
• Tools and crews as constraints. A tool in use on one workstation is not scheduled on another at the same time. A job that needs three operators gets three. When the primary machine or person is unavailable, the engine considers alternatives.
• A plan that stays current. Autopilot reschedules automatically when production changes, so the weekly leveling session becomes a daily plan that follows the shop floor.
• Confirmations from the floor. Operators see their queue and log work on a phone or tablet with Mobile Confirmations, Production Timer and Quick Log Mode. The integration posts those timelogs to S/4HANA as production order confirmations.

Choose SkyPlanner when several work centers limit output and leveling one pacemaker no longer holds the plan.

Choose SkyPlanner when changeovers depend on sequence, or shared tools and multi-operator jobs decide what can run next.

Choose SkyPlanner when your plant has outgrown manual leveling, a PP/DS project is more than the problem needs, and you want a finite schedule of your own production in weeks.

S/4HANA keeps materials, BOMs, routings, work centers, production orders and stock. SkyPlanner integrates with it in both directions:

• Production orders and operations come in from API_PRODUCTION_ORDER_2_SRV, and work centers from API_WORK_CENTERS.
• Each operation is dispatched in S/4HANA through the ScheduleProductionOrderOperation action, with forward mode, dispatch status and SkyPlanner’s start date and time.
• Logged hours post through API_PROD_ORDER_CONFIRMATION_2_SRV.
• SkyPlanner webhooks push every schedule change as it happens.

No two plants configure work centers, capacity categories and routings the same way. That is why the SkyPlanner team configures the integration to your S/4HANA setup during onboarding and supports it after go-live. Your SAP partner or your own developers can also build on SkyPlanner’s documented REST API (API reference), and an API key is enough to start.

Start with CSV or Excel exports from S/4HANA in the 30-day free trial (up to 20 workstations, no credit card). You see your own schedule before anyone touches an API. After that, pricing is 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.

See SkyPlanner for SAP S/4HANA for what moves between the systems and the S/4HANA integration guide for the technical route. Scheduling detail is under features and in the SkyPlanner docs, and other ERPs are under ERP integrations.