How To Fix PU359 - Entry updated in object directory TADIR for package &

SAP Error Message - Details

• Message type: E = Error

• Message class: PU - Upgrade and Transport Log Messages

• Message number: 359

• Message text: Entry updated in object directory TADIR for package &

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 PU359 - Entry updated in object directory TADIR for package & ?

  The SAP error message PU359 indicates that there is an issue related to the object directory (TADIR) for a specific package in the SAP system. This message typically arises during transport or development activities when there is an inconsistency or a problem with the package or its objects.
  Cause:
  
  Inconsistent Object Directory: The object directory (TADIR) may have inconsistencies, such as missing entries or incorrect package assignments.
  Transport Issues: There may be issues with the transport request, such as missing objects or incorrect transport configuration.
  Authorization Issues: The user may not have the necessary authorizations to update the object directory or the package.
  Package Deletion or Renaming: If the package has been deleted or renamed, it can lead to this error when trying to update or transport objects associated with it.
  
  Solution:
  
  Check Package Status: Verify the status of the package in transaction SE80 or SE21. Ensure that the package exists and is not in a deleted or inconsistent state.
  Review Transport Requests: Check the transport requests associated with the package. Ensure that all objects are correctly included and that there are no missing dependencies.
  Authorization Check: Ensure that the user has the necessary authorizations to perform actions on the package and its objects. This can be checked in transaction SU53 or by consulting with your security team.
  Consistency Check: Use transaction SE03 (Transport Organizer Tools) to perform a consistency check on the transport directory and the object directory. This can help identify any inconsistencies that need to be resolved.
  Recreate the Package: If the package is corrupted or has been deleted, you may need to recreate it and reassign the objects to the new package.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: SE80 (Object Navigator), SE21 (Package Builder), SE03 (Transport Organizer Tools), SU53 (Authorization Check).
  SAP Notes: Always check for relevant SAP Notes that may provide specific fixes or workarounds for this error.
  Documentation: Review SAP documentation related to transport management and package handling for best practices and guidelines.
  
  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.