SAP PM Task List Upload Worksheet (Excel)
Preventive maintenance in SAP starts with task lists: the reusable list of operations that planned orders copy. Preparing them in a spreadsheet first lets planners agree the content and total hours before anyone loads a single record.
| Task list group | Group counter | Task list description | Plant | Usage | Planner group | Operation | Work center | Control key | Operation short text | Persons | Work per person (h) | Total work (h) | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0.25 | |||||||||||||
0.5 | |||||||||||||
0.5 | |||||||||||||
0.25 | |||||||||||||
3 | |||||||||||||
1 |
Task list group and counter identify the list. Usage 4 is normally plant maintenance, but confirm in your system. Use the exported file as the source for LSMW, a migration tool or manual entry in IA05 or IA01. Check column order against your load program.
Have your task list file reviewed
Send your worksheet and we will check for missing fields, duplicate keys and unusual work values. Optional, the worksheet is free without it.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Each row is one operation. Repeat the task list group, counter and description on every row that belongs to the same list. Enter the work center, control key, a short text and the persons and work per person. The worksheet computes total work for each row and sums the hours at the bottom. Add or delete rows as needed, and export to Excel or CSV when the content is approved. Rename the columns to match your load program if it expects a specific layout.
How task lists are structured in SAP
A task list has a header with the group, counter, description, plant, usage and planner group, followed by operations. Each operation carries a work center, control key, short text and planned work and duration. General task lists, created in IA05, are not tied to a technical object and can be assigned to many. Equipment task lists, created in IA01, and functional location task lists, created in IA11, are tied to one object. Operations may also have material components and inspection characteristics. Keep operation text short and instructional because it prints on the order.
- Use 10 step numbering (0010, 0020) so you can insert steps later
- One work center per operation, one craft per step
- Use the control key to decide whether an operation is internal or external
- Write the text as an instruction, not a title
Worked example and checks
The sample pump lubrication list has four operations with a combined total of 1.5 work hours. The compressor inspection list totals 4 hours. Before loading, check that every row has a valid plant, a work center that exists in that plant, a valid control key and a numeric work value. Check that the group and counter are unique. A good habit is to load five lists first, review the resulting order printouts with a planner, and only then load the rest.
Common mistakes
The usual mistakes are copying operation text that is too long for the short text field, assigning work centers from the wrong plant, and mixing the work per person with total work. Another is building one very large task list for a whole machine instead of smaller lists per task, which makes planned orders hard to use. Finally, remember that task lists only help when they are assigned to maintenance items in the maintenance plan.
Frequently Asked Questions
What is the difference between IA05, IA01 and IA11?
IA05 creates a general maintenance task list that can be used for many objects. IA01 creates a task list for one piece of equipment, and IA11 creates one for a functional location. Choose the type that matches how widely you want to reuse the list.
Can I upload task lists in bulk?
Yes. Common approaches are an LSMW recording, a custom BAPI or batch program, or the migration tooling provided for your release. Prepare and validate the data in a worksheet like this one first, then map the columns to your chosen load method.
What does the control key do?
The control key decides how SAP treats the operation, for example whether it is scheduled, confirmed, costed or processed externally. Delivered keys such as PM01 are for internal operations, but check your own system for the exact settings.
Why do my planned orders have no operations?
The maintenance item in the maintenance plan must point to a valid task list, and the task list must be released for use. Also check that the task list plant and usage match the item. IP10 simulation will show whether the list is found.
If you are migrating legacy maintenance routines to SAP, Netray can help extract and structure the source text, with a human review step before anything is loaded.
Related Tools
SAP Maintenance Plan Scheduling Calculator
Work out call horizon lead days, shifted next dates and calls per scheduling period for a time-based SAP PM maintenance plan.
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.
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 PM Maintenance Order Settlement Checklist
A step-by-step checklist for technically completing and settling SAP maintenance orders without period-end surprises.
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)