SAP PP Repetitive Manufacturing - Assign Production Version to Planned Independent Requirement for REM Materials

CLICK here to view Presentation

Question no 4134 : Discount-in-Kind in MM Purchase Order

In SAP Material Management as at S/4 HANA 2023, what are the prerequisites for "Free Goods" (Discount-in-Kind) in Purchase Order ?

(more than one answers)

A) set "Grant Free Goods" in the General data view of the Purchasing Info Record.
B) set "Grant Free Goods" in the Purchasing Organization data view of the Business Partner Vendor. 
C) set "Grant Free Goods" in the Source List for the Vendor and Material combination in the Source List. 
D) set "Grant Free Goods" in the Plant data view of the Material Master. 
E) Set "Grant Free Goods" in the Plant Parameter in the Configuration. 
.

Answer: B, D

SAP S/4EWM-ECC6 - Inbound Process with Quality Inspection

CLICK here to view the Presentation

SAP MM - Valuation Type and Batch

 

CLICK here to view the Presentation

SAP S/4 EWM-ECC6 - Counting Difference Adjustment to Inbound Delivery

 

CLICK here to see the Presentation

Question no 4133 : Supply Region in Procurement

In SAP Material Management as at S/4 HAHA 2023, which of the following are functionality provided by the REM Profile assigned to the MRP 4 data view of a Repetitive Manufacturing Product/Material ?

(more than one answers)

A) GI backflush at GR Posting. 

B) Reporting Point Backflush. 

C) Also Post Activities to the Product Cost Collector when Backflushing. 

D) Determination of Backflushing and Goods Receipt Storage Location. 

E) Determination of Movement Type to be used for Goods Receipt and Goods Issue Movement Type.

Answer: A, B, C, E

SAP S/4EWM-ECC6 - Issue of Drag Material Instead of WT for Material in aa PO Incoming HU to a Deconsolidation HU in Work Center Bin

 

CLICK here to view the Presentation

SAP S/4EWM-ECC6 - Explore the Process of Receiving Goods (Same as Embedded EWM)

CLICK here to view the Presentation

Q&A in Class (2026-06-26) EWM100

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

Question: What is the difference between "Physical Stock" vs "Available Stock" in the EWM Monitor?

Answer: See the following Blog Posts or a demonstration and exlanations:

Click link to Blog Posts:

https://froggysap.blogspot.com/2026/06/blog-post_22.html

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

Question: How to display a list of Products and Warehouse Products in SAP EWM system ?

Answer: Methods of getting a list of Warehouse Products:

1. via Query from the Table above (see below link to other EWM tables)
2. via the EWM Warehouse Monitor
1. Goto folder Product Master Data - Warehouse Attributes (double-click).
2. Change Layout to ADD fields desired.
3. Export to Spreadsheet.

Click link to Blog Posts for Common Tables for EWM:

https://froggysap.blogspot.com/2024/05/blog-post_11.html

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

Question: Review the Process of EWM Inbound Delivery (both Distributed and Embedded EWM).

Answer: The core inbound process steps are fundamentally the same for both Distributed (Decentralized) EWM and Embedded EWM. In both deployment options, the process guides goods from arrival to their final bin using the exact same transactional sequence:

The standard step-by-step process flow is as follows:

• Purchase Order Creation: The process starts in the ERP/SAP S/4HANA core system, a Purchase Order item created with EWM activated Storage Location (Receive in Dock SLoc RD00) and Confirmation Control key relevant for Inbound Delivery.
• LE Inbound Delivery Creation: The process starts in the ERP/SAP S/4HANA core system, which automatically generates an LE inbound delivery document (often based on a Purchase Order or Advanced Shipping Notification).
• Replication (Warehouse Request): The LE inbound delivery document is replicated into the EWM system as a EWM inbound delivery to act as a Warehouse Request.
• Unloading & Deconsolidation (Optional): Goods are received at the door, unloaded, and may be split into smaller units if necessary.
• Goods Receipt (GR) Posting: Goods receipt is posted in EWM and subsequently updated in the ERP system. Best practice is to received into Dock Storage Location (SLoc RD00) which is mapped to EWM GR-ZONE. (if Goods Receipt step is not executed at this point, it can be delayed to the WT confirmation step). 
• Warehouse Task (WT) Creation: EWM creates warehouse tasks where the system will determine EWM stock movement from the GR-ZONE to the Final Putaway Storage Type & Storage Bin.
• Putaway & Confirmation: Warehouse workers physically move the items and confirm the putaway in the system. The Stocks is Putaway to teh Final Final Putaway Storage Type & Storage Bin according to the WT. In the ERP/S/4HANA core system, the stocks is transferred to SLoc RD00 (Receive in Dock) to AF00 (Available for Sales/Use). 

Click the following for the Process steps:

https://froggysap.blogspot.com/2026/06/blog-post_23.html

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

Question: The common issue of drag the "Materials" instead of "WT" to a HU in Work Center Bin resulting in disconnected WT and the Material, how to resolve?

Answer: The problem is SAP do not stop user to select "Material" to drag-and-drop it to another HU in Work Center BIN which end-up causing disconnecting the original Material's WT like the above simulation screen. If follow proper step (recommended in the Blog Posts below will auto resolve the issue); however, if the HU still stuck without the WT in the Work Center BIN, then it is recommended to use t-code /SCWM/ADHU to create a manual WT for the Movement. Both resolution method above is found in the following blog posts.

When we wrongly drag the Material instead of the WT out from a HU# to a new HU#, there are 2 options:

1. Preferred method:
• In /SCWM/DCONS, do not drag the "lost" WT#200157 back to the material "Hollow Shaft".
• Set complete to both HU# 665 and HU# 10546.
• Go back to the Warehouse Task and Confirm all WTs.
• There should be ONE WT which cannot be confirmed ie: WT#200157 where it does not have any Material and Qty. 
• Set the WT#200157 to Cancel status. 
• The system should AUTO created a new WT# for the Material "Hollow Shaft" in HU#10546. 
• Confirm that new WT should move the HU#10546 from the DECO Bin to the Final Putaway Storage Bin.
• Verify the completed MOVEment of the HU#10546 from the DECO Bin to the Putaway Bin. 
• Verify that there is no more HU in the Deconsolidation Work Center in /SCWM/DCONS.
2. What if system did not Auto create the new WT for HU#10546:
• Use EWM t-code /SCWM/ADHU to create a new WT manually for the MOVEMENT.
• Load the Product/Material "Hollow Shaft" in /SCWM/ADHU which will show the HU#10546 in the current DECO Bin location.
• Create WT
• Enter Destination Bin as HU#10546, using WPT "9999", Enter the QTY, Enter the Putaway Bin manually.
• SAVE the WT (will also create a WO).
• Then Confirm the manually created WT.
• Verify the completed MOVEment of the HU#10546 from the DECO Bin to the Putaway Bin. 
• Verify that there is no more HU in the Deconsolidation Work Center in /SCWM/DCONS.

See the following demo:

https://froggysap.blogspot.com/2026/06/blog-post_208.html

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

Question: Review of MIGO (Synchronous Goods Receipt) without Inbound document in Embedded EWM scenario for Purchase Order receiving. 

Answer: In SAP S/4HANA embedded Extended Warehouse Management (EWM), Synchronous Goods Receipt is a feature that allows you to record physical stock arrivals in both Inventory Management (IM) and EWM simultaneously in real-time, completely eliminating the need to create traditional intermediate inbound delivery documents.

How it Works:

• Delivery-less Processing: Instead of waiting for an inbound delivery document to trigger warehouse tasks, posting a Goods Receipt (e.g., via the Post Goods Movement app or Inventory Management BAPIs) automatically triggers the EWM receipt and creates putaway warehouse tasks at the same time.

• Direct Bin Placement: The system determines the putaway destination bin directly from the transaction and triggers the warehouse tasks independently of a warehouse request.

• Supported Scenarios: It applies to external procurements (Purchase Orders, scheduling agreements, Stock Transport Orders) and production orders (discrete and process manufacturing).

Key Benefits:

• Simplified Process: Cuts down document clutter by processing without Inbound Delivery documents or warehouse requests.
• Increased Speed: Streamlines the putaway process for simple scenarios (e.g., direct to fixed bin, no Value-Added Services needed), getting stock available faster.
• Real-Time Visibility: Synchronizes IM and EWM financial and physical records instantly without delayed queued processing (aRFC/qRFC).

See the following Blog Posts:

https://docs.google.com/MIGO-EmbeddedEWM/

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

Question: Depict EWM Inspection for MM EWM Inbound Delivery process.

Answer: SAP Extended Warehouse Management (EWM) integrates with the Quality Management (QM) module to automate quality checks during goods receipt, internal stock transfers, and production. When inventory is received, EWM stock is placed in quality status (Q-stock) and a QM inspection lot is triggered automatically for the warehouse team to evaluate.

EWM handles various types of inspections depending on where it integrates with the supply chain with the following Key Inspection Types::

• Counting (IOT 3): Standard 100% quantity verification upon inbound deliver.

• Inbound Deliveries / Goods Receipt (IOT 4): Triggers an inspection (e.g., lot type 1701) automatically as soon as goods are received from a vendor or production.

• Returns & Internal Stock (IOT 5): Evaluates products currently stored in the warehouse or when being returned by customers.

See the following Blog Posts:

https://froggysap.blogspot.com/Inbound Delivery QM/

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

Question: What is the "9-series" ERROR in Outbound Queue in EWM, and specifically the Message Action"/SCWM/MSG_DTN_PRD_OUT_SEND" not supported below?

Answer: Deleting a stuck Post Processing Framework (PPF) outbound queue in SAP EWM (SMQ1 or SMQ2) is generally not recommended and unsafe as a first step. Doing so permanently deletes the transactional message, leading to broken document flows, inconsistent delivery statuses between EWM and ERP, and missing deliveries.

Note: However, It is generally safe to delete hung or obsolete printing-related Post Processing Framework (PPF) outbound queues (via SMQ1) or stuck triggers (via SPPFP) in SAP EWM, as it only removes the print command data. This action will not alter your inventory balances or harm your underlying delivery or warehouse documents.

To resolve printing issues with /SCWM/PRD_OUT_LOAD_LIST_PRINT (the smartform/PDF used for the Outbound Loading List in SAP EWM), you must troubleshoot the Post Processing Framework (PPF) condition technique and ensure the associated Adobe Form / SmartForm is correctly mapped and activated.

Resolve the issue by following these steps:

1. Check the PPF Action Profile Configuration: 

Ensure the PPF action profile assigned to your outbound delivery or transportation unit is active and configured correctly. [1]

Go to the PPF condition configuration using transaction SPPFCADM.

Select Application /SCDL/DELIVERY (or your specific TU application).

Check the Action Profile for outbound loading and verify that /SCWM/PRD_OUT_LOAD_LIST_PRINT is maintained in the action definition.

Ensure the Schedule Condition and Start Condition are met

2. Verify Output Condition Records:

If the system fails to trigger the output, your condition records might be missing or incorrect.

Go to the condition maintenance transaction for outbound deliveries: /SCWM/DLV_PRINT or /SCWM/PRDO.

Ensure that a valid condition record exists for the print profile, document type, and warehouse number.

Verify that the SmartForm / Adobe Form name is correctly mapped in the condition record.  

3. Check Spool and Printer Mapping:

If EWM reports that the print job was successfully processed but nothing prints, the issue is likely with the spool generation or device type. [1]

Review transaction SP01 or SP02 to see if the spool request was generated.

Check if the specific output device (printer) is set to immediately print and ensure the user profile has the correct default printer assigned.

Common Workflow to Fix Stuck Queues:

1. Open SMQ2 (for Inbound) or SMQ1 (for Outbound).

2. Double-click the queue name to view the error status.

3. Fix the underlying data or configuration issue (e.g., missing storage bin or wrong mapping).

4. Select the failed queue line and click Activate (or hit F6) to reprocess it.

Essential T-codes for resolving queue issues include:
1. Queue Monitors

• SMQ2 (Inbound Queues): View and process queues coming into EWM (or going into ERP) that are blocked or stuck in an error status.

• SMQ1 (Outbound Queues): View and manage queues sending data out of EWM to the ERP/Core Interface (CIF).

• SMQ3 (Queue Administration): Used to view saved queues or LUWs (Logical Units of Work) that were temporarily parked for later processing.

2. Diagnosis & Logs

• /SCWM/MON (Warehouse Management Monitor): The central hub. Navigate to Tools > Queue Manager to monitor and restart delivery queues directly inside the EWM framework.

• SLG1 (Application Log): Analyze error logs to uncover granular details on why an inbound/outbound delivery failed to post or update.

3. System & IDoc Troubleshooting

• ST22 (ABAP Dump Analysis): Investigate short dumps. If an integration queue fails with a system error, a dump is often generated in either EWM or ERP.

• WE02 (IDoc List): Use this to display and trace IDoc messages (particularly if your integration with SAP ERP uses decentralized delivery interfaces).

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

Question: What is the method to MASS Delete specific types of EWM Outbound Queue ?

Answer: Methods to Delete Queues:

Direct SMQ1 Manual Mass Deletion:

1. Open transaction SMQ1 (qRFC Monitor for Outbound Queues).

2. Enter your specific criteria (e.g., Target Destination, *DLV* in the Queue Name field).

3. Press Enter or Execute (F8).

4. Go to the menu: Edit -> Select All.

5. Click the Delete icon (Shift + F2), or go to Edit -> Delete Selected Objects.

6. Confirm the deletion.

Automating Mass Deletion (for large volumes):

If you have thousands of entries and manual deletion is too slow, 

1. Go to transaction SE38 or SA38.

2. Enter program name RSTRFCQDS.

3. Execute.

4. Input your specific queue names and destination, then run to safely purge the targeted queues in bulk. 

Note: It is not safe to mass delete SAP EWM (Extended Warehouse Management) outbound queues as a first resort. Deleting them permanently removes the transactional data, which breaks document flow and creates severe data inconsistencies (e.g., missing deliveries, broken stock status) between your EWM and ERP/S4H systems.

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

Question: Who suppose to look into this SMQ2 is it all i.e All modules i.e CPL, FICO, PS, PM ?

Answer: Transaction SMQ2 manages inbound qRFC (Queued Remote Function Call) queues. It is not specific to just one module. Any module (like FICO, PS, PM, or CPL) that relies on asynchronous data replication, interfaces, or IDocs will have its respective module consultants and business teams analyze the stuck queues.

Who is Responsible for Checking SMQ2?

Because SMQ2 acts as a central holding area for incoming data, the responsibility is divided by data ownership, not the system itself:

• Module Consultants (FICO, PS, PM, CPL): They are responsible for understanding the functional errors in the queue. If a queue is stuck due to a missing configuration, wrong master data, or a financial period being closed, the respective functional module expert must investigate.
• Integration / PI / CPI Team: If the queues are backed up because of broken communication channels between systems (e.g., between SAP ECC/S4HANA and EWM/CRM), the integration team steps in.
• BASIS Team: They handle the underlying technical infrastructure, such as resetting the locks, checking RFC destinations, and making sure the queue monitor is actively processing data (e.g., via SMQR).

Responsibility for monitoring and clearing SAP EWM inbound (SMQ2) and outbound (SMQ1) queues is typically a shared process, with distinct roles for business application users (super users) and technical support.

1. Business / Application People (Key Users, Super Users, Functional Analysts):

• Work: They check queues daily using transactions like /SCWM/MON (Warehouse Monitor) or SMQ2. They are responsible for queue entries that fail due to business or master data issues.
• Common Examples: Missing master data (e.g., product weight/volume missing, incorrect packaging specs), unposted Goods Issues, or closed posting periods in ERP
• Action: They fix the underlying business data, then manually restart the stuck queue.

2. Technical People (ABAP Developers, Basis Administrators):

• Work: They step in when errors are tied to system issues or code faults.
• Common Examples: Custom program bugs, RFC communication dropouts, system dumps (e.g., ST22), or lock table conflicts.
• Action: They perform root cause debugging, review short dumps, or apply infrastructure-level fixes.

Standard Industry Best Practice:

• Tier 1 (Business Analysts/Super Users): First-line of defense. They should review the queues daily, clear simple data errors, and notify the business.
• Tier 2 (Technical/ABAP): Second-line of defense. Engaged if the super user cannot identify the error or if the failure is a recurring technical issue.

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

Question: Review EWM Physical Inventory.

Answer: The standard execution flow relies on designated SAP Transactions codes and Fiori Apps to process, post, and clear inventory adjustments, Step-by-Step EWM Process Flow as below:

• 1. Create and Activate the PI Document: 
• T-Code: /SCWM/PI_CREATE
• Action: Select your inventory procedure code (e.g., HL for ad-hoc bin specific or HS for product specific). Input your target search criteria, select the generated item rows, click Set Flag, and change the initial status to Active before saving. User can decide to either set "Posting Block" or "Freeze Inventory" at time of the PI activity. 
• 2. Execute the Physical Count:
• Mobile (RF Method): 
• Access transaction /SCWM/RFUI. Navigate to 04 Internal Processes ➔ 01 Inventory Counting ➔ 02 Inventory Counting Manually. Scan the bin, verify handling units, and enter the physical quantity directly on your mobile scanner.
• Manual Paper-Driven Method: 
• Print the physical selection sheet via /SCWM/PRPI_DOC. Hand the list to a warehouse associate to tally items manually. Once written down, use /SCWM/COUNTLIST or /SCWM/PI_PROCESS to type the actual quantities into the system.
• Fiori App Method: 
• Count Physical Inventory - Paper-Driven Counting (App ID: F3340): Allows users to filter, view, and print Physical Inventory documents. It is primarily used to enter count results into the system after physical counting is completed.
• Physical Inventory Document Overview (App ID: F0379A): Provides a comprehensive look at all created physical inventory documents. You can search by storage location or count status and drill down to check item-level counting results.
• External System/ (Spreadsheet):
• /SCWM/PI_DOWNLOAD: Used to export storage bin and stock data to external systems or spreadsheets to facilitate offline inventory plannint.
• /SCWM/PI_UPLOAD): Allows you to upload storage bin data and count results from external systems back into your SAP EWM system.
• 3. Post Differences in EWM:
• T-Code: /SCWM/PI_PROCESS
• Action: Locate your reference document number, review the variance between the book inventory and actual entry, and click Post. This step completes the counting run and adjusts the physical inventory availability balance at the local bin architecture leve
• 4. Clear Differences at ERP / IM Level:
• T-Code: /SCWM/DIFF_ANALYZER
• Action: Discrepancies posted in EWM are held temporarily in a virtual interface component. Execute the Difference Analyzer tool to evaluate value variances against user tolerance groups. Select the item lines and hit Post and Save. This generates the official ERP Material Document (similar to MM's MI07), aligning Inventory Management valuation with the warehouse floor.

Click below to see EWM PI steps:

https://docs.google.com/Physical Inventory Desktop/

https://docs.google.com/Physical Inventory Mobile/

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

Question: PM-EWM integration preview.

Answer: Integrating SAP Plant Maintenance (PM/EAM) with SAP Extended Warehouse Management (EWM) automates the picking, staging, and issue of spare parts for maintenance orders. This eliminates manual coordination, accelerates repair times, and streamlines inventory visibility for Maintenance, Repair, and Operations (MRO) processes.

See the following Blog Posts on steps:

https://docs.google.com/presentation/pm qm integration steps/

Notes: the Post only show steps, actual SAP Demo creation will be created in a separate Blog Post as and when the EWM system is available soon in the future.

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

SAP S/4 EWM - Physical Stock vs Available Stock in EWM Warehouse Monitor

 

CLICK here to view the Presentation

Question no 4132 : Revenue G/L Account Determination at Sales Order Billing

In SAP Sales & Distribution, select the possible direct influencing factors for the Revenue G/L Account at Billing ?

(more than one answers)

A) Condition Type.
B) Material Master Valuation Class.
C) Account Assignment Group assigned to the Customer Master.
D) Sales Area.
E) Chart of Account. 
.

Answer: A, C, E

The following are direct influencing factors:
(IMG - SD - Basic Functions - Account Assignment/Costing - Revenue Account Determination - Assign G/L Accounts)
. Application "V" for Sales Order
. Condition Type "KOFI" (from the Account Determination Procedure assign to the Billing Document Type)
. Chart of Accounts
. Sales Organization
. Account Assignment Group assign to Customer Master
. Account Assignment Group assign to Material Master
. Account Key (which is assigned to the Condition Type PR00 to the Billing Pricing Procedure)

SAP SD - Delivery Processing using FIORI Apps for Classic MM Storage Location

CLICK here to view the Presentation

Question no 4131 : Effective Price Calculations

In SAP Material Management as at S/4 1909, Effective Price Calculation in "Info Record List Display Report (Transaction code 1E1M" includes/considers which of the following?

(more than one answers)

A) Freight costs.
B) Discounts.
C) Customs and Duties (Taxes).
D) Surcharges
E) All of the above.
.

Answer: A, B, C, D, E

Effective price calculation in SAP MM determines the actual procurement cost of a material by adjusting the gross price with discounts, surcharges, freights, and taxes. It serves as the baseline for evaluating price variances against the Material Master and drives accurate accounting entries at Goods Receipt. 

Key Price Tiers:

• Gross Price: The base price of the material before any deductions or additions.
• Effective Price: The resulting price after deducting all discounts (cash, quantity, special) and adding surcharges.
• Net Price: The final payable amount. Calculated by taking the Effective Price and adding delivery costs (freight), packaging costs, and relevant taxes.

Price Calculations example:

• Purchase Order for a Material with Quantity of 100 units
• Gross Price: $10.00 per unit 
• Standard Discount (2%): -$20.00 (2% x $1,000)
• Surcharge: +$70 fixed amount
• Freight Charge: +$50.00 fixed amount
• Tax: 10% based on Gross Value
• Payment Term Cash Discount (2% in 30 Days)

• Gross Value: Gross Price × Quantity 
• Gross Value: $10.00 per unit x 100 units 
• Gross Value: $1,000.00 (or $10.00 per unit)

• Net Value: (Gross Price × Quantity) - Discounts + Surcharges
• Net Value: ($10.00 per unit x 100 units) - (2% of $1,000) + ($70)
• Net Value: $1050.00 (or $10.50 per unit)

"Info Record List Display Report (Transaction code 1E1M" offers the calculation of "Effective Price" calculation as follow:

• Effective Value: Gross Value - Standard Discounts + Surcharges + Freight + Taxes - Cash Discount
• Effective Value: $1,000 - $20 + $70 + $50.00 + (10% x $1,000) - (2% of $1050)
• Effective Value: $1,179.90 ($11.79 per unit)

Payment Term Cash Discount via standard condition type SKTO condition type (based on the Payment Term agreed with the Vendor) for cash discounts is included in the pricing schema on a purely statistical basis. It calculates the discount amount for informational purposes but does not alter the actual net price, effective price, or inventory value. Payment Term Cash Discounts are (usually) only considered when actual payment to the Vendor is done within the Payment term stipulated Days to enjoy that Cash Discount; therefore only effectively "Gain" at the point of Actual payment. 

Important Note: in SAP MM Condition calculations in the PURCHASING DOCUMENTs, the Calculation Schema (Pricing Procedure) dictates how the system computes the final procurement price. It defines the exact sequence of conditions (such as gross price, discounts, freight, and taxes), the mathematical operations (addition or subtraction), and the subtotals required to arrive at the final net or effective price. Therefore, the derivation of price values are configurable based on the company requirements. In this context paragraph, the Payment Term Cash Discount is often designed to be STATISTICAL in Standard SAP.

SAP PM - Teams & Responsibilities

 

CLICK here to view the Presentation

SAP PM - Maintenance Scheduling Board Fiori APP

 CLICK here to view the Presentation

SAP PM - Perform Maintenance JOB Fiori APP

CLICK here to view the Presentation 

SAP MM - Consumption History update

CLICK here to view Presentation

Question no 4130 : Cash Discount "SKTO" in MM Purchase Order

In SAP Material Management, note the Cash Discount of Standard Condition Type "SKTO", how did the system retrieve the 3% Cash Discount of "SKTO" Condition Type ?

(only one answer)

A) Purchasing Info Record.

B) Material Master Purchasing data view Condition Record.

C) General Condition.

D) Vendor Master Payment Term in the Purchasing Organization data.

E) Rebate Condition.

.

Answer: D

Notes on Condition Type SKTO: 

• In SAP MM (Materials Management) and SD, SKTO is a standard condition type used to calculate and display cash discounts (prompt payment discounts). It retrieves the discount percentage based on your agreed payment terms and displays it for information purposes during pricing.
• Statistical Condition: SKTO is marked as statistical in the pricing procedure. This means it only calculates for information, it does not alter the actual net value of the material or affect the final inventory valuation.
• Payment Terms Trigger: The discount rate and amount are automatically fetched from the payment terms maintained in the vendor master or Purchase Order (PO). It is important to note that there 2 payment terms in the vendor master; one in the company code level (for non-po based invoice) and another one in the purchasing org data level (for po based invoice). 
• How it works in MM:
• When you create a Purchase Order (ME21N), the system applies the Payment Terms (e.g., Pay within 14 days, get a 2% discount).
• The SKTO condition automatically reads these payment terms and calculates the potential discount amount.
• Because it is statistical, the Purchase Order remains correctly valued at the gross price, but the system stores the SKTO data so the Finance team knows exactly what discount to expect if the invoice is paid early.
• Accounting Impact: When the actual invoice is processed in Logistics Invoice Verification (MIRO), the cash discount is handled directly by SAP's financial accounting component (FI). Depending on your company code settings, the discount taken is either posted to a cash discount received/cleared account or reduces the material's inventory value.
• In SAP, you can post vendor invoices in transaction MIRO using either Gross (Document Type RE) or Net (Document Type RN) methods, primarily depending on how you want to handle cash discounts and taxes:
• Gross Invoice Posting (Document Type: RE): 
• This is the default, standard method in MIRO. The vendor is credited with the full invoice amount (including taxes), and the cash discount is not considered during the initial invoice entry.
• Cash discounts are only recognized when the payment is actually made, reducing the cash discount account.
• d
• Net Invoice Posting (Document Type: RN): 
• The invoice amount is entered exclusive of the cash discount. The system automatically deducts the expected cash discount from the stock or cost account. This means that the cash discounts are already realized when the invoice is first posted.
• The discount amount is posted to a Cash Discount Clearing account and then cleared at the time of payment.
• Organizations that strictly enforce automatic cash discount deductions and want their inventory/material costs accurately reflected at the net cost immediately. 
• Net invoice posting via transaction code MIRO is an acceptable practice in accounting, but its acceptability depends heavily on strict internal controls and consistent accounting policies. 

SAP S/4 Embedded EWM - ABC Analysis to Update Storage Section Indicator

 

CLICK here to view the Presentation

SAP PP - Quota Arrangement for Production Versions

CLICK here to view Presentation

S/4 EWM Fiori - Warehouse KPIs (App iD F4024) & Confirm open WT (App iD F4150)

 CLICK here to view the Presentation

SAP: Wáhrung 貨幣 (货币) Currency (通貨 Tsūka つうか) Mata Wang

Q&A in Class (2026-06-12) EWM100

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

Question: Review of Expected Goods Receipt for PO with ERP to EWM Integration (EWM side use provided FIORI App).

Answer: Expected Goods Receipt (EGR) in SAP EWM is a temporary, EWM-specific document created in advance based on an open Purchase Order or Production Order. It acts as an electronic template that allows warehouse operators to process and receive goods even before the formal inbound delivery is created in the ERP. 

Expected Goods Receipt (EGR) is relevant for embedded SAP EWM, but it operates differently than it did in decentralized or older ERP systems.In an SAP S/4HANA embedded EWM environment, the standalone "Notification of Expected Goods Receipt" and persistent "EGR" database documents have been eliminated. Instead, EWM accesses purchase orders and manufacturing orders from SAP S/4HANA directly in real-time.

How it Works in Embedded EWM:

• Transient Documents: Rather than storing a separate EGR document in EWM, the system emulates "transient" EGR data on the fly by reading directly from the open purchase or manufacturing order.
• No Middleware: Since both EWM and Inventory Management are in the same S/4HANA system, you no longer need to replicate or update transactional EGR data between separate systems.
• Delivery Creation: This transient data still acts as a template, allowing warehouse operators to manually or automatically create inbound deliveries in EWM based on the purchase order or production order.
• Synchronous Goods Movements: Embedded EWM supports "Synchronous Goods Movements," allowing you to post the goods receipt directly in S/4HANA Inventory Management or Production without even needing to create an inbound delivery.

Click below to view the Process and related configuration:

https://froggysap.blogspot.com/2026/06/blog-post_13.html

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

Question: Review of EWM Process steps in class: 

Click below to overview the Processes in EWM

https://froggysap.blogspot.com/S4 EWM Embedded Features

https://froggysap.blogspot.com/EWM Enterprise Structure

https://froggysap.blogspot.com/Process Flow of EWM Inbound Delivery

https://froggysap.blogspot.com/Process Flow of EWM Outbound Delivery

https://froggysap.blogspot.com/S4 MM Inbound Delivery Procssing 3

https://froggysap.blogspot.com/SAP S/4 EWM - Setup and Processing Inbound Delivery for a Purchase Order

https://froggysap.blogspot.com/SCM EWM End-to-End Inbound

https://froggysap.blogspot.com/SD Outbound with EWM Basics

https://froggysap.blogspot.com/SCM EWM End-to-End Outbound

https://froggysap.blogspot.com/Outbound Process with Process-Oriented Storage Control

https://froggysap.blogspot.com/Fixed Bin Replenishment

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

Question: Review of Serial Number Processing from ERP to EWM system. 

Answer: Serial number processing in SAP EWM provides end-to-end traceability for individual items. Serial numbers are mapped from the ERP system and captured or generated during goods receipt, tracked throughout warehouse movements (putaway/picking), and validated upon goods issue to guarantee absolute item accuracy.

Process steps: 

Goods Receipt (GR): EWM copies serial numbers from the ERP inbound delivery. If missing, you must enter them during warehouse task confirmation or use Provisional Serial Numbers (which automatically assign a placeholder if numbers aren't known yet).

Putaway & Picking: You can assign serial numbers manually or automatically. During RF transactions, EWM allows you to scan or input entire serial number ranges instead of typing them out individually.

Goods Issue (GI): Serial numbers are copied from the outbound delivery. If EWM picks in the background, it automatically assigns known serial numbers (e.g., using FIFO) to complete the pick.

Master Data & Customizing:

Serial Number Profiles: Assigned in the material master plant stoage view 2. Both the ERP backend and EWM must share an identical profile configuration.

ERP configuration: IMG - MM - Purchasing - Serial Numbers - Determine Serial Number Profile

Harmonized Profiles: From S/4HANA 2020 onward, you can use harmonized serial number profiles to maintain both ERP serialization rules and EWM requirements in a single profile.

EWM configuration: IMG - SCM EWM - EWM - Master Data - Product - Serial Number Profiles - Harmonized Serial Number Profiles - Define Serial Number Profiles

Length Constraints: While S/4 EWM supports serial numbers up to 30 characters, it is highly recommended to restrict them to 18 characters to maintain master data compatibility with legacy SAP ERP systems.

Click below to overview the Processes in EWM

https://froggysap.blogspot.com/2026/06/blog-post_11.html

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

Question: Review of Batch Processing from ERP to EWM system. 

Answer: SAP Extended Warehouse Management (EWM) Batch Number Processing tracks groups of identical products, such as managing expiration dates, manufacturing dates, and quality statuses. It integrates batch records between the core ERP system and EWM, allowing batches to be created, determined, and updated across both inbound and outbound warehouse tasks.

Essential Transactions:

• Batch Master Maintenance: Use MSC1N (Create), MSC2N (Change), and MSC3N (Display).

• Batch Determination: Configured in the system to automatically filter or propose optimal batch numbers during the outbound picking process. (Logistics - Central Functions - Batch Management - Batch Determination - Batch Search Strategy - For SD - Use VCH1 (Create), VCH2 (Change), and VCH3 (Display).

Click below to overview the Processes in EWM

https://docs.google.com/Batch Processing for EWM Inbound

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

Question: Review Physical Inventory in EWM with available Fiori Apps. 

Answer: Physical Inventory (PI) in SAP Extended Warehouse Management (EWM) is the process of verifying actual warehouse stock quantities and conditions against system records to ensure accurate financial reporting and stock control.

Click below to overview the Processes in EWM

https://docs.google.com/Physical Inventoy Fiori App

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

S/4 EWM Fiori - Expected Goods Receipt for MM with EWM integration

CLICK here to view the Presentation

S/4 EWM Fiori - Serial creation and WT Putaway Confirmation

 CLICK here to view the Presentation

SAP SD - Delivery Processing (Part 3) (Adjust Delivery & Transportation Scheduling)

CLICK here to view the Presentation

Question no 4129 : Kanban call for Scheduling Agreement

In SAP MM as at S/4 1909, Kanban Replenishment with Control Type "2 Working with Scheduling Agreement" expects which of the following pre-requisites ?

(more than one answers)

A) Storage Location with PSA for Kanban assigned to the Scheduling Agreement item.
B) Kanban Indicator in the Scheduling Agreement item.
C) Kanban Indicator in the Material Master Purchasing data view.
D) MRP 4 data view for Storage Location without Planning in the Material Master MRP 4 data view.
E) A Source List.
.

Answer: A, B

The following setup is desirable:
. Replenishment Strategy for External Procurement with Control Type "2 Working with Scheduling Agreements" with default Goods Receipt Movement Type.
. PSA assigned to SLoc for Kanban.
. MRP Area assigned to SLoc for Kanban.
. Material Master MRP1 vew assigned to MRP Area (Kanban SLoc) with MRP type "ND" for No Planning.
. Extend Material Master to the Kanban SLoc.
. Scheduling Agreement item assigned to Kanban SLoc.
. Scheduling Agreement item detail (via Additional data) assign to Kanban Indicator "X".
. Setup Control cycle for the Material with the Replenishment Strategy and assign the Scheduling Agreement item to it.

SAP SucccessFactors - Add a Performance Goal

 

CLICK here to view the Presentation