SAP Maintenance Plan Scheduling Calculator
A time-based maintenance plan in SAP PM is only as good as its scheduling parameters. This calculator lets you test call horizon, shift factor and lead time on a cycle before you change the plan and generate orders in IP10.
Your numbers
Cycle of the maintenance plan or strategy package, expressed in days.
Percent of the cycle after which the call object is created. 100 means on the planned date.
Share of the completion delay that moves the next planned date. 0 means no shift.
Days between the planned date and the actual completion date.
Time your planners and buyers need before the work can start.
Length of the period you schedule in one IP10 run.
Your results
Simplified model. SAP applies tolerances, shift rules, cycle start and the scheduling indicator (time, time with key date, factory calendar) in its own logic. Use this to size parameters, then confirm in IP10 simulation.
Effective interval vs late completion
Sweeps Late completion of last order from 0 to 60, holding your other inputs fixed.
Review your SAP maintenance plan parameters
Send an export of your plans and we will point out call horizons that leave no lead time. Optional, the calculator is free without it.
Optional. The tool and every export work without this. No spam.
How to use the calculator
Enter the cycle length in days, the call horizon you plan to use and the shift factor for late completion. Then set the planning lead time your team needs to procure parts and schedule labor. The result shows how many days before the planned date SAP will create the order, whether that leaves enough time, and the highest call horizon that still covers your lead time. The chart shows how a late completion pushes the effective interval to the next planned date. Export the numbers to Excel when you document the scheduling parameters in your design.
The logic behind the numbers
The call horizon is a percentage of the cycle. At 100 percent the call object is created on the planned date. At 80 percent on a 90 day cycle, it is created when 80 percent of the cycle has elapsed, so 18 days before the planned date. The shift factor is applied in SAP to move the next planned date when the last order was completed early or late. Here it is modelled as a simple share of the delay, so a 12 day delay at a 50 percent shift moves the next date by 6 days. The calls per period figure is the whole number of cycles that fit in the scheduling period.
Worked example
A quarterly lubrication plan has a 90 day cycle, an 80 percent call horizon, and a 14 day lead time for planning and consumables. The order is created 18 days before the planned date, which leaves 4 spare days. If the last order closed 12 days late and the shift factor is 50 percent, the next date moves by 6 days, giving an effective interval of 96 days. Four calls fall inside a 365 day scheduling period. If spare days were negative, raising the call horizon or shortening the lead time would be the two levers to test.
Common mistakes
Setting every plan to 100 percent call horizon means orders appear on the planned date with no time to prepare. Setting it too low floods the planner with orders months ahead and ties up reservations. Another mistake is using a shift factor on safety or statutory inspections where the interval must not drift. Use a fixed schedule or a key date based scheduling indicator for those. Also remember that a multiple counter or strategy plan with packages adds its own offsets, so test those in IP10 simulation.
Frequently Asked Questions
What is the call horizon in an SAP maintenance plan?
The call horizon is the percentage of the cycle after which SAP generates the call object, such as a maintenance order. At 100 percent the order is created on the planned date. At lower values the order is created earlier, giving planners time to prepare.
What does the shift factor do?
The shift factor lets the next planned date move when the last order was completed earlier or later than planned. A higher factor makes the plan follow the actual completion date more closely. A factor of zero keeps the original schedule.
Should statutory inspections use a shift factor?
Usually not. If a regulation or insurer fixes the interval, you generally want a schedule that does not drift. Use scheduling settings that anchor to the cycle start or a key date, and confirm with your compliance owner.
Which transaction runs the scheduling?
IP10 schedules a single maintenance plan and IP30 runs deadline monitoring for many plans. Both create the call objects according to the scheduling parameters, and the simulation in IP10 lets you check dates before creating orders.
If you want a report that compares planned vs actual call dates across all your maintenance plans, Netray can build it over your SAP data, read-only, with the query visible.
Related Tools
SAP PM Preventive Maintenance Compliance Calculator
Turn counts from your SAP PM order list into PM compliance, overdue rate, planned work share and labor variance.
SAPSAP PM Task List Upload Worksheet
Build equipment or general task list operations row by row, total the work hours and export a clean Excel file for your SAP upload.
SAPSAP PM Maintenance Order Types, Tables and Transactions Reference
Searchable lookup of SAP plant maintenance order types, order transactions, order tables and system statuses.
SAPSAP Equipment Master Data Template
Collect the data needed to create an equipment master record in SAP PM and export it as a clean data sheet.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)