TutorialKart.comHow to create a single cycle maintenance plan in SAP PM using IP41
A single cycle maintenance plan in SAP PM is used when the same maintenance activity has to repeat at one fixed interval, such as every 30 days, every 6 months, or every 500 operating hours. In this tutorial, you create a time-based single cycle plan in SAP by using transaction code IP41 and assigning the reference object, planning data, task list, and scheduling parameters.
This type of maintenance plan is suitable for simple preventive maintenance where one cycle is enough. If the business requirement has different packages such as monthly inspection, quarterly service, and yearly overhaul in the same plan, a maintenance strategy plan is usually a better fit.
When to use a SAP PM single cycle maintenance plan
Use a single cycle plan when the maintenance call should be generated at one regular interval for one maintenance item. The call object can be a maintenance order, notification, or another object depending on the maintenance plan category configured in your SAP system.
| Requirement in SAP PM | Recommended maintenance plan type |
|---|---|
| One repeated interval, such as every 50 days | Single cycle maintenance plan |
| Several planned intervals using packages, such as 1 month, 3 months, and 12 months | Strategy maintenance plan |
| Maintenance based on several counters, such as running hours and distance | Multiple counter maintenance plan |
SAP PM prerequisites before creating a single cycle plan
Before you start IP41, check that the master data required for the maintenance plan is available. This avoids errors while assigning the maintenance item and scheduling the plan.
- The functional location or equipment is already created and active.
- The planning plant, main work center, and planner group are maintained.
- The correct maintenance order type or notification category is known.
- A general task list, equipment task list, or functional location task list is available if you want the maintenance order to contain predefined operations.
- The required scheduling rule is clear, for example date-based scheduling with a 50-day cycle.
IP41 navigation for single cycle maintenance plan creation
You can create a single cycle maintenance plan in SAP PM by using the following transaction code or SAP menu path.
| Transaction Code | IP41 |
| SAP Menu Path | Logistics > Plant Maintenance > Preventive Maintenance > Maintenance Planning > Maintenance Plans > Create > Single Cycle Plan |
For SAP S/4HANA systems, the same business process is also covered in SAP documentation and learning content for maintenance plans and preventive maintenance scheduling. You can refer to SAP Help for maintenance plans and SAP Learning for scheduling a single cycle plan when you need product documentation context.
Step 1: Open transaction IP41 for creating the single cycle plan
Execute t-code IP41 in the SAP command field as shown below.
Step 2: Select the SAP PM maintenance plan category
On the Create Maintenance Plan: Initial Screen, update the following details.
- Maintenance plan: Leave this field blank if internal number assignment is configured. SAP will generate the maintenance plan number when you save the plan.
- Maint. Plan Cat.: Choose the appropriate maintenance plan category from the drop-down list. The category controls the type of call object that will be generated, such as a maintenance order or a maintenance notification.
After entering the maintenance plan category, press Enter to continue.
Step 3: Enter the single cycle interval for the maintenance plan
On the Create Maintenance Plan: Single Cycle Plan screen, maintain the plan description and cycle information. In this example, the maintenance activity is an oil filter change for every 50 days.
- Maintenance plan description: Enter a clear description, for example Oil filter change for every 50 days.
- Cycle/Unit: Enter the maintenance cycle and unit, for example 50 d for 50 days. Use the unit that matches your scheduling requirement.
- Cycle text: Enter a short explanation of the cycle, for example Operating days or Periodic oil filter change.
Step 4: Assign the reference object for the SAP PM maintenance item
The reference object tells SAP which technical object is covered by the maintenance plan. You can enter a functional location, equipment, or both depending on how the asset structure is maintained in your system.
- Functional location: Update the functional location key that is required for the maintenance work.
- Equipment: Update the equipment key that is required for the maintenance work.
Step 5: Maintain planning data for the single cycle plan
Planning data decides how the maintenance call will be processed after scheduling. Enter the plant, order type, work center, priority, planner group, and task list according to the maintenance business process.
- Planning Plant: Update the planning plant for the maintenance plan, for example TKBL.
- Order type: Update the order type in the given field when the plan category creates orders.
- Main Work Center: Enter the work center responsible for maintaining the functional location or equipment.
- Priority: Enter the priority for the maintenance work.
- Planner group: Enter the relevant planner group for the technical object or planning plant.
- Task List: Assign the task list by choosing the Select Task List icon. The task list helps copy standard operations into the maintenance order when the plan is called.
Step 6: Maintain scheduling parameters for the IP41 maintenance plan
Choose the Maintenance Plan Scheduling Parameters option and maintain the required details for date determination, call control, and scheduling indicator. These parameters influence when the next planned date is calculated and when the maintenance call object is created.
- Scheduling indicator: Select the indicator that matches the cycle logic, such as time-based scheduling for a plan that runs every fixed number of days or months.
- Call horizon: Define how early SAP should generate the call object before the planned date.
- Start of cycle: Use this when the schedule should calculate from a known cycle start date.
- Completion requirement: Use this carefully if the next call should depend on completion of the previous call.
- Shift factors and tolerances: Maintain these only when early or late completion should influence the future planned dates.
Step 7: Save the SAP PM single cycle maintenance plan
Click the Save icon to save the configured maintenance plan. The start date screen appears. Choose No if the start date will be specified later during scheduling, and press Enter to continue.
After saving, SAP creates the single cycle maintenance plan number. The plan is created, but it must still be scheduled before SAP can calculate planned dates and create maintenance calls. In many SAP PM processes, transaction IP10 is used to schedule or start the maintenance plan.
Single cycle plan and strategy plan difference in SAP PM
The main difference is the way the interval is controlled. A single cycle plan has one cycle entered directly in the plan, while a strategy plan uses a maintenance strategy with packages. Strategy plans are useful when different tasks must occur at different intervals under the same preventive maintenance structure.
| Comparison point | Single cycle maintenance plan | Strategy maintenance plan |
|---|---|---|
| Cycle structure | One cycle, such as every 50 days | Multiple packages, such as monthly and yearly |
| Setup effort | Simple and direct in IP41 | Requires a maintenance strategy and packages |
| Best use | One repeated maintenance activity | Several repeated activities with different intervals |
| Typical SAP table relevance | Plan and item data are more important | Maintenance strategy package data, such as table T351P, becomes relevant |
Common checks before scheduling the single cycle maintenance plan
Before you schedule the plan, review the important fields once more. A small field mismatch can create the wrong call object or calculate dates differently from the maintenance requirement.
- The maintenance plan category matches the required call object, such as order or notification.
- The cycle and unit are correct, for example 50 d instead of 50 mon.
- The equipment or functional location is the correct asset for the planned maintenance.
- The planning plant, work center, priority, and planner group are valid for the technical object.
- The assigned task list contains the required operations for the preventive maintenance work.
- The call horizon and scheduling indicator match the business expectation.
- The plan is scheduled after saving, if automatic calls are required.
SAP PM single cycle maintenance plan FAQs
How do I create a maintenance plan in SAP PM?
To create a single cycle maintenance plan in SAP PM, use transaction code IP41. Enter the maintenance plan category, cycle and unit, reference object, planning data, task list, and scheduling parameters. Save the plan and then schedule it, commonly by using IP10.
What is the difference between a single cycle plan and a strategy plan?
A single cycle plan uses one fixed interval directly in the plan, such as every 30 days. A strategy plan uses a maintenance strategy with packages, so it is better when different tasks must run at different intervals, such as monthly inspection and yearly overhaul.
What are the types of maintenance plans in SAP PM?
The common preventive maintenance plan types are single cycle plans, strategy plans, and multiple counter plans. A single cycle plan is used for one regular interval, a strategy plan is used for package-based intervals, and a multiple counter plan is used when more than one counter or measurement condition is involved.
What is table T351P in SAP PM?
Table T351P stores maintenance package data for maintenance strategies. It is mainly relevant for strategy-based maintenance plans. A simple IP41 single cycle maintenance plan does not normally need strategy packages because the cycle is entered directly in the plan.
Why is the start date not entered while saving the single cycle plan?
If you choose No on the start date screen, the plan is saved without immediately starting the schedule. The start date can then be entered during scheduling, for example when the maintenance planner schedules the plan in IP10.
QA checklist for this SAP PM single cycle maintenance plan tutorial
- Confirm that IP41 is shown as the transaction for creating a single cycle maintenance plan.
- Confirm that the tutorial explains both time-based notification and time-based order scenarios through the maintenance plan category.
- Confirm that the difference between single cycle, strategy, and multiple counter maintenance plans is explained in SAP PM terms.
- Confirm that existing SAP PM master data links for functional location, equipment, planning plant, order type, and planner group are retained.
- Confirm that scheduling parameters and the follow-up scheduling step are covered so readers do not stop at plan creation only.
Successfully, we have created a single cycle maintenance plan in SAP PM.