Knowledge Atlas

SAP goods receipt diagnostics

A goods receipt connects a physical event to purchasing, stock, accounting, quality, and later invoice matching.

Reviewed

Begin with three versions of reality

For a goods-receipt incident, compare three things: what physically arrived, what the purchase order expects, and what SAP already posted. Most confusion starts when one of these is treated as the truth without checking the other two.

A truck at the gate does not prove that the PO item is open. A PO with open quantity does not prove that the material can be posted to the requested plant or stock type. A material document does not prove that stock is available for the business use the user expects.

First identify the exact failure

SymptomFirst questionLikely next evidence
The receipt cannot be postedWhat exact validation stops the posting?PO item/status, material/plant data, movement/reference context, batch/serial/QM requirements, posting date.
The receipt posted against the wrong reference or quantityWhat was posted and what should have been posted?Material document, PO history, delivery note, user input, reversal/follow-on documents.
PO history does not look as expectedIs the receipt missing, reversed, or posted to another item/reference?PO history sequence and material-document references.
Stock exists but is not usableWhich plant, storage location, batch, special-stock or quality status received it?Stock overview and stock type/status after posting.
Invoice matching is now blockedDo PO, receipt and invoice quantities/values describe the same business event?PO history, GR quantity/value, invoice variance and reversal history.

A diagnostic sequence

  1. Capture the physical evidence. Supplier, delivery note, material, delivered quantity, unit, batch/serial information where relevant, and receiving location.
  2. Read the PO item. Check ordered and open quantity, delivery-completed/deletion or other relevant status, plant, delivery tolerances, units, and any expected receiving controls.
  3. Read PO history before reposting. A receipt may already exist, may have been reversed, or may have been posted against a different item.
  4. Capture the exact posting error. The message and posting context tell you whether the issue belongs to purchasing data, material controls, inventory configuration, accounting period, quality, batch/serial handling, or another layer.
  5. Check the material and organizational context. Confirm that the material is valid for the plant and that required stock, batch, serial, valuation, or quality controls are satisfied.
  6. Confirm the result after posting. Check the material document, PO history, stock location/status, and any accounting or quality follow-on result expected from the movement.

Movement type is important, but it is not the whole diagnosis

The movement type controls important posting behaviour, but changing it to make an error disappear can create the wrong stock or accounting result. First confirm the business event and reference: purchase-order receipt, reversal, return, transfer, subcontracting, consignment, or another scenario. Then check whether the movement used by the process matches that event.

For deeper movement-type questions, use the movement type diagnostic rather than turning every receiving issue into configuration work.

Quality, batch, serial, and warehouse controls change the path

A valid receipt may not land in unrestricted-use stock. Quality inspection, batch management, serial-number requirements, EWM or warehouse execution, and special-stock scenarios add their own evidence and status. Do not “correct” the inventory because the stock category differs from a simple PO receipt example.

Be careful with reversal and reposting

Reversing an incorrect receipt can be the right correction, but it is not a harmless reset button. Check whether the receipt already affected invoice verification, stock consumption, quality, warehouse tasks, valuation, or later material movements. The later the process has moved, the more important the document flow becomes.

Tools depend on the release and process

In classic GUI-based processes, consultants commonly use MIGO or the relevant Fiori app for the receipt, ME23N for PO and history context, and stock/material-document views for the posted result. S/4HANA data structures and apps differ from older ECC habits, so avoid building the diagnosis around one legacy transaction or table name.

What belongs in the ticket

  • PO and item, supplier, material, plant and receiving location.
  • Physical quantity/unit versus ordered, already received, and remaining quantity.
  • Exact posting error or the material document if posting already occurred.
  • Batch, serial, quality, warehouse, or special-stock context when relevant.
  • Delivery note and business date/posting date.
  • Downstream impact: stock unavailable, invoice blocked, production waiting, accounting period issue, or another concrete result.

The useful end state

A goods-receipt incident is solved when physical delivery, PO history, material document, and resulting stock tell the same story. If support only makes the posting screen accept the entry, the interesting problems have merely been moved downstream to invoice verification or inventory reconciliation, where humans traditionally rediscover them at a worse time.