How To Fix ME685 - Statistical goods receipt for purchase order item &1 &2 not posted

SAP Error Message - Details

• Message type: E = Error

• Message class: ME - Purchasing: General Messages

• Message number: 685

• Message text: Statistical goods receipt for purchase order item &1 &2 not posted

What causes this issue?

The system tried to create a shipping notification sent via EDI, with
message type DESADV, and at the same time tried to post a goods receipt
with the transmitted quantity.

System Response

The statistical goods receipt for
<DS:GLOS.3526C03EAFAB52B9E10000009B38F974>third-party purchase orders
</> &V1& item &V2& with the goods receipt quantity &V3& and the unit of
measure &V4& could not be posted.

How to fix this error?

Check to see if you can post the goods receipt with reference to the PO
item for the material:
<DS:TRAN.MIGO>Post Goods Receipt</>.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

INCLUDE NA_SYSADMIN OBJECT DOKU ID TX
The latter can check the settings in Customizing for <ZK>Sales and
Distribution</> under <ZK>Definition of Sales and Distribution</> . It
is possible that, for example, the movement type ('101') is missing:
<DS:SIMG.SIMG_CFMENUSAPCOVX5>Define, copy, delete, check sales
organization</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ME685 - Statistical goods receipt for purchase order item &1 &2 not posted ?

  The SAP error message ME685 indicates that a statistical goods receipt for a purchase order item has not been posted. This error typically arises in the context of inventory management and procurement processes within SAP. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Missing or Incorrect Configuration: The system may not be configured correctly for statistical goods receipts. This could involve settings in the material master or purchasing info records.
  Purchase Order Status: The purchase order may be in a status that does not allow for goods receipt posting, such as being blocked or not fully released.
  Material Master Settings: The material may not be set up to allow statistical goods receipts. This can happen if the material type does not support statistical postings.
  Document Type Issues: The document type used for the purchase order may not be configured to allow statistical goods receipts.
  Authorization Issues: The user may not have the necessary authorizations to post a statistical goods receipt.
  
  Solutions:
  
  Check Purchase Order Status: Verify that the purchase order is in a status that allows for goods receipt posting. If it is blocked, resolve the blocking issue.
  Review Material Master Settings: Check the material master record to ensure that it is configured to allow statistical goods receipts. You can do this by navigating to the material master (transaction MM03) and reviewing the relevant views.
  Configuration Review: Ensure that the configuration for statistical goods receipts is correctly set up in the system. This may involve checking the settings in the material type and document type.
  Authorization Check: Ensure that the user attempting to post the goods receipt has the necessary authorizations. This can be checked with the security team or by reviewing the user roles.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error message. SAP Notes can provide patches or additional configuration steps that may resolve the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME23N (Display Purchase Order), and MIGO (Goods Movement) for managing purchase orders and goods receipts.
  Documentation: Review SAP documentation related to inventory management and procurement processes for further insights into statistical goods receipts.
  SAP Community: Engage with the SAP Community or forums where other users may have encountered similar issues and can provide insights or solutions.
  
  If the issue persists after checking these areas, it may be beneficial to involve your SAP support team or consult with an SAP expert for further troubleshooting.