JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

June 26, 2026 · 12 min read

SAP PM Production Resource Tool

The Production Resource Tool (PRT) is the master data object that identifies and governs the physical tools, measuring instruments, and documents required to execute a maintenance operation. PRTs are assigned to task list operations and are carried forward to work order operations, enabling resource planning, availability checking, and usage tracking. Unlike work centers (which model who performs the work), PRTs model what is needed to perform it — torque wrenches, vibration analyzers, inspection documents, or specific equipment items. This article maps PRT types, their organizational structure, integration with task lists and work orders, and the field-level detail PM consultants must own.

Part 1: Production Resource Tool — Core Concepts (All Modules)#

1.1 What Is the Production Resource Tool?#

A Production Resource Tool is a reusable resource assigned to production or maintenance operations to indicate that a specific tool, device, or reference document must be available before the work can begin. In the SAP PM context, PRTs are assigned to task list operations and are automatically pulled into work order operations when the task list is referenced. They serve two purposes: operational (ensuring the right tool is on hand) and tracking (recording tool usage, wear, and calibration status).

1.2 Four PRT Types#

The PRT type determines the source master record that backs the PRT, and consequently which data it inherits and which availability check logic applies. Selecting the wrong type causes incorrect availability checks, missing tool data in work orders, and gaps in tool traceability.

Design principle: For calibrated instruments requiring calibration records and individual tracking, always use PRT type E (Equipment). Using type M for these items loses the individual lifecycle trace. Agree on the PRT type matrix during blueprint — changing it later requires re-creation of PRT master records and re-assignment to task lists.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Client
   │
   ├── PRT Master
   │      Vibration Meter VM-4500
   │      Type E (Equipment) — Equipment 10005678
   │
   └── Plant 1000
          │
          └── Task List MAINT-GEN-01, Operation 0010
                 Inspect Bearing Vibration
                 ── references ──> PRT Master VM-4500
                 Usage: 1 unit

1.4 Integration with Other Master Data Objects#

The PRT sits at the intersection of the work management master data chain. It is created and managed independently, but its operational value is realized only through its assignment to task list operations and, from there, to work orders.

Part 2: PM-Specific Field Details#

2.0 Scope of PM Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 General Data (PRT Header)#

The General Data section defines what the PRT is — its type, classification, physical quantity, and administrative status. This data is set at creation and rarely changes; any change to PRT type requires deletion and re-creation of the master record.

2.2 Default Values#

Default Values define the standard parameters that are proposed when the PRT is assigned to a task list operation. These defaults reduce data entry effort and ensure consistency across all task list assignments — critical when the same tool appears in dozens of maintenance procedures.

2.3 Task List Assignment (PLWP)#

Task List Assignment is where the PRT is operationalized. This data is not stored on the PRT master record itself but on the task list operation (PLWP table), and it is the primary place where PM consultants configure how, when, and how much of each PRT is required for a given maintenance procedure.

Prerequisite: The task list must be in status “Created” (CRTD) or changed back to editable status before PRT assignments can be modified. Once a task list is set to Released (status 4 in PM usage), changes require explicit status management.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction