Schedule Maintenance Plan
Application component: Task Lists
App type: SAP GUI
Scope items: Preventive Maintenance
Description:  You schedule a maintenance plan with which the system generates maintenance call objects (for example, maintenance orders or service orders) for the defined cycles. You have the following scheduling options: Schedule individual maintenance plans (transaction IP10) Automatic schedulingYou can use automatic scheduling to simplify the creation of maintenance call objects for maintenance plans and update the scheduling dates. Start the deadline monitoring at regular intervals: For example, if the shortest cycle is "weekly", plan scheduling on a weekly basis. The system then generates the maintenance call objects and maintenance calls according to the defined cycles and scheduling parameters. To do this, it starts the scheduling of individual maintenance plans (transaction IP10). When you run the deadline monitoring function, the system converts all the maintenance calls, for which the call horizon has been reached, into maintenance call objects and generates new maintenance calls.With automatic scheduling you can schedule a maintenance plan for the first time or reschedule it:Deadline monitoring (transaction IP30)Automatic scheduling of multiple maintenance plans. You can restrict the selection of maintenance plans that are to be scheduled using various selection criteria (for example, all maintenance plans with a specific maintenance strategy). Mass schedule maintenance plans (transaction IP30H)Automatic scheduling of all maintenance plans that are due within a specific timeframe. You need only to enter a timeframe within which the maintenance calls and call objects should be generated. The system goes through all maintenance plans taking parameters such as date, maintenance strategies, and counter readings into account and determines whether a maintenance plan is due to be scheduled.This type of scheduling is essential if customers need to schedule very large numbers of maintenance plans, for example, customers from asset-intensive industries.   Note The log messages that are generated from mass scheduling of maintenance plans using IP30H will be different from the log messages that are generated when the maintenance plans are mass scheduled through IP30. 
Key features: For each scheduling, the system calculates the due date (planned date) for a maintenance call object based on the scheduling parameters and the maintenance cycles or packages and generates maintenance calls. When the maintenance call is due, the system generates a maintenance call object for each due maintenance item (for example, plant maintenance or service orders). Which object the system generates is determined by the maintenance plan category. You can control special scheduling requirements using the scheduling parameters in the maintenance plan. The system calculates the cycles in which maintenance call objects should be generated using these scheduling parameters. If you specify a scheduling period for a maintenance plan in the scheduling parameters, the system calculates the due dates for this period of time, and generates maintenance calls. For example, you can enter a scheduling period of 365 days to obtain an overview of the due dates for the entire year. Even if you do not specify a scheduling period in the maintenance plan, automatic scheduling is performed at least once, and the system generates at least one maintenance call. The maintenance plan is automatically extended. You no longer need to schedule the maintenance plan manually using the scheduling function. Additionally, the following data is taken into consideration during scheduling: For performance-based or time-based strategy plans: the maintenance strategy For single cycle plans: the maintenance cycles defined in the maintenance plan For multiple counter plans: the maintenance cycles defined in the maintenance planExample You schedule a maintenance plan which contains a 2-month and a 6-month package. The first due package is the 2-month package. After four months, the 2-month package is due again. After six months, both the 2-month package and the 6-month package are due.  The following special features apply to scheduling: The scheduling takes into consideration the change status of task lists. If notifications and orders are generated through a maintenance plan, the date of the notification or order completion is used for the further scheduling of the maintenance plan. You can find further information under Technical Completion of an Order and Notification Completion. You can, however, influence the maintenance processing process when you complete notifications and orders, and, for example, prevent every employee who is authorized to complete notifications from using this data simultaneously to influence the scheduling of maintenance plans. For further information, see Separate Completion of Maintenance Call Dates. You can also complete maintenance call dates directly in the scheduling function. For further information, see Completion of Maintenance Call Dates. In some cases, it may be necessary to reschedule the maintenance plan or cancel scheduling. For more information, see special scheduling functions. The system generates a scheduling log (application log). You can also use the maintenance plan menu to call up the log independently of scheduling (for example, for a certain timeframe). You can use the application log to perform a targeted analysis of the corresponding notifications and, for example, hide certain error categories.  
Business roles: Maintenance Planner| Service Planner - Recurring Service
Maintenance Planner : 
Carries out preliminary costing, work scheduling, material provisioning, resource planning, and, if necessary, requests permits to ensure that maintenance activities can be performed most efficiently and safely.

Service Planner - Recurring Service : 
Plans and manages all the related aspects of the recurring service process, from the management of maintenance plans to triggering the generation of service orders.