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

▼

Thursday, August 20, 2026

Q&A in Class (2026-08-21) S4H00

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

Question: Video Library and SAP Official Resources for SAP S/4HANA


Answer: See the following links:
See the following official SAP link to Video Library for SAP S/4HANA:
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/VideoLibraryforSAPS4HANA/ 
(Note that the "Manufacturing" Video Library may still be "in Construction" at the time of access)
(* You can revisit in the near future for new Video updates by the SAP team members)

See comprehensive SAP resources main page:
https://community.sap.com/
https://community.sap.com/t5/all-sap-community-blogs/ct-p/all-blogs

See the following links on official SAP resources on S4HANA:
https://blog.sap-press.com/key-differences-between-sap-ecc-and-sap-s4hana/

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

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:

  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:
https://froggysap.blogspot.com/2026/05/sap-fiori-30-explore.html

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

Question: A structural presentation of an example SAP Enterprise Structure for the above Question



Answer: The above "lines" linking between Enterprise objects are necessary for FI, CO, HR, MM, PP, SD, PS, QM, PM, CS, E&HS, TM, LE, and PDM except there is no direct assignment (dotted lines) from Purchasing Group to the Purchasing Organisation in the Enterprise Structure IMG configuration.

As for the PP (Production for Discrete and Process), QM (Quality Management), PM (Plant Maintenance), CS (Customer Service), PS (Project System) module, the Logistics Plant (Apple Green above) is used. In PM and CS, the Plant is used as the Maintenance Plant and the Maintenance Planning Plant. AND in PP-DI or PP-PI, the Plant is referred to as either a Planning Plant or Production Plant. BUT regardless of how the individuals give names to the Plant for its declared usages (this case Planning or Execution), it is the same Plant object. 

PLANT is part of LO (Logistics) Enterprise Structure and not specifically for MM, PP or SD, use of Plant is necessary in the following:
Materials Management (MM-PUR): for creating Purchasing Documents 
Materials Management (MM-IM): for managing Material with Stock scenario 
Sales & Distribution (SD-DLV): as Delivery Plant for creating Outbound Delivery for Stock scenario 
Production Planning & Execution (PP): as Planning Plant and Production Plant
Project System (PS): for Network Activities and Component Assignment 
Plant Maintenance (PM): for Maintenance Order Processing 
Customer Service (CS): for Service Order Processing
Quality Management (QM): for Inspection Lot Processing

Important Structure Changes in S/4HANA note mentioning:

  • LE-TRA (Transportation) - is officially being phased out and will lose all usage rights and support by December 31, 2030. Companies must transition to modern alternatives as SAP shifts entirely toward newer supply chain architectures. The Successor Solution: SAP Transportation Management (TM) replaces LE-TRA completely. 
    • The Enterprise Structure TPP (Transportation Planning Point) is no longer valid for thew new SAP TM module. 
  • LE-WM (Warehouse) - SAP LE-WM (Logistics Execution Warehouse Management) compatibility scope in SAP S/4HANA ended on December 31, 2025. For older classic SAP ECC 6.0 systems, mainstream maintenance ends on December 31, 2027, which marks the absolute end of support for the classic module. SAP urges migration to SAP Extended Warehouse Management (EWM) because mainstream support for legacy SAP Warehouse Management (WM) and SAP ECC ends on December 31, 2027. Compatibility mode for WM on S/4HANA expired at the end of 2025, making early transition critical to avoid unsupported systems and logistics disruptions.
    • The classic Enterprise Structure LE-WM Warehouse configuration can be still migrated to S/4HANA as it is still required to link the MM Storage Location to the EWM Warehouse. 
  • MM-IM Storage Location - MM Sloc is still used and an important Enterprise Structure for Inventory Storage; However, the Storage Location segment data in the Material Master MRP4 view is not longer available. Also note the t-code OMIR (used to define storage location MRP parameters per plant) is obsolete and no longer possible. SAP recommend to now use MRP Area for MRP Parameters at the Storage Location level.

When attempting the TS410 certification, it is important to have some understanding of the Enterprise Structure Relationships like below:
Operating Concern: Each Client must have at least ONE Operating Concern, SAP do not recommend to have more than ONE Operation Concern for each installed Client. Reason is for for simplicity and efficient data management, particularly when all controlling areas within the client share the same fiscal calendar. This approach reduces complexity and simplifies reporting, especially when dealing with a single, global business structure. 
Controlling Area: An Operating Concern can be assigned with ONE or MORE Controlling Areas, a Controlling Area can only be assigned to ONE Operating Concern because the Operating Concern is the highest level in the Profitability Analysis (CO-PA) organizational structure, and it defines the scope for analyzing profitability. The assignment links the cost accounting information from controlling areas (which manage cost and revenue) to the profitability analysis performed within the operating concern. 
Company Code: A Controlling Area can be assigned with ONE or MORE Company Code where the Company Codes need not necessarily be in the same Country. It is Mandatory to assign a Company Code to only ONE Company Code. This assignment is crucial for transferring financial data from FI (Financial Accounting) to CO (Controlling) for internal reporting and management decision-making. Without this assignment, cost and revenue information cannot be tracked and analyzed within the controlling module.  
Plant: A Company Code can be assigned with ONE or MORE Plants BUT each Plant can be assigned to only ONE Company Code, because a plant represents an operational unit within a company, and the company code is the smallest organizational unit for financial accounting. This assignment ensures that all operational activities within a plant are properly reflected in the company's financial records. Specifically, it allows for accurate valuation of materials, inventory, and other operational aspects within the plant's context, which are then rolled up into the company code's financial statements. 
Purchasing Organization: In order to be able to create Procurement Orders (like PR or PO), the Purchasing Organization must be assigned to a PLANT. However the SAME Purchasing Organization can be assigned to MORE than ONE Plant. However, assigning a purchasing organization to a company code in SAP is optional because it allows for different purchasing strategies. A purchasing organization can be configured to be company-specific (procuring only for one company code) or cross-company (procuring for multiple company codes). If a purchasing organization is not assigned to a specific company code, it can procure for any plant within the enterprise, regardless of its assigned company code. 
Purchasing Group: A purchasing group in the SAP system is a specific buyer or a team of buyers identified by a three-character code who handle everyday buying activities. Key features include managing material procurement, acting as the main contact for vendors, and helping with reports.
Sales Organization: Assigning a Sales Organization to a company code is mandatory in SAP's Sales and Distribution (SD) module. Each Sales Organization must be assigned to exactly ONE Company Code, though a company code can have multiple Sales Organizations. However, one DO NOT assign the Sales Organization to the Plant. 
EWM Warehouse: An EWM warehouse uses SAP Extended Warehouse Management (SAP EWM), an advanced software system designed to control inventory, track goods, and optimize high-performance logistics operations. It manages all steps of product movement from factory or supplier receipt to final shipping.

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

Question: Basic introduction to AI framework in SAP.


Answer: SAP introduced its Generative AI Hub in November 2023 at the SAP TechEd conference, announcing its general availability through SAP AI Core by December 2023. SAP AI Core is a cloud-based service in the SAP Business Technology Platform (SAP BTP). It gives companies a place to run, scale, and manage artificial intelligence and machine learning models. It connects custom AI code directly with enterprise business data.

LLM (Large Language Models (LLMs) in SAP:
• SAP does not build its own foundational LLM from scratch; instead, it provides an orchestration layer that connects enterprise data with leading third-party and open-source models (such as OpenAI, Anthropic, Google, Meta, and IBM Granite). 

SAP provides access to and integrates Large Language Models (LLMs) through its Generative AI Hub in SAP AI Core on the SAP Business Technology Platform (BTP) via the following Capabilities:
  • SAP Joule Agentic AI - is an autonomous artificial intelligence system built by SAP that evolves Joule from a basic conversational chatbot into an active, multi-step enterprise decision-maker. Instead of just answering questions, it plans, reasons, and executes complex business workflows across ERP, finance, supply chain, and human resources.
    • In Non-Technical words - is a smart digital coworker for your company’s software. Instead of just answering questions like a basic chat bot, it can plan and finish multi-step work tasks all by itself.
  • SAP RAG - in the SAP ecosystem, RAG stands for Retrieval-Augmented Generation. It is an artificial intelligence technique that connects large language models (LLMs) to a company's private business data. Instead of guessing an answer, the AI searches internal documents or databases first, then uses that real data to write an accurate response.
    • In Non-Technical words - is an AI technique that lets an intelligent assistant look up your company's private files, invoices, or inventory data in systems like SAP HANA Cloud Vector Engine before answering a question, ensuring the AI gives accurate, fact-based business answers instead of guessing
  • SAP MCP - refers to the use of the open-source Model Context Protocol (MCP) to connect Large Language Models (LLMs) and AI agents directly to SAP enterprise systems, data, and development tools. It provides a standardized plug-and-play architecture so AI assistants can securely query data, run business logic, or assist with development without needing custom point-to-point APIs for every single task. MCP is used to connect the User + AI Agent to the SAP system. 
    • In Non-Technical words - is like a universal USB-C port that connects AI smart assistants (like ChatGPT or Claude) to an enterprise's massive, complex SAP business system
  • SAP Vector Database - The SAP vector database works through the SAP HANA Cloud vector engine, which stores and processes vector embeddings directly inside a standard enterprise database. In other words, a SAP vector database (built into SAP HANA Cloud) is a smart digital filing cabinet. It stores business data not just by matching exact words, but by understanding what the data means. It helps AI chatbots find answers from your company's private files. SAP HANA Cloud Vector Engine maintain this Vendor Database in SAP.
    •  In Non-Technical words - is like giving an AI assistant the ability to understand the "meaning" or "vibe" of your company's data instead of just searching for exact words. It serves as a secure, smart memory bank built directly into SAP's database system.
  • SAP OData service - OData (Open Data Protocol) is a key SAP standard for connecting SAP systems to external applications, cloud services, and third-party tools. It uses standard web tech like HTTP, JSON, and XML so different systems can talk to each other easily. 
    • In Non-Technical words - is a secure, standard translator that lets an AI system talk to an SAP database. It acts like a smart menu. The AI asks for data in plain terms, and the service fetches only that information without breaking the database. 
Click here for link to the Blog Posts on the above topic:
Click here for official links to SAP AI development and applications:
https://discovery-center.cloud.sap/serviceCatalog/sap-ai-core/
https://help.sap.com/docs/sap-ai-core/
https://learning.sap.com/courses/introduction-to-ai-core

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

Question: Purchase-to Pay (P2P process) or MM Procurement Process steps:  

Answer: SAP Materials Management (SAP MM) is a core functional module within the SAP ERP and SAP S/4HANA systems that manages an organization's end-to-end procurement and inventory functions. It serves as the operational backbone of the supply chain, ensuring that materials, goods, and resources are available in the right quantity, at the right location, and at the optimal cost
Key Components of SAP MM
The module is divided into several interconnected sub-components that govern specific logistical and financial operations: 
1. SAP-M-MD Master Data: The centralized database repository containing vital records like the Material Master (item specs and storage info) and Vendor Master (supplier details and payment terms)
2. SAP-MM-PUR Purchasing (Procurement): Handles external sourcing workflows including purchase requisitions (PR), requests for quotation (RFQ), and purchase orders (PO).
3. SAP-MM-IM Inventory Management: Real-time tracking of physical stock quantities and financial values across multiple warehouses, managing goods receipts, stock issues, and transfers. Accounting example of GR with reference to Stock scenario PO is:
• Debit Stock G/L Account (Balance Sheet)
• Credit GR/IR Clearining Account (Balance Sheet)
4. SAP-MM-LIV Logistics Invoice Verification: The final auditing step that executes a "three-way match" comparing the vendor’s invoice against the original Purchase Order PRICE and the received goods QUANTITY (Material Document) before releasing payment.
Accounting example of LIV with reference to Stock scenario PO is:
• Debit GR/IR Clearining Account (Balance Sheet)
• Credit Vendor Control Account (Balance Sheet) + record amount owed in Accounts Payable (Subsidiary Ledger)
5. SAP-MM-CBP Consumption Based Planning (MRP): Consumption-based planning tools that automatically calculate how much raw material to purchase based on historical data or production schedules. This module heavily uses re-order planning planning with safety stock and forecasting calculation methods. 
SAP introduced the Material Management (MM) Module in 1972 at the time of the Release of R2, the MM module initially was introduced with the above MM components from PUR, IM, LIV to CBP. It is not until sometime before mid 2000s coincide with transition to ECC that SAP change the MM name to Procurement. 
SAP's Procure-To-Pay (P2P) or Purchase-To-Pay (P2P) process is not a specific product or release date but rather a comprehensive approach to integrating purchasing and accounts payable systems. It's a business process framework within SAP, not a single product launch date. This framework encompasses the entire cycle from identifying needs to making payments. SAP's focus on P2P has been a gradual evolution, with different aspects being addressed through various solutions and modules over time.
The latest buzz word is now Source-to-Pay (S2P)! While P2P is more operational, dealing with ordering, receiving, invoicing, and paying for goods and services, S2P extends even further to include involves strategic activities like market analysis, supplier evaluation, and contract negotiation. The new Source-to-Pay (S2P) name likely coincides with SAP introduction of Central Procurement with the release of SAP S/4HANA 1809 (2018) or maybe around 2000. This release included the Central Procurement hub and features like central contracts, purchase orders, requisitioning, and source of supply assignment. It also provided centralized analytics for procurement processes. 
See the following Presentations for a Basic flow of MM Purchase Requisition to Invoice Verification:

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

Question: Review of Self-Service Procurement Scenario in SAP S/4HANA MM.


Answer: Self-Service Procurement (SSP) in SAP S/4HANA lets casual users and employees buy indirect goods—like office supplies or IT equipment—using simple SAP Fiori apps. Employees pick items from catalogs, managers approve requests, and the system automatically creates purchase orders without heavy buyer input or buyer convert the PR to PO. Then, the Employee who request the indirect goods vai the SSP process will also perform the Goods Receipt via a dedicated Fiori App and if necessary upload the XML-based Supplier Invoice via another Fiori App.
Click here to view the process steps for Self-Service Procurement scenario in S/4HANA:

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

Question: S/4HANA MM process flow and tables.

Answer:
Click the following for MM process flow charts and S/4HANA tables:

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

Question: Review on Design-to-Operate or Production Planning & Execution (PP) Process.


Answer: SAP PP or Production Planning and Execution which was likely introduced some time around 1979 when SAP R2 was Released (remember that R1 was mostly Financial functionality which was released in 1972)! Early versions of SAP, like SAP R/2, included capabilities for manufacturing, sales, and distribution, which formed the foundation for what later became the PP module. 
Some Milestone of major PP module development timeline: 
• 1998: SAP's Advanced Planning and Optimization (APO) module was launched, which included Demand Planning (DP), Supply Network Planning (SNP), PP/DS (Production Planning and Detailed Scheduling) functionality, and Global ATP (GATP) etc.
• 2015: SAP Integrated Business Planning (IBP) was introduced, and in later years, PP/DS was integrated into S/4HANA. SAP Integrated Business Planning (IBP) is a cloud-based solution that helps companies streamline and optimize their supply chain planning processes. It provides a unified platform for demand planning, supply planning, sales and operations planning (S&OP), and inventory management, enabling better decision-making and improved supply chain performance. 
• 2018: PP/DS was launched as an embedded version within SAP S/4HANA. 
The remaining PP component in S/4HANA 2023 are:
Planning: Sales.& Operations Planning (SOP)
Planning: Long Term Planning (LTP) - Simulations
Planning: Master Production Scheduling (MPS) - Planning for Finished Goods
Planning: Material Requirement Planning (MRP) - Planning for Raw Materials
Planning: Embedded Production Planning & Detailed Scheduling (PPDS) - Advanced Planning
Execution: PPDI Discrete Manufacturing Execution using Production Orders 
Execution: PPDI Discrete Manufacturing Execution using Repetitive Manufacturing 
Execution: PPPI Process Manufacturing Execution using Processn Orders 
Execution: PPDI or PI using Kanban
Here are 2 Blog Post of using FIORI App to perform PP Planning and PP Execution: 
https://docs.google.com/Production Planning/
https://docs.google.com/Production Execution/

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

Question: Review of "Predictive MRP" Fiori App capabilities for PP Planning.


Answer: SAP Predictive MRP (pMRP) and Long-Term Planning (PP-MP- LTP) are both forward-looking simulation tools used to predict future material and capacity constraints without affecting live transactional data. LTP is a classic, highly detailed multi-level MRP simulation, whereas pMRP is a streamlined, modern S/4HANA Fiori-based tool built for fast, high-level capacity and demand balancing.

See link to the pMRP apps in Fiori App Library:

Click here to view the link to the Presentation of example of how to use pMRP.

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

at

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.