How To Fix WP747 - Void transaction & not found in IDoc &

SAP Error Message - Details

• Message type: E = Error

• Message class: WP - Messages from POS interface

• Message number: 747

• Message text: Void transaction & not found in IDoc &

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 WP747 - Void transaction & not found in IDoc & ?

  The SAP error message:
  WP747: Void transaction & not found in IDoc &
  typically occurs during IDoc processing, especially in scenarios involving workflow or change pointers, where the system expects a certain transaction or change pointer but cannot find it in the IDoc data.
  
  Explanation / Cause
  
  Void transaction & not found means that the system is trying to process a transaction (change pointer or workflow transaction) identified by a certain code (represented by & placeholders in the message), but this transaction is missing or not available in the IDoc being processed.
  This can happen if:
  
  The IDoc does not contain the expected segment or data for the transaction.
  The transaction type or change pointer is not correctly configured or activated.
  The IDoc is incomplete or corrupted.
  There is a mismatch between the expected transaction type and the actual IDoc data.
  The system is trying to process a "void" or deletion transaction that is not present in the IDoc.
  
  
  
  
  Common Scenarios
  
  When using change pointers (transaction BDCP2) to trigger IDoc creation, if the change pointer is deleted or not found, this error can occur.
  During workflow processing where a transaction is expected but missing.
  When processing outbound IDocs for master data changes, and the system expects a certain transaction but the IDoc does not contain it.
  
  
  How to Analyze
  
  Check the IDoc data:
  
  Use transaction WE02 or WE05 to display the IDoc.
  Verify if the expected transaction segment or data is present.
  
  
  Check the transaction type:
  
  Verify the transaction code or change pointer type that the system is trying to process.
  
  
  Check change pointer configuration:
  
  Use transaction BDCP2 to check if the change pointer exists and is active.
  
  
  Check partner profiles:
  
  Use WE20 to verify if the partner profile is correctly configured for the transaction.
  
  
  Check the application logs:
  
  Use SLG1 to find detailed logs related to the error.
  
  
  
  
  Possible Solutions
  
  Ensure the transaction exists in the IDoc:
  
  If the IDoc is missing the transaction segment, regenerate or correct the IDoc.
  
  
  Activate change pointers:
  
  If using change pointers, ensure they are active and not deleted.
  
  
  Correct partner profile and message type:
  
  Make sure the partner profile is set up correctly for the transaction.
  
  
  Reprocess or recreate the IDoc:
  
  If the IDoc is incomplete or corrupted, recreate it.
  
  
  Check for custom code or user exits:
  
  Sometimes custom enhancements may cause this error if they expect certain data.
  
  
  Check for SAP Notes:
  
  Search for SAP Notes related to WP747 for your SAP version.
  
  
  
  
  Related Transactions and Tools
  
  WE02 / WE05 — Display IDocs
  WE20 — Partner Profiles
  BDCP2 — Change Pointers
  SLG1 — Application Log
  BD87 — Reprocess IDocs
  SM58 — Update Requests (if related to update errors)
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Expected transaction (change pointer or workflow) not found in the IDoc data.
  
  
  Effect
  IDoc processing fails with WP747 error.
  
  
  Solution
  Verify and correct IDoc data, activate change pointers, check partner profiles, reprocess IDoc.
  
  
  Tools
  WE02, WE20, BDCP2, SLG1, BD87
  
  
  
  
  If you provide the exact transaction codes or IDoc types involved, I can help you with more specific troubleshooting steps.