This Blog is mainly on SAP Exam Questions and Selected "How-to" SAP processes

Wednesday, July 1, 2026

SAP PM - Permit Master approval at Order Release

CLICK here to view the Presentation

at No comments:
Labels:

Q&A in Class (2026-07-01) S43000

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review of Plant Maintenance Enterprise Structure.

Answer: While the foundational physical PM enterprise structure (such as Maintenance Plants and Planning Plants) remains unchanged,

1. Maintenance Plant
A Logistics (LO) Plant can be used for MM, PP, SD, PS, QM, PM, CS (all Logistics activities). The Logistics (LO) Plant is also the maintenance plant (for PM) is "Location-based". Therefore, a Maintenance Plant is a specific physical site or production facility where technical objects (functional locations and equipment) are located. 
Another purpose of the Maintenance Plant (Logistics Plant) is that the Maintenance Work Center is created at the Maintenance Pant (where Technicians are at). 

2. Maintenance Planning Plant
It is the planning plant is "Planning-based". It is the organizational unit responsible for organizing and preparing all maintenance tasks, ie: the Planning tasks of Maintenance. 
It is important to note that the Maintenance Plant can also be designated as a Planning Plant if it perform planning for itself. However, a specific Logistics Plant can be created as Planning Plant (example a office space of Maintenance Planning where there are technical objects or maintenance work center in that plant), in this case only the planners are that AND this P'anning Plant can be responsible for more than one Maintenance Plant. 

Click here to view posts of Planning Plant & Maintenance Plant:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Show the steps to create a Shift Sequence for Plant Maintenance Work Center.


Answer: In SAP S/4HANA Plant Maintenance (PM), a shift sequence defines how daily working times and breaks rotate for a work center. Its significance for scheduling accuracy lies in translating theoretical "calendar days" into precise capacity availability, preventing resource overload, and ensuring alignment between maintenance activities and production schedule.
Click the following the see how a Shift Sequence is created:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: How to create "Variant" of a Standard FIORI app for a specific data filter? PLUS review of the related demonstration on Fiori Apps navigations.


Answer: SAP Fiori is not an acronym and does not stand for anything. It gets its name from the Italian word for "flower". SAP chose this name to symbolize the freshness, simplicity, and natural 

beauty they wanted to bring to their software's user interface.

Rather than a specific product, SAP Fiori is the official design system and User Experience (UX) layer for SAP products, Here are the key takeaways about what it does:

  • Role-Based: It provides simplified, task-oriented applications tailored to exactly what a specific user needs to do their job.
  • Intuitive Design: It replaces clunky, traditional enterprise screens with a modern, consumer-grade interface.
  • Cross-Device: Fiori apps are designed to work smoothly on desktops, tablets, and smartphones.
  • Design Principles: The system is built on five core pillars: role-based, adaptive, simple, coherent, and delightful.

There are 3 main interfaces for SAP access today:

  1. SAP GUI: The classic, desktop-based interface. It relies on specific transaction codes and is still widely used for heavy backend configurations and legacy systems.
  2. SAP Business Client (NWBC): An integration shell that allows users to access both traditional SAP GUI screens and modern web-based applications within a single desktop window.
  3. SAP Fiori: The standard, web-based UX for modern environments like SAP S/4HANA. It features a role-based, personalized launchpad with specific apps for transactional, analytical, and informational tasks.

Answer: SAP introduced SAP Fiori in 2013. It launched initially at the SAPPHIRE conference with a set of 25 apps, focusing on a mobile-first, role-based user design. Since its release in 2013, the SAP Fiori design system has gone through major updates:

  • 2013 (Fiori 1.0): 25 apps initially mainly for mobile-first specifically for example PO approval.
  • 2016 (Fiori 2.0): Expanded to ERP scenarios with features like the Fiori Launchpad and enhanced navigation.
  • 2019 (Fiori 3): Introduced a unified user experience across the entire suite of SAP products along with the Quartz and Horizon design themes.

Key updates in Fiori 3.0:

SAP Fiori 3 introduces a redesigned, intelligent user experience focused on consistency across all SAP products, featuring
  • a new "Quartz theme" ( is the default design system and visual theme family for SAP Fiori 3)
  • new interface called "Spaces and Pages" layout for improved navigation.
  • embedded AI capabilities with Joule (SAP's built-in generative AI copilot embedded within the SAP Fiori Launchpad).
  • proactive situation handling (an intelligent framework that automatically detects, tracks, and alerts users about critical business issues).
  • a conversational UI (digital assistant).
  • enhanced analytics for actionable insights.
The future of SAP Fiori is centered around AI-driven interfaces, cloud-native delivery, and intelligent automation. While Fiori remains the visual foundation for SAP S/4HANA, users will increasingly interact with enterprise data through natural language and autonomous agents rather than traditional click-based navigation.

To help you to understand SAP Fiori, here are some official links:
https://learning.sap-press.com/sap-fiori

To help you to understand SAP Fiori, here are Blog Posts to show the step by steps guides:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Classic vs S/4 FIORI Technical Object creation for SAP Plant Maintenance. 


Answer: The FIORI "UX" (User Experience) App "Create Technical Object" is a combined "UX" App to Create either Functional Location or Equipment and therefore combining the classic transaction code of IL01 and IE01. Besides layout changes of the look and feel in the FIORI interface via "Create Technical Object" FIORI App, there is really not much difference comparing this App to IL01 or IE01 in terms of data fields to be entered in the classic GUI transaction or Fiori App. 
See link 

Another FIORI App for Technical Objects perhaps worth reviewing is the "Find Technical Object" FIORI App ID "F2072"


See the link below for a demonstration of this App:
Some of the key features this App are:
  • List Display FL and EQ plus download to Excel.
  • Display Installation information for the Technical Object in the Hierarchy.
  • Perform Installation and Dismantling.
  • Shows details of related Notification and Order for the Technical Object of FL an EQ.
  • etc.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: References for SAP documentations on SAP Plant Mainteannce. 


Answer: The SAP Plant Maintenance (PM) process is an enterprise asset management lifecycle framework. It helps organizations track, plan, execute, and settle maintenance activities for physical assets. The core workflow spans from initial asset structuring to work execution, order settlement, and continuous historical analysis. SAP PM Process can be described as 5 distinct components: 
  1. Technical Object Structuring:
    • Functional Locations - Hierarchical structures representing specific areas or plants where maintenance activities take place (e.g., Hydraulic system room).
    • Equipment - Individual physical objects installed to functional locations (e.g., Equipments like Pump, Motor installed to the Functional Location called Hydraulic system room).
    • Bill of Materials (Material BOMs) - Spares lists associated with equipment to ensure the right materials are available for repairs.
  2. Maintenance Notification:
    • Breakdown Maintenance- Handles sudden equipment failures to restore operations and document the incident. 
    • Corrective Maintenance - Breakdown maintenance is emergency, reactive work performed only after an asset fails completely. In contrast, corrective maintenance is typically a proactive or planned approach to fix minor flaws or wear-and-tear before a total failure stops operations, minimizing unplanned downtime.
    • Preventive Maintenance - Is a proactive strategy of regularly inspecting, servicing, and repairing equipment before it breaks down in specific intervals. Its main goal is to avoid costly unplanned downtime, extend asset lifespan, and ensure smooth, safe operations.
    • Refurbishment - Repair damaged or defective repairable spare parts so they can be reused and returned to warehouse stock. This practice saves significant procurement costs over buying brand-new replacements.
    • Inspection Rounding - Is a planned maintenance process where a technician inspects multiple, similar technical objects in a specific sequence (a "round"). Technicians use rounds to record specific measuring point values, such as temperature, pressure, or run hours, and to create subsequent maintenance notifications when required.
    • Calibration - SAP Plant Maintenance (PM) integrates with the Quality Management (QM) module to handle equipment calibration. This ensures that measuring and test instruments operate accurately and meet regulatory compliance. The system schedules maintenance, generates calibration orders, tracks measurement results, and updates equipment status automatically.
  3. Maintenance Planning & Scheduling:
    • Operations & Task Lists - Defining the specific steps, time required, and spare parts  required to complete the maintenance work and the maintenance work centers (technicians) responsible.
    • Maintenance Plan - It can automatically generates maintenance orders, notifications, or service entry sheets at predefined intervals, ensuring equipment is regularly serviced to prevent breakdowns. 
    • Material Reservations - Checking the availability of spare parts in inventory and reserving them in Material Management as Reservations for the maintenance work. 
    • Capacity Planning - Scheduling the dates and times to ensure maintenance doesn't severely disrupt daily production or operations.
  4. Maintenance Execution:
    • Permits/Safety - Tagging and safety clearance documents (if applicable) are assigned. 
    • Goods Issue - Spare parts are physically issued from the warehouse to the specific maintenance order.
    • Confirmation - Technicians or supervisors confirm the work is completed, log the actual hours spent, and provide feedback on the machinery's condition.
  5. Completion, Settlement, Close:
    • Technical Completion (TECO) - The order is marked as finished, releasing any unneeded reserved materials and freeing up capacity.
    • Costs Settlement - Actual costs incurred (labor, materials, services) are settled against the appropriate cost centers or general ledger accounts.
    • Business Completion (CLSD) - The order is locked against further changes, finalizing its history for reporting and predictive analysis.
Click the following for official documentations on SAP Plant Maintenance:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Technical Permits in SAP Maintenance Order.


Answer: A Permit in SAP Plant Maintenance (PM) is a safety and compliance control mechanism. It acts as an operational barrier, ensuring that high-risk maintenance tasks (like hot work or confined space entry) cannot begin until necessary approvals, safety protocols, and regulations are strictly met.
When Technical Permit is assigned to the Technical Object (Functional Location and Equipment), Maintenance Order creation with the Permit will require Permit (issue) approval before the Maintenance Order can be Released, and it is also possible to required Permit approval before the Maintenance Order can be set to TECO.
Click here to view the Presentation:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Demonstrate the LEAN Service Scenario introduced for S/4HANA in both MM and PM process. 

Answer: Lean Service in SAP S/4HANA Plant Maintenance (EAM) refers to a simplified, Fiori-based approach for procuring and managing external maintenance services. It replaces the older, highly complex MM-SRV framework (ML81N) by streamlining how maintenance planners request, approve, and record supplier-provided services.
Click the following Blog Posts to see the process flow for lean service in S/4HANA:

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

Question: Outline the key aspects of Corrective Maintenance Steps (BH1 - Standard Process).

Answer: The standard BH1 process for corrective maintenance involves a series of steps to address equipment failures, starting with detection and diagnosis, followed by planning and execution of repairs, and concluding with testing and documentation. This process ensures that equipment is restored to operational status efficiently and effectively, minimizing downtime and potential losses. 

See the Blog Posts links to the Step-by-Step illustration from Create Notification to Complete Order.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Outlines the key aspects of Simplified Emergency Maintenance Process in S4 HANA Asset Management (BH2 - Emergency Maintenance). 

Answer: Report Malfunction app is designed mainly for technicians for to be used in Emergency Breakdown process.
• Emergency maintenance involves creating a malfunction report, planning repair work, assigning work items and spare parts, and documenting the repair. 
• It is included in default role SAP_BR_MAINTENANCE_TECHNICIAN.
• Emergency Maintenance, where all the steps are covered in one Fiori App ID F2023'
• Scope ID BH2 in SAP Best Practices is using this app which contains 3 tiles as below:
1. Report Malfunction Tile - used to create malfunction reports.
2. Manage Malfunction Reports Tile - list of malfunction reports.
3. Repair Malfunctions-My Job List Tile - list of work items assigned to Me and My Team.

Blog Posts step by step, Fiori App and SAP online help below:
https://froggysap.blogspot.com/2024/10/sap-pm-malfunction-report-scenario.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Outline of Phased-Based Maintenance "Reactive Maintenance" (scope item 4HH) and "Proactive Maintenance" (scope item 4HI) scenarios.


Answer: SAP phase-based maintenance is encompassed within the Reactive Maintenance (scope item 4HH) and Proactive Maintenance (scope item 4HI) scenarios. Phase-Based Maintenance is a structured, 9-stage lifecycle process in SAP S/4HANA Enterprise Asset Management (EAM/PM) that standardizes how work requests are initiated, planned, approved, and executed. It prevents users from jumping steps by requiring the previous phase to be completed before moving to the next.
The nine sequential phases in this lifecycle are:
• Initiation: Creating the maintenance request.
• Screening: Reviewing and approving/rejecting the request.
• Planning: Creating and detailing the maintenance order.
• Approval: Authorizing work.
• Preparation: Securing parts and preparing the work environment.
• Scheduling: Dispatching the technicians.
• Execution: Carrying out the maintenance work.
• Post-Execution: Recording times, confirmations, and failure data.
• Completion: Performing technical and business completion.

Bog Posts step by step:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Measuring Point (Counter) Preventive Maintenance Plan Process flow.

Answer: SAP Preventive Maintenance using counters enables usage-based maintenance, triggering work orders based on actual equipment performance (e.g., running hours, mileage, or cycles) rather than fixed dates. This prevents both over-maintenance and unexpected equipment failures.

Key SAP Transaction Codes
• IK01 / IK02 / IK03: Create, Change, or Display Measuring Point/Counter.
• IK11 / IK12 / IK13: Create, Change, or Display Measurement Document (Enter actual usage here).
• IP11: Create/Edit Maintenance Strategy.
• IP11Z: Create/Edit Cycle Sets (useful for grouping multiple counters).
• IP41 / IP42: Create Counter-Based Maintenance Plan.
• IP43: Create Multiple Counter Plan.
• IP10: Schedule Maintenance Plan.
Bog Posts step by step:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

at No comments:
Labels:
Subscribe to: Posts (Atom)