Customizing in SAP S/4HANA Asset Management (formerly S4133) — Lesson 3: Task Lists, Maintenance Plans, Scheduling, and Execution Settings

Learning Objectives

• Explain how Task Lists, Maintenance Plans, Scheduling, and Execution Settings supports controlled asset-management configuration.
• Complete the workflow and produce a reviewable preventive-maintenance configuration and test pack.
• Evaluate the condition where a maintenance plan generates calls at the wrong interval or without required operations and select a supported response.

Detailed Topics

• General and equipment task lists: settings, dependencies, and derivation rules that control the selected process behavior.
• Single-cycle and strategy plans: integration touchpoints and downstream effects that must remain aligned with business intent.
• Maintenance strategies and packages: authorization, governance, and change controls required to protect the configuration outcome.
• Scheduling parameters and call objects: test conditions and regression evidence needed before transport or operational release.

Instructor Demonstration

The guided walkthrough links General and equipment task lists, Single-cycle and strategy plans, Maintenance strategies and packages, Scheduling parameters and call objects to business outcomes and control evidence. Learners see how the process should appear in SAP, what belongs in preventive-maintenance configuration and test pack, and how the team should respond when a maintenance plan generates calls at the wrong interval or without required operations.

Hands-On Exercise

Complete a controlled activity covering General and equipment task lists, Single-cycle and strategy plans, Maintenance strategies and packages, Scheduling parameters and call objects and preserve the final result in preventive-maintenance configuration and test pack.

1. Define the expected business result and the SAP objects that should produce it.
2. Perform the lesson scenario, capturing before-and-after evidence for every material decision.
3. Test the exception without changing unrelated settings or data, then explain the first divergence.
4. Apply proportionate remediation and complete a focused regression test before handover.

Scenario Analysis

• Which SAP object, rule, master record, or process step most strongly influences the observed result?
• What evidence distinguishes a configuration problem from data, authorization, integration, or timing causes?
• How should the preventive-maintenance configuration and test pack be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected SAP behavior differs from the observed result. Review process sequence, master data, organizational assignments, configuration, authorization, integration, and timing separately. Treat “a maintenance plan generates calls at the wrong interval or without required operations” as a testable hypothesis until settings, documents, logs, reports, and retest outcomes confirm the cause.

Validation Checklist

• Required structures, master data, roles, settings, and dependencies for Task Lists, Maintenance Plans, Scheduling, and Execution Settings are present.
• The preventive-maintenance configuration and test pack connects each conclusion to objective, reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, documentation, monitoring, and operational handover are complete.

Lesson Outcome

Learners can apply Task Lists, Maintenance Plans, Scheduling, and Execution Settings, explain the resulting SAP behavior, and defend the outcome through preventive-maintenance configuration and test pack.