Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TR_AUSL - Software Delivery Composer Messages
Message number: 678
Message text: No relevant entries found in table TRDELVNEGL
To prepare for the check on <ZH>Invalid Objects</>, a search is run for
the entries in the table TRDELVNEGL in accordance with the following
logic:
Entries for which the component and component release match the
component that is to be checked
Entries for deeper components in the system (as long as the flag is not
set indicating that these entries apply explicitly only for this
component). The entries of deeper components are "propagated upwards".
At the same time, the relevant component release is compared with the
release in the system.
If the component is an add-on, a search is also run for entries with the
component <ZH>ADDON</> (dummy component for all add-on components). The
Basis release present in the system is checked.
The system displays a warning.
Since the Add-On Assembly Kit always delivers table TRDELVNEGL with
content, the table must contain data. If the table does not contain
data, open a problem message under component XX-PROJ-AAK.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL678
- No relevant entries found in table TRDELVNEGL ?The SAP error message TR_AUSL678, which states "No relevant entries found in table TRDELVNEGL," typically occurs in the context of transport management within SAP systems. This error indicates that the system is unable to find relevant entries in the specified table (TRDELVNEGL) that are necessary for processing a transport request.
Cause:
Missing Entries: The most common cause of this error is that there are no entries in the TRDELVNEGL table for the transport request you are trying to process. This table is used to manage transport deliveries, and if it is empty or lacks the necessary entries, the system cannot proceed.
Transport Request Issues: The transport request itself may not have been properly created or may have been deleted or not released correctly.
Configuration Issues: There may be configuration issues in the transport management system that prevent the proper entries from being created or recognized.
Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or process the entries in the transport tables.
Solution:
Check Transport Request: Verify that the transport request you are working with is valid and has been properly created. Ensure that it is released and contains the necessary objects.
Check Table Entries: Use transaction SE11 or SE16 to check the TRDELVNEGL table directly. If there are no entries, you may need to investigate why they are missing.
Recreate Transport Request: If the transport request is corrupted or incomplete, consider recreating it. Make sure to include all necessary objects and release it properly.
Check Transport Management Configuration: Review the transport management configuration in your SAP system to ensure that everything is set up correctly. This includes checking the transport routes and landscape configuration.
Authorization Check: Ensure that the user has the necessary authorizations to access and process transport requests. You may need to consult with your SAP security team.
Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues related to transport management.
System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
Related Information:
If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL677
Table PUTTB is empty
What causes this issue? The table PUTTB does not contain any entries for the Basis release of the system. This means that the check for used objects ...
TR_AUSL676
Object also required for '&1, &2, &3'; see note &4
What causes this issue? The object matches the entry &V1& &V2& &V3& in table TRDELVNEGL and requires a further object in the ...
TR_AUSL679
Nonexistent object (deletion): [not included in reference list]
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL680
Reference list &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.