Question 4126 : Routing Operation Scrap Factor and BOM item Operation Scrap Factor

In SAP Product Costing as at S/4 1909, which of the following are TRUE about Routing Operation Scrap Factor and BOM item Operation Scrap Factor ?

(more than one answers)

A) When BOM item Operation Scrap Factor is entered, a Net ID indicator must be selected.
B) When Routing Operation Scrap Factor is entered, a Net ID indicator must be selected.
C) When the BOM item Operation Scrap Factor is entered with the Net ID indicator selected, the system will ignore Assembly Scrap Factor calculation for the Component concerned.
D) When the BOM item Operation Scrap Factor is entered without the Net ID indicator selected, the system will include Assembly Scrap Factor calculation for the Component concerned.
E) When the BOM item Component Scrap Factor is entered without the Net ID indicator selected, the system can include both the Assembly Scrap Factor and the Component Scrap Factor. 

Answer: A, C, E

SAP PP - Planning Strategy Multiple (40/10/20) and Advanced Planning (S/4 2024)

 

CLICK here to view the Presentation

Question 4125 : CK40N Mass Costing

In SAP Product Costing as at S/4 1909, identify the correct steps in CK40N ?

I. Marked
II. Release
III. Selection
IV. Analysis
V. Costing

(only one answer)

A) III, IV, I, II, V
B) III, V, I, III, IV
C) V, IV, III, I, II
D) III, V, IV, I, II
E) V, II, IV, I, II
.

Answer: D

SAP PP - Handling Unit for Prod Order Goods Receipt

CLICK here to view Presentation

iEE2E MM26.B1 - Create Material for Purchasing

 

CLICK here to view the Presentation

SAP SD - Create Billing Document without Accounting Posting Issue

 

CLICK here to view the Presentation

Q&A in Class (2026-05-25) BT100

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

Question: Review of End-to-End Order-to-Cash Process with SD-FI Integration. 

Answer: The SAP Order-To-Cash (O2C) process is an end-to-end workflow spanning the Sales and Distribution (SD), Materials Management (MM), and Finance (FICO) modules. It manages the entire customer lifecycle from the moment an inquiry is made, through product delivery, to final payment collection.

The OTC process bridges sales, logistics, and finance through six key stages:

1. Pre-Sales Activities:

• What happens: Capturing customer inquiries, negotiating prices, and creating sales quotations.

• SAP Focus: Helps businesses track customer demand and determine if inventory is available before making commitments.

SAP Transaction Code: VA11 (Create Sales Inquiry).

SAP Transaction Code: VA21 (Create Sales Quotation).

2. Order Creation:

• What happens: The customer places an order, establishing the contract terms, pricing, quantities, and delivery dates.

SAP Transaction Code: VA01 (Create Sales Order).

3. Inventory Check & Fulfillment:

• What happens: The warehouse confirms stock availability, prepares the shipment, and executes picking and packing.

SAP Transaction Code: MMBE (Stock Overview).

SAP Transaction Code: VA02 (Availability Check).

SAP Transaction Code: V_RA or CO06 (Backorder Processing)

SAP Transaction Code: VL01N (Outbound Delivery)

4. Shipping & Delivery (Goods Issue):

• What happens: The shipment is dispatched to the customer. This triggers the Post Goods Issue (PGI), which updates inventory records and books the Cost of Goods Sold (COGS).

SAP Transaction Code: VL02N (Post Goods Issue).

5. Billing & Invoice Creation:

• What happens: An invoice is generated and sent to the customer. This officially recognizes revenue in the system.

SAP Transaction Code: VF01 (Billing Document).

6. Payment Collection:

• What happens: The customer pays the invoice, which is then recorded in the system, clearing the Accounts Receivable balance.

SAP Transaction Code: F-28 (Post Incoming Payments).

Click the following link to demonstration of the Order-to-Cash process in SAP.

• https://docs.google.com/1_CreateReconciliationGLAccount/

• https://docs.google.com/2_CreateBPCustomer/
• https://docs.google.com/3_CreateMaterialForSales/
• https://docs.google.com/4_CreateSalesOrder/
• https://docs.google.com/5_CreateOutboundDelivery/
• https://docs.google.com/6_Billing/
• https://docs.google.com/7_CheckAR&FinancialStatement/
• https://docs.google.com/8_IncomingPaymnet/

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

Question: Review of End-to-End Purchase-to-Pay Process with MM-FI Integration. 

Answer: The SAP Purchase-to-Pay (P2P) or Procure-to-Pay process is an end-to-end supply chain cycle. It digitally integrates purchasing, inventory, and accounts payable. The cycle manages everything from identifying a need for goods/services to the final payment to the vendor, relying on a strict three-way match to ensure accuracy.

The P2P cycle in SAP consists of six key, sequential stages:

1. Purchase Requisition (PR):

• What it is: An internal document created by a department to request specific goods or services.

SAP Transaction Code: ME51N.

2. Sourcing & Request for Quotation (RFQ):

• What it is: The purchasing department sends out inquiries to multiple vendors to gather pricing and delivery terms. The quotations are then compared in the system.

SAP Transaction Code: ME41 (Create RFQ) 

SAP Transaction Code: ME47 (Maintain Quotation

3. Purchase Order (PO):

• What it is: A formal, legally binding contract sent to the chosen vendor specifying the material, price, quantity, and delivery terms.

SAP Transaction Code: ME21N

4. Goods Receipt (GR):

• What it is: When the vendor delivers the materials, the warehouse staff receives the goods and verifies the delivery against the PO. This updates the inventory and creates financial documents.

SAP Transaction Code: MIGO

5. Invoice Verification (MIRO):

• What it is: The vendor sends an invoice for the supplied goods. Accounts payable performs a three-way match, ensuring the PO, Goods Receipt, and Invoice all match in price and quantity before authorizing payment.

SAP Transaction Code: MIRO

6. Payment Processing:

• What it is: The finance department processes the final payment to the vendor (via check, wire, or automatic payment run), clearing the financial liability.

SAP Transaction Code: F-53 (Manual) 

SAP Transaction Code:F110 (Automatic

Click the following link to demonstration of the Purchase-to-Pay process in SAP.

• https://docs.google.com/1_CreateExpensesGLAccount/

• https://docs.google.com/2_CreateBPVendor/

• https://docs.google.com/3_CreateSupplierInvoiceVerificationWithoutPO/

• https://docs.google.com/4_OutgoingPayment/

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

Question: What are the possible scenario for Accounting entries not created when the SD Billing Document is created?

Answer: When an SAP SD (Sales and Distribution) billing document is created but failed to generate an accounting entry, it is almost always due to the following scenarios:

• Account Determination Errors: 

The system cannot determine which G/L account to post the revenue, discounts, or freight to. Use the Account Determination Analysis or check OBYC configuration settings to ensure your condition types and valuation classes are correctly mapped to General Ledger accounts.

• Missing Master Data:

The Customer is not extended to the Company Code specified in the billing document. The Material has incorrect accounting views (e.g., missing Valuation Class).

• Closed Posting Periods: 

The billing date of the invoice falls into a fiscal year/period that has already been closed in FI (Financial Accounting).

• Posting Blocks: 

The billing type may be configured to require manual release, or a credit block is preventing the transfer to FI.

• Pro Forma Invoices: 

If the billing type is set as a pro forma invoice (e.g., F5 or F8), the system intentionally marks them as "Not Relevant for Accounting" (Posting status D).

• Zero Net Value: 

If the net value of the billing document is zero, the system typically does not generate an accounting document.

• Missing Tax data: 

If the Tax Rates are incorrectly defined example the Tax Code should be Output Tax but was wrongly configured as Input Tax or the Tax Accounts not correctly defined in the customizing. 

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

SAP Handling Unit Management - VLMOVE Transfer Posting from SLoc to SLoc

CLICK here to view Presentation

SAP PP - Planning PPDS Activation and Setup

 
CLICK here to view the Presentation

Question 4124 : Co-Product Costing

In SAP Product Costing as at S/4 1909, which if the following characteristics are CORRECT about Co-Product Costing ?

(More than one answers)

A) Set Co-Product indicator in the Co-Product in the BOM item detail.
B) Set Co-Product indicator in the Header BOM of the Primary Material.
C) Assign "Join Product Costing" in the Primary Product Material Master MRP2 data view.
D) Assign "Join Product Costing" in the Co-Product Material Master MRP2 data view.
E) Enter a negative quantity for the Co-Product Material Master to the Primary product BOM.
.

Answer: A, B, C, E

Q&A in Class (2026-05-22) S4H00

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

Question: Review of  FIORI in S/4HANA.

Fun Facts: SAP Fiori is not an acronym and does not stand for anything. It gets its name from the Italian word for "flower". SAP chose this name to symbolize the freshness, simplicity, and natural 
beauty they wanted to bring to their software's user interface.

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

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

There are 3 main interfaces for SAP access today:

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

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

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

Key updates in Fiori 3.0:

SAP Fiori 3 introduces a redesigned, intelligent user experience focused on consistency across all SAP products, featuring

• a new "Quartz theme" ( is the default design system and visual theme family for SAP Fiori 3)
• new interface called "Spaces and Pages" layout for improved navigation.
• embedded AI capabilities with Joule (SAP's built-in generative AI copilot embedded within the SAP Fiori Launchpad).
• proactive situation handling (an intelligent framework that automatically detects, tracks, and alerts users about critical business issues).
• a conversational UI (digital assistant).
• enhanced analytics for actionable insights.

The future of SAP Fiori is centered around AI-driven interfaces, cloud-native delivery, and intelligent automation. While Fiori remains the visual foundation for SAP S/4HANA, users will increasingly interact with enterprise data through natural language and autonomous agents rather than traditional click-based navigation.

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

https://learning.sap-press.com/sap-fiori

https://www.sap.com/technology-platform/fiori.html

https://www.sap.com/fiori-design-web/

https://fioriappslibrary.hana.ondemand.com/

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

https://froggysap.blogspot.com/2022/04/s4-discover-fiori-applications.html

https://froggysap.blogspot.com/2018/06/hana-for-logistics-create-fiori-group.html

https://froggysap.blogspot.com/2024/11/sap-fiori-update-2023.html

https://froggysap.blogspot.com/2024/12/sap-s4hana-fiori-2023-space-pages.html

https://froggysap.blogspot.com/2026/05/sap-fiori-30-explore.html

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

Question: Review of  Basic Enterprise Structure for FI-MM integration S/4HANA.

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

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

Question: iEE2E Certification syllabus.

Answer: iEE2E = "End-to-End Business Processes for SAP Business Suite",  the IEE2E (End-to-End Business Processes for the Intelligent Enterprise) certification officially replaces the legacy TS410 certification. SAP retired the TS410 exam and its associated courses to better align with the current shift toward cloud-based enterprise solutions.

The TS410, known as "Integrated Business Processes in SAP S/4HANA," focused primarily on on-premise systems. In contrast, the IEE2E program—and its corresponding exam, C_IEE2E—provides a modern, system-based approach centered on SAP S/4HANA Public Cloud Edition.

Key Differences at a Glance:

• Focus: TS410 focused on traditional, on-premise ERP modules. IEE2E focuses on end-to-end business scenarios in the Cloud ERP ecosystem.Exam 
• Format: The new C_IEE2E exam features updated, system-based practical elements rather than just strictly theoretical or isolated multiple-choice testing.
• Prerequisites: To fully prepare for the IEE2E certification, candidates are also encouraged to complete the "Managing Clean Core with SAP S/4HANA Cloud" learning journey.

Link to Certifications interested: 

• IEE2E: https://sap-certified-associate-end-to-end-business-processes/
• Exam Code: C_IEE2E
• MM: https://sap-certified-associate-sap-s-4hana-sourcing-and-procurement/
• Exam Code: C_TS452 (SAP Certified - SAP S/4HANA Cloud Private Edition, Sourcing and Procurement)
• S4500 - Business Processes in SAP S/4HANA Sourcing and Procurement
• S4520 - Purchasing in SAP S/4HANA
• S45250 - Consumption-Based Planning and Forecasting in SAP S/4HANA
• S4510 - Inventory Management and Physical Inventory in SAP S/4HANA
• S4515 - Invoice Verification in SAP S/4HANA
• S4550 - Cross-Functional Customizing in SAP S/4HANA
• SL_RISE419 - Introducing RISE with SAP Methodology for SAP Partners and Customers
• S4C03 - Implementing SAP S/4HANA Cloud Private Edition
• SD: https://sap-certified-associate-sap-s-4hana-sales/
• Exam Code: C_TS462 (SAP Certified - Implementation Consultant for SAP S/4HANA Cloud Private Edition, Sales)
• S46000 - SAP S/4HANA Sales Essentials
• S46001 - The Concept of Available-to-Promise (ATP) in SAP S/4HANA Sales
• S46050 - Customizing Fundamentals in SAP S/4HANA Sales
• S46051 - Defining Outline Agreements in SAP S/4HANA Sales
• S46052 - Configuring Incompletion Procedures in SAP S/4HANA Sales
• S46055 - Customizing Output Control in SAP S/4HANA Sales
• S46056 - Setting up Text Control in SAP S/4HANA Sales
• S46100 - Configuring Delivery Processing in SAP S/4HANA Sales
• S46150 - Configuring Billing in SAP S/4HANA Sales
• S46200 - Configuring Pricing in SAP S/4HANA Sales
• SL_RISE419 - Introducing RISE with SAP Methodology for SAP Partners and Customers
• S4C03 - Implementing SAP S/4HANA Cloud Private Edition
• FI: https://sap-certified-associate-sap-s-4hana-financial-accounting/
• Exam Code: C_TS4FI (SAP Certified - SAP S/4HANA Cloud Private Edition, Financial Accounting)
• S4F10 - Business Processes in Management Accounting in SAP S/4HANA
• S4F12 - Basics of Customizing for Financial Accounting: GL, AP, AR in SAP S/4HANA
• S4F13 - Additional Financial Accounting Configuration in SAP S/4HANA
• S4F15 - Financial Closing in SAP S/4HANA
• S4F17 - Asset Accounting in SAP S/4HANA
• SL_RISE419 - Introducing RISE with SAP Methodology for SAP Partners and Customers
• S4C03 - Implementing SAP S/4HANA Cloud Private Edition
• CO: https://sap-certified-associate-sap-s-4hana-management-accounting-associates/
• Exam Code: C_TS4CO (SAP Certified - SAP S/4HANA Cloud Private Edition, Management Accounting)
• S4F20 - Business Processes in Management Accounting in SAP S/4HANA
• S4F22 - Cost Center and Internal Order in SAP S/4HANA
• S4F25 - Cost Object Controlling in SAP S/4HANA
• S4F28 - Profit Center Accounting in SAP S/4HANA
• S4F29 - Profitability Analysis in SAP S/4HANA
• S4F23 - Product Cost Planning in SAP S/4HANA
• SL_RISE419 - Introducing RISE with SAP Methodology for SAP Partners and Customers
• S4C03 - Implementing SAP S/4HANA Cloud Private Edition

Disclaimer: The best source of appropriate courses for each SAP Certification are those suggested by SAP Certification authorities. The refer to SAP Certification authorities for the latest courses required and gain those knowledge through SAP Learning Hub self-studies or instructor-led classes before attempting the Certification Exam. 

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

Question: What are "Simplification List" in SAP S/4HANA?

Answer: The SAP Simplification List is a crucial, functional document detailing all technical and business changes, innovations, and deprecations when transitioning from SAP ECC to SAP S/4HANA (or between S/4HANA versions). It also identifies obsolete transactions, master data changes, and necessary adaptations.

See the following links for Simplification List downloads:

https://help.sap.com/SIMPL_OP2023.pdf/

Other documentation which can be useful are: 

https://help.sap.com/FSD_OP2025_latest.pdf/

https://help.sap.com/CONV_OP2025.pdf/

https://help.sap.com/UPGR_OP2025.pdf/

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

Question: Review of Business Partner Vendor/Supplier in S/4HANA.

Answer: In SAP S/4HANA, the Business Partner (BP) is the mandatory, centralized object used to maintain all vendor (now called supplier) and customer master data. Traditional ECC transaction codes like XK01/XK01/XK02 or FK01/FK02/FK03 or MK01/MK02/MK03 are obsolete; all maintenance is consolidated under transaction BP using specific supplier roles.

Key Structure:

Business Partner Category

Person: Represents a natural person (a private individual, employee, or consumer).

Organization: Represents a legal entity or part of a legal entity (specifically representing the vendor or supplier organization).

Group: Represents a community of people sharing a relationship (such as a sales department, purchasing group etc). 

BP Grouping

Number Range Assignment: Every BP grouping is linked to a specific number range. This dictates whether the system automatically generates a BP ID (internal number range) or if the user must manually input it (external number range).

Direction & Synchronization: Because Customer and Vendor master records are integrated into the BP object in S/4HANA, you must configure the direction of synchronization (e.g., BP to Customer or BP to Vendor). This mapping aligns the BP Grouping with the corresponding Customer/Vendor Account Group.

Account Group determination: Each BP Grouping is assign with an Account Group (carried over from ECC to S/4HANA) which contains configurations such as Field Selection (field behavior like display, hide, mandatory), partner functions determination etc. 

Role Based concept

• FLVN00: Central Master Data Entry for all general data (e.g., name, address, tax, bank details).

• FLVN00: Used for Financial Accounting (FI) supplier data based on Company Code. 

• FLVN01: Used for Supplier/Vendor purchasing data based on Purchasing Organization.

See the following links for step-by-step of creating Business Partner Vendor:

https://froggysap.blogspot.com/2018/06/hana-for-logistics-business-partner-for.html

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

Question: Review of Material Master creation. 

Answer: Using a Material Master in purchasing provides a single source of truth that standardizes data, eliminates manual entry, and prevents duplicate purchases. It automatically populates purchasing documents, enforces organizational compliance, and improves. 

Click here to view a demonstration of how an example material is created for Purchasing scenario. 

https://docs.google.com/MaterialCreation/

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

Question: Review on Materials Management (MM) or Purchase-to Pay (P2P 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:

https://docs.google.com/Business Partner Vendor/

https://docs.google.com/MaterialMaster/

https://docs.google.com/process/PR-PO-GR-LIV/

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

SAP MM - Subcontracting setup and processing via ADSUBCON and ME2ON

 

CLICK here to view the Presentation

Question 4123 : Kanban Replenishment for REM Planned Orders

In SAP Production Planning & Execution S/4 HANA 2023, Kanban Replenishment for REM Planned Orders are the following ?

(more than one answers)

A) Production Version and REM Allowed must be set for the Assembly with this Kanban scenario.
B) The Assembly for the REM Kanban must be extended to the Storage Location for the PSA for the Control Cycle.
C) The Assembly for REM Kanban must be created with a Cost Collector. 
D) Both the Assembly and Component's MRP Area must be set without Planning.
E) The Assembly MRP Area must be set without Planning for the PSA Storage Location.
.

Answer: A, B, C

SAP PP - COGI for Production Orders

CLICK here to view Presentation

SAP SD - Delivery Processing (Part 1) (Doc Type & Item Category) in SO Doc Type and Delivery Type

 

CLICK here to view the Presentation

Question 4122 : "Warehouse Monitor" objects

In SAP WMS at at S/4 1909, the "Warehouse Activity Monitor" in LE-WM (or new referred to as StRM "Stock Room Management") offers the monitoring of which types of objects ?

(more than one answers)

A) Unconfirmed Transfer Orders.
B) Unconfirmed Transfer Requirements.
C) Interim storage stocks without Movements.
D) Critical Stocks for Production Supply.
E) Open Posting Change Notices.
.

Answer: A, B, C, D, E

Open transfer requirements - Open transfer requirements which have not been fully processed within the time parameters defined in the system.
Open posting change notices - Open posting change notices which have not been fully processed within the time parameters defined in the system. A posting change is not considered to be fully processed until the status of the posting change notice has been set to "U" (processed).
Open deliveries - All "WM-relevant" deliveries for which not all items have been picked that meet one of the following conditions: The time requirements for which staging must be completed were not met, The time deadline for loading the delivery was not met or The time period for the goods issue for the delivery was exceeded.
Negative stock - Negative stock that has existed in the warehouse longer than the time parameters defined for this object. Negative stock is recorded in the system when Posting changes have not been completely processed or Goods receipts have been processed in WM that have not yet been posted in Inventory Management
Stock in interim storage areas - Positive stock in an interim storage area that has not moved within the time parameters defined in the system. Critical processes displayed including Critical stock in the interim shipping area for deliveries may indicate goods issues for deliveries that have not yet taken place, Stock in the interim storage area for differences may indicate differences (from inventory or when confirming transfer orders) that have not yet beeen cleared, Stock in the interim storage area for posting changes may indicate posting change notices that have not been fully processed or Stock in the interim area for goods receipts may indicate stock that has not yet been putaway.
Critical Transfer Requirements for Production Supply - Inconsistencies in stock quantities that are used for material staging to production. Inconsistencies can occur when Transfer requirements are created manually to supply storage bins in production or Reservations are deleted without making necessary corrections to open transfer requirements in WM

SAP Fiori 3.0 Explore

 

CLICK here to view the Presentation

Question 4121 : STO with SD Delivery parameter requirements

In SAP MM-SD integration as at S/4 1909 for Stock Transport Order via SD Delivery for Step 1 of Goods Issue from the Supplying Plant, which of the following are the desired parameter requirements ?

(more than one answers)

A) Sales Area assigned to the Receiving Plant in the Configuration.
B) Material Master to be created at the Sales Area.
C) Assign the Document Type to the Receiving Plant and not for the Supplying Plant.
D) Customer Master to be assigned to the Receiving Plant.
E) Assign the SD Delivery Type to the MM STO Purchasing Document Type.
.

Answer: A, B, E

Question 4120 : Subcontracting for MM

In Material Management as at S/4 1909, which of the following are possible requirements for Subcontracting process flow requires ?

(more than one answers)

A) Production Version.
B) BOM Application assigned to the Plant with a valid Selection ID.
C) Special Procurement key for Subcontracting in both the Assembly and Components material master to be provided the the Subcontractor.
D) Special Procurement key for Subcontracting in Assembly and but not for the Components to be provided the the Subcontractor.
E) Subcontracting Purchasing Info Record for the Assembly.
.

Answer: A, B, D, E