How To Fix WG305 - No purch. requisitions or purchase orders found for the data entered

SAP Error Message - Details

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 305

• Message text: No purch. requisitions or purchase orders found for the data entered

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message WG305 - No purch. requisitions or purchase orders found for the data entered ?

  Certainly! Here's a detailed explanation for the SAP error message WG305: No purch. requisitions or purchase orders found for the data entered:
  
  Error Message
  WG305: No purch. requisitions or purchase orders found for the data entered
  
  Cause
  This error occurs when you try to perform an operation (such as creating a goods receipt, invoice verification, or delivery processing) that requires referencing an existing purchase requisition (PR) or purchase order (PO), but the system cannot find any PR or PO matching the criteria you have entered.
  Common reasons include:
  
  The purchase requisition or purchase order number entered does not exist in the system.
  The document number is mistyped or incorrect.
  The document exists but does not match the selection criteria (e.g., company code, plant, vendor).
  The document is not yet released or approved, so it is not available for further processing.
  The document has been deleted or archived.
  The user is trying to reference a document type that is not valid for the transaction.
  The system is being accessed with incorrect parameters or filters that exclude the relevant documents.
  
  
  Solution
  To resolve this error, you can take the following steps:
  
  
  Verify Document Number:
  
  Double-check the purchase requisition or purchase order number you entered.
  Ensure there are no typos or extra spaces.
  
  
  
  Check Document Status:
  
  Confirm that the PR or PO is released and approved.
  Use transaction codes like ME53N (Display Purchase Requisition) or ME23N (Display Purchase Order) to verify the document status.
  
  
  
  Check Selection Criteria:
  
  Make sure the plant, company code, vendor, or other selection parameters match the document.
  Remove or adjust filters that might be restricting the search.
  
  
  
  Check Document Existence:
  
  Use standard SAP reports or transactions to confirm the document exists.
  If the document was recently created, ensure it has been saved and posted correctly.
  
  
  
  Authorization Check:
  
  Ensure you have the necessary authorizations to view or process the PR or PO.
  
  
  
  Check Document Type and Transaction:
  
  Verify that the document type is valid for the transaction you are performing.
  For example, some transactions only allow referencing purchase orders, not purchase requisitions.
  
  
  
  System Issues:
  
  If the document exists but still cannot be found, check for system inconsistencies or indexing issues.
  Consult your SAP Basis or technical team if needed.
  
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  ME21N: Create Purchase Order
  ME22N: Change Purchase Order
  ME23N: Display Purchase Order
  ME51N: Create Purchase Requisition
  ME52N: Change Purchase Requisition
  ME53N: Display Purchase Requisition
  MIGO: Goods Movement (where this error often appears)
  MIRO: Enter Incoming Invoice
  
  
  
  SAP Notes:
  
  Check SAP Service Marketplace for notes related to WG305 for any known bugs or patches.
  
  
  
  User Guides:
  
  Refer to SAP MM (Materials Management) documentation for proper procedures on creating and referencing PRs and POs.
  
  
  
  
  If you provide the exact transaction and context where the error occurs, I can help with more specific troubleshooting steps.