How To Fix SCPR134 - No data records found in the transport request for the tables

SAP Error Message - Details

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 134

• Message text: No data records found in the transport request for the tables

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 SCPR134 - No data records found in the transport request for the tables ?

  The SAP error message SCPR134, which states "No data records found in the transport request for the tables," typically occurs when you are trying to transport changes related to database tables, but the transport request does not contain any data records for those tables. This can happen for several reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Empty Transport Request: The transport request may not have been properly populated with the changes made to the tables.
  Incorrect Transport Method: The changes might have been made in a way that does not capture the data in the transport request (e.g., changes made directly in the database without using the appropriate SAP tools).
  Transport Request Not Released: The transport request may not have been released, which can prevent the data from being included in the transport.
  Data Not Included: The specific data records you are trying to transport may not have been included in the transport request due to selection criteria or other filters.
  Transport Layer Issues: There may be issues with the transport layer configuration that prevent the data from being captured.
  
  Solutions:
  
  Check Transport Request: Verify that the transport request contains the necessary changes. You can do this by checking the transport request in the Transport Organizer (SE09 or SE10).
  Recreate Transport Request: If the transport request is empty, you may need to recreate it and ensure that you include the necessary changes to the tables.
  Use Correct Tools: Ensure that you are using the correct SAP tools (like SE11 for table changes) to make changes to the database tables, which will automatically include them in the transport request.
  Release Transport Request: If the transport request is not released, release it and check if the data records are now included.
  Check Transport Layer: Review the transport layer settings in transaction STMS to ensure that everything is configured correctly.
  Manual Data Transport: If necessary, you may need to manually transport the data using other methods, such as data export/import tools (e.g., LSMW, SAP Data Services).
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE09 (Transport Organizer), SE10 (Transport Organizer - Modifiable Requests), and SE11 (Data Dictionary).
  Transport Management System (TMS): Understanding how TMS works can help in troubleshooting transport-related issues.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to transport requests and the SCPR134 error.
  Documentation: Review SAP documentation for best practices on managing transport requests and changes to database tables.
  
  By following these steps, you should be able to identify the cause of the SCPR134 error and implement a solution to resolve it.