How To Fix TR563 - Class &1 for user-defined update of table &2 missing in request

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 563

• Message text: Class &1 for user-defined update of table &2 missing in request

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 TR563 - Class &1 for user-defined update of table &2 missing in request ?

  The SAP error message TR563 indicates that there is a problem with a user-defined update of a table in a transport request. Specifically, it means that the transport request is missing an update for a specific class and table. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Transport Request: The update for the specified table (denoted as &2) is not included in the transport request (denoted as &1). This can happen if the changes were not properly captured in the transport request.
  Incorrect Configuration: The configuration for the transport system may not be set up correctly, leading to issues with capturing changes.
  Manual Changes: If changes were made directly in the production environment without being transported from the development environment, this error can occur.
  User-Defined Updates: The error specifically mentions user-defined updates, which may not be automatically included in transport requests.
  
  Solution:
  
  Check Transport Request: Verify that the transport request includes the necessary changes for the specified table. You can do this by checking the transport logs or the contents of the transport request.
  Recreate Transport Request: If the changes are missing, you may need to recreate the transport request and ensure that all relevant changes are included.
  Use Transaction SE09/SE10: Use transaction codes SE09 or SE10 to manage transport requests. You can check for any inconsistencies or missing objects in the transport request.
  Manual Inclusion: If the changes were made manually, you may need to manually include the changes in the transport request. This can be done by using the appropriate transport tools or by redoing the changes in the development environment.
  Consult Documentation: Review SAP documentation or notes related to transport management to ensure that your transport system is configured correctly.
  Check for User Exits or BAdIs: If the update is related to user exits or BAdIs, ensure that these are properly implemented and included in the transport request.
  
  Related Information:
  
  Transport Management System (TMS): Understanding how TMS works can help in managing transport requests effectively.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Development and Production Environment: Ensure that changes are consistently transported from development to production to avoid discrepancies.
  Testing: Always test changes in a quality assurance environment before transporting them to production to minimize errors.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.