# SAP Maintenance Plan Scheduling Calculator > Source: https://netray.co/tools/sap-maintenance-plan-scheduling-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Work out call horizon lead days, shifted next dates and calls per scheduling period for a time-based SAP PM maintenance plan. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PM consultant - Maintenance planner - Reliability engineer ## Tool **Kind:** calculator **Inputs:** #### Cycle length **Key:** cycle **Type:** number **Default:** 90 **Min:** 1 **Step:** 1 **Unit:** days **Help:** Cycle of the maintenance plan or strategy package, expressed in days. #### Call horizon **Key:** call_horizon **Type:** slider **Default:** 80 **Min:** 1 **Max:** 100 **Step:** 1 **Unit:** % **Help:** Percent of the cycle after which the call object is created. 100 means on the planned date. #### Shift factor for late completion **Key:** shift_late **Type:** slider **Default:** 50 **Min:** 0 **Max:** 100 **Step:** 5 **Unit:** % **Help:** Share of the completion delay that moves the next planned date. 0 means no shift. #### Late completion of last order **Key:** delay **Type:** number **Default:** 12 **Min:** 0 **Step:** 1 **Unit:** days **Help:** Days between the planned date and the actual completion date. #### Planning and procurement lead time **Key:** plan_lead **Type:** number **Default:** 14 **Min:** 0 **Step:** 1 **Unit:** days **Help:** Time your planners and buyers need before the work can start. #### Scheduling period **Key:** period **Type:** number **Default:** 365 **Min:** 1 **Step:** 1 **Unit:** days **Help:** Length of the period you schedule in one IP10 run. **Outputs:** #### Order created before planned date **Key:** lead **Expr:** cycle * (100 - call_horizon) / 100 **Format:** days **Description:** Days ahead of the planned date that the call object is generated. #### Shift applied to next date **Key:** shift **Expr:** delay * shift_late / 100 **Format:** days #### Effective interval to next planned date **Key:** next_interval **Expr:** cycle + shift **Format:** days **Description:** Cycle plus the shift, measured from the previous planned date. #### Calls in scheduling period **Key:** calls **Expr:** floor(period / cycle) **Format:** integer #### Spare days after planning lead time **Key:** spare **Expr:** lead - plan_lead **Format:** days **Primary:** true **Description:** Negative means the order is created too late for your procurement lead time. #### Call horizon needed to cover lead time **Key:** min_horizon **Expr:** clamp(100 - plan_lead / cycle * 100, 1, 100) **Format:** percent **Primary:** true **Description:** Highest call horizon that still leaves your planning lead time. **Chart:** #### Effective interval vs late completion **Type:** line **X:** delay **From:** 0 **To:** 60 **Steps:** 30 **Series:** - next_interval **Disclaimer:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the calculator **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is the call horizon in an SAP maintenance plan? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap maintenance plan scheduling, sap call horizon, sap shift factor maintenance plan, ip10 schedule maintenance plan, sap pm scheduling parameters, sap maintenance plan cycle calculator, sap pm preventive maintenance planning --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json