Does SAP Business One Have Finite Capacity Scheduling? Resources, MRP and Where SkyPlanner APS Fits

1. Item planning data and the MRP Wizard

MRP settings live on the Planning Data tab of Item Master Data:

• Planning Method (MRP or None) and Procurement Method (Buy or Make)
• Order Interval, Order Multiple and Minimum Order Quantity
• Lead Time and Tolerance Days

The MRP Wizard runs in six steps: scenario, planning horizon and lead time settings, items, Company or Warehouse level, data sources, and recommendations. The output lands in the MRP Results window and the Order Recommendations window, where you turn recommendations into purchase orders, production orders or inventory transfer requests.

The run checks materials. SAP’s training course puts it this way: “the system checks if all the components are available for making the item” (SAP Learning). The documented inputs are demand, supply, stock and lead time. Resource capacity is not among them.

2. Resources and daily capacity

Resources are master data with a Resource Type of Machine, Labor or Other. A Machine resource links to one or more fixed assets, a Labor resource to employees. Resources are managed by capacity, not quantity. Linking machines to fixed assets requires the Fixed Assets functionality to be enabled first.

Capacity is set per day. On the resource’s Planning Data tab you set four capacity factors for each weekday, such as hours per shift, shifts per day and machines. B1 multiplies them into one Daily Capacity. Then you generate a period in the Set Daily Internal Capacities window. There are two capacity types: Daily Internal Capacity and Single Run Capacity, the second switched on with the Relevant for Single Run Capacity flag. SAP is explicit about the granularity: “These capacities are defined on a daily basis” (SAP Learning).

3. Routing as Route Stages inside the BOM

SAP Business One has no separate routing master. A routing is a set of Route Stage lines inside the Bill of Materials (Product Tree), each with a Route Sequence and Waiting Days that you type in. Resource lines sit under the stages. For routed production orders, the system calculates Required Days and Total Days per stage, where Total Days = Required Days + Waiting Days.

4. Production orders and resource allocation

Each resource line on a production order gets one of four allocation methods:

Allocation method	What it does
On Start Date	Allocates all of the resource time to the start date
On End Date	Allocates all of the resource time to the end date
Start Date Forwards	Fills each day from the start date forward, up to the Single Run Capacity
End Date Backwards	Fills each day from the end date backward, up to the Single Run Capacity

Each method places one order’s resource time. Forwards and Backwards are capped by Single Run Capacity, the hours one production order can consume per day, not by what other orders already hold on that resource.

5. The Resource Capacity window

The Resource Capacity window shows Internal, Available and Single Run views. On the Capacity Data tab, Available = Internal – Committed – Consumed. Committed is capacity allocated to production orders but not yet issued, Consumed is capacity already issued to production. When orders commit more than the resource has, Available drops below zero.

6. Fixing overloads by hand

A negative Available figure is a signal, not a correction. SAP’s 9.1 training material introduces the resource module so planners can see whether production can go ahead as planned. The alternative it names is “manual scheduling adjustments need to be made to meet deadlines” (SAP B1 9.1 Production Enhancements). The adjusting is the planner’s job: change the order’s dates or allocation, then check the window again.

Standard B1 planning holds up in these cases:

• Few machines and low variety. With a handful of resources and one or two routings per product, a planner reads the Resource Capacity window each morning. The occasional negative figure takes minutes to fix.
• Stable make-to-stock. When demand is steady, MRP lead times match reality and the bottleneck stays in the same place, lead-time-based dates hold up.
• Day-level precision is enough. If your customers care about the day and not the hour, daily capacity buckets are the right resolution.
• Changeovers are short and tooling is not shared. If setup time does not depend on the previous job and each machine has its own tools, fixed time per order through Additional Quantity is close enough.

SkyPlanner APS is the cloud finite capacity scheduler for B1 manufacturers who want to keep standard production orders and stop fixing negative Available by hand. It closes each gap above:

• Daily buckets become a real capacity model. Finite capacity per workstation, with shifts, personnel, leave, absences and overtime shifts.
• One order, one machine becomes full sequencing. The Arcturus engine sequences all jobs across all workstations in seconds, with alternative workstations and jobs split across machines. Planners edit it on an interactive Gantt timeline while the engine keeps the schedule consistent.
• Fixed setup time becomes a changeover matrix. The setting time matrix holds sequence-dependent changeover times between products (blue to red 30 minutes, red to blue 60), and the engine picks the order with the least setup. Setup and teardown times are modeled per job.
• Tools and crews become finite resources. Tools are finite resources that cannot be scheduled on two workstations at once. A job can need several operators at the same time. The engine moves work to alternative machines or personnel when the primary resource is unavailable.
• Lead-time dates become material-driven dates. Each job is checked against stock and incoming B1 purchase orders. The open PO quantity counts as available on the line delivery date. A Goods Receipt PO in B1 moves it into stock in SkyPlanner, partial receipts included.
• Due dates become real priorities. Job priority, completion-date prioritisation, customer priority, Fast Track and Dynamic Priorities decide which job goes first.
• Manual adjustments become automatic. Autopilot reschedules automatically when production changes, within your locks and priorities.
• Scheduling and shop-floor execution sit in one tool. Operators see their queue and log work on phone or tablet with Mobile Confirmations, Production Timer and Quick Log Mode.

Choose SkyPlanner when the Resource Capacity window shows overloads every week and fixing them takes hours.

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

Choose SkyPlanner when you want finite scheduling on standard B1 production orders, not a new manufacturing module.

The full feature list is on the features page.

SkyPlanner integrates with SAP Business One in both directions. Production orders, route stages, resources and open purchase orders come in through the Service Layer. Planned dates go back to ProductionOrders, and logged output and hours are posted as Receipt and Issue for Production. SkyPlanner webhooks push every schedule change as it happens.

Every plant runs B1 differently, from route stages in the BOM to resource groups and add-ons. The SkyPlanner team configures the integration to your setup during onboarding and supports it after go-live. Your B1 partner or your developers can also build it on SkyPlanner’s documented REST API (API reference) with just an API key. Product and API documentation is public at SkyPlanner docs.

Laboratory & Allied, a pharmaceutical manufacturer in Nairobi, runs SAP Business One on HANA with Power BI. Around 1,000 people work there, roughly 800 of them in production, and it has used SkyPlanner since 2025. Its in-house IT team did the SAP integration largely on its own with SkyPlanner’s help. The company reports on-time delivery and on-time reporting to customers up 50%.

Start with a CSV or Excel export from B1 in the 30-day free trial, with up to 20 workstations and no credit card. You see your own orders scheduled before any integration work. 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.

Read the overview on the SkyPlanner for SAP Business One page, or see what moves between the systems in the SAP Business One integration guide. Other ERPs are listed under ERP integrations.