Back to interview questions

100+ SAP MM Interview Questions and Answers

100+ SAP MM Interview Questions and Answers

Explore 120 SAP MM interview questions and answers on procurement, master data, inventory, valuation, invoice verification, and practical S/4HANA scenarios.

Explore 120 SAP MM interview questions and answers on procurement, master data, inventory, valuation, invoice verification, and practical S/4HANA scenarios.

By

Team Sherlock.sh

Add Sherlock as a preferred source on Google

SAP Materials Management connects purchasing and inventory processes with master data, organizational structure, and financial integration. Functional consultants and business users need to explain how a requirement becomes an order, how goods movements affect stock, and how purchasing and receipt evidence supports invoice verification.

This guide to 100+ SAP MM Interview Questions and Answers contains 120 questions across beginner, intermediate, and experienced levels. It covers procurement, inventory, valuation, controls, and practical process exceptions, using SAP S/4HANA concepts while identifying relevant ECC, deployment-edition, and configuration differences.

How can recruiters detect AI-assisted cheating, deepfakes, and impersonation during SAP MM interviews?

SAP MM interviews often use a purchase-order history, a stock discrepancy, or an invoice exception to test functional reasoning. A candidate may need to distinguish missing master data from a configuration issue, explain a quantity or value difference, and identify which document or setting would confirm the cause. Unauthorized real-time help can hide whether the candidate understands that process independently.

Sherlock AI helps recruiters detect potential AI-assisted cheating, deepfakes, candidate impersonation, and unauthorized real-time assistance during SAP MM interviews.

Pair interview-integrity checks with a small, clearly scoped business scenario and a follow-up change to its quantity, price, or process conditions. Ask candidates to explain the document flow, expected stock and accounting effects, and the checks needed before correcting an issue. Review suspicious activity in context rather than treating a signal as proof of misconduct.

SAP MM Interview Questions

Select questions that reflect the role’s procurement, inventory, configuration, and support responsibilities. State the SAP product, deployment edition, process variant, and relevant assumptions before asking for a transaction, app, or posting outcome. Evaluate the candidate’s reasoning and verification steps rather than transaction-code recall alone.

SAP MM Interview Questions for Beginners

These beginner questions establish procurement and inventory fundamentals, organizational units, key master data, purchasing documents, goods movements, and invoice verification. They test whether a candidate can explain the purpose and sequence of the process before discussing configuration details.

  1. What does SAP MM cover, and how does it connect procurement to Finance, Production Planning, and Sales?

  2. What should you establish about ECC, S/4HANA, and the deployment edition before discussing an MM solution?

  3. How do company code, plant, and storage location differ in SAP MM?

  4. How is a purchasing organization different from a purchasing group?

  5. How are material master views and organizational levels used in procurement?

  6. What is the difference between material type and material group?

  7. How do base unit, order unit, and order price unit differ?

  8. How is a supplier represented by Business Partner roles in S/4HANA compared with the classic vendor master approach?

  9. What information does a purchasing info record hold?

  10. How do a source list and a quota arrangement solve different sourcing problems?

  11. What is the difference between a purchase requisition and a purchase order?

  12. When would a buyer use an RFQ and supplier quotation before creating a purchase order?

  13. How do purchasing document type and item category affect a purchase order?

  14. What does an account assignment category specify in a purchasing document?

  15. How does procurement for stock differ from procurement for direct consumption?

  16. What belongs at purchase order header, item, and delivery schedule-line level?

  17. How does a purchasing contract differ from a scheduling agreement?

  18. What happens when a goods receipt is posted against a stock purchase order?

  19. How do goods receipt, goods issue, and transfer posting differ?

  20. What do movement types control, and what are common examples such as 101, 102, 201, 261, 311, and 551?

  21. How do unrestricted-use stock, quality inspection stock, blocked stock, and GR blocked stock differ?

  22. What is special stock, and why must ownership and account assignment be considered separately?

  23. What is a reservation, and does creating one physically move or deduct stock?

  24. How do valuation area and valuation class differ?

  25. How do standard price and moving average price differ in material valuation?

  26. What are the basic accounting entries for a valuated stock receipt and a matching supplier invoice?

  27. What does Logistics Invoice Verification check, and how does it differ from paying a supplier?

  28. What is goods-receipt-based invoice verification?

  29. Why are delivery and invoice tolerances used instead of requiring every quantity and price to match exactly?

  30. What are the main steps in a physical inventory process?

  31. How does a batch differ from a serial number?

  32. What does MRP do for externally procured materials?

  33. How do procurement type and special procurement influence a material's replenishment?

  34. How does subcontracting procurement differ from a normal purchase order?

  35. When does supplier consignment create an ownership change and a liability?

  36. What is a stock transport order, and why use one instead of a simple transfer posting?

  37. What is a service entry sheet, and why is accepting a service different from receiving physical stock?

  38. How do a classic release strategy and S/4HANA flexible workflow differ?

  39. What can purchase order history tell you about delivery and invoice status?

  40. Where does Inventory Management stop and warehouse management begin?

SAP MM Interview Questions for Intermediate

These intermediate questions examine procurement variants, stock and valuation behavior, approval controls, invoice differences, and integration points. They ask candidates to interpret a concrete exception and separate master-data, process, and configuration causes.

  1. How would you configure purchasing organization assignments for one company code with several plants?

  2. A material exists but cannot be purchased for a new plant. What master-data extensions would you check?

  3. A supplier is available in one purchasing organization but not another. What Business Partner data and blocks would you inspect?

  4. Why can a purchase order propose a different price from the one a buyer expects from the info record?

  5. How is a quota rating calculated, and which supplier receives the next unsplit requirement?

  6. Why can automatic source determination produce different results in MRP and in a manually created requisition?

  7. What prerequisites must be satisfied before purchase requisitions can be converted automatically into purchase orders?

  8. When should recurring deliveries use a scheduling agreement rather than repeated releases against a contract?

  9. How are characteristics, class type 032, release codes, and release indicators used in a classic release strategy?

  10. How do workflow order, start conditions, step conditions, and recipients interact in flexible purchase order approval?

  11. How can changing a purchase order after approval trigger a new approval cycle?

  12. Why might the same field be mandatory in one purchasing document but optional or hidden in another?

  13. How do condition types, access logic, scales, and the calculation schema determine a purchase order price?

  14. How do BSX, WRX, PRD, and GBB participate in automatic account determination?

  15. How can one consumption purchase order item be distributed across multiple cost centers?

  16. How would you calculate the postings for a standard-price material when PO and invoice prices differ?

  17. How does a receipt and a later invoice difference change moving average price when sufficient stock remains?

  18. How do the 103/105 and 107/109 goods receipt processes differ?

  19. When should you use a receipt reversal, a return delivery, or a returns purchase order?

  20. How do partial delivery, underdelivery tolerance, and the delivery completed indicator affect an open purchase order?

  21. How can an order-price-unit conversion cause a goods receipt or invoice value discrepancy?

  22. How do valuation category and valuation type support split valuation?

  23. Which material and purchasing settings control shelf-life checks at goods receipt?

  24. When can negative stock be permitted, and what reconciliation risks does it create?

  25. How do one-step and two-step transfers between storage locations differ?

  26. What changes in a stock transport process when the supplying and receiving plants belong to different company codes?

  27. How are components provided to a subcontractor and consumed when the finished material is received?

  28. How are consignment withdrawals valued and settled with the supplier?

  29. How would you choose between a classic blanket order and a lean-service limit item?

  30. What should be validated before a lean-service entry sheet is approved?

  31. How are price and quantity variances handled when an invoice is posted, blocked, and later released?

  32. How does a subsequent debit or credit differ from an invoice or credit memo that changes the invoiced quantity?

  33. How are planned and unplanned delivery costs treated during invoice verification?

  34. How does evaluated receipt settlement create invoices, and what makes a supplier and PO eligible?

  35. What is the difference between holding, parking, and posting a supplier invoice?

  36. Why can the GR/IR account retain a balance after an order appears commercially complete?

  37. How do reorder-point planning and requirements-based MRP produce different replenishment decisions?

  38. How do lot size, safety stock, and planned delivery time change a procurement proposal?

  39. How do a posting block and freezing book inventory affect a physical inventory count?

  40. Which supplier-evaluation KPIs would you compare, and what data-quality checks make the comparison meaningful?

SAP MM Interview Questions for Experienced

These experienced-level questions focus on process design, cross-functional incidents, reconciliation, migration, and controlled change. They assess how a consultant evaluates business impact, competing requirements, data quality, and the evidence needed to accept a solution.

  1. How would you design central procurement across several company codes without confusing purchasing responsibility with inventory valuation?

  2. Which MM design assumptions must be revisited in an ECC-to-S/4HANA conversion?

  3. How would you reconcile opening inventory quantities and values during a new-system cutover?

  4. How would you handle partially received or invoiced purchase orders when moving to a new S/4HANA Cloud Public Edition system?

  5. MRP created a requisition without the expected source of supply. How would you isolate the reason?

  6. An MRP Live run leaves some materials unplanned or sends them to classic MRP. How would you investigate?

  7. A newly added supplier receives nearly every new requirement in a quota arrangement. How would you correct the allocation design?

  8. A high-value purchase order was approved automatically despite a required approval policy. How would you investigate the flexible workflow?

  9. A classic purchase order release strategy is not determined although the value threshold seems correct. What would you inspect?

  10. A purchase order is approved but the supplier has not received it. How would you trace output without creating duplicate orders?

  11. How would you design and diagnose a procurement process in which the ordering supplier, goods supplier, and invoicing party differ?

  12. How would you separate buyer, receiver, invoice processor, and approver access in an MM control design?

  13. A goods movement fails with an account-determination error. How would you trace the missing account without changing the material arbitrarily?

  14. A team proposes changing valuation class for a material with stock and open purchasing documents. What must be evaluated first?

  15. Why can a late invoice produce an unexpected moving average price or a price-difference posting after most stock has been consumed?

  16. How does mandatory Material Ledger differ from activating actual costing, and what does that mean for MM period-end work?

  17. A receipt must be posted to the previous month. Which MM and FI period checks and valuation consequences should be reviewed?

  18. How would you investigate and resolve aged GR/IR differences without treating every residual balance as a write-off?

  19. How would you investigate a suspected duplicate supplier invoice and improve prevention without blocking legitimate credits?

  20. How can an exchange-rate difference arise between a purchase order, goods receipt, and supplier invoice?

  21. What can go wrong when reversing a goods receipt after a GR-based invoice has already been posted?

  22. Stock is visible in the system but a production goods issue fails. How would you distinguish stock type, reservation, batch, and availability problems?

  23. How would you reconcile an inventory quantity difference between IM and EWM without making a blind adjustment?

  24. Actual subcontractor component consumption differs from the PO component proposal. How would you correct and reconcile it?

  25. Consignment settlement fails or uses an unexpected price. How would you trace the withdrawal and pricing data?

  26. Goods have left a supplying plant but not reached the receiving plant. How would you investigate stock in transit and financial ownership?

  27. How would you stop procurement from a disqualified supplier while distinguishing source-list, purchasing, posting, and quality restrictions?

  28. Physical inventory repeatedly finds differences in the same materials. How would you identify the process cause rather than merely post differences?

  29. A lean-service entry sheet was approved with an incorrect quantity and an invoice now exists. How would you plan the correction?

  30. A contract price changed, but existing purchase orders still show the old price. What should you check before repricing?

  31. A purchase requisition's delivery date is too late to prevent a shortage. How would you trace scheduling and choose an operational response?

  32. How would nonvaluated goods receipt change expense recognition for an account-assigned purchase order?

  33. Why should an ECC-era inventory report not be moved to S/4HANA by assuming the same physical tables and stock aggregates?

  34. When should an MM requirement use standard configuration, an approved extension point, or a side-by-side extension?

  35. How would you design purchasing controls for capital assets and project expenditure rather than ordinary cost-center consumption?

  36. How would you manage a defective-goods return when the business expects a replacement rather than a supplier credit?

  37. Why can a free-of-charge receipt affect standard-price and moving-average-price inventory differently?

  38. Which inventory analytics would you use to distinguish excess stock, slow movement, and genuine supply shortages?

  39. What would an end-to-end MM test matrix include before releasing a purchasing and inventory design?

  40. How would you release an MM configuration change safely when it works in test but causes a different posting or approval result in production?

SAP MM Interview Questions and Answers

The answers follow the question bank in order and connect business requirements to master data, document flow, stock or value changes, and controls. Treat numerical examples as scoped illustrations: units, currencies, price control, account assignment, and configuration can change the outcome. Confirm the stated assumptions before applying an answer to a real system.

SAP MM Interview Questions and Answers for Beginners

The beginner answers distinguish common documents, data objects, and process steps with practical examples. They explain what a business event changes and which related document or status helps verify that the step completed as intended.

1. What does SAP MM cover, and how does it connect procurement to Finance, Production Planning, and Sales?

SAP MM, or Materials Management, covers purchasing, inventory management, material valuation, and Logistics Invoice Verification. Its central job is to connect a material or service requirement with an approved source, an order, receipt, and financial follow-through.

The integration points are concrete:

  • Finance: Valuated goods movements update inventory or consumption accounts; invoice posting establishes the supplier payable.

  • Production Planning: MRP translates shortages into procurement proposals, while production consumes purchased components.

  • Sales: Customer demand can drive replenishment, and delivery goods issues reduce inventory. Third-party procurement can connect a sales requirement directly to a supplier order.

For example, demand for 50 assemblies may create a requirement for 100 purchased components. MM manages their procurement and receipt; production uses them; Finance records the associated values. Supplier payment is a subsequent Finance activity.

2. What should you establish about ECC, S/4HANA, and the deployment edition before discussing an MM solution?

Establish the product, release, deployment edition, and enabled business process before naming transactions or proposing configuration. ECC, S/4HANA on-premise, S/4HANA Cloud Private Edition, and Public Edition share procurement concepts but do not offer identical configuration access, applications, or extension options.

Important distinctions include:

  • S/4HANA uses Business Partner maintenance with customer/vendor integration for suppliers.

  • Material Ledger is mandatory in S/4HANA, but actual costing remains optional.

  • Approval and output frameworks depend on the edition, release, document type, and implemented scope.

  • MRP Live does not eliminate every need for classic MRP.

A useful starting description is “S/4HANA Private Edition, specified release, stock procurement with plant-level valuation.” That is much more actionable than “SAP MM.” An ECC transaction-based procedure should not be presented as universal Public Edition navigation.

3. How do company code, plant, and storage location differ in SAP MM?

These units answer different organizational questions:

Unit

Main purpose

Illustrative example

Company code

A complete set of financial accounts and financial statements

US legal accounting unit US10

Plant

Operational unit for procurement, production, planning, or distribution

Dallas distribution plant D100

Storage location

Quantity-based differentiation of inventory within a plant

D100 locations RAW1 and SPAR

A plant belongs to one company code; a storage location belongs to one plant. A company code can contain several plants, and a plant can contain several storage locations. Consequently, 20 pieces in RAW1 and 30 in SPAR are separate storage-location balances but contribute 50 pieces to that plant's relevant stock total. A storage location is not itself a warehouse bin.

4. How is a purchasing organization different from a purchasing group?

A purchasing organization is the organizational unit responsible for purchasing transactions and negotiated commercial conditions. Its assignments determine which plants it can procure for; its company-code assignment depends on the organizational design.

A purchasing group identifies an individual buyer or buying team responsible for day-to-day activities and supplier contact. It is not structurally assigned to a purchasing organization or plant in the enterprise structure.

For example, purchasing organization P100 could buy for three plants, while purchasing groups MET and ELE handle metals and electrical components. A PO records both the commercial purchasing organization and the responsible buying group. Changing the purchasing group does not extend the supplier's purchasing-organization data or authorize the organization to purchase for another plant.

5. How are material master views and organizational levels used in procurement?

The material master is shared across functions, but its data is organized into views and organizational levels. Views group data by business use; organizational levels determine where particular values apply.

Typical procurement-relevant data includes basic data such as description and base unit, purchasing data such as purchasing group, MRP data such as planning procedure and delivery time, accounting data such as valuation class and price control, and storage-location data for inventory handling. Accounting data belongs to the valuation area; many purchasing and planning parameters are plant-specific.

For example, material M-100 can have the same description company-wide but different planning settings in plants A100 and B100. Creating the material number alone does not make every required view available everywhere: using it in a new plant may require extending the existing record.

6. What is the difference between material type and material group?

Material type is a control-oriented classification. Its configuration influences matters such as allowed views, number assignment, field selection, quantity/value updating, and the valuation classes available through the account category reference. Standard examples include raw materials and trading goods, although customers may define their own types.

Material group groups materials or services with similar characteristics for purchasing analysis and responsibility. It is useful for spend reporting and also for text-based purchasing items without a material number.

For example, two differently controlled materials could both belong to the material group “Fasteners.” Reporting their combined spend does not make their inventory valuation behavior identical. Conversely, two raw materials can share a material type while belonging to different groups, such as fasteners and chemicals.

7. How do base unit, order unit, and order price unit differ?

The base unit is the inventory-management unit. The order unit expresses the quantity bought. The order price unit is the unit to which the purchase price relates. The numeric price unit, such as a price per 100 KG, is a separate multiplier and must also be checked.

Assume base unit KG, order unit BAG, and a fixed conversion of 1 BAG = 25 KG. A PO for 8 BAG represents 200 KG. If the price is USD 240 per 100 KG, the net order value is USD 480, excluding tax and freight.

Conversions connect quantities, but the price basis determines value. For variable-weight purchases, actual order-price-unit quantities at receipt can differ from the planned conversion; counting packages alone is therefore insufficient to validate the receipt value.

8. How is a supplier represented by Business Partner roles in S/4HANA compared with the classic vendor master approach?

In the classic ECC approach, vendor master data is commonly maintained across general, company-code, and purchasing-organization segments. In S/4HANA, Business Partner is the leading maintenance approach, with roles exposing the relevant supplier data.

BP role

Relevant business data

FLVN00, Supplier Financial Accounting

Company-code accounting data, including reconciliation-account and payment-related settings

FLVN01, Supplier

Purchasing-organization data, including purchasing conditions and partner functions

Shared identity data belongs to the Business Partner. Customer/vendor integration synchronizes the linked vendor records required by accounting and logistics; those records do not disappear. A supplier may exist generally but still lack the purchasing or accounting extension required for a particular transaction. Having a BP number alone is therefore insufficient proof of purchasing readiness.

9. What information does a purchasing info record hold?

A purchasing info record stores purchasing information for a supplier and material, or a relevant material group where supported. It connects supplier-specific commercial and delivery data with the purchasing process.

Typical contents include supplier material references, order unit, planned delivery time, purchasing tolerances, texts, and prices or conditions. Data has a general segment and a purchasing-organization segment, which can also be plant-specific. Separate info categories support processes such as standard purchasing, subcontracting, consignment, and pipeline procurement.

For example, supplier A may deliver the same component in 10 days at USD 8 per piece, while supplier B offers a different lead time and price scale. The info records preserve these differences. They support proposals and pricing; they are not purchase orders and do not themselves create an obligation to buy.

10. How do a source list and a quota arrangement solve different sourcing problems?

A source list controls eligible sources for a material and plant over specified validity periods. Entries can identify suppliers or outline-agreement items and carry controls such as a source block, fixed-source indicator, or MRP relevance.

A quota arrangement distributes requirements among sources over a period according to quotas and the quantities already allocated. It addresses allocation rather than simply maintaining an approved supplier list.

Suppose suppliers A and B are eligible and have quotas of 3 and 2. That expresses a 60:40 allocation objective over the relevant requirements, not an instruction to split every 100-piece PO into 60 and 40. An individual unsplit requirement can go entirely to one source; splitting depends on the planning process and settings. Source-determination behavior also differs between manual purchasing and MRP.

11. What is the difference between a purchase requisition and a purchase order?

A purchase requisition (PR) is an internal request to procure a quantity of material or a service by a required date. It may come from a requester, MRP, or another business process and may still need source assignment and approval.

A purchase order (PO) is the purchasing document used to order from a supplier or supplying plant, with quantities, prices, delivery details, and relevant commercial terms. It provides the reference for subsequent receipt and invoice processing.

For example, a maintenance team requests 12 filters in a PR; Purchasing selects a supplier and orders them in a PO. A PO can also be created without a PR when the process permits. Neither document by itself posts an FI journal entry; commitment updates are a separate matter.

12. When would a buyer use an RFQ and supplier quotation before creating a purchase order?

An RFQ is useful when the buyer needs comparable supplier offers before choosing a source, particularly for a new requirement, an expired agreement, or a competitive purchase. It describes what is required and invites quotations; the supplier quotation records the offered terms for evaluation.

Comparison should use a consistent basis: specification, quantity, currency, price unit, delivery date, freight, and payment terms. In an illustrative tax-exclusive comparison for 100 pieces, supplier A quotes USD 10 per piece plus USD 100 freight, totaling USD 1,100; supplier B quotes USD 10.50 per piece with freight included, totaling USD 1,050. Delivery capability may still change the decision.

The selected quotation can support PO creation. RFQs are not mandatory for every purchase, particularly where a valid source and agreed terms already exist.

13. How do purchasing document type and item category affect a purchase order?

The document type controls the purchasing document as a whole. Depending on its configuration, it determines number ranges, field-selection behavior, permitted item categories, and process-specific settings. Standard document types such as NB provide a starting point, but customer-defined types can differ.

The item category describes the procurement process for an individual line, such as standard procurement, subcontracting, consignment, or stock transfer. It influences what data is required and which follow-on activities are expected or permitted.

For example, a standard item buys a material from a supplier, while a subcontracting item also requires components to be provided. A document can contain different permitted item categories. The account assignment category is a separate control: it identifies the cost or asset object to be charged rather than replacing the procurement-process classification.

14. What does an account assignment category specify in a purchasing document?

The account assignment category specifies the kind of object to which procurement costs are assigned and helps determine the required accounting fields and follow-on behavior. Common standard categories include K for a cost center, A for an asset, F for an order, and P for a project/WBS element.

For example, an illustrative PO item for USD 600 of office supplies, excluding tax, may use category K with the relevant expense G/L account and cost center ADMIN. An equipment purchase capitalized to an asset requires a different assignment and accounting treatment.

The category is not itself a G/L account or valuation class. It controls the assignment framework; the actual account and object must also be valid. Ordinary procurement into valuated warehouse stock generally does not require a consumption account assignment.

15. How does procurement for stock differ from procurement for direct consumption?

Stock procurement receives a material into inventory for later use. For valuated stock, the receipt increases inventory quantity and value; consumption is recorded when stock is subsequently issued.

Direct-consumption procurement identifies the receiving cost object in the PO. The purchase is charged to that object rather than capitalized as ordinary warehouse inventory. A material master is not always required, and the same stock-managed material can also be purchased directly for consumption.

Assume ten maintenance items at USD 20 each, excluding tax and freight. A valuated stock receipt initially adds USD 200 to inventory. A valuated cost-center receipt instead charges USD 200 to the designated consumption account and cost center. If the account-assigned item uses a nonvaluated GR, the receipt records the logistics event while the expense is recognized at invoice posting.

16. What belongs at purchase order header, item, and delivery schedule-line level?

A PO has several levels because some data applies to the whole order while other data applies only to a material or delivery date.

Level

Typical content

Header

Supplier, company code, purchasing organization, purchasing group, document currency, and overall commercial terms

Item

Material or service description, plant, total quantity, price, item category, account assignment, and receipt/invoice controls

Schedule line

A delivery date and the quantity due on that date

For example, item 10 may order 100 pieces at USD 12 per piece, excluding tax. Its schedule can require 40 pieces on November 5 and 60 on November 19. Those are two scheduled deliveries of the same item, not two suppliers or two independent prices. Header defaults may have item-level variations where supported.

17. How does a purchasing contract differ from a scheduling agreement?

Both are outline purchasing agreements, but they communicate delivery requirements differently.

A contract establishes terms for a validity period and a target quantity or value. Individual purchase orders referencing it, called contract release orders, specify what is needed and when.

A scheduling agreement carries delivery schedule lines containing dates and quantities directly against the agreement item. This suits repeated deliveries, and eligible schedule lines can be generated by MRP. Supplier communication may use scheduling-agreement releases, depending on the agreement type and configuration.

For example, a 12-month contract for up to 5,000 bearings can support separate POs as needs arise. A scheduling agreement can instead organize weekly bearing deliveries on one continuing item. “Release” in an outline-agreement process should not be confused with the internal approval of a purchasing document.

18. What happens when a goods receipt is posted against a stock purchase order?

Posting a goods receipt against a stock PO records the received quantity with reference to the ordered item. The system creates a material document, updates the relevant inventory balance, and adds the receipt to PO history. The selected stock type determines whether the receipt is immediately available for normal use.

For a valuated receipt, an accounting document is also created. Assuming a receipt of 20 pieces at USD 15 per piece, no tax, freight, or price difference, inventory is debited USD 300 and GR/IR is credited USD 300. No supplier payable is created at this step.

This illustrates an ordinary stock receipt, not every receipt process. Nonvaluated materials, consignment, and nonvaluated GR blocked stock have different financial effects. A material document therefore does not automatically imply an FI posting.

19. How do goods receipt, goods issue, and transfer posting differ?

A goods receipt brings material into a relevant stock balance, for example a supplier delivery or production receipt. A goods issue reduces stock for a purpose such as cost-center consumption, production, scrapping, or customer delivery.

A transfer posting changes the stock's classification or assignment, such as quality-inspection stock becoming unrestricted-use stock. A physical stock transfer moves material between storage locations or plants. Some transfer postings involve physical movement; others are status changes only.

For example, releasing 15 pieces from quality inspection changes their usability without adding 15 pieces to total inventory. Moving those pieces from storage location A to B also preserves the plant's total quantity. Financial effects depend on valuation relevance, ownership, and organizational boundaries, rather than on whether somebody physically moved a pallet.

20. What do movement types control, and what are common examples such as 101, 102, 201, 261, 311, and 551?

A movement type is a three-digit control key for a goods movement. Together with other settings, it controls quantity updates, value/account determination behavior, required entry fields, and follow-on processing.

Standard movement type

Common use

101

Receipt against a purchase or production order

102

Reversal of a 101 receipt

201

Goods issue to a cost center

261

Goods issue to an order, commonly production

311

One-step storage-location transfer within a plant

551

Scrapping from unrestricted-use stock

These codes identify business events, not a universal debit/credit formula. For example, 311 normally changes storage-location quantities without changing inventory value, whereas 201 for valuated own stock records consumption. Special-stock indicators and material valuation settings must be considered alongside the movement type.

21. How do unrestricted-use stock, quality inspection stock, blocked stock, and GR blocked stock differ?

Stock type describes usability, while receipt procedure can also affect valuation:

Stock category

Meaning

Unrestricted-use

Normally usable for regular withdrawals

Quality inspection

Awaiting inspection or release; normal use is restricted

Blocked

Held from normal use, for example because of damage

Nonvaluated GR blocked stock

A conditional receipt tracked against the PO before acceptance into valuated warehouse stock

Quality-inspection and blocked stock can both be valuated. A 101 receipt into blocked stock is therefore not financially equivalent to a 103 receipt into nonvaluated GR blocked stock. In the 103/105 process, valuation normally occurs on release with 105. SAP also supports a distinct valuated GR blocked-stock process using 107/109. “Blocked” alone does not establish whether an inventory value or accounting posting exists.

22. What is special stock, and why must ownership and account assignment be considered separately?

Special stock separates quantities that require additional identification beyond ordinary own stock, such as a supplier, sales order, or project. It is important to distinguish three questions: who owns the goods, where they are held, and what requirement or account assignment they serve.

For example, supplier consignment stock K is physically in the buyer's warehouse but still belongs to the supplier. Stock provided to a subcontractor O is physically with the supplier but generally remains the company's own valuated material. Sales-order and project stocks instead identify stock dedicated to particular business requirements; their valuation treatment depends on the configured scenario.

Consequently, neither physical location nor the label “special stock” is sufficient to decide ownership or valuation. The special-stock category and its associated business reference must be examined.

23. What is a reservation, and does creating one physically move or deduct stock?

A reservation records a planned goods movement, commonly a future issue for an order or cost center. It identifies material, quantity, requirement date, movement purpose, and relevant organizational/account-assignment data. It may be entered manually or generated by another process, such as an order's component requirements.

Creating the reservation does not physically move material, post a goods issue, or reduce the on-hand quantity. It can affect requirements and availability calculations according to the planning and checking settings.

For example, assume 100 pieces are on hand and a reservation requests 30. On-hand stock remains 100 until a movement is posted; a simplified availability view considering that reservation alone would show 70 uncommitted pieces. A later 30-piece goods issue reduces on-hand stock to 70 and updates the reservation's withdrawal status.

24. How do valuation area and valuation class differ?

A valuation area is the organizational scope within which material stock is valued. Plant-level valuation allows the same material to carry different valuation data in different plants. Classic and applicable on-premise/Private Edition configuration also distinguishes company-code-level valuation; the implemented product scope must be checked rather than treating the level as a per-PO choice.

A valuation class groups materials with similar account-determination requirements. It is maintained in material accounting data and works with the chart of accounts, transaction keys, and other configuration to determine the relevant G/L accounts.

For example, plants A and B may be separate valuation areas, while materials in both use the same raw-material valuation class. The area answers “where is this stock valued?”; the class helps answer “which account grouping applies?”

25. How do standard price and moving average price differ in material valuation?

With standard price, S, inventory is valued at a maintained standard price. Purchase-price variances normally go to a price-difference account rather than changing that standard during the transaction. With moving average price, V, receipts and eligible invoice differences update inventory value, and the average reflects total stock value divided by stock quantity.

Illustration: opening stock is 100 pieces worth USD 1,000; receive another 100 pieces at USD 12 per piece, with price unit 1 piece, no tax/freight, and no intervening movements.

  • At a USD 10 standard price, stock becomes 200 pieces worth USD 2,000; the USD 200 receipt variance is a price difference.

  • With moving average price, stock becomes 200 pieces worth USD 2,200, giving USD 11 per piece.

Later invoice differences under moving average price depend on available stock coverage; they do not always fully revalue remaining inventory.

26. What are the basic accounting entries for a valuated stock receipt and a matching supplier invoice?

Assume an ordinary valuated stock PO for 10 pieces at USD 50 per piece, price unit 1 piece. The goods receipt occurs before the matching invoice. Ignore tax, freight, exchange differences, and discounts, and assume the material valuation produces no price difference.

Event

Debit

Credit

Goods receipt, USD 500

Inventory 500

GR/IR clearing 500

Supplier invoice, USD 500

GR/IR clearing 500

Supplier payable 500

The receipt increases the inventory asset before the invoice arrives. GR/IR bridges the timing gap; the matching invoice clears that receipt-related balance and establishes the payable in the supplier subledger, reflected in the reconciliation account.

Creating the PO itself does not post this journal. Payment is another event, normally debiting the supplier payable and crediting the relevant bank or bank-clearing account.

27. What does Logistics Invoice Verification check, and how does it differ from paying a supplier?

Logistics Invoice Verification checks and records a supplier invoice in the procurement context. For a PO-based invoice, it uses order and, where relevant, receipt information to compare invoiced quantities, prices, and amounts. It also handles tax data and configured tolerances. Posting creates the invoice document and its accounting effects, including the supplier liability.

Paying the supplier is a separate Accounts Payable/Finance process. Payment depends on factors such as due date, payment terms, payment method, and applicable blocks.

For example, an invoice for 100 pieces can be posted even though a quantity variance causes a payment block. The payable exists, but payment must await resolution and release of the block. Therefore, “invoice posted,” “invoice released for payment,” and “supplier paid” are different statuses, not interchangeable descriptions.

28. What is goods-receipt-based invoice verification?

Goods-receipt-based invoice verification matches invoice items to individual goods-receipt items rather than only aggregating against a PO item. The PO item's GR-based invoice-verification indicator determines this behavior, so a relevant receipt must exist for the matching process.

Suppose a PO for 100 pieces has receipts of 40 and 60. An invoice covering the first delivery can be assigned to the 40-piece receipt; PO history preserves that relationship. Referencing the PO can propose multiple receipt-related invoice items when several deliveries exist.

This improves traceability for partial deliveries and delivery-note-based billing. It does not mean that every SAP invoice must follow a GR, or that a variance becomes impossible. Quantity/price checks and configured tolerances still apply, and reversal handling must respect the receipt-to-invoice linkage.

29. Why are delivery and invoice tolerances used instead of requiring every quantity and price to match exactly?

Tolerances allow agreed operational variation without sending every rounding difference, packaging variation, or small discrepancy into an exception process. They also establish a boundary beyond which the business must investigate.

Delivery tolerances govern receipt quantities relative to the PO. If 100 pieces are ordered with a 5% overdelivery tolerance, a cumulative receipt of 104 is within that illustrative quantity limit; 106 exceeds it unless another applicable setting permits it. The actual delivered quantity must still be recorded accurately.

Invoice tolerances address differences such as price or quantity variances. Their consequences differ from delivery controls: exceeding a relevant upper invoice tolerance may still allow posting while blocking the invoice for payment. Other checks can prevent posting. Tolerance settings therefore require both a business limit and an understood system response; they are not blanket permission to ignore discrepancies.

30. What are the main steps in a physical inventory process?

Physical inventory reconciles recorded stock with counted stock through a controlled document process:

  1. Define the count scope and create physical inventory documents for the relevant stock-management units.

  2. Establish the movement cutoff or appropriate posting controls so that book and physical quantities can be compared consistently.

  3. Count the stock and enter the results, explicitly recording a zero count where appropriate.

  4. Review differences, investigate unusual results, and request recounts when necessary.

  5. Post approved differences, updating stock quantities and, for valuated differences, accounting values.

For example, assume the valid book quantity is 100 pieces, the confirmed count is 97, and the applicable valuation is USD 8 per piece. Posting the three-piece shortage reduces stock by three and inventory value by USD 24. Merely entering the count does not itself make that adjustment.

31. How does a batch differ from a serial number?

A batch identifies a quantity of a material sharing relevant characteristics, such as production lot, supplier lot, or expiry information. A serial number identifies an individual physical unit of a material.

For example, 500 containers of the same product may belong to batch B-240. Ten separately traceable pumps can each have a different serial number even though they share one material number. Where the process supports and requires both controls, serialized units can also belong to a batch.

Batch management supports lot-level traceability and selection; serialization supports unit-specific movement and lifecycle history. Neither should be treated as a substitute for the material number. Required entries during goods movements depend on the material's batch-management and serial-number-profile settings, together with the applicable process configuration.

32. What does MRP do for externally procured materials?

MRP evaluates requirements against relevant stock and scheduled receipts, identifies shortages, determines procurement quantities, and schedules replenishment. For externally procured materials, the result is a procurement proposal rather than a supplier payment or, ordinarily, a finished PO.

A simple illustration assumes demand of 120 pieces, usable stock of 40, and a timely firm receipt of 30, with no safety stock or lot-size rounding. The uncovered requirement is 50 pieces. Real planning also considers dates, lot-sizing rules, lead times, and source data.

The generated element depends on the planning method and configuration: purchase requisitions, or delivery schedule lines for a suitable scheduling agreement, are possible; classic MRP can also create externally procured planned orders for later conversion. MRP Live behavior and restrictions must be evaluated for the actual release.

33. How do procurement type and special procurement influence a material's replenishment?

Procurement type establishes whether a material is procured externally, produced in-house, or can use both methods for the relevant planning context. Common material-master values are F for external procurement, E for in-house production, and X for both.

Special procurement refines that route. An externally procured material may require subcontracting, consignment, or replenishment from another plant rather than an ordinary supplier purchase. The key's detailed meaning comes from configuration; a key number should not be assumed to mean the same thing in every customer system.

For example, a shortage of 80 pieces at plant B could create a stock-transfer requisition requesting supply from plant A instead of a normal supplier requisition. Source selection and usable master data must still support the chosen route.

34. How does subcontracting procurement differ from a normal purchase order?

Subcontracting orders a finished or processed material from a supplier while providing some or all of the components that the supplier needs. The PO item uses the subcontracting process and includes a component requirement, which may be derived from a bill of material or maintained as appropriate.

The provided components are tracked as supplier-related special stock and normally remain company-owned and valuated while held by the subcontractor. When the finished material is received, the receipt is accompanied by component-consumption postings. The supplier's commercial charge represents the subcontracting work rather than a purchase of those already-owned components.

For example, an illustrative order for 10 assemblies requiring two supplied housings each needs 20 housings available to the subcontractor. Simply issuing those housings to an ordinary expense account would lose the intended special-stock and consumption trail.

35. When does supplier consignment create an ownership change and a liability?

In supplier consignment, delivery into the buyer's consignment stock does not itself transfer ownership or create the ordinary supplier payable. The supplier still owns that stock, and the receipt is nonvaluated for the buyer.

The relevant change occurs when stock is withdrawn for consumption or transferred from supplier consignment into the buyer's own stock. That event creates a consignment liability; the withdrawal is valued using the applicable consignment info-record price. Settlement subsequently clears the accumulated consignment liability into supplier accounting rather than processing an ordinary invoice against the consignment PO receipt.

For example, assume 100 pieces are delivered and 25 are consumed at USD 4 per piece, with price unit 1 piece and no tax. The withdrawal creates USD 100 of liability; the remaining 75 pieces still belong to the supplier.

36. What is a stock transport order, and why use one instead of a simple transfer posting?

A stock transport order, or STO, is a purchasing document used to plan and control supply from one plant to another. It records the material, receiving plant, supplying plant, quantity, and required delivery information, then supports monitoring of issue and receipt.

A simple transfer posting can record a stock movement without that purchasing-document planning layer. An STO is useful when the receiving plant needs an explicit replenishment request, delivery-date visibility, document history, or a shipping/delivery process. Depending on configuration, it can also support stock-in-transit tracking and intercompany processing.

For example, plant B can request 200 pieces from plant A for next week rather than merely record a transfer after it happens. Not every STO uses outbound delivery or billing: the chosen variant and company-code relationship determine the additional documents and accounting treatment.

37. What is a service entry sheet, and why is accepting a service different from receiving physical stock?

A service entry sheet records the services actually performed against a purchase order, such as labor hours or completed activities. Acceptance confirms that the business has received the agreed service; there is no physical warehouse quantity to put away.

Assume a maintenance PO authorizes 10 hours at USD 80 per hour, price unit 1 hour, excluding tax. If eight hours are completed and accepted, the entry sheet documents USD 640 of performed work rather than an increase of eight stock units.

In the referenced S/4HANA lean-services process, saving an entry sheet alone does not post to Finance; approval triggers the relevant receipt/accounting effects. Classic external services and lean services use different document and application models. The implemented service process must therefore be identified before specifying item categories, acceptance steps, or invoice prerequisites.

38. How do a classic release strategy and S/4HANA flexible workflow differ?

A classic release strategy uses configured release criteria and approval controls. In the classification-based approach, characteristics determine the applicable strategy, while release codes, prerequisites, and indicators govern approvals and document status.

Flexible workflow uses scenario-specific workflow configuration, commonly managed through Fiori apps. Start conditions select a workflow, step conditions control approval steps, and recipient rules identify approvers. It supports business-facing approval maintenance and inbox processing.

Both can implement a policy such as requiring an additional approval above a value threshold, but their configuration and troubleshooting paths differ. In supported S/4HANA on-premise/Private Edition scenarios, the selected framework can depend on document type. Public Edition has its own supported workflow configuration approach. “S/4HANA” alone does not prove that an existing purchasing document uses flexible workflow rather than a classic strategy.

39. What can purchase order history tell you about delivery and invoice status?

PO history shows posted follow-on activity for an item, including relevant goods receipts, invoices, reversals, and returns, with quantities, values, dates, and document references. It helps distinguish “ordered,” “received,” and “invoiced” rather than relying on a single overall status.

For example, assume an item orders 100 pieces, has a 60-piece receipt, a 10-piece receipt reversal, and an invoice for 50 pieces. Net received quantity is 50, matching the invoice quantity. That does not mean the other 50 pieces were delivered or that the invoice has been paid.

Delivery-completed settings and other controls affect open-quantity interpretation, while payment and clearing are checked in supplier accounting. With GR-based invoice verification, history also supports tracing which receipt an invoice relates to. Always include reversal signs and the correct unit of measure.

40. Where does Inventory Management stop and warehouse management begin?

Inventory Management maintains stock quantities by organizational and stock dimensions such as plant, storage location, stock type, batch, and special stock, together with valuation-relevant goods movements. It answers questions such as “How many unrestricted-use pieces do we hold in this storage location?”

Warehouse management adds the detailed physical execution layer: storage bins, putaway, picking, internal movements, and the tasks or confirmations needed to perform them. In EWM, warehouse structures and execution documents provide that operational detail and integrate with the inventory perspective.

For example, IM may show 500 pieces in one storage location while EWM distributes them across bins A-01, A-02, and B-04. Posting an IM receipt does not by itself prove that putaway is finished. The particular WM/EWM product and integration model depend on the landscape, not on the MM label alone.

SAP MM Interview Questions and Answers for Intermediate

The intermediate answers trace the relevant documents and settings before proposing a correction. They make quantity, value, ownership, and approval assumptions explicit and distinguish a technical posting from a complete, controlled business outcome.

41. How would you configure purchasing organization assignments for one company code with several plants?

For a centralized purchasing team serving several plants in one company code, use a cross-plant purchasing organization. Assign the plants to their company code, assign the purchasing organization to that company code, and explicitly assign every plant it serves to the purchasing organization. The company-code assignment alone does not authorize purchasing for all its plants.

For example, company code US10 could contain plants P100, P200, and P300, with purchasing organization USPO assigned to all three. Buyers can share negotiated conditions while delivery, inventory, and valuation remain associated with the relevant plant. Purchasing groups represent buyer responsibility; they do not replace these enterprise-structure assignments.

Separate plant-specific purchasing organizations are another valid design when local procurement responsibility genuinely differs. Extend supplier purchasing data and applicable purchasing conditions to the chosen organizations rather than assuming organizational assignments automatically create master data.

42. A material exists but cannot be purchased for a new plant. What master-data extensions would you check?

An existing material number proves only that some master-data segments exist. Inspect the exact error and the target plant before creating another material.

  • Check that the Purchasing view exists for the new plant and that required plant-specific purchasing fields are maintained.

  • For valuated stock procurement, check accounting data for the relevant valuation area, including valuation class, price control, and valuation price. With plant-level valuation, an extension in the old plant is insufficient.

  • If MRP should create procurement proposals, inspect MRP views, procurement type, planning parameters, and any relevant MRP-area data.

  • Check plant-specific and cross-plant material status, validity dates, and deletion flags for restrictions on purchasing.

Storage-location and warehouse data may also be needed for the later receipt process; their absence is not automatically the cause of a PO-creation error. Material type controls which views and quantity/value updates are permitted. Extend the existing material consistently, rather than changing its type merely to bypass validation.

43. A supplier is available in one purchasing organization but not another. What Business Partner data and blocks would you inspect?

Check whether the existing Business Partner has supplier purchasing data for the target purchasing organization, not merely a general BP record or data for another organization. In the standard role model, FLVN01 supports purchasing data; FLVN00 supports supplier accounting data at company-code level. Company-code accounting data does not substitute for purchasing-organization extension.

Inspect order currency, purchasing payment terms, partner functions, and other mandatory purchasing fields. Then distinguish restrictions: a central purchasing block can affect all purchasing organizations, while an organization-level purchasing block affects the selected organization. Check deletion indicators and the actual application message as well.

A company-code posting block or payment block addresses a different part of the process; it is not interchangeable with a purchasing block. If purchasing data is complete and unblocked, continue with the user's authorization and source-of-supply restrictions. Do not create a duplicate supplier just because one organizational segment is missing.

44. Why can a purchase order propose a different price from the one a buyer expects from the info record?

The PO price is the result of condition determination in the document's context, not simply the number last seen on an info-record screen. Compare the supplier, material, purchasing organization, plant, info category, currency, order unit, order price unit, price unit, quantity scale, and relevant pricing date.

A plant-specific record can differ from an organization-level record. A referenced contract, copied PO conditions, a manually entered condition, or additional discounts and surcharges can also explain the result. Inspect the PO's condition details and pricing analysis to identify the actual condition record and access used.

For example, an expected USD 900 per 100 EA is USD 9 per EA, not USD 900 per EA. An order of 500 EA may qualify for a different scale than 50 EA. Existing PO conditions are document-specific: changing an info record does not automatically reprice every saved PO.

45. How is a quota rating calculated, and which supplier receives the next unsplit requirement?

The quota rating is (quota-allocated quantity + quota base quantity) ÷ quota. For an eligible, unsplit requirement, the source with the lowest rating receives the whole requirement; the quota is not a percentage split applied to each individual requisition.

Assume two valid suppliers, no other allocation constraints, and all quantities in EA:

Supplier

Quota

Allocated quantity

Base quantity

Rating

A

3

900

0

300

B

2

400

100

250

Supplier B receives the next 80 EA. If that requisition updates quota allocation, B's rating becomes (480 + 100) ÷ 2 = 290. B would still have the lower rating for the next otherwise eligible requirement. The base quantity adjusts the calculation without representing a physical receipt. Validity, quota usage, source eligibility, and planning-specific splitting settings must also be satisfied.

46. Why can automatic source determination produce different results in MRP and in a manually created requisition?

Source determination is process-dependent. MRP runs in the background and applies its sourcing priorities and MRP-relevance settings; interactive requisition processing can present or assign sources differently. A source list's fixed-source indicator and its MRP indicator serve different purposes.

Dates can explain an apparent contradiction. Manual requisition source determination checks source-list validity against the delivery date, whereas MRP uses the requirements date. A supplier valid next month may therefore qualify for a manually entered future-delivery requisition but not for a current reorder-point requirement.

Compare the same material, plant, date, quota validity and usage, source-list MRP relevance, outline agreement, and applicable info-record sourcing settings. In supported S/4HANA planning logic, outline agreements and automatically sourceable info records can also matter; “MRP always requires a source list” is too broad. The expected outcome must be tied to the target release and planning process, not to a universal sourcing sequence.

47. What prerequisites must be satisfied before purchase requisitions can be converted automatically into purchase orders?

For standard material-based automatic conversion, the requisition must have a valid, usable source assigned and enough data to create a complete PO without interactive correction. The Automatic Purchase Order indicators must be enabled in the material's purchasing data and the supplier's purchasing data for the relevant organizational levels.

The requisition must also be eligible for conversion: required approval is complete, an open quantity remains, and deletion or blocking status does not prevent processing. Conditions, organizational assignments, account assignment where required, and mandatory fields must be resolvable. For example, an ERS-enabled item needing a tax code cannot rely on a buyer filling it in during a background job.

The job's selection and grouping settings determine which eligible requisitions are processed together. A successful job status alone is insufficient: review the item-level results and created PO references. Automatic conversion neither substitutes for source assignment nor guarantees that the resulting PO needs no approval.

48. When should recurring deliveries use a scheduling agreement rather than repeated releases against a contract?

A scheduling agreement fits repeated deliveries of the same material when the supplier should receive a changing time-phased delivery schedule rather than a new PO for each call-off. Quantities and dates are maintained as schedule lines against the agreement, and MRP can generate schedule lines when the necessary sourcing and planning settings are in place.

For example, a packaging supplier delivering 2,000 EA every Monday can work from one agreement with dated requirements. A process using release documentation can distinguish forecast and just-in-time releases, where supported and configured.

A contract is preferable when the business primarily needs a negotiated quantity or value ceiling, but individual purchases require separate PO releases, delivery instructions, or account assignments. A USD 250,000 annual maintenance-parts contract with irregular call-offs is a different need from a repetitive delivery program. The decision turns on scheduling and communication requirements, not merely annual purchasing volume.

49. How are characteristics, class type 032, release codes, and release indicators used in a classic release strategy?

In a classic release procedure with classification, characteristics define the document attributes used to select a strategy—for example, purchasing organization, document type, and total value. They reference the relevant communication structure: CEKKO for external purchasing documents or CEBAN for requisitions. A class of type 032 groups the characteristics, and the release group links that class to the release object.

Release codes identify approval points, not necessarily individual named users. The strategy specifies which codes participate and their prerequisites, such as manager approval before finance approval. Classification values determine which document enters that strategy.

Release indicators represent the resulting processing status, including whether follow-on processing or output is permitted and how changes are handled. For example, a USD 60,000 PO can require codes M1 then F1 before output is allowed. Authorization to execute a release code is a separate control. This classification design is distinct from flexible workflow configuration.

50. How do workflow order, start conditions, step conditions, and recipients interact in flexible purchase order approval?

Flexible workflow separates which workflow applies from which steps within it apply. Active workflows are checked in their configured order, and the first matching set of start conditions selects the workflow. Step conditions then determine which approval steps apply to that document; recipient rules identify the approvers for those steps.

For example, a workflow for POs above USD 100,000 should precede a broad workflow for all POs. Within it, purchasing approval might always apply, with an additional finance step for specified account assignments. Recipient determination must resolve valid users or responsibility roles; configuring an amount threshold alone does not identify an approver.

Check fallback behavior and cases where every step condition is false. Depending on the configured scenario, such gaps can result in automatic release rather than an approval error. Available conditions, recipient options, and configuration tools differ by edition and release; the actual active workflow definition is the evidence.

51. How can changing a purchase order after approval trigger a new approval cycle?

Approval is tied to the document and the configured change rules, not an irrevocable endorsement of every later version.

With a classic release strategy, the release indicator's changeability settings and any permitted value-change tolerance determine whether a change is allowed and whether existing release must be reset. A changed characteristic can also require a different strategy. An increase from USD 40,000 to USD 55,000, for example, might cross an approval threshold, but the precise outcome depends on configuration.

With flexible workflow, restart-relevant changes can trigger a new workflow instance and reassessment of the applicable workflow. SAP provides restart configuration and, in supported scenarios, custom logic for critical changes. Do not assume every text edit restarts approval or that the same fields behave identically in every edition.

A sound check compares old and new document values, approval history, configured restart conditions, and the resulting status before supplier output is sent.

52. Why might the same field be mandatory in one purchasing document but optional or hidden in another?

In classic purchasing-document processing, field status results from a combination of field-selection keys, not just the document type. Influences include transaction/activity, document type, item category, function authorization, and release status. Account assignment can introduce additional requirements for its relevant fields.

The standard linkage distinguishes hidden, display-only, required, and optional. Hidden overrides the other statuses; display-only takes precedence over required or optional; required takes precedence over optional. Consequently, making a field optional under the document type will not override another active key that makes it mandatory.

For example, the material group can be optional in the transaction and document-type settings but required by the item category, making entry mandatory overall. Compare the same field under the actual document, item, and processing mode. Fiori app behavior or UI adaptation is another layer and should not be confused with the backend field-selection rules or with authorization to perform the business action.

53. How do condition types, access logic, scales, and the calculation schema determine a purchase order price?

A condition type represents a pricing element such as gross price, discount, surcharge, or freight. Where automatic determination is configured, its access sequence controls the search through condition tables for a matching record. Organizational keys, supplier/material combinations, validity dates, and other access fields determine which record is found. Scales select the applicable rate for the relevant quantity or value.

The calculation schema specifies the included condition types, their sequence, calculation bases, subtotals, and settings such as statistical treatment. It therefore matters whether a discount applies to gross price or to an already adjusted subtotal.

Assume 200 EA at USD 12 per EA, a 5% discount on gross value, and USD 80 freight, with no tax or other conditions. Gross value is USD 2,400; discount is USD 120; goods net value is USD 2,280. Including the freight produces USD 2,360 for this illustration. Freight's accounting treatment depends on its condition configuration, not merely its position on screen.

54. How do BSX, WRX, PRD, and GBB participate in automatic account determination?

These transaction keys identify posting purposes; they are not themselves G/L account numbers.

Key

Typical purpose

BSX

Inventory stock posting

WRX

GR/IR clearing

PRD

Price differences

GBB

Offsetting entry for inventory postings such as consumption or scrapping

The business transaction and movement-type/value-string logic determine which keys participate. Account determination then uses the applicable chart of accounts and configured rules, potentially including valuation grouping code, material valuation class, and account modifier.

For example, a valuated PO receipt commonly uses BSX and WRX, with PRD if standard-price valuation differs from the receipt value. A goods issue to a cost center commonly credits BSX and debits an expense account through GBB. GBB modifiers distinguish purposes such as ordinary consumption and scrapping. Not every key uses every possible determinant, and a movement type alone is not enough to identify the final account.

55. How can one consumption purchase order item be distributed across multiple cost centers?

Use multiple account assignment on the consumption PO item, with an appropriate category such as K for cost center. Enter separate assignment lines with valid cost centers and G/L/account-assignment data, then choose a quantity-, percentage-, or amount-based distribution supported by the process.

Assume a PO for 100 EA at USD 20 per EA, no tax or delivery costs, allocated 60% to C100 and 40% to C200. The full USD 2,000 becomes USD 1,200 and USD 800 respectively. For a valuated partial receipt of 50 EA, proportional distribution allocates the USD 1,000 as USD 600 and USD 400.

Progressive fill-up is different: it fills the first assignment before moving to the next. The partial-invoice distribution setting also matters for valuated partial receipts. Verify the intended distribution before posting, because follow-on documents restrict changes. Multiple account assignment does not inherently require a nonvaluated receipt.

56. How would you calculate the postings for a standard-price material when PO and invoice prices differ?

Assume standard price USD 10 per EA, a PO for 100 EA at USD 12 per EA, full receipt before invoice, and a later invoice for 100 EA at USD 13 per EA. Price unit is 1 EA; exclude taxes, freight, exchange differences, and period-end actual-costing adjustments.

Event

Debit

Credit

Goods receipt

Inventory USD 1,000; price difference USD 200

GR/IR USD 1,200

Invoice

GR/IR USD 1,200; price difference USD 100

Supplier payable USD 1,300

The receipt values inventory at the standard price, while GR/IR reflects the PO-based receipt value. The additional invoice difference does not increase standard-price inventory; it adds to price differences. GR/IR clears because the received and invoiced quantities match under these assumptions. The total adverse difference is USD 300, and the standard price remains USD 10. Creating the PO itself is not an FI journal posting.

57. How does a receipt and a later invoice difference change moving average price when sufficient stock remains?

Assume an opening stock of 100 EA valued at USD 1,000, moving average price USD 10 per EA, and a receipt of 100 EA at USD 14 per EA. The price unit is 1 EA. Exclude taxes, freight, currency effects, and other movements; all 200 EA remain when the invoice is posted.

The receipt debits inventory and credits GR/IR by USD 1,400. Stock becomes 200 EA worth USD 2,400, so the new moving average price is USD 12 per EA.

If the invoice is 100 EA at USD 15 per EA, debit GR/IR USD 1,400 and inventory USD 100, and credit the supplier USD 1,500. The final stock value is USD 2,500 and the moving average price is USD 12.50 per EA. Invoice verification changes value, not physical quantity. This full capitalization assumes sufficient stock coverage; insufficient coverage can send some or all of the difference to a price-difference account.

58. How do the 103/105 and 107/109 goods receipt processes differ?

The key difference is when valuation occurs, not simply whether the goods are called blocked.

Process

First posting

Release posting

103 → 105

103 records nonvaluated GR blocked quantity; no inventory valuation yet

105 accepts the quantity into stock and performs valuation

107 → 109

107 posts into valuated GR blocked stock; valuation occurs now

109 releases the already-valuated quantity into the receiving stock type

The 107/109 process can support origin acceptance: ownership and acceptance are recorded before physical arrival. If origin acceptance is specified in the PO, the accepted quantity can be proposed for invoice settlement. Posting 107 ad hoc does not imply identical invoice-proposal behavior.

For a simple USD 1,000 receipt with no price differences or taxes, the stock/GR/IR entry occurs at 105 in the first process and at 107 in the second. Ordinary blocked stock received with 101 is a separate concept and can already be valuated.

59. When should you use a receipt reversal, a return delivery, or a returns purchase order?

A receipt reversal corrects an erroneous posting, such as a receipt entered for the wrong quantity or before the goods actually arrived. Reversing a normal 101 receipt uses 102; referencing the original material document preserves the correction trail.

A return delivery records a real return after a genuine receipt, for example 10 defective EA returned from a received batch of 100 EA. The usual standard movement is 122, referenced to the receipt or PO. It is not merely a technical correction of history.

A returns PO provides a purchasing document for a planned commercial return, especially when the return needs its own authorization, quantities, and supplier communication. The standard returns-item flow commonly uses 161, with shipping variants where configured.

Before choosing the route, inspect invoicing, GR-based matching, stock availability, and whether the commercial outcome is replacement or credit. A stock return alone does not automatically resolve the supplier invoice or settle the financial claim.

60. How do partial delivery, underdelivery tolerance, and the delivery completed indicator affect an open purchase order?

A partial receipt normally reduces the open PO quantity by the quantity actually received. Underdelivery tolerance specifies how much short delivery may be accepted; it does not mean that every smaller partial delivery is forbidden.

Assume an order of 100 EA with 5% underdelivery tolerance. After 60 EA are received, another 40 EA are normally expected. If cumulative receipts reach 96 EA, the shortfall is 4%, so the item can qualify for automatic delivery completion where the plant setting permits it.

The Delivery Completed indicator tells planning and follow-on monitoring that no further delivery is expected, making the open quantity zero even if the original ordered quantity was not fully received. It is not an absolute prohibition on further goods receipts: some posting functions still permit them within the relevant controls, while certain apps omit completed items from selection. It also does not mean the supplier invoice is complete or GR/IR has cleared.

61. How can an order-price-unit conversion cause a goods receipt or invoice value discrepancy?

The order unit measures what was ordered; the order price unit measures the quantity to which the price applies. Incorrect conversion or an incorrect actual price-unit quantity can therefore produce a value difference even when the ordered piece count is correct.

Assume 10 coils are ordered at USD 4 per kg, price unit 1 kg, with a provisional conversion of 20 kg per coil. The PO expectation is 200 kg and USD 800. If the delivered 10 coils actually weigh 215 kg and actual weight is the agreed pricing basis, the receipt basis is USD 860. A USD 860 invoice is not necessarily a price increase: the unit rate is unchanged.

Compare quantities in both units at PO, GR, and invoice, along with the conversion and price unit. Invoice verification can detect a differing ratio as an order-price-quantity variance. Check whether the selected receipt app supports entering the actual price-unit quantity; do not assume every app does.

62. How do valuation category and valuation type support split valuation?

The valuation category defines the reason for separating a material's stock valuation, such as procurement origin or quality. Valuation types are the individual categories of stock under that criterion, such as NEW and REFURBISHED. They are not storage locations: both types can exist within the same plant and storage location.

Configure permitted categories and types and their applicability to valuation areas. In the material master, maintain the category in the valuation header and create the relevant valuation-type accounting records. In the standard split-valuation model, the header uses price control V to aggregate partial-stock values; the individual valuation types can use standard or moving average price and may have different valuation classes.

For example, 10 NEW units at USD 100 and 10 REFURBISHED units at USD 60 total USD 1,600 across 20 EA. The header average is USD 80, but that does not make both partial stocks worth USD 80 each. Goods movements must identify the correct valuation type.

63. Which material and purchasing settings control shelf-life checks at goods receipt?

Check the minimum remaining shelf life in the material master or PO item, the total shelf life where maintained, and whether shelf-life checking is active for the plant and movement type. Also inspect whether the configured movement behavior merely requests a date or actually checks it, and how insufficient shelf life is handled by the relevant message settings.

If total shelf life is maintained, the system can calculate expiration from the production date plus total shelf life. Otherwise, the expiration date is entered directly. Date units and rounding settings must be consistent with the business requirement.

For a simple example using calendar days, a receipt requiring at least 90 days of remaining life fails that acceptance criterion if only 75 days remain, even though the product is not yet expired. Batch management supports continued tracking of the expiration date, but it is not universally required merely to perform a shelf-life check at receipt.

64. When can negative stock be permitted, and what reconciliation risks does it create?

Negative stock can support a controlled timing difference when the material physically exists but the goods issue is entered before the corresponding receipt. It is a system-permitted book balance, not proof that material can physically be consumed before it arrives.

The relevant organizational settings and material permission must allow negative stock, and the stock category/process must support it. It should not be enabled broadly merely to suppress an insufficient-stock error.

Assume the system shows 0 EA, 20 EA have physically arrived but are unposted, and 6 EA are issued to production. The book quantity temporarily becomes −6 EA; entering the genuine 20-EA receipt brings it to 14 EA. The risk is that the missing receipt is never posted, is duplicated, or belongs to a different period. Moving-average valuation can also produce price-difference consequences. Reconcile the negative quantities promptly and eliminate them before physical inventory and the balance-sheet key date.

65. How do one-step and two-step transfers between storage locations differ?

For a standard unrestricted-use transfer within one plant, 311 posts removal and placement in one step. One material document records the decrease at the issuing storage location and increase at the receiving location. There is no interval represented as stock in transfer.

In the two-step process, 313 removes the quantity and records it as stock in transfer at the receiving storage location; 315 subsequently places it into unrestricted-use stock. This supports a separate receiving confirmation.

For example, moving 30 EA from A to B with 313 leaves 30 EA awaiting placement. If B confirms only 28 EA using 315, 2 EA remain in transfer for investigation rather than silently becoming available at B. For the same material and valuation type within one plant, these location transfers do not change overall inventory value or generate an FI posting. Stock in transfer here should not be confused with an STO's stock-in-transit process.

66. What changes in a stock transport process when the supplying and receiving plants belong to different company codes?

Different company codes introduce separate legal-accounting books, so the design must establish how the receiving company acquires and values the goods and how the supplying company records the transfer.

In a classic cross-company STO with delivery and billing, the supplying plant uses shipping processing and intercompany billing, while the receiving plant processes its PO receipt and supplier invoice. Supplier/customer relationships, plant assignments, sales-area and shipping data, pricing, account determination, and applicable tax configuration must support that flow. The commercial transfer price need not equal the supplying plant's inventory valuation price.

Not every cross-company stock transfer uses this billed variant. A direct cross-company transfer posting instead uses company-code clearing accounts and separate accounting documents; its timing and valuation should not be generalized to the billed STO. Document type, one- or two-step procedure, and any advanced intercompany functionality determine the actual document chain. Reconcile both companies' documents and the transit quantity, rather than checking only the receiving plant.

67. How are components provided to a subcontractor and consumed when the finished material is received?

A subcontracting PO orders the finished or processed material while identifying components that the company provides to the supplier. Components may be proposed from a BOM or maintained in the item. In the usual one-step provision process, movement 541 transfers components to supplier-specific special stock O. They remain company-owned, valuated stock; provision is not yet component consumption.

Assume an order for 100 assemblies needs 2 component EA per assembly, with no scrap. Providing 200 component EA establishes the subcontractor stock. Receiving 40 assemblies with 101 normally triggers a linked 543 consumption of 80 component EA, leaving 120 EA at the subcontractor if no other movements occurred.

The receipt's material document therefore contains both finished-material receipt and component-consumption items. Verify actual consumption before posting rather than accepting the proposal blindly. Reports received after the finished-material receipt may require a subsequent adjustment. The supplier's processing charge and the supplied component value are distinct elements of the resulting valuation.

68. How are consignment withdrawals valued and settled with the supplier?

Consignment receipt does not create company-owned inventory value or a supplier invoice liability because the supplier still owns the stock. Liability arises when goods are withdrawn for consumption or transferred to the company's own stock. The withdrawal is priced using the applicable consignment info-record conditions on the withdrawal date.

Assume a direct consumption withdrawal of 25 EA at USD 8 per EA, price unit 1 EA, with no tax. It creates USD 200 of consumption expense and USD 200 of consignment liability. A transfer to own stock, such as 411 K, instead capitalizes inventory subject to valuation rules; it is not the same as immediate consumption.

Periodic consignment settlement, classically MRKO, processes unsettled withdrawals and transfers the consignment liability to the supplier account, producing settlement documentation. Payment remains a separate AP process. Reconcile withdrawal quantities, reversals, supplier identity, pricing validity, and settled status; settlement is based on withdrawals, not on invoicing the original consignment PO receipt.

69. How would you choose between a classic blanket order and a lean-service limit item?

Choose according to the required evidence of performance, not merely because both options contain a spending limit.

A classic blanket order, commonly FO with item category B in the classic process, supports repeated low-value expenditure within a validity period and overall limit without goods receipt or service-entry-sheet processing. Invoices reference the order. Expected value and overall limit serve different purposes; an expected value is not automatically the hard spending ceiling.

A lean-service limit item supports unplanned services that must be described and accepted through a service entry sheet. It uses product type group Service and, in the relevant S/4HANA apps, enhanced-limit functionality with expected value, overall limit, performance period, and account assignment.

For example, an incidental invoice-only supplies budget differs from repair work whose hours and activities require acceptance. Item category E alone does not prove that the process is lean services: enhanced limits can also support other limit-item scenarios. Confirm edition, supported app, product type, and receipt/acceptance controls.

70. What should be validated before a lean-service entry sheet is approved?

Approval should establish that the service was actually performed and is correctly represented against the PO. Check the supplier and PO item, service description, quantity and unit, rate or amount, performance dates, account assignment, tax data where required, and supporting evidence such as a signed work report. Compare prior entry sheets to avoid accepting the same work twice.

For unplanned services, verify that an appropriate limit item exists and that cumulative accepted value remains within the authorized overall limit. For example, if a USD 5,000 limit already has USD 3,800 accepted, a new USD 1,500 claim needs resolution before acceptance; the remaining capacity is USD 1,200, assuming no reversals or other entries.

Saving a lean-service entry sheet alone does not post the accounting impact. Successful approval normally creates the associated goods-receipt document and financial updates for the valuated process. Approver authority and evidence matter because approval is acceptance, not just clerical completion.

71. How are price and quantity variances handled when an invoice is posted, blocked, and later released?

Invoice verification compares the invoiced price and quantity with the relevant PO and receipt history and applies company-code tolerance settings. Exceeding an applicable upper blocking tolerance can allow the invoice to post while blocking the entire invoice for payment. A posted, blocked invoice has accounting consequences; it is not the same as a parked document. Other validation errors or tolerance types can prevent posting, so “every variance simply blocks payment” is also incorrect.

Resolve the cause rather than only removing the block. A missing receipt, incorrect invoice quantity, agreed price change, or supplier overcharge requires different evidence and correction. A price difference posts according to valuation/account-assignment rules even when payment is blocked.

Automatic release rechecks eligible blocking reasons and releases the invoice when those reasons no longer apply. Manual header payment blocks require separate handling. An authorized manual release may accept an exception, but releasing a block does not itself correct the original invoice amounts or pay the supplier.

72. How does a subsequent debit or credit differ from an invoice or credit memo that changes the invoiced quantity?

An ordinary invoice increases invoiced quantity and value; an ordinary credit memo generally reduces them. A subsequent debit or credit adjusts the value of quantities already invoiced without changing the cumulative invoiced quantity. The reference quantity identifies which invoiced quantity is being repriced, not an additional delivery.

Assume 100 EA were received and invoiced at USD 10 per EA, price unit 1 EA, with no tax. A later agreed surcharge of USD 100 is a subsequent debit: the invoiced quantity remains 100 EA and total invoiced value becomes USD 1,100. A quantity-based credit for 10 EA at the original price would instead reduce invoiced quantity to 90 EA and value to USD 900.

Neither invoice adjustment physically moves stock. For already delivered quantities, the offsetting amount goes to inventory, price differences, or consumption according to valuation and account assignment. If the affected invoiced quantity has not yet been received, GR/IR can be involved.

73. How are planned and unplanned delivery costs treated during invoice verification?

Planned delivery costs are represented by appropriate PO conditions before receipt, such as freight charged by a separate carrier. At a valuated receipt they affect inventory valuation or the consumption assignment, with an offset to the configured delivery-cost clearing account. The freight invoice subsequently settles that planned cost. Standard-price differences still follow the material's valuation rules.

Unplanned delivery costs are introduced during invoice verification. Configuration can distribute them across invoice items or post them to a separate G/L account. Distributed amounts follow price-difference treatment: moving-average inventory can absorb them with sufficient stock coverage, while standard-price materials generally use price differences.

For an illustrative first invoice with item values of USD 600 and USD 400 and USD 50 of automatically distributed unplanned freight, proportional allocation is USD 30 and USD 20, excluding tax. A separate-account configuration instead posts the USD 50 there. Also distinguish automatic allocation from manually increasing item values, because the price-check behavior differs.

74. How does evaluated receipt settlement create invoices, and what makes a supplier and PO eligible?

Evaluated receipt settlement means the buyer's system generates invoice documents from accepted receipt data and PO conditions under an agreement with the supplier, rather than waiting for the supplier to send an invoice. It is self-billing, not automatic payment.

Typical prerequisites include:

  • ERS enabled in the supplier's relevant purchasing data and in the PO item.

  • GR-based invoice verification enabled for the item.

  • A valid tax code and appropriate payment terms, including baseline-date determination.

  • A firm price rather than the estimated-price indicator.

  • A qualifying goods receipt referencing the PO and the necessary settlement-output setup.

An info record's No ERS setting can affect the default proposed in the PO, so inspect the saved item rather than relying solely on the supplier flag. For 50 EA received at USD 6 per EA, the goods value to settle is USD 300 before tax and other applicable conditions. Accurate receipt quantities and PO prices remain essential even though no supplier invoice is manually matched.

75. What is the difference between holding, parking, and posting a supplier invoice?

The states distinguish incomplete entry from a posted accounting obligation.

State

Main effect

Hold

Saves work with minimal checks; creates a held MM invoice but no FI transfer or PO-history update

Park

Saves an invoice for completion or review; creates parked FI information and updates PO history, without normal G/L posting

Post

Creates the accounting entries, including the supplier liability and the relevant GR/IR, expense, or valuation entries

“Save as complete” is a further parked status: the document must be postable and passes additional checks, but it is not yet the same as posting. Exact labels and available actions depend on the app.

For example, an invoice lacking an account-assignment clarification can be held or parked while the issue is resolved. By contrast, a posted invoice blocked for payment already affects accounting; the payment block does not turn it back into a parked invoice. Posting and paying are separate events.

76. Why can the GR/IR account retain a balance after an order appears commercially complete?

Commercial closure flags do not themselves match receipts and invoices or erase GR/IR balances. Residuals commonly reflect received-but-uninvoiced quantities, invoiced-but-unreceived quantities, returns, reversals, or documents assigned to the wrong PO item. Planned delivery costs also have their own clearing differences.

Assume 100 EA are received at USD 10 per EA and only 90 EA are invoiced at the same price, with no taxes or other differences. GR credits GR/IR USD 1,000; the invoice debits it USD 900. The remaining USD 100 credit represents 10 EA still unmatched, even if someone marks delivery complete.

Reconcile PO-item quantities and values, including reversals and account-maintenance documents, and confirm whether a further receipt, invoice, or credit is genuinely expected. Correct missing or incorrect business documents first. Only when no further GR or IR is expected should approved GR/IR account maintenance resolve a final difference. A zero overall account balance can still conceal offsetting unresolved PO-item balances.

77. How do reorder-point planning and requirements-based MRP produce different replenishment decisions?

Reorder-point planning triggers replenishment when available stock plus relevant fixed receipts falls below a defined reorder level. The threshold reflects expected consumption during replenishment and the intended protection against uncertainty; the lot-sizing procedure determines how much to propose.

Requirements-based MRP instead time-phases requirements such as sales demand, planned independent requirements, and dependent requirements against available stock and receipts. It can detect a future shortage while today's stock still looks comfortable.

Assume 120 EA on hand, no scheduled receipts, a reorder point of 100 EA, and a requirement of 150 EA next week. A simple reorder-point setup that excludes external requirements does not trigger solely from the current 120 EA. Requirements-based MRP identifies a 30-EA shortage by next week before safety-stock and lot-sizing adjustments. Reorder-point variants can include external requirements, so the MRP type and settings matter. Conventional requirements-based MRP should not be confused with the separate buffered Demand-Driven Replenishment approach.

78. How do lot size, safety stock, and planned delivery time change a procurement proposal?

Safety stock influences the shortage calculation, lot sizing changes the procurement quantity, and lead times determine when the proposal must be acted on. They solve different planning problems.

Assume requirements-based MRP, 60 EA available, 110 EA required on one date, no existing receipts, and 20 EA of safety stock that must be preserved. Net procurement need is 110 + 20 − 60 = 70 EA. Lot-for-lot would propose 70 EA before other restrictions. If a rounding value of 50 EA applies, the proposal rounds to 100 EA; a fixed-lot procedure can produce a different proposal structure.

For scheduling, assume a seven-day working calendar, five calendar days of planned delivery time, two days of GR processing, and one day of purchasing processing. Availability on day 20 requires delivery by day 18, order dispatch by day 13, and purchasing start by day 12. Real factory calendars, source-specific lead times, and planning settings must replace these simplified assumptions.

79. How do a posting block and freezing book inventory affect a physical inventory count?

A posting block prevents goods-movement postings for the affected stock-management units during the count. It is a transaction restriction, not a physical barrier; warehouse staff still need a movement cut-off. In the standard process, entering the count lifts the movement block, while inventory processing remains incomplete until differences are posted.

Freezing book inventory preserves the book quantity used for comparison in the inventory document while ordinary stock movements can continue. It does not freeze the live stock balance.

Assume book quantity is frozen at 100 EA, the physical count is 98 EA, and a later correctly dated receipt adds 10 EA. The count difference remains −2 EA; posting it leaves current stock at 108 EA, assuming no other movements or book-inventory adjustment. Without a clear cut-off, staff might mistakenly count the later receipt or compare against the wrong snapshot. Also inspect backdated movements and the configured book-inventory-adjustment rules, which can legitimately change the comparison quantity.

80. Which supplier-evaluation KPIs would you compare, and what data-quality checks make the comparison meaningful?

Compare delivery timeliness, quantity reliability, price variance, and quality outcomes rather than ranking suppliers by purchase price alone. SAP's operational evaluation can use weighted time, quantity, and price criteria; quality inspection or notification data and questionnaire-based assessments add different evidence where available.

Data quality determines whether the comparison is fair. Use consistent periods, purchasing categories, units, currencies, and supplier identities. Check original versus revised promised dates, partial deliveries, receipt-posting delays, returns and reversals, invoice completeness, and quality-lot coverage. A score based on two deliveries should not be treated as equally reliable as one based on 2,000.

For an illustrative operational measure, 90 on-time lines out of 100 eligible lines is 90%; it is not automatically the formula used by a configured SAP supplier-score app. A quantity-weighted calculation could give a different result. Publish the denominator, tolerance window, exclusions, and weighting, and compare similar materials and service levels before drawing a sourcing conclusion.

SAP MM Interview Questions and Answers for Experienced

The experienced answers connect design decisions to financial and operational consequences, test coverage, and accountable resolution. They distinguish a temporary workaround from a sustainable correction and identify what must be validated with the relevant business and finance owners.

81. How would you design central procurement across several company codes without confusing purchasing responsibility with inventory valuation?

Centralize commercial responsibility without centralizing every legal or valuation boundary. In a same-system on-premise/Private Edition design, a cross-company-code purchasing organization is not assigned to one company code; it is assigned to the plants it serves. Each plant still belongs to its company code, and inventory valuation follows the configured valuation area—not the purchasing organization.

For example, purchasing organization C100 can negotiate for plant US10 in company code US01 and plant CA10 in CA01. Purchase orders and receipts still identify the relevant company code and receiving plant; C100 does not create a shared inventory balance or common local currency.

The design must also cover supplier purchasing and company-code extensions, local tax and payment data, approval responsibility, account determination, and reporting. A cross-system Central Procurement hub is a separate architectural choice, not merely another organizational assignment.

82. Which MM design assumptions must be revisited in an ECC-to-S/4HANA conversion?

An ECC conversion requires a process-and-data impact assessment, not just transaction-code replacement. Important MM assumptions include:

  • Supplier maintenance moves to Business Partner with Customer/Vendor Integration; integrated vendor accounting records still exist.

  • Material Ledger is mandatory in S/4HANA, but actual costing remains a separate decision.

  • Inventory persistence and aggregate handling change; custom reports and interfaces that depend on ECC tables need review.

  • MRP Live eligibility, classic fallback, planning enhancements, and proposal behavior need scenario testing.

  • Approval, output, service procurement, apps, and authorizations must be checked against the target release and adopted process.

A useful conversion inventory maps each custom report, interface, enhancement, and background job to its replacement or retained function. Regression tests should reconcile stock quantities, values, purchasing history, and accounting entries. Neither flexible workflow nor a particular output framework should be assumed to replace every classic setup automatically.

83. How would you reconcile opening inventory quantities and values during a new-system cutover?

Reconciliation needs a frozen cutover timestamp and a common stock key: material, plant, storage location, stock type, batch, valuation type, and special-stock ownership where applicable. Counts and movements after that timestamp require an explicit delta procedure.

Assume 240 EA of company-owned stock at USD 8 per EA, price unit 1, with no tax or freight adjustments. The approved opening value is USD 1,920. Reconcile both 240 EA and USD 1,920; matching quantity alone would not detect a wrong valuation price. Supplier-owned consignment must remain distinguishable from company-valued stock.

Load master data and valuation prerequisites before inventory. Then compare source totals, migration results, material valuation, and FI stock accounts, including the opening-balance offset. Coordinate the inventory load with G/L balance migration so stock is not counted twice. Exception ownership and signed reconciliation are stronger acceptance criteria than a technically successful load.

84. How would you handle partially received or invoiced purchase orders when moving to a new S/4HANA Cloud Public Edition system?

For SAP S/4HANA Cloud Public Edition migration-cockpit scope, a purchase order with follow-on documents is not simply migrated together with its history. SAP's 2608 documentation requires partially open purchase orders to be closed or cancelled in the source system. This is different from an in-place system conversion.

Consider an old PO for 100 EA: 60 received, 50 invoiced, and 40 still due. The cutover design must separately address the 40-EA future procurement obligation, the 10-EA received-not-invoiced exposure, existing inventory, and any supplier payable. Recreating a 100-EA PO would overstate remaining demand.

Agree how the old commercial obligation is closed, how supported residual transactions are established, and where later invoices will be processed. Maintain a source-to-target reference register and retain historical evidence outside the migrated document flow. Validate the exact migration object and release before deciding which residual items can be loaded.

85. MRP created a requisition without the expected source of supply. How would you isolate the reason?

Start with one affected requisition and its planning-run context: material, plant or MRP area, requirement date, procurement type, and selected planning engine. Then trace the source records that were valid when the proposal was created.

Check the quota arrangement's validity and usage, source-list validity and MRP relevance, supplier or agreement blocks, and the organizational coverage of contracts, scheduling agreements, and info records. An info record merely existing is not sufficient evidence that it qualifies for automatic sourcing. For an outline agreement selected through a quota supplier, the relevant source-list linkage also matters in the documented process.

Compare with a successful material using the same run parameters, then reproduce with the corrected master data in a controlled test. A manual requisition finding a supplier does not prove MRP should find it: their source-determination logic differs. Also distinguish a new proposal from an existing firmed proposal that was not redetermined.

86. An MRP Live run leaves some materials unplanned or sends them to classic MRP. How would you investigate?

Separate three outcomes: the material was outside the planning scope, it was planned through classic MRP, or planning failed. These are not equivalent defects.

Inspect the run selection and logs, material or MRP-area planning data, MRP type, lot-sizing procedure, planning-file relevance, and any explicit classic-planning settings or enhancements. The applicable release restrictions are decisive; a restriction list copied from an older release is not sufficient. SAP documents that MRP Live can direct unsupported materials or certain errors to classic processing.

Next verify the actual result in the current stock/requirements situation: proposal quantity, date, source, and exception messages. Absence of an MRP list is not by itself failure because MRP Live does not create the classic static MRP lists. A focused rerun should demonstrate that every required material was either planned successfully or has an identified, owned exception.

87. A newly added supplier receives nearly every new requirement in a quota arrangement. How would you correct the allocation design?

The new supplier can have a much lower quota rating because it has no allocated history. The rating uses (quota-allocated quantity + quota base quantity) / quota; the base quantity is an intentional balancing input, not a real receipt.

For an unsplit sourcing illustration, assume supplier A has quota 3 and 900 EA allocated: rating 300. New supplier B has quota 2 and zero allocation: rating 0. B can keep winning requirements while it catches up. A 600-EA base quantity gives B an initial rating of 300 without inventing historical orders.

The appropriate base is a business decision: immediate proportional participation, controlled ramp-up, or deliberate catch-up may require different settings. Confirm validity, quota usage, lot constraints, and whether MRP splitting is enabled. Do not rewrite genuine allocated history or promise that every individual PO will split exactly 60/40.

88. A high-value purchase order was approved automatically despite a required approval policy. How would you investigate the flexible workflow?

Read the PO's approval history before changing any rule. Identify the workflow instance actually selected, the order of active definitions, their validity, and the PO values evaluated at that time. A broad automatic-release workflow placed before the high-value workflow can intercept the document.

In Public Edition 2608, also inspect step conditions: a selected workflow can approve automatically when all its steps are skipped or none applies. Review steps are monitoring steps, not approval steps. For a USD 50,000 policy, test USD 49,999, exactly USD 50,000, and USD 50,001; a strict 'greater than' condition does not include equality. Check currency conversion where the workflow threshold uses another currency.

Correct the condition coverage and ordering, validate recipients and fallback behavior, and review affected POs for remediation. Do not assume a later configuration change retroactively withdraws an already completed approval.

89. A classic purchase order release strategy is not determined although the value threshold seems correct. What would you inspect?

The amount threshold is only one characteristic in classic release determination. Inspect the complete document values passed through CEKKO, the characteristics' field references and data types, the class of type 032, the release-group assignment, and the strategy's classification values.

Typical mismatches include an unexpected document type or purchasing organization, a blank value, an interval boundary that excludes the amount, or a currency characteristic evaluated differently from the buyer's displayed total. Confirm any custom characteristic-population logic rather than assuming the visible PO field is the exact determination input.

Compare the full characteristic combination with a working PO and use the available classification or release simulation in the relevant system. Then distinguish 'no strategy determined' from 'strategy found but user cannot release': release codes, prerequisites, indicators, and authorizations belong to the latter investigation. Changing the threshold alone can hide the real configuration gap.

90. A purchase order is approved but the supplier has not received it. How would you trace output without creating duplicate orders?

Approval establishes internal authorization; it does not prove transmission or supplier receipt. Open the existing PO's output history and inspect whether an output item was determined, its channel and recipient, dispatch timing, processing status, and error log.

In Public Edition output management, trace Output Parameter Determination for output type, receiver, channel, email settings or print queue, form template, and output relevance. In an ECC or Private Edition landscape using classic message control, investigate that configured framework instead; the diagnostic objects are not interchangeable.

If an output failed, correct the specific address, rule, template, job, or interface problem and retry the existing output through the supported action. If processing says successful but receipt is disputed, inspect downstream delivery evidence and confirm with the supplier before resending. Keep the original PO number and identify a retransmission clearly; creating another PO risks a duplicate commercial commitment.

91. How would you design and diagnose a procurement process in which the ordering supplier, goods supplier, and invoicing party differ?

Model the parties as partner functions rather than repeatedly overwriting one supplier's address. The main supplier is the commercial purchasing partner; a different ordering address can receive the PO, a goods supplier can ship or receive returns, and an invoicing party can submit the invoice. Alternative partners need appropriate Business Partner master records.

Maintain partner assignments at the relevant purchasing-organization level and, where used, plant or supplier-subrange level. Partner-function and schema configuration determine which functions are available or required, whether multiple partners are allowed, and how defaults are proposed into the purchasing document.

For an incident, compare the PO's actual partners with master-data defaults, document changes, output receiver rules, delivery or return address, and invoice party. A correct goods supplier does not prove the invoice creditor is correct. Verify the invoicing party's company-code accounting data and the commercial authorization for the relationship before accepting the invoice.

92. How would you separate buyer, receiver, invoice processor, and approver access in an MM control design?

The control design separates business actions, not merely job titles. An illustrative access matrix is:

Role

Primary permitted action

Separate conflicting authority

Buyer

Create or change authorized POs

Final approval of own PO

Receiver

Record evidenced receipts

Supplier bank-data maintenance

Invoice processor

Verify and post invoices

Payment approval or unrestricted release of own exceptions

Approver

Approve within delegated scope

Uncontrolled changes to the approval rules

Implement organizational restrictions, document and movement permissions, and approval-agent rules in the target edition. Test direct transactions, apps, APIs, and emergency access, not just visible menu tiles. Purchasing function controls such as EFB in applicable classic transactions supplement rather than replace a complete authorization design.

Small teams may need documented independent review instead of perfect staffing separation. The evidence should show denied conflicting actions, permitted legitimate work, delegation behavior, and monitored exception access.

93. A goods movement fails with an account-determination error. How would you trace the missing account without changing the material arbitrarily?

Capture the exact error and account-determination key, then trace the attempted business transaction. The relevant chain can include company code and chart of accounts, plant or valuation area, valuation grouping code, transaction/event key, account modifier where active, and material valuation class or valuation type.

For example, a consumption issue may need BSX for inventory and GBB with the applicable modifier for the offsetting expense. A valid BSX entry does not prove the GBB combination exists. Confirm the movement type and special-stock context before selecting an account.

If the combination is missing, Finance must approve the intended G/L mapping. If a mapped account exists, inspect its company-code extension, posting blocks, field requirements, and required cost object. Compare an equivalent successful posting, correct the proven cause, and regression-test related movements. Arbitrarily changing valuation class merely to bypass the error can misstate later postings.

94. A team proposes changing valuation class for a material with stock and open purchasing documents. What must be evaluated first?

A valuation-class change is an accounting design change, not a cosmetic master-data edit. First establish why the classification is wrong and whether the proposed class is permitted for the material type through its account category reference.

Inspect current and previous-period stock and value, open purchase orders and schedules, production-related documents, invoice exposure, split-valuation records, and the system's change checks. Existing stock and open documents can prevent or complicate the change; the exact supported procedure must be verified for the target release.

Then map the old and new BSX and offsetting accounts with Finance. Simply changing the class or account mapping does not reclassify historical ledger balances automatically. Any supported stock-clearing, document-completion, or reclassification sequence needs a controlled cutover, reconciled quantities and values, and a reversal plan. Do not delete valid business documents or make direct table changes to defeat a consistency check.

95. Why can a late invoice produce an unexpected moving average price or a price-difference posting after most stock has been consumed?

Moving-average valuation considers stock coverage when the invoice arrives; it does not retrospectively reprice every earlier consumption posting.

Assume USD, price unit 1 EA, no tax or freight, and no other movements. Receive 100 EA at USD 10, then consume 90 EA. Stock is now 10 EA worth USD 100. An invoice for all 100 EA at USD 12 creates a USD 200 variance. With only 10% quantity coverage, USD 20 increases inventory and USD 180 goes to price differences. Remaining stock becomes USD 120, or USD 12 per EA.

The investigation must reconstruct the posting sequence, invoice quantity, stock coverage, price unit, and reversals. Multiple invoices can each pass a coverage check against the same remaining quantity and accumulate variances, producing an unexpectedly high moving average. A high price therefore requires document-level analysis rather than an immediate manual price correction.

96. How does mandatory Material Ledger differ from activating actual costing, and what does that mean for MM period-end work?

Material Ledger provides the S/4HANA inventory-valuation foundation, including the configured currency and valuation views. Its mandatory status does not mean that every customer must run actual costing or automatically replace standard prices with actual prices.

Actual costing is optional additional functionality. When implemented, it collects relevant differences and supports periodic actual-cost calculation and the configured allocation or revaluation of those differences. Its period-end run has dependencies on complete goods movements, invoices, production costs, and settlement activity.

For MM, the distinction changes the close checklist. All systems still need disciplined posting cutoffs, inventory-to-FI reconciliation, GR/IR analysis, and investigation of valuation exceptions. An actual-costing implementation also needs coordination with Controlling on run status, errors, late postings, and any rerun or closing implications. 'Material Ledger is active' is therefore not enough information to prescribe a specific actual-costing close procedure.

97. A receipt must be posted to the previous month. Which MM and FI period checks and valuation consequences should be reviewed?

Check the posting date—not just the supplier's document date—and establish whether the intended prior month is the permitted previous MM period. The company-code MM period settings must allow backposting, and the relevant FI posting period must also be open for the accounts involved. An open MM period alone is insufficient.

Review stock and valuation in both periods, price-control method, intervening issues or price changes, and any Material Ledger or actual-costing close already completed. A backdated material posting can affect prior-period reporting and current inventory valuation; its impact is not limited to moving a date on a report.

For a receipt physically accepted on September 30 but entered in October, retain evidence of the real receipt date and have Finance authorize the period treatment. Simulate the accounting in the controlled environment and reconcile the affected periods. Do not reopen periods or reinitialize MM period control merely to bypass an error.

98. How would you investigate and resolve aged GR/IR differences without treating every residual balance as a write-off?

Investigate aged GR/IR at PO-item and receipt-reference level rather than netting balances. A USD 700 credit on one item and USD 700 debit on another can net to zero while hiding two unresolved obligations.

Evidence

Likely investigation

Appropriate owner/action

Receipt exceeds invoice

Missing invoice or disputed quantity

Buyer and Accounts Payable confirm what is still due

Quantities agree but value remains

Wrong receipt linkage, reversal, or replacement history

MM and Finance trace document references and valuation

Final surplus with no further GR or IR expected

Commercially closed difference

Authorized account maintenance after review

Include planned delivery-cost clearing, previous maintenance documents, and the last movement date in the analysis. Assign each exception a reason, owner, and next action; aging alone does not justify a write-off. Reconcile the resulting maintenance document and ledger posting. If a later receipt or invoice arrives, assess reversal of earlier maintenance before treating it as unexplained.

99. How would you investigate a suspected duplicate supplier invoice and improve prevention without blocking legitimate credits?

First distinguish a second entry of the same supplier invoice from installments, separate deliveries, a credit memo, or a reversal and corrected reposting. Compare supplier, company code, currency, gross amount, reference, invoice date, document type, PO allocation, and payment status with the original evidence.

Check the supplier's duplicate-check setting and the applicable Logistics Invoice Verification configuration. Company code, reference, and invoice date can be included in the comparison, and message behavior matters: a warning is not a guaranteed posting stop. Reference-format inconsistencies can defeat exact matching. SAP documents an additional credit-memo duplicate-check option from S/4HANA 2023; availability must be confirmed in the target release.

Place a payment hold where authorized while investigating, then cancel or credit only the proven duplicate with Finance. Prevention should combine consistent reference capture, sensible check criteria, exception review, and tests showing that legitimate credits and recurring invoices still work.

100. How can an exchange-rate difference arise between a purchase order, goods receipt, and supplier invoice?

A foreign-currency PO expresses the commercial price; the local-currency valuation can change when exchange rates differ at receipt and invoice. A fixed PO exchange rate is therefore materially different from an unfixed rate.

Assume company-code currency USD, PO currency EUR, price EUR 10 per EA, price unit 1, quantity 100 EA, and no tax, freight, or price variance. With no fixed rate, a receipt at USD 1.10 per EUR has USD 1,100 value. The same EUR 1,000 invoice at USD 1.15 per EUR creates a USD 1,150 supplier liability: a USD 50 translation difference.

Where that difference posts depends on account assignment, price control, stock coverage, and exchange-difference configuration; it is not universally an exchange-loss account. If the PO rate is fixed, SAP uses that PO rate for GR and IR translation in the documented process. Later payment exchange differences are a separate FI event.

101. What can go wrong when reversing a goods receipt after a GR-based invoice has already been posted?

With GR-based invoice verification, the invoice item is linked to a particular goods receipt. Reversing the receipt does not cancel the supplier invoice or remove its liability. It can also leave a receipt-reference and GR/IR inconsistency, especially where the invoice included a price variance.

First confirm whether the physical event calls for cancellation of an erroneous receipt or return of genuinely received goods. Then check the configured rule permitting reversal or return after invoicing. If it is not permitted, the invoice must be cancelled before the inventory correction. If it is permitted, a subsequent correcting or replacement receipt may need the supported subsequent-delivery reference to the original transaction rather than an unrelated new GR.

Review stock availability, batches or serial numbers, posting periods, and downstream warehouse movements before execution. Finish by reconciling PO history, received and invoiced quantities, supplier liability, and GR/IR value—not just the total stock quantity.

102. Stock is visible in the system but a production goods issue fails. How would you distinguish stock type, reservation, batch, and availability problems?

A plant total is not the same as stock eligible for a particular production issue. Read the exact error and inspect the required material, plant, storage location, batch, stock type, special stock, and quantity in the reservation or production order.

For example, 80 EA unrestricted and 40 EA in quality inspection give a 120-EA total, but they do not automatically support a 100-EA issue from unrestricted stock. The unrestricted quantity may also be in another storage location or an unsuitable batch.

Separate the physical stock-type check from any configured dynamic availability check that includes planned receipts and requirements. A reservation normally records demand rather than physically deducting stock, although it can influence dynamic availability. Check final-issue or deletion indicators, batch eligibility, serial-number requirements, and EWM staging where relevant. Resolve the real stock, master-data, or document issue; enabling negative stock or releasing quality stock without authorization is not a valid generic fix.

103. How would you reconcile an inventory quantity difference between IM and EWM without making a blind adjustment?

Compare equivalent stock dimensions at a common timestamp before concluding that inventory is missing. Align material or product, plant and storage-location mapping, warehouse, batch, stock type, special stock, owner or party entitled to dispose, and units of measure. EWM bin-level availability is not identical to an IM total.

Next trace the deliveries, goods movements, warehouse-task confirmations, pending difference postings, and integration messages. Where the deployment uses asynchronous communication, an unprocessed message can create a temporary difference; replaying it after a manual adjustment could create a second correction.

Resolve the document or interface failure first and recompare. If physical stock is genuinely wrong, conduct the authorized count and difference process in the responsible warehouse system, then verify the corresponding IM and financial updates. SAP's EWM Difference Analyzer supports analysis and transfer of inventory differences; it should not be used to conceal an unresolved mapping or integration defect.

104. Actual subcontractor component consumption differs from the PO component proposal. How would you correct and reconcile it?

Correct the component consumption, not the finished-product receipt quantity, when the finished delivery itself is accurate. If the actual consumption is known before posting GR, adjust the proposed component quantities there. If it is reported later, use the supported subcontracting subsequent-adjustment process against the PO item.

Assume 100 assemblies were received and the proposal consumed 200 kg of a component. The subcontractor later confirms 210 kg actual consumption. Post the additional 10 kg, not another 210 kg. If 300 kg had been provided and there were no other movements, the subcontractor balance should become 90 kg. Underconsumption instead reverses the excess consumption and increases stock provided to the supplier.

Reconcile the PO, component material documents, supplier-specific special stock, batch details, and valuation impact. Investigate whether scrap, unit conversion, component substitution, or an outdated BOM caused the variance, and correct future proposals without rewriting historical evidence.

105. Consignment settlement fails or uses an unexpected price. How would you trace the withdrawal and pricing data?

Trace the actual consignment withdrawal or transfer to own stock first. A receipt into supplier consignment stock does not itself create the liability that settlement clears. Inspect the material document, supplier, plant, special-stock indicator, posting date, quantity, and prior settlement status.

The withdrawal is valued using the applicable consignment info-record price on the withdrawal or transfer-posting date—not simply today's price or a price typed into a consignment PO. Verify the correct purchasing organization, consignment info category, validity period, currency, price unit, conversion, scales, and tax data.

For example, 25 EA withdrawn at USD 6 per EA, price unit 1 and tax excluded, creates USD 150 of consignment liability even if today's price is USD 7. Check settlement selection dates, account determination, supplier accounting data, and logs. Correct the proven source error using the approved process; changing a price record alone does not demonstrate that an already posted withdrawal was revalued.

106. Goods have left a supplying plant but not reached the receiving plant. How would you investigate stock in transit and financial ownership?

Identify the transfer variant first: simple two-step transfer, stock transport order without delivery, delivery-based STO, or cross-company process with billing. These variants differ in document flow, transit representation, and accounting timing.

Reconcile issued quantity against receipts, cancellations, returns, and delivery status. If 100 EA were issued and 65 EA received, with no reversals, the expected open transit quantity is 35 EA. Then match those 35 EA to dispatch evidence, carrier status, receiving discrepancies, and any blocked integration messages.

For valuation, inspect the actual accounting documents and configured process. A simple two-step plant transfer between valuation areas is valued on removal; a cross-company STO with billing has additional sales and invoice steps. Physical location, system transit stock, and legal ownership are not interchangeable evidence. Escalate lost or damaged shipments through the agreed commercial and accounting process rather than posting a fictitious receipt merely to clear the transit report.

107. How would you stop procurement from a disqualified supplier while distinguishing source-list, purchasing, posting, and quality restrictions?

Use the restriction that matches the intended scope, then handle existing commitments separately.

  • A source-list block can target a material, plant, supplier, and validity period. Blocking only an outline-agreement entry does not necessarily prevent an order without that agreement reference.

  • A supplier purchasing block stops relevant new purchasing activity at its configured scope.

  • An accounting posting block affects supplier postings, including invoices; it is not a substitute for a purchasing restriction.

  • A quality-related block depends on the active QM procurement controls for the relevant materials.

Audit open POs, scheduling lines, inbound deliveries, invoices, and automatic sourcing jobs. SAP documents that open-document processing, including receipts, can remain possible despite purchasing blocks. Decide explicitly whether existing deliveries should be accepted, quarantined, returned, or commercially cancelled. Test both manual and automatic procurement paths, preserve the disqualification reason, and assign authority for any temporary exception or later unblock.

108. Physical inventory repeatedly finds differences in the same materials. How would you identify the process cause rather than merely post differences?

Repeated differences call for a movement-to-count analysis, not merely another adjustment. Segment results by material, storage location or bin, batch, unit, shift, reason code, and transaction type. Compare both quantity and value; a frequent low-value error can reveal a systematic process weakness.

Pattern

Evidence to investigate

Differences in full-carton multiples

Base/order-unit conversion and scan quantity

Shortages after production

Missed issues, delayed backflush, scrap recording

Differences around count time

Movement cutoff, posting block, frozen book quantity

Opposite differences in two bins or batches

Misidentified transfer or picking location

For example, recurring shortages of 11 EA where one carton equals 12 EA justify checking whether an issue physically removes a carton but records one piece. Recount significant exceptions, trace documents around the count timestamp, and reconcile approved adjustments. Measure recurrence after correcting the cause; a posted difference only restores the book balance, not the process.

109. A lean-service entry sheet was approved with an incorrect quantity and an invoice now exists. How would you plan the correction?

Do not edit or reapprove the service entry sheet independently of its invoice. In the documented lean-service approval process, approval creates a goods receipt; approval can be revoked when no follow-on documents exist other than that receipt. An existing invoice therefore changes the correction sequence.

Suppose 12 hours were approved instead of 10 at USD 100 per hour, price unit 1 hour and tax excluded. The intended service value is USD 1,000, not USD 1,200. Inspect the invoice, payment status, accounting period, PO history, and service evidence with Accounts Payable.

Where full reversal is appropriate, reverse the invoice through the supported process, then verify that the app permits revoking approval before correcting and resubmitting the entry sheet. A commercial credit may settle value without making the entry sheet editable; those are different outcomes. Confirm the target release's supported sequence and reconcile the corrected receipt, invoice, expense, and supplier balance.

110. A contract price changed, but existing purchase orders still show the old price. What should you check before repricing?

An existing PO is a commercial document with its own adopted conditions; it is not a live display of the contract's current price. SAP distinguishes time-dependent contract and info-record conditions from time-independent PO conditions. Updating a contract condition does not automatically mean every existing PO should change.

Check the PO's actual contract reference, creation and pricing dates, condition validity, quantity scale, currency, price unit, manual conditions, and the agreed effective date. Also determine whether any receipt or invoice has already used the old price.

If the supplier agreement authorizes repricing open POs, use the supported condition-update approach and review its scope before saving. Recalculate freight and other dependent conditions, consider approval restart and change output, and verify later invoice treatment. A retroactive price settlement for already invoiced quantities may require a subsequent debit or credit rather than rewriting an otherwise correct PO history.

111. A purchase requisition's delivery date is too late to prevent a shortage. How would you trace scheduling and choose an operational response?

Start with the requirement's true availability date and work backward through goods-receipt processing time, planned delivery time, and purchasing processing time. Check the applicable calendars, source-specific delivery time, firming, existing supply, and whether overdue dates caused forward scheduling.

For an illustration using a seven-day working calendar, assume 2 days of purchasing processing, 8 calendar days of supplier lead time, and 1 day of receipt processing. Starting today gives availability in 11 days. A requirement in 6 days is therefore five days short; merely changing the requisition date cannot make the supplier deliver faster.

Assess feasible responses: expedite a confirmed PO, use an approved alternate source, transfer eligible stock, split the requirement, or reschedule production. Record the real supplier commitment and rerun the relevant planning checks. Correct inaccurate lead-time master data for future planning, but do not shorten valid planning parameters just to make the shortage disappear from the screen.

112. How would nonvaluated goods receipt change expense recognition for an account-assigned purchase order?

A nonvaluated GR confirms receipt quantity and updates purchasing history without making the receipt's accounting entry. For an account-assigned consumption PO, the expense is then posted at invoice receipt in the basic process, rather than at goods receipt.

Assume a cost-center PO for 20 EA at USD 50 per EA, price unit 1, followed by an exact invoice, with tax and freight excluded:

Event

Valuated GR design

Nonvaluated GR design

Receipt

Debit expense USD 1,000; credit GR/IR USD 1,000

No FI journal from GR

Invoice

Debit GR/IR USD 1,000; credit supplier USD 1,000

Debit expense USD 1,000; credit supplier USD 1,000

The nonvaluated setting does not make the purchase free or eliminate receipt control. Finance must separately assess period-end accrual requirements for received-but-uninvoiced consumption. Confirm the account-assignment category and PO indicators before applying this illustration to services, assets, or other variants.

113. Why should an ECC-era inventory report not be moved to S/4HANA by assuming the same physical tables and stock aggregates?

S/4HANA changed the MM inventory data model, so a familiar ECC object name does not guarantee the same physical storage or aggregation behavior. SAP's historical simplification documentation introduced MATDOC for material-document data and compatibility mechanisms for older objects; stock aggregates were no longer to be treated as universally persisted ECC totals.

The functional review should define exactly what the report means: current or key-date quantity, stock type, special-stock owner, batch, plant, valuation type, and currency. Then the technical team can select a supported standard report, released CDS view, or API appropriate to the target release.

Reconcile representative cases against standard inventory and accounting reports, including reversals, transfers, backdated postings, and archived data. Avoid a blind table-name substitution or direct database updates. The old simplification list explains the transition; it is not a current-release guarantee for every reporting interface or physical table.

114. When should an MM requirement use standard configuration, an approved extension point, or a side-by-side extension?

Use the least invasive mechanism that satisfies the real process requirement and its control needs.

Requirement

Preferred starting point

Approval threshold by company code

Standard workflow configuration

Supported extra validation within PO processing

Released extension point appropriate to the edition

Separate supplier-risk application using several systems

Side-by-side service using released APIs or events

The choice also depends on transaction consistency, latency, data volume, authorization, failure recovery, and who will maintain the solution. A synchronous posting validation cannot automatically be moved to an asynchronous external service without changing its control behavior.

Document the standard gap, selected API or extension contract, error handling, test cases, and upgrade responsibility. Public Edition and Private Edition have different extension possibilities. Clean core favors released interfaces and avoiding modifications; it does not mean every historical Private Edition enhancement is automatically forbidden or that every extension belongs on SAP BTP.

115. How would you design purchasing controls for capital assets and project expenditure rather than ordinary cost-center consumption?

Start with the expenditure's business purpose and Finance-approved accounting treatment. In the classic account-assignment model, category A identifies an asset assignment and category P identifies a project/WBS assignment; neither should be replaced with a convenient cost center simply to complete the PO.

Validate the asset and subnumber or WBS element, company code, status, account determination, and any active budget-availability or investment controls. Distinguish direct project consumption from project stock and from expenditure ultimately settled to an asset under construction. A WBS assignment alone does not decide capitalization.

For a USD 40,000 machine, Finance may require an asset or investment-project process, while spare parts for routine maintenance may follow consumption or stock procurement. Receipt valuation affects when the accounting entry occurs. Test receipt, invoice difference, partial delivery, return, and final settlement with the Asset Accounting or Project System team, preserving the correct approval and budget owner throughout.

116. How would you manage a defective-goods return when the business expects a replacement rather than a supplier credit?

Separate the logistics correction from the commercial settlement. Returning defective goods reduces or reclassifies the relevant stock through the chosen return process; it does not itself prove that the supplier should issue a credit, cancel an invoice, or receive a second paid order.

Assume 50 EA were received and invoiced, but 8 EA are defective and the supplier agrees to replace them at no extra charge. Record the defect and return authorization, identify the original receipt, batch or serial numbers, and the 8-EA replacement obligation. Do not create a new paid PO for those 8 EA without a commercial reason.

For GR-based verification, check whether return after invoice is allowed and use the supported subsequent-delivery linkage where applicable. If invoice cancellation or a credit/reinvoice sequence is required, coordinate it with Accounts Payable. Close the case only when net accepted stock, receipt references, GR/IR, and the supplier balance reflect 50 satisfactory EA at the agreed total charge.

117. Why can a free-of-charge receipt affect standard-price and moving-average-price inventory differently?

For the standard free-of-charge receipt without a PO, movement type 511, price control determines whether the additional quantity also increases stock value. This should not be generalized to every promotional or zero-price purchasing design.

Assume 100 EA initially worth USD 1,000, price unit 1, and a free receipt of 20 EA, with no other movements, tax, or freight:

Price control

Closing quantity

Closing stock value

Price per EA

Moving average V

120 EA

USD 1,000

About USD 8.3333

Standard S at USD 10

120 EA

USD 1,200

USD 10

With V, quantity rises while total value stays unchanged, reducing the average. With S, the receipt is valued at standard price: inventory is debited USD 200 and the configured price-difference revenue account is credited USD 200. No supplier liability arises from this free receipt. Verify the movement and price-control assumptions before interpreting the accounting.

118. Which inventory analytics would you use to distinguish excess stock, slow movement, and genuine supply shortages?

Use complementary measures rather than equating high stock value with excess inventory.

  • Excess stock: Compare usable stock and firm receipts with dated demand, safety-stock policy, and replenishment lead time.

  • Slow movement: Review consumption over a stated horizon, last movement, turnover, and material lifecycle. Transfers alone need not indicate real demand.

  • Shortage: Examine time-phased usable supply against requirements at the relevant plant or MRP area, including overdue receipts and quality restrictions.

For example, 500 EA on hand can coexist with a shortage if only 150 EA are usable and tomorrow's demand is 200 EA: the immediate gap is 50 EA. The other 350 EA may be blocked, allocated, or in the wrong location.

Validate units, stock categories, inventory accuracy, demand history, and obsolete master data before acting. SAP inventory analytical apps provide stock, movement, slow/nonmoving, and transit perspectives; the exact app availability and KPI definitions depend on the landscape.

119. What would an end-to-end MM test matrix include before releasing a purchasing and inventory design?

An MM test matrix should prove business outcomes and controls across the whole document chain, not just that a PO saves.

Test dimension

Representative cases

Purchasing

Stock/consumption, units, pricing scales, source choice, approval boundaries, output

Receiving

Partial/overdelivery, blocked or inspection stock, batch/serial requirements, returns and reversals

Invoicing

GR-based and PO-based verification, price/quantity variance, payment block, credit, duplicate control

Accounting

S/V valuation, account assignment, freight, currency, period boundaries, GR/IR

Integration and access

MRP, production, warehouse interfaces, permitted and denied user actions

Include relevant special processes such as consignment, subcontracting, STOs, services, assets, and projects rather than testing unused scope mechanically. Each case needs explicit input data, expected quantities and debit/credit values, workflow and output expectations, and reconciliation evidence. Add negative and recovery cases, including message retries and reversal sequences. A passed screen-level test without correct accounting or authorization is not a passed business process.

120. How would you release an MM configuration change safely when it works in test but causes a different posting or approval result in production?

Contain the affected process first and capture one production example with its document data, actual posting or approval result, timestamp, and configuration version. Do not repeatedly retry a posting with an unknown outcome or change production master data simply to make it resemble the test case.

Compare the complete determination inputs: organizational assignments, valuation class, account modifier, condition records, workflow order and validity, user authorizations, active enhancements, and transport dependencies. Configuration equality alone does not establish data or runtime equality.

Reproduce the mismatch using equivalent data in a controlled environment, correct the proven cause, and regression-test adjacent scenarios. Release through the landscape's approved transport or configuration mechanism; Public Edition configuration and workflow content do not all follow classic transport assumptions.

After deployment, verify a controlled business result and reconcile affected documents. Separate rollback of configuration from correction of transactions already posted: restoring yesterday's rule does not reverse today's accounting entry or completed approval.

SAP MM Documentation and Further Reading

The conceptual baseline is SAP S/4HANA sourcing and procurement, inventory management, and their financial integration in on-premise or private-edition environments. ECC or classic-process behavior and SAP S/4HANA Cloud Public Edition differences are identified where relevant; transaction codes, apps, workflows, configuration access, and supported processes are not assumed to be identical across editions or releases. Confirm the actual system release, activated scope, organizational setup, master data, and configuration. Numerical and posting examples use stated assumptions and are not records of transactions executed in an SAP system. Where relevant, account for units, currencies, taxes, delivery costs, valuation, and account-assignment rules before expecting the same result. Use authorized test data and controlled change procedures; do not bypass approval, tolerance, authorization, or reconciliation controls merely to clear an exception.

Use these curated SAP references to verify procurement, inventory, valuation, and invoice-processing behavior. Match each source to the product, deployment edition, release, and process variant in the question. Documentation and a worked example support an explanation but do not replace testing and reconciliation in the intended system.

Team Sherlock.sh

Building fraud intelligence for live high-stake video interactions (financial discussions, hiring interviews, board meeting etc).

Catch candidate fraud before it costs you.

Sherlock AI helps you detect AI-assisted, proxy, and deepfake candidates, so every hiring decision is backed by evidence.

Ask AI about Sherlock.sh

Similar Posts