Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix TRS0704 - Internal Error: Call READ_BY_OID not GET_PERSISTENT_BY_OID


SAP Error Message - Details

  • Message type: E = Error

  • Message class: TRS0 - Messages for Reconciliation

  • Message number: 704

  • Message text: Internal Error: Call READ_BY_OID not GET_PERSISTENT_BY_OID

  • Show details Hide details


  • 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 TRS0704 - Internal Error: Call READ_BY_OID not GET_PERSISTENT_BY_OID ?

    The SAP error message TRS0704, which states "Internal Error: Call READ_BY_OID not GET_PERSISTENT_BY_OID," typically indicates an issue related to the Transport Management System (TMS) or the transport directory in SAP. This error can occur during transport operations, such as when trying to import or export transport requests.

    Causes:

    1. Corrupted Transport Directory: The transport directory may be corrupted or not properly configured.
    2. Database Issues: There may be issues with the database that prevent the system from retrieving the necessary data.
    3. Transport Request Issues: The transport request itself may be incomplete or corrupted.
    4. System Configuration: Misconfiguration in the transport management settings or inconsistencies in the transport landscape.
    5. Version Mismatch: There may be a version mismatch between the source and target systems.

    Solutions:

    1. Check Transport Directory:

      • Verify the integrity of the transport directory. Ensure that all necessary files are present and not corrupted.
      • You can use transaction SE01 to check the status of transport requests.
    2. Database Consistency Check:

      • Perform a database consistency check to ensure that there are no underlying issues with the database.
      • Use transaction DB02 to analyze the database and check for inconsistencies.
    3. Transport Request Review:

      • Review the transport request for any inconsistencies or errors. You can do this in transaction SE09 or SE10.
      • If the transport request is corrupted, you may need to recreate it.
    4. TMS Configuration:

      • Check the Transport Management System configuration using transaction STMS. Ensure that all systems are correctly configured and connected.
      • Reconfigure the TMS if necessary.
    5. System Logs:

      • Check the system logs for any additional error messages or warnings that may provide more context about the issue. Use transaction SM21 to view the system log.
    6. SAP Notes:

      • Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates available that resolve the issue.
    7. Contact SAP Support:

      • If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error and the steps you have already taken.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SE01, SE09, SE10, STMS, and SM21 for managing transport requests and checking system logs.
    • SAP Notes: Regularly check for updates and patches related to transport management in the SAP Support Portal.
    • Documentation: Review SAP documentation related to the Transport Management System for best practices and troubleshooting steps.

    By following these steps, you should be able to diagnose and resolve the TRS0704 error in your SAP system.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant