Subcontracting Components Not Consumed at GR
The finished material is received against the subcontract PO but the linked component consumption (movement type 543 O) does not post, or posts for the wrong quantity, leaving stock at vendor unreduced. Usual cause is a missing or incorrect component list on the PO, a BOM component not flagged for subcontracting, or components never transferred to the vendor in the first place.
Covers why the automatic component backflush at subcontract goods receipt fails to consume the expected quantity, leaving stock at vendor stuck. Walks through the component list, BOM relevance flags, fixed-quantity indicator, and provision-transfer checks that account for most cases, and separates data fixes from master data corrections.
Published 16 Sept 2026· 1,156 words
The business symptom
Plant or subcontracting controlling reports that finished goods have arrived from the vendor and the goods receipt is posted, but the stock at vendor for the components has not gone down, or has gone down by the wrong amount. Someone doing a stock reconciliation for the vendor notices the special stock quantity does not match what should have been consumed for the number of units produced. Sometimes it is finance flagging that a subcontracting cost account looks understated because no consumption ever hit it. Occasionally the report is the opposite: the components disappear from stock at vendor but no corresponding finished goods receipt exists yet, which points to a timing or sequence problem rather than a missing posting. Either way, the complaint arrives as a stock discrepancy, not as an error message, because the goods receipt itself usually completes without any warning.
The configuration behind it
- Component list on the purchase order item is missing, incomplete, or was never populated because the BOM explosion failed at PO creation time (no valid BOM found for the material, plant, or usage at that date).
- A BOM component exists but is not flagged as relevant for subcontracting, or is marked as bulk material, so it is excluded from the component list SAP builds for the PO item.
- The component quantity field on the PO item is not marked as fixed, so the system tries to recalculate the required quantity proportionally against the still-open PO quantity at goods receipt time; on partial deliveries this can round down to a tiny or zero consumption quantity.
- Components were never physically or logically transferred to the vendor as stock at vendor (no 541 movement or equivalent provision posting), so there is nothing in the special stock segment for the 543 O movement to consume.
- The goods receipt was posted through a path that lets the user override or blank out the components tab quantities before saving, disconnecting the consumption from the actual component list.
- A background job used for collective or automatic goods receipt for subcontracting orders failed on the component posting step while the finished-goods receipt step still went through, leaving a document flow with a 101 but no 543 O.
- The BOM alternative or production version referenced by the PO differs from the one the planner intended, so the component list is technically populated but with the wrong components or quantities entirely.
- The material master for the component is blocked for the plant or lacks a valid unit of measure conversion, causing the backflush line to be skipped silently during the posting.
What to check
- ME23N on the subcontract PO item, components tab: confirm the component list exists, quantities look right, and the fixed-quantity indicator is set as expected for the scenario.
- MB51 filtered by the PO number, movement types 101 and 543, to see whether the 543 O line exists at all and whether its quantity matches the 101 quantity and the component ratio.
- MMBE or MB25 for the component material and vendor to check the stock at vendor special stock balance before and after the goods receipt date.
- CS03 for the finished material's BOM, checking the component's subcontracting relevance flag and whether the alternative or usage matches what the PO explosion should have picked up.
- MB03 or the material document display for the 101 receipt to confirm whether a components tab was even shown at posting, or whether the receipt was done through a variant that skips it.
- SM37 or the relevant job log if a batch or collective goods receipt process is in use, to check for a failed component posting step that did not roll back the finished-goods line.
How to prove it in the data
Pull MB51 for the PO number across movement types 101 and 543 O and lay the two quantities side by side against the component list ratio from the PO. A 101 line with no matching 543 O line, or a 543 O quantity that does not scale with the 101 quantity by the BOM ratio, is the proof. Cross-check against MMBE for the component and vendor combination to confirm the special stock balance did not move on the goods receipt date.
Resolution path
If the component list on the PO was wrong or missing before the goods receipt, correct it on the PO item directly, a data change, then reverse and repost the goods receipt so the backflush picks up the corrected list. If the goods receipt already posted with a bad or absent component list, the only clean fix is to reverse the 101, correct the PO component list, and post the receipt again; editing the component tab after the fact does not retroactively fix a posting that already happened. If the root cause is the BOM component missing the subcontracting relevance flag or wrong alternative, that is a master data correction in the BOM, not a config transport, but it needs coordination with production planning since it affects manufacturing too. If the fixed-quantity indicator is the issue, setting it on future POs is a data-entry standard, not something fixed centrally; existing open POs with the wrong behavior need manual correction item by item. If components were never provided to the vendor, the fix is a process one: post the missing transfer to stock at vendor before the consumption can ever balance, and check why the transfer step was skipped upstream.
The fix people try first (and why it fails)
The common reflex is to post the missing component consumption manually with a direct movement against the vendor's special stock, bypassing the PO entirely. This makes the stock at vendor balance look correct again but it disconnects the consumption from the purchase order history and the goods receipt document. The PO's component list and its remaining open quantity no longer reconcile with what was actually consumed, any later cancellation of the original goods receipt cannot reverse the manually posted quantity, and the cost of the subcontracting operation gets misattributed. It hides the underlying BOM or PO configuration problem, which then repeats on the next order.
Whose problem this is
This sits with the MM or procurement functional consultant supporting subcontracting, working alongside production planning where the BOM component flag is the cause. The handover note should state the PO number, whether the 101 was already posted, the component list quantities expected versus consumed, and whether a reversal and repost is needed or whether the fix is a forward-only BOM correction.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-functional-issues/subcontracting-components-not-consumed-at-goods-receiptERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.