How To Fix WRF_CONS003 - Cons.: Goods issue document &1 &2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: WRF_CONS - Retail Fashion: Consignment Processing Stock Transfers

• Message number: 003

• Message text: Cons.: Goods issue document &1 &2 not found

What causes this issue?

You want to post the goods receipt for a stock transport order. During
processing of vendor consignment stock, the stock category of the goods
receipt posting is derived from the stock category of the goods issue
posting. To do so, the system determines the corresponding goods issue
document. However, the system cannot read the determined goods issue
document &V1& &V2&.

System Response

Processing is cancelled because the system cannot determine the stock
category for the goods receipt posting.

How to fix this error?

Check material document &V1& &V2&.
Check the corresponding purchase order and/or delivery.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WRF_CONS003 - Cons.: Goods issue document &1 &2 not found ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WRF_CONS003 Cons.: Goods issue document &1 &2 not found
  
  Meaning / Cause:
  This error occurs when the system tries to reference or process a goods issue document (material document) that does not exist or cannot be found in the system. The placeholders &1 and &2 typically represent the document number and the fiscal year or other identifying parameters.
  Common causes include:  
  
  The goods issue document number entered is incorrect or mistyped.  
  The document has been deleted or archived and is no longer available in the current system.  
  The document belongs to a different company code or plant than the one currently being processed.  
  There is a mismatch in document number and year or other key fields.  
  The document has not yet been posted or saved properly in the system.
  
  
  When does it occur?
  
  During consumption posting or confirmation in production orders or process orders.  
  When trying to reference a goods issue document in a confirmation or goods movement transaction.  
  In custom programs or user exits that validate or process goods issue documents.  
  During integration processes between production and inventory management.
  
  
  Solution / How to fix:
  
  
  Verify Document Number and Year:
  
  Check the goods issue document number and fiscal year or other key fields to ensure they are correct.
  
  
  Check Document Existence:
  
  Use transaction MB03 (Display Material Document) to verify if the goods issue document exists in the system.
  
  
  Check Document Status:
  
  Ensure the document is not deleted or archived. If archived, you may need to retrieve it or check the archive system.
  
  
  Check Company Code / Plant:
  
  Confirm that the document belongs to the correct company code and plant.
  
  
  Repost or Recreate Document:
  
  If the document was never posted or was deleted, you may need to repost the goods issue or create a new one.
  
  
  Check Custom Code / User Exits:
  
  If this error occurs in a custom program or user exit, debug or review the logic to ensure the correct document number is passed.
  
  
  Check Authorization:
  
  Ensure the user has authorization to view or process the goods issue document.
  
  
  
  Related Transactions and Tools:
  
  MB03 – Display Material Document  
  MB51 – Material Document List  
  MB1A – Goods Withdrawal (for posting goods issue)  
  CO02 – Change Production Order (to check confirmations and goods movements)  
  MB5T – Stock in transit (if cross-plant issues)  
  SE38 / SE80 – For debugging custom programs or user exits
  
  
  Additional Notes:
  
  This error is often encountered in production order confirmations where the system expects a goods issue document to be referenced but cannot find it.  
  Always ensure that the document numbers are consistent across integrated modules (PP, MM, WM).  
  If the problem persists, check SAP Notes or OSS messages for any known bugs or patches related to this error.
  
  
  If you provide the exact context or transaction where this error occurs, I can help with more specific troubleshooting steps.