Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

Task lists: the standard work

9 min

Listen to this lesson

0:00 / 6:56

Preventive maintenance is corrective maintenance's opposite: the work is known in advance, so it can be written down once and reused. SAP's training describes the preventive process in five steps: a task list defines the work, a maintenance plan says when it is due, scheduling calls the work at the right time, the resulting maintenance order is processed like any other, and technical completion closes the call and feeds the next due date.

  1. Task listThe standard work: operations, work centers, times, parts
  2. Maintenance planWhich object, which task list, how often
  3. SchedulingCalculates due dates and creates calls within the call horizon
  4. Maintenance orderCreated by the call; released, executed and confirmed as usual
  5. Technical completionCompletes the call; the completion date feeds the next due date
SAP's preventive maintenance process in five steps.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-203

Three task list types

TypeRefers toSAP GUIContoso example
Equipment task listOne piece of equipmentIA01 / IA02 / IA03Overhaul of winding machine 10000451, which has a unique tooling setup
Functional location task listOne functional locationIA11 / IA12 / IA13Monthly check of compressed air distribution at 1710-UTL-CA
General maintenance task listNo specific object; reusableIA05 / IA06 / IA07CMC-COMP: service for any compressor of the same model in 1710 and 1720

Object-dependent and object-independent task lists.

The first two are object-dependent: each belongs to one technical object. The general maintenance task list is object-independent and can serve many objects of the same kind, which is why it is the workhorse in plants with standard equipment. In the standard system, the three types are identified by type letters (E for equipment, T for functional location, A for general task lists). Task lists are organized in groups, and one group can hold several task lists, each with a group counter.

The task list data model: one group holds several task lists by group counter, operations carry components and strategy packages, and plans reference a task list.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-203

What goes in a task list

The header holds the maintenance planning plant, the planner group and, for strategy-based work, the maintenance strategy. Each operation holds a work center, the planned work, the spare parts (components) and any tools (production resources and tools). When a maintenance plan uses the task list, its operations and components are copied into every order the plan creates, so a mistake in the task list repeats in every order.

Header: CMC-COMP, group counter 1Planning plant 1710, planner group D01, strategy CMC-TIME
Operation 0010Visual check and leak test · MECH1710 · 0.5 h · packages 1M, 3M, 12M
Operation 0020Change oil and filters · MECH1710 · 2 h · packages 3M, 12M · components: filter kit, 8 l compressor oil
Operation 0030Pressure switch and motor check · ELEC1710 · 1 h · package 12M
Contoso's general task list for its screw compressors, with strategy packages.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-203

In a strategy-based task list, each operation is assigned one or more maintenance packages from the strategy, such as 1M, 3M or 12M. That is how one task list can carry work with different intervals. Only task lists with the same strategy as the maintenance plan can be assigned to it.

Task lists save planners time in corrective work too. When Rosa creates a repair order for a compressor, she can reference a task list instead of typing operations, and SAP copies the operations and components into the order. SAP's training highlights exactly this: orders and plans can reference a task list so operations do not have to be entered one by one. In Contoso's ECC system, many task lists were created years ago and never reviewed; the conversion carries them over unchanged, so Rosa's team reviews the ones attached to active plans before the first test cycle.

One general task list feeds many orders, preventive and corrective, so a mistake in it repeats everywhere it is referenced.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-203

Walkthrough: a general task list for the line 1 compressors

  1. Create the general maintenance task list with IA05 (group CMP-QTR, plant 1710, planner group D01, strategy for time-based packages).
  2. Operation 0010 inspect and drain: work center MECH1710, 1.5 h, package 3M. Operation 0020 replace intake filter: 0.5 h, package 12M, component filter kit from 171S.
  3. Check the operations in IA07 (list display) or the task list Fiori app, including package assignment.
  4. Assign the task list to the maintenance item of each compressor plan; one change to the list now updates future calls for every compressor.
  5. Test: schedule a plan and check that the first 3M call contains only operation 0010 and the 12M call contains both.
Key points
  • Task lists hold the standard work that preventive plans reuse.
  • Equipment and functional location task lists are object-dependent; general maintenance task lists are reusable.
  • Operations carry work centers, times, components and tools; strategy packages set how often each operation runs.
  • Task list errors repeat in every order the plan creates.

Check your understanding · not graded

Lesson check

  1. 1. Which task list type can be used for many compressors of the same model?

  2. 2. Which transaction creates an equipment task list?

  3. 3. How can one task list carry work with monthly, quarterly and annual intervals?

  4. 4. Why does a task list error matter more than an error on one order?