Goods Receipts for PO Does Not Contain Any Items – Top Reasons and Fixes


When trying to post a Goods Receipt (GR) against a Purchase Order (PO) in SAP, users may encounter a frustrating error message: "Purchase Order does not contain any items."

Interestingly, upon displaying the PO, all items appear to be listed correctly. So, what causes this discrepancy?

This issue often stems from backend validation failures or overlooked configurations. Below are the most common root causes and how you can resolve them.

Common Reasons Why a PO Shows No Items During GR Posting

1. PO Blocked Due to Incomplete Release Strategy

If the PO is subject to a release strategy, it must undergo all levels of approval before it becomes active for further processing. Issue: If the final release has not been executed, the system considers the PO "blocked," thereby restricting Goods Receipt posting. 

Fix: - Verify the release status of the PO using ME23N. - Ensure all required approval steps are completed.

2. Confirmation Control with GR Assignment Active

SAP allows configuration of confirmation control keys that dictate how goods and services are confirmed before GR. Issue: If the confirmation control category includes a key where GR Assignment is flagged, and a confirmation isn't maintained, GR cannot be posted. 

Fix: - Check the confirmation tab in the PO. - Either maintain the required confirmation or adjust the confirmation control key settings.

3. Early Goods Receipt Date Before PO Delivery Date

Another common configuration checks the GR posting date against the scheduled PO delivery date. Issue: If you're trying to post the GR before the delivery date, SAP may reject the entry. 

Fix: - Check the delivery date on the PO. - Post the GR on or after the defined delivery date.

4. Incorrect Movement Type Selection (MIGO Specific Issue)

Sometimes, during the last GR posting in MIGO, users unknowingly change the default movement type. Issue: Accidentally setting movement type to 102 (reversal) instead of 101 (GR for PO) may cause item visibility issues. 

Fix: - Open MIGO and verify the movement type set in the current session. - Reset it back to 101 for standard GR posting.

Pro Tip: Install the latest SAP hot packages to ensure movement type is always visible during MIGO transactions.

Additional Tips to Prevent This Issue

  • Regularly review PO approval workflows to avoid missing final releases.
  • Use SAP roles and authorizations to control access to movement type changes.
  • Consider enabling error logs for GR to pinpoint mismatches early.

Frequently Asked Questions (FAQs)

Q1. Why does the PO show items in display mode but not during GR posting?

Because the system checks backend validations like approval, delivery dates, and confirmation controls during GR posting, not during PO display.

Q2. How can I check if my PO is fully released?

Use transaction code ME23N and navigate to the Release Strategy tab to view the release status.

Q3. What is movement type 101 in SAP?

Movement type 101 is used for Goods Receipt against a Purchase Order. It adds the stock into inventory.

Q4. How do I fix incorrect movement type settings in MIGO?

Open MIGO, check the movement type dropdown, and change it back to 101 before proceeding with GR posting.

Q5. Can I change the confirmation control after PO creation?

Yes, if allowed by your system configuration, you can adjust confirmation control settings via ME22N.

Q6. Does SAP allow GR before the delivery date?

Not by default. You need to configure tolerance settings or modify the PO to allow early GR.

See also

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Material Management Certification, Interview and Configuration Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.