_U0103_OrgStructureSD_Blogged.jpg)
Monday, September 22, 2025
Sunday, September 21, 2025
_U0101_Fiori.jpg)
Saturday, September 20, 2025
Question no 4067 : Material Specification Attributes
In SAP Quality Management (as at S/4HANA 2023), which of the following features are not possible for direct assignment in the "Material Specification"?
(more than one answers)
A) Sampling Procedure
B) Dynamic Modification Rule.
C) Sample Drawing Procedure
D) Inspection Point.
E) Inspection Method.
.
Answer: B, C, D, E
The following can be assigned to Material Specification:
. Master Inspection Characteristics (with Version)
. Sampling Procedure
(more than one answers)
A) Sampling Procedure
B) Dynamic Modification Rule.
C) Sample Drawing Procedure
D) Inspection Point.
E) Inspection Method.
.
Answer: B, C, D, E
The following can be assigned to Material Specification:
. Master Inspection Characteristics (with Version)
. Sampling Procedure
Dynamic Modification Rule: can be assigned at three different levels: the inspection plan header (for lot-level or inspection type level) (QP02) , the inspection plan characteristic (QP02), or the material master's inspection type setup in the QM data view (MM02) .
.jpg)
Friday, September 19, 2025
_U0514_UseTheSalesOrderFulfillmentApp.jpg)
Wednesday, September 17, 2025
Tuesday, September 16, 2025
Monday, September 15, 2025
Sunday, September 14, 2025
Saturday, September 13, 2025
_Blogged.jpg)
Thursday, September 11, 2025
Question no 4066 : Task list based Inspection Characteristics
In SAP Quality Management, when using Inspection Characteristics in Task List; it can be used for which of the following scenarios ?
(more than one answers)
A) In-Process Quality Inspection.
B) Recurring Inspection for Batches.
C) Calibration of Equipment.
D) Inspection for Physical Samples.
E) Goods Receipt Inspection for External Processing.
.
Answer: A, C
A) In-Process Quality Inspection is for Production Order/Process Order (Inspection Type "03") and Repetitive Manufacturing (Inspection Type "13") Inspection during Production. Master Inspection Characteristics are assigned to Routing, Recipe, and Rate Routing.
C) To perform Equipment Calibration, Master Inspection Characteristics are assigned to the Maintenance Task List.
(more than one answers)
A) In-Process Quality Inspection.
B) Recurring Inspection for Batches.
C) Calibration of Equipment.
D) Inspection for Physical Samples.
E) Goods Receipt Inspection for External Processing.
.
Answer: A, C
A) In-Process Quality Inspection is for Production Order/Process Order (Inspection Type "03") and Repetitive Manufacturing (Inspection Type "13") Inspection during Production. Master Inspection Characteristics are assigned to Routing, Recipe, and Rate Routing.
C) To perform Equipment Calibration, Master Inspection Characteristics are assigned to the Maintenance Task List.
Tuesday, September 9, 2025
Monday, September 8, 2025
Q&A in Class (2025-09-16) EWM110
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review Integration setup steps for EWM as a Distributed system (from an Application perspective)
.jpg)
Steps (some are combined steps):
01. ECC - Enterprise Structure Configuration (Plant + SLoc + LE-WM)
02. ECC - Connection (Local/EWM/Dist.WM + Serialized Asynchronous qRFC)
03. ECC - Logical System (for both ECC and EWM and RFC Connection)
04. ECC - Generate Distribution Model (Data Channel activation for Objects from ECC to EWM)
05. ECC - Messages (Log and Register)
06. ECC - Delivery Split (Delivery Type or Warehouse basis)
07. EWM - Business System (Own EWM and ECC + commit to Logical System)
08 EWM - Enterprise Structure (EWM)
09. EWM - Business Partner (Plant, Ship-from and Ship-to)
10. EWM - EWM and Business Partner (Mapping for Custodian, STO etc)
11. EWM - qRFC ("Inbound" from which Source)
12. EWM - Availability Group
13. EWM - Map Availability Group to Plant + SLoc
14. EWM - Supply Chain Unit (Mapping to Business Partners)
14. EWM - Create Availability Group, related configuration and MM SLoc Mapping
15. ECC - Create new MM Storage Location for EWM processing
16. EWM - Create Availability Group, related configuration and MM SLoc Mapping
17. ECC to EWM - Material Master BDC Send to EWM
18. ECC to EWM - Simulate PO GR into EWM-based SLoc
**** when simulating exercise in Learning Hub ****
• Use your Group ID for all data to be created or when requested in the Exercises
• When creating anything else in SPRO, please code start with X, Y or Z and end with ## (your Group ID when Enroll to the LH)
• Do not change any other SPRO configuration at Client or 'given' Plant level (eg: Plant SPCW)
• Do not deactivate any Technical integration settings
See the following Blog Post for the step-by-step above:
**** Use the following data for the above exercise steps in the Blog ****
## is your assign Group number for the Exercises
• Step 15 MM Storage Location use XM##, YM##, or ZM##
• Step 16 EWM Stock Type "F6", "F7", "F8" or create X#, Y#, or Z#
• Step 17 Material T-EW03-## or copy to Material Z-EW03-## (Basic, Purchasing, Accounting views)
• Step 18 Receiving Shipping Point use XM##, YM##, or ZM##
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review Integration setup steps for EWM as an Embedded system (from an Application perspective)
.jpg)
Answer: The following Integration steps are for S/4HANA 2023 Embedded EWM scenario, some of these steps may differ slightly depending on version used and further "Simplification" by SAP for S/4HANA Embedded scenarios.
Steps (some are combined steps):
01. EWM - Enterprise Structure Configuration (Plant + SLoc + LE-WM)
02. EWM - Connection (Local/EWM/Dist.WM + Serialized Asynchronous qRFC)
03. EWM - Logical System (for both ECC and EWM and RFC Connection)
04. EWM - Generate Distribution Model (Data Channel activation for Objects within Embedded EWM)
05. EWM - Messages (Log and Register)
06. EWM - Delivery Split (Delivery Type or Warehouse basis)
07. EWM - Business System (EWM to Logical System)
08. EWM - Business Partner (Plant, Ship-from and Ship-to) OPTIONAL
09. EWM - EWM and Business Partner (Mapping for Custodian, STO etc)
10. EWM - qRFC ("Inbound" within EWM)
11. EWM - Availability Group
12. EWM - Map Availability Group to Plant + SLoc
13. EWM - Supply Chain Unit (Mapping to Business Partners)
14. ECC - Create new MM Storage Location for EWM processing
15. EWM - Create Availability Group, related configuration and MM SLoc Mapping
16. ECC to EWM - Material Master BDC Send to EWM (NOT REQUIRED in Embedded EWM)
17. ECC to EWM - Simulate PO GR into EWM-based SLoc
See the following Blog Post for the step-by-step above:Pending
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: ERROR in Storage Type determination when create WT for an Outbound Scenario.
Answer: The above ERROR in the in-class exercise, investigated and see the following Blog Post link:
S/4EWM-ECC6 Configuration - Optimize Access Strategies for Storage Types
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Is it possible for a receiving into a single Receive to Dock SLoc to Final Putaway into different Storage Locations (and different EWM Storage Types)?
Answer: Refer to the following Blog Post demonstration which will show that it is possible with some manual interventions at time of WT creation. However, the scenario in the Blog Posts below is to demonstrate the case for Storage Locations for the SAME Plant. However, for a CENTRAL EWM Warehouse to SLoc assigned from different Plants (same or different companies) may required further thought processes albeit perhaps not logistics related but accounting impacts.
S/4EWM-ECC6 Configuration - Receive into SLoc RD06 but Putaway into SLoc AF06, AA06, and AB06
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review relevant navigation in the EWM Monitor.
Answer: The SAP EWM Monitor is a centralized tool for warehouse managers to gain real-time visibility into a warehouse's operations within SAP Extended Warehouse Management (EWM). It provides detailed information on warehouse processes, stock levels, resource utilization, and documents, enabling users to track activities, identify issues using alert monitoring, and take immediate corrective actions. The monitor is highly customizable, allowing users to create personalized views and access specific data points for efficient warehouse management.
Key Functions and Features
• Real-time Overview: Provides a comprehensive view of inbound and outbound processes, stock in bins, and resource status.• Alert Monitoring: Signals actual and potential problems in the warehouse, allowing for timely intervention.
• Exception Handling: Offers tools to correct or manage problematic situations directly within the monitor.
• Direct Action Execution: Enables users to execute various warehouse functions, such as creating or confirming tasks and orders, or blocking bins.
• Document and Process Tracking: Allows users to track the status of various documents, including inbound and outbound deliveries, warehouse tasks, physical inventory, and other warehouse activities.
• Resource Management: Provides insights into the utilization of warehouse labor and resources.
• Customization: Users can customize the monitor by creating custom nodes, saving selection variants for automatic filtering, and hiding unnecessary branches.
• Access: From the SAP Easy Access screen, choose Extended Warehouse Management Monitoring /SCWM/MON - Warehouse Management Monitor. Enter the warehouse number and the monitor name or alternative access will be vai to enter the following t-code /N/SCWM/MON in the Command Box to directly access the monitor.
Click here to the Blog Post:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of EWM Process steps illustrated in class.
_Blogged.jpg)
https://EWM Enterprise Structure
https://Storage Type & Storage Section Configuration
https://Generate Bin from Bin Structure
https://Master Data Integration for EWM
https://Warehouse Monitor Naviation
https://Transfer QI to Unrestricted using MIGO
https://Transfer QI to Unrestricted using EWM t-code
https://GI to Cost Center using EWM t-code
https://Production Supply Area Staging and Backflushing
https://Expected Goods Receipt for Production Order
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What happen when the ERP Cost Center is obsolete and it is Send to Distributed EWM via the Replication Program in EWM?
.jpg)
Answer: It is not possible to delete a Cost Center in the ERP system when the Cost Center has been used in any ERP transactions with transaction history exist for a Cost Center. Deletion of a cost center using transaction KS04 is only possible if no transactions have been posted to it, and in most cases, changing the validity period is the preferred method to "deactivate" a cost center. However, it is possible to change the validity date of a Cost Center in KS02.
According to SAP documentation, if a cost center is deleted in the ERP, the deletion is replicated to SAP Extended Warehouse Management (EWM), and the cost center is marked as deleted or invalid in EWM, preventing its further use.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to find Standard User Exit for an SAP Program?
Answer: Check the following Blog Posts for how the check User Exits for a T-code in SAP.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How is the "Reason Code" for GI directly (t-code /SCWM/ADGI or Post Unplanned Goods Issue) via EWM system is configured and is there a "Replication Program" in the EWM system for ERP "Reason Code" to be replicated to the EWM system, the 3rd question is there any Field Selection for the EWM "Reason Code" for Unplanned GI to match the Field Selection for ERP Movement Type based "Reason Code"?
Answer: There is a 2 part answer to the question for SAP EWM /SCWM/ADGI transaction code:
Replication for Movement Reason and Cost Center.
Movement Reason• Define EWM Movement Reason Configuration: Extended Warehouse Management > Cross-Process Settings > Warehouse Task > Manage Reasons for Goods Movement• Map EWM Reason to ERP Reason: Go to the Customizing activity: Interfaces > ERP Integration > Goods Movements > Define Custom Specific Movement Types > Communication EWM --> ERP custom movement types.• Use the activity Map EWM Reason Code to ERP Reason for Movement.• Ensure the movement reason defined in EWM matches the reason code in SAP ERP for accurate integration and reporting, such as for scrapping or stock corrections.Cost Center• Replication: use t-code /SCWM/ACC_IMP_ERP to replicate ERP Cost Center to the EWM system.• Check Cost Center replicated in Structure "/SCWM/S_ACC_ADD_COSTCENTER" in the EWM system.
Field Selection for Movement Reason and Additional Text.
How to Control Field Behavior in /SCWM/ADGI
• Navigate to Warehouse Task Settings in the EWM IMG via SAP Extended Warehouse Management (EWM) > Cross-Process Settings > Warehouse Task > Go to Manage Reasons for Goods Movement.
• Define or Modify Movement Reasons: In the IMG, you can define or modify specific movement reasons (e.g., Consumption, Scrapping).• Make Fields Mandatory: Goto IMG SAP Extended Warehouse Management (EWM) >Extended Warehouse Management>Interfaces>ERP Integration>Goods Movements>Map EWM Reason Code to ERP Reason for Movement
• Map EWM Reason for Movement to ERP: Map EWM Warehouse + EWM Reason for Movement to ERP Movement Type + ERP Reason for MovementSee the following Blog Post for Configuring "Movement Reason" for /sCWM/ADGI to be Mandatory:
https://froggysap.blogspot.com/2025/09/s4ewm-ecc6-scwmadgi-movement-reason.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the BAPI for /SCWM/ADGI for Movement type
Answer: There isn't a specific BAPI for SAP Extended Warehouse Management (EWM) transaction /SCWM/ADGI; instead, you would use the standard SAP Goods Movement BAPI, BAPI_GOODSMVT_CREATE, and configure it for Movement Type 201 by providing the required cost center and other details. The BAPI-created material document will then reflect the goods issue to the cost center from the warehouse, and a subsequent warehouse task is created and confirmed.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the transaction code for "Change Pointer" for the ERP Material Master (not BD10), to transfer the field changes to /SAPAPO/MAT1?
.jpg)
.jpg)
Answer: Transaction Code BD10 in ERP system can be used to Create the APO Product in the EWM system. AND Transaction Code BD10 in the ERP system can also be used to Change Client-level data in the Material Master to the APO Product in the EWM system as shown in the demo slides above.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Provide a T-code List of SAP EWM system.
Answer: The following is a QUICK Transaction Code for S/4HANA EWM, it is not a complete list and periodically may update to this list when time permits:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
%20(1).jpg)
Friday, September 5, 2025
_U0201_ExploreHANADB.jpg)
Tuesday, September 2, 2025
Q&A in Class (2025-09-03) S4H01
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
See the following official SAP link to Video Library for SAP S/4HANA:
See comprehensive SAP resources main page:
https://www.linkedin.com/company/sap/
https://www.sapsumikko.jp日本/entry/2019/04/05/opensap-badge
See the following links on official SAP resources on S4HANA:
https://blog.sap-press.com/key-differences-between-sap-ecc-and-sap-s4hana/
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Official SAP Fiori Resources:
The following are Froggy's Blog Posts on some step-by-steps of Fiori Navigation:
Answer: List of current Fiori Transactions.
Click here to the spreadsheet:
Official SAP Videos on SAP Fiori:
https://learning.sap.com/video-playlists/managing-the-user-experience-of-sap-s-4hana-cloud-private-edition
https://help.sap.com/docs/SAP_FIORI_OVERVIEW/
https://fioriappslibrary.hana.ondemand.com/
https://www.sap.com/design-system/fiori-design-web/
https://sapui5.hana.ondemand.com/what-is-new-in-UI5/
https://sapui5.hana.ondemand.com/sdk/developing-apps-with-ui5-elements/
The following are Froggy's Blog Posts on some step-by-steps of Fiori Navigation:
https://froggysap.blogspot.com/sap-navigation-fiori-browser-enterprise.html--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
https://froggysap.blogspot.com/sap-navigation-fiori-default-values-and.html
https://froggysap.blogspot.com/sap-navigation-fiori-browser-2023.html
https://froggysap.blogspot.com/sap-fiori-save-as-new-tile-in-space-and.html
https://froggysap.blogspot.com/sap-fiori-fiori-app-for-fi-user-pfcg.html
https://docs.google.com/presentation/S4H01(26)_U0513_SearchServiceContracthttps://docs.google.com/presentation/S4H01(26)_U0514_PerformActualCostAnalysishttps://docs.google.com/presentation/S4H01(26)_U0515_CreateBillingDocumenthttps://docs.google.com/presentation/S4H01(26)_U0516_AnalyzePostedInvoicesInFIhttps://docs.google.com/presentation/S4H01(26)_U0517_PostAnIncomingPaymenthttps://docs.google.com/presentation/S4H01(26)_U0618_UseTheViewBrowserhttps://docs.google.com/presentation/S4H01(26)_U0619_CreateKPIGroupKPITilehttps://docs.google.com/presentation/S4H01(26)_U0620_ExploreCDSViewsUsingEclipse_
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review list of Fiori Transactions.
Click here to the spreadsheet:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question no 4065 : Stock Postings at UD
In SAP Quality Management, the following are Stock Postings are possible at Usage Decision EXCEPT ?
(only one answer)
A) Unrestricted.
B) Scrap.
C) Blocked Stock.
D) GR-Blocked Stock.
E) New Material.
.
Answer: D
When UD, the following are possible Stock Postings:
. Unrestricted
. Scrap
. Sample Consumption
. Block Stock
. New Material
. Reserves
. Return Posting
(only one answer)
A) Unrestricted.
B) Scrap.
C) Blocked Stock.
D) GR-Blocked Stock.
E) New Material.
.
Answer: D
When UD, the following are possible Stock Postings:
. Unrestricted
. Scrap
. Sample Consumption
. Block Stock
. New Material
. Reserves
. Return Posting
Monday, September 1, 2025
Thursday, August 28, 2025
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
. 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
Monday, August 25, 2025
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":
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:
See the following Blog Posts on how to "Save as a New Tile" with new Filter and new Columns Display:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: MM Enterprise Structure
.jpg)
• 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
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:
• The BP approach aims to harmonize master data across different SAP modules and applications, improving data consistency and simplifying data management.• BP for Vendor or Customer via "Organization" (to create Vendor or Customer)• BP for Individuals via "Persons"
• BP for Groups of People via "Groups"
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)
.jpg)
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.
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 master2. 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.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------