--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Overview of User-define Fiori Catalog and Fiori Group (Presentation) in SAP Fiori Administration.
Answer: /n/UI2/FLPD_CUST is an SAP transaction code used to open the Fiori Launchpad Designer in client-specific customizing mode (CUST). It allows administrators to create and manage custom SAP Fiori catalogs, groups, tiles, and target mappings for a specific client. (this is the Classic method available since Fiori was introduced in 2015).
Modern Alternatives:
- Fiori Content Manager (/UI2/FLPCM_CUST): SAP now recommends using the Content Manager instead of the Launchpad Designer for most day-to-day catalog and role management because it offers a faster, cleaner SAP GUI interface and better mass-maintenance features.
- Spaces and Pages: Newer SAP S/4HANA implementations increasingly rely on spaces and pages via /UI2/FLP_CONF rather than classic catalogs and groups.
CLICK here to see an example how ICF, OData activations.
Step-by-Step Activation in SICF:
https://froggysap.blogspot.com/2025/06/sap-fiori-fiori-app-for-fi-user-pfcg.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Steps to Activate ICF services and ODATA services.
• 1) Open Transaction: Log in to your SAP system and run transaction SICF.• 2) Filter or Navigate: Enter the service name in the filter details or manually expand the tree via default_host down to your specific application path (e.g., sap -> bc -> ui5_ui5 or webdynpro).• 3) Activate Service: Right-click the selected service node and choose Activate Service (or go to menu Service/Host > Activate).• 4) Include Subservices: Choose to activate all dependent subservices if prompted.
.jpg)
Step-by-Step Activation ODATA Service:
• 1) Open Transaction:
• Enter transaction code /IWFND/MAINT_SERVICE in the SAP command line.
• Alternatively, go via SPRO: SAP Reference IMG > SAP NetWeaver > SAP Gateway > OData Channel Administration > General Settings > Activate and Maintain Services.• 2) Add Service: Click the Add Service button at the top.• 3) Specify System and Name:
• Enter the System Alias (e.g., LOCAL for embedded/local systems).
• Type the Technical Service Name or use wildcards (e.g., * or specific service name) in the filter field.
• Click Get Service.
• 4) Select and Register: Choose the desired OData service from the list.
• Click Add Selected Services.
• Assign a package (or select Local Object $TMP) and confirm the transport request prompt.
• 5)Activate ICF Node: Back in the service catalog (/IWFND/MAINT_SERVICE), find your newly added service.
• Click on ICF Node and choose Activate Node if it is not green by default.
- This task is typically performed on the SAP ABAP front-end server (SAP Gateway) and relevant back-end systems during implementation, system upgrades, or when deploying SAP Fiori apps.
- Activating Internet Communication Framework (ICF) and OData services in SAP exposes HTTP endpoints and expands your system's attack surface. Always restrict access using authorization object S_ICF, activate only required nodes, and verify transport states to prevent security vulnerabilities or broken Fiori/UI5 integrations.
- Do consult or work together with qualified Basis Consultants (internal or external) when performing the tasks mentioned.
Key Transaction Codes Used:
_Blogged.jpg)
Answer: The SAP Migration Cockpit (part of the Migrate Your Data Fiori app) is SAP’s standard, built-in tool for transferring master data, open transactions, and balances into SAP S/4HANA. It uses pre-built migration objects and guided steps to eliminate manual ABAP coding. It officially supersedes older methods like the legacy SAP S/4HANA Migration Cockpit transaction (LTMC) and LSMW.
Part2_SerialEQ_Blogged.jpg)
The IBAU Material Type (ECC and S./4HANA the same functionality) is often used to represent the Header of the Material BOM to assign with Spare Parts, where the Header (IBAU BOM) is then assigned as a Construction Type to the FL or EQ. This is especially true when the Header BOM is not to be procured or inventoried; it is to be used like a "Phantom" to link the Spare parts to the Functional Location and Equipment master. Creation of the IBAU Material is easy as it only need the Basic data view with the Material code, Description, and UOM.
- /IWFND/MAINT_SERVICE: To register, maintain, and activate OData services and link their ICF nodes on the front-end server.
- SICF: To directly enable or inspect ICF service paths under /default_host/sap/bc/ui5_ui5/ or /default_host/sap/opu/odata/.
- STC01: To run automated configuration task lists for mass-activating ICF and Gateway services.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the Alternative Data migration technique in S/4HANA (other than the classic LSMW)?
_Blogged.jpg)
Answer: The SAP Migration Cockpit (part of the Migrate Your Data Fiori app) is SAP’s standard, built-in tool for transferring master data, open transactions, and balances into SAP S/4HANA. It uses pre-built migration objects and guided steps to eliminate manual ABAP coding. It officially supersedes older methods like the legacy SAP S/4HANA Migration Cockpit transaction (LTMC) and LSMW.
How It Works:
• Predefined Migration Objects: Comes with ready-to-use templates and logic for common business objects like equipment, functional location, bom, measuring point etc.• Two Transfer Approaches:
• Staging Tables: You populate database tables using XML/CSV templates or ETL tools (supporting non-SAP and SAP sources).• Direct Transfer: An automated remote function call (RFC) pipeline extracts data directly from legacy SAP ECC systems.
• Simulation and Validation: Checks data rules, catches errors, and lets you test-run loads before writing to the live database.
Click below to see the step by step example of Equipment upload via Migration Cockpit:
Answer: These are the key changes for Plant Maintenance in S/4HANA worth mentioning:
.jpg)
https://froggysap.blogspot.com/2025/04/sap-technical-migration-cockpit-first.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of MAIN functionality improvements in S/4HANA for PM.
Answer: These are the key changes for Plant Maintenance in S/4HANA worth mentioning:
• Technical Object & Master Data Enhancements: SAP S/4HANA for Plant Maintenance harnesses SAP Fiori UI5 involves leveraging the SAPUI5 JavaScript framework to build modern, responsive business applications that adhere to SAP Fiori design principles offering a significant improvement for maintenance planner/engineer role working with PM master data.
• Improved Search (Fiori Search): Instant search capability for functional locations and equipment using full-text search.• Simplified Technical Object Creation: Streamlined screens for creating equipment and functional locations.• Mass Data Changes: Improved capability to handle mass updates to technical objects and maintenance plans.
• "360°" View (Object Pages): Fiori apps, such as "Manage Technical Objects," provide a comprehensive view of equipment or functional locations, consolidating maintenance history, BOMs, measuring points, and structured data onto one page.
• QR Code Integration: Enabling technicians to scan equipment to instantly view history, create notifications, or access checklists. QR codes on SAP Fiori screens are primarily implemented for scanning materials (MM), assets (PM), or navigation using mobile device cameras, supported via sap.ndc.BarcodeScanner in UI5 applications. This requires running Fiori within the SAP Fiori Client or mobile app, rather than a standard web browser, to enable native camera integration.
• 360° Asset Viewer: The SAP S/4HANA Asset Viewer is a central tool in Plant Maintenance (PM) that provides a comprehensive, 360-degree view of technical objects (equipment and functional locations) within the SAP Fiori environment. It allows maintenance planners and technicians to access master data as well as related master data like material BOM, structural hierarchies, and related transactional data (maintenance notifications, maintenance orders), maintenance plans etc in a single interface.
• Intelligent Asset Management & IoT Integration: Moving from reactive to proactive maintenance in SAP S/4HANA involves leveraging real-time data, AI-driven insights, and structured Fiori-based processes to prevent failures rather than just repairing them. The transition centers on moving from a "run-to-failure" model to a "predictive/preventive" approach, AI-Based Analysis, utilizing SAP S/4HANA's speed and integration with IoT (Internet of Things) for condition-based monitoring.
• Proactive Maintenance Processes: SAP S/4HANA (2022+ releases) introduces a standardized 9-phase model (4HH for Reactive, others for Proactive) to bring structure to maintenance.
• Manage Maintenance Plans app: Configures time-based or usage-based preventive plans.
• Technical Object Breakdown/Damages Insights app: Analyzes historical data to identify which assets fail frequently.
• The Manage Maintenance Planning Buckets Fiori app: enables leveling workload and assigning technicians ahead of time.
• Manage Maintenance Backlog app: Provides a comprehensive view of all pending proactive work.
• Advanced Resource Scheduling app: SAP S/4HANA Asset Management for resource scheduling (RSH) is a dedicated suite of Fiori apps designed to visualize, schedule, and dispatch maintenance work orders, offering real-time insights into work center utilization. Key apps include Resource Scheduling for Maintenance Planners (F2227) for analytics and Maintenance Scheduling Board (F3664) for graphical scheduling.
• Graphical Scheduling: Visual tool to manage capacity, balance workload across work centers, and drag-and-drop operations.• Scheduling Simulation: Simulates scheduling scenarios and dispatching for better efficiency.• Maintenance Backlog Optimization: Tools specifically designed to analyze and reduce backlogs.
• Improved Breakdown Maintenance record-and-report: In SAP S/4HANA, the Report Malfunction (F2023) Fiori app enables technicians to instantly report, plan, and close technical breakdowns, replacing traditional SAP GUI transactions with a streamlined interface. It supports emergency maintenance, allowing technicians to document damage, assign materials, and confirm repair work immediately via a mobile device.
• Improved Corrective Maintenance request-screen-approve-process steps: Phase-based Maintenance (PM) in SAP EAM is a structured, 9-step approach to managing technical object maintenance—from initiation to completion. It replaces traditional status management with standardized phases (Planning, Approval, Execution, etc.), improving efficiency and granular visibility for both reactive and proactive maintenance tasks.
• Improved Inspection Rounding process and integration with QM: New inspection checklists in SAP PM (available from S/4HANA 2021) allow technicians to record structured, audit-ready inspection results (qualitative/quantitative) directly within maintenance orders. This feature blends EAM with Quality Management (QM), using inspection lots (via inspection type 8914) for standardized checks, and is best utilized via the SAP Service and Asset Manager app for mobile recording.
• Improved Calibration via Enhanced User Experience & Mobility (Fiori): SAP S/4HANA offers improved calibration capabilities within Plant Maintenance (PM) compared to ECC, driven primarily by deeper integration with Quality Management (QM), enhanced user experience (Fiori), and modern asset management functionalities.
• Improved Refurbishment Procssing: S/4HANA offers a more structured, transparent, and user-friendly approach, moving away from fragmented transaction codes toward streamlined Fiori-based workflows for the refurbishment process.
• Improved User Experience (Fiori Apps): Refurbishment orders and associated inventory movements are now supported by Fiori apps, offering a, faster, and mobile-friendly interface for planners and technicians.• Real-Time Data Processing: Maintenance managers can track KPIs, such as Mean Time to Repair (MTTR), in real-time, allowing for better tracking of the repairable spare parts lifecycle without waiting for batch jobs.• Serialized & Batch Management: Enhanced integration between maintenance orders and inventory management, allowing for precise tracking of damaged, refurbished, and new equipment, including automatic equipment creation for serialized items upon goods receipt.• Streamlined External Refurbishment (Subcontracting): S/4HANA improves the integration of subcontracting (external refurbishment) by creating automatic purchase requisitions (PR) from refurbishment orders, facilitating seamless communication with vendors for repairable items.• Split Valuation Integration: SAP S/4HANA enhances the ability to differentiate the valuation of repaired materials (e.g., distinguishing between a new part, a refurbished part, and a defective part) throughout the refurbishment cycle.
• Event-Based Settlement for Maintenance Order: Event-based maintenance order settlement in SAP S/4HANA represents a shift from periodic, month-end closing processes to real-time, event-driven cost recognition. Unlike traditional methods, it eliminates the need to execute individual settlement transactions (like KO88/KO8G) to transfer costs, making the closing process faster. Overhead costs are automatically based on the Costing Sheet at time of final confirmation of the maintenance order, a shift to immediate TECO and Business Closing quickly when maintenance work are done; therefore assist in faster periodic financial closings. Post Processing Framework (PPF) in SAP to automate the Technical Completion (TECO) and Settlement of maintenance orders.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of FIORI in S/4HANA.
Fun Facts: 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:
- 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.
- 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.
- 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:
https://froggysap.blogspot.com/2026/05/sap-fiori-30-explore.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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"
.jpg)
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: DMS (Document Management System) Document creation.
Answer: SAP DMS (Document Management System) can store its documents in Microsoft SharePoint. SharePoint acts as an external content repository rather than relying purely on the internal SAP database.
Content Repository Setup: SharePoint is configured as an external content repository in SAP (via transaction OACT / OAC0), creating a storage category that SAP DMS uses when you upload files. One of the advantages of Leverages within SharePoint's native version control, co-authoring, and security permissions while maintaining a link inside SAP DMS.
CLICK below link to view how DMS is created and use in SAP Plant Maintenance from Equipment to Maintenance Order.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review steps of setting up of Equipment-Serial link in S/4HANA.
Part2_SerialEQ_Blogged.jpg)
Answer: To create an equipment serial number in SAP S/4HANA, configure a serial number profile and serial level in the material master (MM02), and create the serial number via transaction IQ01 (or link it directly during equipment creation in IE01). Alternatively, automatic creation occurs during goods movements like MIGO for a purchase order with a material with serial profile setup.
Prerequisites:
- Material Master Setup: Ensure the material has a Serial Number Profile assigned in the General Plant Data/Storage 2 or Sales: General/Plant Data view (MM02.
- Serialization Level: Check your system's serialization level setting (such as synchronizing equipment and serial numbers) in customizing (SPRO) if you want the serial number to automatically trigger or link an equipment master record.
CLICK below link to see step by step of how to setup Material-Equipment-Serial.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: the IBAU BOM, what is it ?
The IBAU Material Type (ECC and S./4HANA the same functionality) is often used to represent the Header of the Material BOM to assign with Spare Parts, where the Header (IBAU BOM) is then assigned as a Construction Type to the FL or EQ. This is especially true when the Header BOM is not to be procured or inventoried; it is to be used like a "Phantom" to link the Spare parts to the Functional Location and Equipment master. Creation of the IBAU Material is easy as it only need the Basic data view with the Material code, Description, and UOM.
Answer: see link for configuration of IBAU material type and application demo for IBAU Material BOM.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.