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

Monday, September 1, 2025

SAP MM - MPN Profile Features

at No comments:
Labels:

Thursday, August 28, 2025

SAP PP - Item Category "R"

CLICK here to view the Presentation

at No comments:
Labels:

Wednesday, August 27, 2025

Question no 4064 : QM Parameters Grouping

In SAP Quality Management as at S/4 1909, the following parameters can be found in which of the following QM configuration ?

. Technical Delivery Term and Q-agreement requirement
. Release required
. Certificate required
. Source Inspection rejection treatment at GR

(only one answer)

A) Quality Info Record.
B) QM Inspection Type in the Material Master QM view.
C) QM Control Key.
D) Status of Supplier Relationship.
E) Inspection Lot Document Type parameter.
.

Answer: C

IMG > QM > QM in Logistcis > QM in Procurement > Define Control Keys

at No comments:
Labels: , ,

SAP MM - GR and GR-non-valuated Indicator effect at GR and LIV

CLICK here to view the Presentation

at No comments:
Labels:

Monday, August 25, 2025

SAP MM - Purchasing Document Release Strategy setup for 4 Release Codes

CLICK here to view the Presenation

at No comments:
Labels:

Q&A in Class (2025-08-28) S4500

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

Question: Review Fiori Navigations in Classic Fiori Group/Tile AND "Space and Pages".


Answer: Fiori Navigation basics as below Blog Posts.
Click the following to check the Navigation basics for Classic Fiori Group AND "Space and Pages":

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

Question: Exploring FIORI in S/4HANA. 

Answer: The first generation of SAP Fiori, version 1.0, was released in 2013. The main interface are Fiori Groups which contain a logical grouping of Fiori Tiles. It introduced a mobile-first design approach with a focus on simplifying business tasks and providing a responsive user experience across different devices. Initially, focused on a mobile-first approach, providing a simplified, user-friendly interface for common business tasks within the existing SAP ECC environment. It initially offered a limited set of 25 transactional apps, like those for approving requests or viewing sales orders, specifically designed to improve the user experience for frequently used functions.

SAP introduced the next generation Fiori interface called Spaces and Pages in the SAP Fiori Launchpad which was release in S/4HANA 2020 to improve user experience by enhancing organization, personalization, and flexibility in accessing and managing applications. Spaces and pages offer a more structured and intuitive way to navigate the Fiori Launchpad, making it easier for users to find the apps they need for their specific roles and tasks. 

To help you to understand SAP Fiori, here are some official links:

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

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

Question: Review Fiori "Save as a New Tile" feature steps


Answer: In SAP Fiori, "Save as a New Tile" allows you to create a persistent shortcut to a currently running Fiori app or a filtered view of a worklist, saving your specific selections, filters, or the app's current state. Clicking this tile later will launch the app or worklist directly in that saved, pre-configured state, saving you time by eliminating the need to re-enter the same filters or settings each time. 
This feature is much easier compare to the Transaction Variant in the ECC system or S/4 Backend Transaction Code. AND the Fiori feature is available for both the Classic Fiori Group as well the new "Spaces and Pages".
See the following Blog Posts on how to "Save as a New Tile" with new Filter and new Columns Display:

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

Question: MM Enterprise Structure 


Answer: Enterprise Structure assignment rules in MM:
• Cross-Company Scenario - A Purchasing Organization assignment to Company Code is OPTIONAL (note Purchasing Organization 1 is NOT assigned to any Company Code), in this case Purchasing Organization 1 can issue Purchase Order for Plants which are assigned to different Plants. Example, the Purchasing Organization 1 is assigned to Plant 1, Plant 2 and Plant 3 which are respectively assigned to Company Code 1 and Company Code 2. SAP refer to this as Cross-Company Scenario.
• Cross-Plant Scenario within a Company - A Purchasing can only assigned to ONE Company Code (not more than 1) and note Purchasing Organization 2 is assigned to the Company Code 2. AND do note that Plant 2 and Plant 3 are both assigned to the same Company Code 2 as well as Purchasing Organization. In this case, the Purchasing Organizaiton 2 can issue PO for Plant 2 and Plant 3 only. 
• Plant Specific Scenario - The relationship of 1:1 between Purchasing Organization and Company Code. AND also with a 1:1 relationship between Purchasing Organization and a Plant. 

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

Question: MM Fiori App to Create PO, Goods Receipt with reference to PO, and Invoice Verification 


Answer: SAP Material Management (MM) is a one of the Logistics module within SAP's Enterprise Resource Planning (ERP) system (or the current S/4HANA system), designed to manage the procurement or materials and services, storage of material, consumption of materials, and invoice verification of supplier invoice to the accounting component. The MM module plays a key role in an organization's supply chain by automating and streamlining processes related to materials, inventory, and vendor Accounts management via FI-Accounts Payable.
SAP MM Components: 
• MM-PUR (Purchasing) - PR, RFQ, Quotation, PO, Contract, Scheduling Agreement
• MM-IM (Inventory Management) - Goods Receipt, Stock Transfers, Goods Issues
• MM-IV-LIV (Logistics Invoice Verification) - 3-way Matching of Supplier Invoice to GR Material Document and Purchase Order Price
• MM-MRP-CBP (Consumption Based Planning) - ReOrder Point Planning, Forecasting, Consumption Based Planning
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 (Purchasing), IM (Inventory Management), LIV (Logistics Invoice Verification) to MRP via CBP (Consumption Based Planning).  
SAP new name for MM is Procure-To-Pay (P2P) or Purchase-To-Pay (P2P) process, these are 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 Enterprise Structure, Primary Master Data, Secondary Master Data, and Process.

 
Answer: The following are the details of understanding the process design principles.
Enterprise Structure:
Company Code is the FI Enterprise Structure for MM-FI integraiton.
Purchasing Organization is MM Enterprise Structure unit for Purchasing Management.
Plant is where Logistics activity takes place for MM process.
Storage Location is for Stock scenario. 
Purchasing Group is strictly not part of the MM Enterprise Structure as it is not assigned directly to any Enterprise Structure in the SPRO (IMG). The Purchasing Group is assigned to the BP Vendor (at the Pur.Org level) as well as the Material Master (at the Plant level). 
Primary Master Data: 
Business Partner vendor is created for the Company Code (Accounting Parameters eg: Reconciliation Account and non-PO based Payment Term).
Material Master is created for the Plant for the Procurement and Storage Activity.
Secondary Master Data: 
Purchasing Info Record specifies the negotiated price and purchasing terms by the Purchasing Organization to the Business Partner Vendor for the Materials receiving into a Plant.
Process: (Stock Procurement Scenario): 
Header PO: 
Business Partner Vendor is the Vendor for the PO issued.
Company Code is legally responsible for the Purchasing Document.
Purchasing Organization is responsible for the PO (Logistics arrangement). 
Purchasing Group is to manage the Life-Cycle of the PO.
PO item level:
Material is the Purchasing Item of intent to the BP Vendor.
Plant is where Vendor will send the Material to.
Storage Location is for MM Inventory Management for Goods Receipt of the Material for Storage.
Purchasing Info Record provides the Price and Purchasing Terms (when the BP Vendor, Material, Plant, Purchasing Organization matches the PIR).

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

Question: Review the Business Partner.


Answer: Classic transaction code in ECC for Vendor Master Creation/Change/Display (XK01, XK02, XK03, MK01, MK02, MK03, FK01, FK02, FK03 etc) are now Obsolete in S/4HANA which is replaced by a Single transaction code "BP". In SAP S/4HANA, the Business Partner (BP) is the central and leading object used to maintain master data for both customers and suppliers. It serves as a single point of entry for managing various types of business relationships. 
•  The Business Partner is used to create the following: 
• BP for Vendor or Customer via "Organization" (to create Vendor or Customer)
• BP for Individuals via "Persons"
• BP for Groups of People via "Groups"
•  The BP approach aims to harmonize master data across different SAP modules and applications, improving data consistency and simplifying data management. 
Advantages:
•  Reduced Redundancy: Basic data like name, address, and bank details are stored centrally at the BP level, avoiding duplication. 
•  Improved Data Consolidation: Centralized data management makes it easier to consolidate and analyze information related to business partners. 
•  Flexibility: The BP model allows for multiple addresses, address usages, and relationships to be managed for a single BP. 
 
Here are 2 Blog Posts using S/4 Backend and Fiori App to create the Business Partner for Vendor: 

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

Question: Review the Product Master Data (or Material Master)


Answer: First thing first, that the ECC "Material Master" is also referred to as "Product Master Data" in SAP S/4HANA. While the "Material Master" can still use Classic GUI via transaction codes like MM01, MM02, MM03 to manage it in S/4HANA Backend System, The "Product Master" is a FIORI "UX" App that acts is a centralized repository of all information related to a product or material. It acts as the single source of truth, containing details like product number, description, attributes, pricing, and more, ensuring consistency across various business processes like sales, procurement, and supply chain. 
It is important to note that "Material Master" = "Product Master Data". 
Here are Fiori Apps for Material Master and Product Master Data in S/4HANA system: 
https://froggysap.blogspot.com/2025/08/sales-and-distribution-manage-product.html
https://froggysap.blogspot.com/2023/02/s4-mm-master-data-create-product-master.html
https://froggysap.blogspot.com/2021/11/material-master-mm01-mm17-mmsc-manage.html

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

Question: Review on GR indicator and GR non-valuated indicator in the PO item detail.

Answer: In SAP, a "GR Non-Valuated" indicator is a setting in a Purchase Order (PO) that prevents financial accounting postings from being made at the time of Goods Receipt (GR). Instead, the financial posting, which includes the value of the goods, occurs only when the supplier's Invoice Receipt (IR) is processed. This indicator is used for items where the physical receipt of goods does not correspond to a financial transaction at that moment, such as for fixed assets to comply with regulations or for items with multiple account assignments.
How it works:
1. GR is posted without financial impact: When the GR non-valuated indicator is active, receiving the material updates the quantity in inventory, but no financial entry is created in the general ledger. 
2. Financial Posting at Invoice Receipt: The actual valuation and financial posting are deferred to the invoice verification stage (MIRO transaction). 
3. GR/IR Clearing Account: If GR non-valuated indicator is active, no GR/IR Clearing Account is posted at Goods Receipt step and therefore, there will not be any posting the the G/IR Clearing Account in time of  invoice verification stage (MIRO transaction). The Expenses Account is directly posted at time of invoice stage. 
When to use it:
• Fixed Assets: To comply with legal requirements in some countries, which state that an asset acquisition cannot be recorded until a valid invoice is received. 
• Multiple Account Assignment: When a single purchase order line item is assigned to several cost centers, plants, or other accounts. 
• Cost Centers: To track the receipt of items for direct consumption to a cost center without creating a value entry at the GR stage. 
• Internal Orders: For procurement related to an internal order with budget allocation, where the financial impact is tied to the order's budget rather than the goods receipt. 
• Service Materials: For certain items like services (DIEN material type), where a valuated GR is not relevant. 
See the following Blog Posts on the detail SAP demonstration of the above case:

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

Question: Review Source Determination and Automatic PR to PO creation.


Answer: SAP Source Determination is a process that allows the SAP system to automatically suggest or assign suitable suppliers (sources of supply) for a material when creating a purchase requisition or during a material requirements planning (MRP) run. It uses pre-defined criteria and master data like source lists and quota arrangements to identify the most appropriate vendor or internal source. This streamlines procurement by finding the best source based on factors such as price, quality, and delivery history, assigning it directly or providing it as a suggestion in the source of supply tab.
To create an SAP Automatic Purchase Order (PO) from a Purchase Requisition (PR), first enable the "Automatic PO" checkbox in both the material master and vendor master records. Next, maintain the source list and the purchase info record for the relevant material and vendor. Then, create a purchase requisition, ensuring you assign a source of supply. Finally, run the ME59N transaction to convert the PR into an automatic PO. 
Prerequisites:
1. Material Master: In the material master (transaction MM02), go to the purchasing view and select the "Automatic PO" indicator at the plant level of the material master
2. Vendor Master: In the vendor master (transaction XK02 for ECC or BP for S/4 HANA), go to the purchasing data for the purchase organization and select the "Automatic PO" checkbox. 
Steps to Create the Automatic PO: 
1. Create Purchase Requisition (PR): Create a purchase requisition using transaction ME51N. 
2. Assign Source of Supply: In the PR, ensure you assign the source of supply (the vendor and material from the info record) either directly in ME51N, ME52N, ME56 or ME57.
3. Execute Automatic Conversion: Run the ME59N transaction. 
4. Provide Details: To filter the PRs can enter combination of Purchasing Group, Vendor, Purchasing Organization, and Plant. Then, select the Combine or Split criterion of Purchasing Group, Plant, Item Category etc. Recommended also to set "Detailed Log = 2 for All Messages", the use "TEST Run" mode to determine results. 
5. Generate PO: Execute the transaction using "ACTUAL Run", and the system will automatically create the purchase order from the PR automatically.
See the following Blog Posts:

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

at No comments:
Labels:

Sunday, August 24, 2025

SAP MM - Create new Unit of Measure

at No comments:
Labels:

Thursday, August 21, 2025

SAP MM - Tolerance Key "VP" at GR with reference to PO

CLICK here to view the Presentation

at No comments:
Labels:

Question no 4063 : Handling Unit Management for Material Management

In SAP HUM for Material Management, which of the following is TRUE about packing a Product into a Packing Material as a HU ?

(more than one answers)

A) The Product to be packed must be assign to a "Material Group Packing Material".
B) The Packing Material must be assign to a "Packing Material Type".
C) The Product to be packed must be assign to a "Packing Material Type".
D) The Packing Material must be assign to a "Material Group Packing Material".
E) The Material Type that used to create Product to be packed must be assigned as Allowed to be packed into Packing material with the "Packing Material Type".
.

Answer: A, B

Basic requirements:
. The Product to be packed must be assign to a "Material Group Packing Material".
. The Packing Material must be assign to a "Packing Material Type".
. "Material Group Packing Material" is assigned to "Packing Material Type" in the Configuration "Allowed Packing Material Type per Material Group for Packing Material".
. The Allowed Weight and Volume of the Packing Material to be set correctly.
. The Tare Weight and Volume of both Packing Material and Products to be set correctly.

at No comments:
Labels: , ,

SAP MM - Source Determination for PR - Auto PO - GR into Stocks

CLICK here to view the Presentation

at No comments:
Labels:

Wednesday, August 20, 2025

Q&A in Class (2025-08-21) S4500

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

Question: Review the Business Partner.


Answer: Classic transaction code in ECC for Vendor Master Creation/Change/Display (XK01, XK02, XK03, MK01, MK02, MK03, FK01, FK02, FK03 etc) are now Obsolete in S/4HANA which is replaced by a Single transaction code "BP". In SAP S/4HANA, the Business Partner (BP) is the central and leading object used to maintain master data for both customers and suppliers. It serves as a single point of entry for managing various types of business relationships. 
•  The Business Partner is used to create the following: 
• BP for Vendor or Customer via "Organization" (to create Vendor or Customer)
• BP for Individuals via "Persons"
• BP for Groups of People via "Groups"
•  The BP approach aims to harmonize master data across different SAP modules and applications, improving data consistency and simplifying data management. 
Advantages:
•  Reduced Redundancy: Basic data like name, address, and bank details are stored centrally at the BP level, avoiding duplication. 
•  Improved Data Consolidation: Centralized data management makes it easier to consolidate and analyze information related to business partners. 
•  Flexibility: The BP model allows for multiple addresses, address usages, and relationships to be managed for a single BP. 
 
Here are 2 Blog Posts using S/4 Backend and Fiori App to create the Business Partner for Vendor: 

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

Question: Review the Product Master Data (or Material Master)


Answer: First thing first, that the ECC "Material Master" is also referred to as "Product Master Data" in SAP S/4HANA. While the "Material Master" can still use Classic GUI via transaction codes like MM01, MM02, MM03 to manage it in S/4HANA Backend System, The "Product Master" is a FIORI "UX" App that acts is a centralized repository of all information related to a product or material. It acts as the single source of truth, containing details like product number, description, attributes, pricing, and more, ensuring consistency across various business processes like sales, procurement, and supply chain. 
It is important to note that "Material Master" = "Product Master Data". 
Here are Fiori Apps for Material Master and Product Master Data in S/4HANA system: 
https://froggysap.blogspot.com/2023/02/s4-mm-master-data-create-product-master.html
https://froggysap.blogspot.com/2021/11/material-master-mm01-mm17-mmsc-manage.html

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

Question: Review on Purchase-to-Pay or Materials Management (MM) Process.


Answer: SAP Material Management (MM) is a crucial module within SAP's Enterprise Resource Planning (ERP) system, designed to manage the procurement, storage, consumption of materials, and invoice verification of supplier invocie. It plays a key role in an organization's supply chain by automating and streamlining processes related to materials, inventory, and vendor management.
SAP MM Components: 
• MM-PUR (Purchasing) - PR, RFQ, Quotation, PO, Contract, Scheduling Agreement
• MM-IM (Inventory Management) - Goods Receipt, Stock Transfers, Goods Issues
• MM-IV-LIV (Logistics Invoice Verification) - 3-way Matching of Supplier Invoice to GR Material Document and PO Price
• MM-MRP-CBP (Consumption Based Planning) - ReOrder Point Planning, Forecasting, Consumption Based Planning
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: Source Determination for Contract and Info Record to PR, Auto PO and GR

Click below to check the step:

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

Question: SAP Course Recommendations for Plant Maintenance Planner.


Answer: See the following Recommendation:
• S43000 - Business Processes in SAP S/4HANA Asset Management (formerly S4130) (3 Days)
• S43400 - Exploring Advanced Functions in Maintenance Processing (1 Day)
• S43410 - Refurbishment of Spare Parts (1 Day)
• S43100 - Managing Technical Objects in SAP S/4HANA (formerly S4131) (3 Days)

(2) Customized MRP for Spare Parts planning (4+4):
Duration: as Discussed (sequence and topics may adjusted at time of actual design preparation)
• SAP CBP 4-steps logic Mechanics in MRP 1, 2 view (Material Master)
• Re-Order Point Principles, Formula and Practice
• Safety Stock Calculation
• Scheduling principles in ROP in SAP
• Understanding Planned and Unplanned Goods Issue
• Forecasting Principles, Formula and Practice
• SAP Forecasting settings in Forecasting view (Material Master)
• Re-Order Point SAP Calculation methods and concerns
• Lead time determination via Supplier Delivery History
• Stock Days Supply Calculations
• Use of Plant Parameter for CBP
• Use of MRP Group Parameter for CBP
• Other IMG Parameters for CBP
• Ensuring PM Spare Parts MRP planning accuracy
• Classic MRP and MRP Live for ROP
• Fiori App for CBP Planning Run
• Re-Order Point with Maintenance Order Reservations
• Using MRP Controller for MRP Evaluations
• Using Product Group for MRP Evaluations
• Controlling MRP run using MD02 via Product Group
• Evaluation tools in MD04 and MD05
• Evaluation tools in MD06 and MD07
• Evaluation tools for MRP Results via FIORI App
• Understanding Exception Messages

(3) Material Management (SAP-MM) Course Recommendations 
• S4510 - Inventory Management and Physical Inventory in SAP S/4HANA (5 Days)

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

Question: During Goods Receipt of PO, there is a WARNING message of MAP Tolerance, what are the calculations, setting and effects of that message?


Answer: In SAP MM, the tolerance key VP is used to manage variances related to the moving average price (MAP) during goods receipt (GR). When a goods receipt is posted, the system checks if the new MAP, calculated after the receipt, exceeds the defined tolerance limits.
The results of the Posting changes the MAP in the Material Master and therefore revaluate the Stocks of the the Material, and this applies to Price Control "V".
See the following Blog Posts for the Simulation:

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

at No comments:
Labels:

Tuesday, August 19, 2025

SAP QM - new Defects Handling (S/4HANA)

 

CLICK here to view the Presentation

at No comments:
Labels:

Monday, August 18, 2025

SAP FIORI - "SAVE as NEW TILE" in "SPACE and PAGES"

CLICK here to view the Presentation

at No comments:
Labels:

Q&A in Class (2025-08-20) S43000

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

Question: Exploring FIORI in S/4HANA. 

Answer: The first generation of SAP Fiori, version 1.0, was released in 2013. The main interface are Fiori Groups which contain a logical grouping of Fiori Tiles. It introduced a mobile-first design approach with a focus on simplifying business tasks and providing a responsive user experience across different devices. Initially, focused on a mobile-first approach, providing a simplified, user-friendly interface for common business tasks within the existing SAP ECC environment. It initially offered a limited set of 25 transactional apps, like those for approving requests or viewing sales orders, specifically designed to improve the user experience for frequently used functions.

SAP Fiori apps are primarily built using SAPUI5, which is a UI development toolkit for HTML5. SAPUI5 utilizes a combination of web technologies, including:

• HTML5: For structuring the content and defining the layout of the user interface.
• JavaScript: The core programming language for implementing application logic, handling user interactions, and manipulating the UI.
• XML: Often used for defining views and structuring the UI components within SAPUI5 applications.
• CSS: For styling the appearance of the Fiori apps and ensuring a consistent look and feel according to the Fiori design guidelines.
• Notes: While SAPUI5 is the foundation for most web-based Fiori apps, native Fiori apps can also be developed for specific platforms using their respective native languages, such as Swift for iOS or Java for Android. However, the majority of standard SAP Fiori apps are built with SAPUI5.

SAP introduced the next generation Fiori interface called Spaces and Pages in the SAP Fiori Launchpad which was release in S/4HANA 2020 to improve user experience by enhancing organization, personalization, and flexibility in accessing and managing applications. Spaces and pages offer a more structured and intuitive way to navigate the Fiori Launchpad, making it easier for users to find the apps they need for their specific roles and tasks. 

To help you to understand SAP Fiori, here are some official links:

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

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

Question: Review how to ceate a New Tile in "Space and Pages".


Answer: To create a new tile within an SAP Fiori Launchpad space and page, you need to first create the tile, then add it to a page, and finally assign that page to a space which is then assigned to a business role. This process ensures users can access the new tile through their personalized launchpad experience. 
Click the following Blog Posts to see steps of how to ceate a New Tile in "Space and Pages" in S/4HANA 2023.

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

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:

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

at No comments:
Labels:

REM Manufacturing (Fiori Apps S/4 1909)

at No comments:
Labels:

Friday, August 15, 2025

Question no 4062 : Serial Level for Equipment-Serial link

In SAP Plant Maintenance as at S/4 1909, when the Serial Master linked to the Equipment was found to not have the same numbers (ie Serial and Equipment not having the same number), which of the following could be true ? 

(only one answer)

A) The Serial Level assigned to the Serial Profile in the Configuration was set with "Serialization with the Stock Material Number". 
B) The Serial Level assigned to the Equipment Category in the Configuration was set with "Serialization with the Stock Material Number". 
C) The Serial Level assigned to the Plant in the Configuration was set with "Serialization with the Stock Material Number". 
D) The Serial Level assigned to the Material Master was set with "Serialization with the Stock Material Number". 
E) The Serial Level assigned to the MIGO (Goods Movement) item detail screen was set with "Serialization with the Stock Material Number". 
.

Answer: D

Serial Level and Serial Profile is the Plant/Storage 2 view in the Material Master

at No comments:
Labels: ,

Thursday, August 14, 2025

SAP PM - Inspection Checklist (S/4) Part 2

 

click "here" to view the Presentation

at No comments:
Labels:

Wednesday, August 13, 2025

SAP Finance for non Accountants - new G/L new Cost Center Posting Outgoing Invoice

 

click "here" to view the Presentation

at No comments:
Labels:

Monday, August 11, 2025

Q&A in Class (2025-08-13) S4H00

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

Question: AI applications in ERP software, hype or real?


Answer: SAP's AI strategy focuses on making AI relevant, reliable, and responsible by embedding it into their business applications and processes. They aim to enhance user experience, streamline operations, and drive innovation by leveraging AI across their entire portfolio. SAP Business AI is built on three pillars: embedded AI, AI services via the SAP Business Technology Platform (BTP), and strategic partnerships.
Current SAP AI Focus Areas:
• Joule: SAP's AI-powered co-pilot, Joule, provides a unified interface for users to interact with their business systems and automate tasks. 
• SAP Joule is a generative AI copilot designed to enhance user experience and productivity within SAP's ecosystem. It acts as a digital assistant, leveraging natural language processing (NLP) to simplify interactions with SAP applications and data.
• Joule analyzes user intent and business context to provide relevant information, automate tasks, and offer insights, ultimately aiming to improve efficiency and decision-making across various business functions.
• Intelligent Automation: SAP uses AI to automate routine tasks, analyze data, and streamline workflows across various business functions. 
• This solution focuses on process automation, integrating intelligent robotic process automation (IRPA), SAP workflow, and workflow management. SAP Intelligent Robotic Process Automation (iRPA) is a platform that uses software robots, or "bots," to automate repetitive, rule-based tasks within SAP systems and other applications.
• It leverages AI and machine learning to handle complex processes and improve efficiency by automating tasks like data entry, data extraction, and system navigation. This allows employees to focus on more strategic and value-added work.
• AI-powered Insights: SAP leverages AI to provide users with actionable insights, predictive analytics, and personalized recommendations. 
• SAP AI-powered Insights refers to the use of artificial intelligence (AI) and machine learning (ML) technologies within SAP's software solutions to provide businesses with actionable insights, automate processes, and improve decision-making.
• SAP AI analyzes real-time data to offer recommendations and predictions, helping businesses make informed decisions faster.
• ML algorithms forecast trends, optimize resource allocation, and improve efficiency in areas like supply chain and finance.

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

Question: What is SAP Simplification List?

Answer: The "Simplification List" for SAP S/4HANA is a document that outlines the functional changes and differences between SAP ECC (or other SAP Business Suite systems) and SAP S/4HANA. It helps customers understand what needs to be done during a conversion or migration to S/4HANA. The list is typically provided as a PDF download

See the following pdf download:

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

Question: Exploring FIORI in S/4HANA. 

Answer: The first generation of SAP Fiori, version 1.0, was released in 2013. The main interface are Fiori Groups which contain a logical grouping of Fiori Tiles. It introduced a mobile-first design approach with a focus on simplifying business tasks and providing a responsive user experience across different devices. Initially, focused on a mobile-first approach, providing a simplified, user-friendly interface for common business tasks within the existing SAP ECC environment. It initially offered a limited set of 25 transactional apps, like those for approving requests or viewing sales orders, specifically designed to improve the user experience for frequently used functions.

SAP Fiori apps are primarily built using SAPUI5, which is a UI development toolkit for HTML5. SAPUI5 utilizes a combination of web technologies, including:
• HTML5: For structuring the content and defining the layout of the user interface.
• JavaScript: The core programming language for implementing application logic, handling user interactions, and manipulating the UI.
• XML: Often used for defining views and structuring the UI components within SAPUI5 applications.
• CSS: For styling the appearance of the Fiori apps and ensuring a consistent look and feel according to the Fiori design guidelines.
• Notes: While SAPUI5 is the foundation for most web-based Fiori apps, native Fiori apps can also be developed for specific platforms using their respective native languages, such as Swift for iOS or Java for Android. However, the majority of standard SAP Fiori apps are built with SAPUI5.

SAP introduced the next generation Fiori interface called Spaces and Pages in the SAP Fiori Launchpad which was release in S/4HANA 2020 to improve user experience by enhancing organization, personalization, and flexibility in accessing and managing applications. Spaces and pages offer a more structured and intuitive way to navigate the Fiori Launchpad, making it easier for users to find the apps they need for their specific roles and tasks. 

To help you to understand SAP Fiori, here are some official links:

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

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

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

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. 
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. 

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

Question: Review the Business Partner.


Answer: In SAP S/4HANA, the Business Partner (BP) is the central and leading object used to maintain master data for customers and suppliers (formerly known as customer master via t-code XD01/FD01/VD01 and vendors master via t-code XK01/FK01/MK01). It serves as a single point of entry for managing various types of business relationships. The Business Partner is used to create the following: 
• BP for Vendor or Customer via "Organization" 
• BP for Individuals via "Persons"
• BP for Groups of People via "Groups"
Here are 2 Blog Posts using S/4 Backend and Fiori App to create the Business Partner for Vendor: 

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

Question: Review the Product Master Data (or Material Master)


Answer: In SAP, the "Product Master Data" is a FIORI "UX" App that acts is a centralized repository of all information related to a product or material. It acts as the single source of truth, containing details like product number, description, attributes, pricing, and more, ensuring consistency across various business processes like sales, procurement, and supply chain. 
However, it is more commonly known as the "Material Master" in the Classic GUI in S/4HANA Backend via transaction code MM01. 
https://froggysap.blogspot.com/2023/02/s4-mm-master-data-create-product-master.html
https://froggysap.blogspot.com/2021/11/material-master-mm01-mm17-mmsc-manage.html

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

Question: Review on Purchase-to-Pay or Materials Management (MM) Process.


Answer: SAP Material Management (MM) is a crucial module within SAP's Enterprise Resource Planning (ERP) system, designed to manage the procurement, storage, consumption of materials, and invoice verification of supplier invocie. It plays a key role in an organization's supply chain by automating and streamlining processes related to materials, inventory, and vendor management.
SAP MM Components: 
• MM-PUR (Purchasing) - PR, RFQ, Quotation, PO, Contract, Scheduling Agreement
• MM-IM (Inventory Management) - Goods Receipt, Stock Transfers, Goods Issues
• MM-IV-LIV (Logistics Invoice Verification) - 3-way Matching of Supplier Invoice to GR Material Document and PO Price
• MM-MRP-CBP (Consumption Based Planning) - ReOrder Point Planning, Forecasting, Consumption Based Planning
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 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 on Order-to-Cash or Sales & Distribution (SD) Process.


Answer: The Sales & Distribution (SD) Module was introduced alongside the MM Module in 1978 when SAP R2 was Released, it is now called Order-to-Cash (O2C). 
The Operation Components of SD are:
• SD-SLS refers to Sales Order Processing
• SD-DLV refers to the Delivery within the SD module
• SD-BIL refers to the Billing step within the SD module 

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

Question: Review a Sales Analytics Fiori App. 


Answer: SAP Sales Analytics refers to the tools and processes within SAP's software solutions that enable businesses to analyze sales data, monitor performance, and gain insights to improve sales strategies and outcomes. This includes leveraging solutions like SAP Analytics Cloud (SAC), SAP S/4HANA Embedded Analytics, and various SAP Fiori analytical apps for sales. 
Click here to view an example of Sales Analytics:

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

Question: What is SAP Signavio Process Navigator.



Answer: SAP Signavio Process Navigator is a tool that helps users explore and understand SAP's pre-defined business processes. It acts as a central repository, providing access to solution scenarios, related processes, and contextual information like integrations and applications. It essentially replaces the SAP Best Practices Explorer and offers a more comprehensive view of SAP solutions and their implementation. 
Purpose: The Process Navigator allows users to discover, analyze, and understand SAP's pre-defined business processes and solution scenarios. 
Content: It provides access to various aspects of SAP solutions, including:
Solution Scenarios: High-level overviews of business processes, such as "Lead to Cash" or "Plan to Fulfill". 
• Solution Processes: Detailed diagrams and information about specific processes within a scenario. 
• Contextual Information: Data on integrations, applications, and solution capabilities related to the processes. 
• Integration: It's integrated into SAP for Me, making it easily accessible for users within the SAP ecosystem. 
Key Features:
• Search and Filtering: Allows users to quickly find specific processes and scenarios. 
Visualizations: Provides flow diagrams to illustrate process flows. 
• Language Support: Offers translated process descriptions to cater to a wider audience. 
Integration with other SAP tools: Links to other SAP solutions like Cloud ALM for implementation and management. 
Benefits:
• Improved Understanding: Helps users grasp the intricacies of SAP solutions and their potential applications. 
• Efficient Implementation: Facilitates the planning and execution of SAP projects by providing a clear understanding of the processes involved. 
• Enhanced Collaboration: Enables teams to work with a shared understanding of business processes. 
See the following post on Signavio Process Navigator:

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

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