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: 677
Message text: Table PUTTB is empty
The table PUTTB does not contain any entries for the Basis release of
the system. This means that the check for used objects in substitution
tables cannot run.
The system displays an error message. The entry is highlighted in red.
Check why the table does not contain a Basis release entry. The system
may have been set up incorrectly.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL677
- Table PUTTB is empty ?The SAP error message TR_AUSL677, which indicates that "Table PUTTB is empty," typically arises in the context of transport management within SAP systems. This error suggests that the system is trying to access a transport table (PUTTB) that does not contain any entries, which can lead to issues when attempting to perform transport-related activities.
Causes:
- Empty Transport Table: The PUTTB table is supposed to hold transport requests or related data, and if it is empty, it means that there are no transport requests available for processing.
- Transport Directory Issues: There may be issues with the transport directory or configuration that prevent the system from reading or writing to the PUTTB table.
- Authorization Issues: Lack of proper authorizations may prevent the system from accessing the necessary data.
- System Configuration: Incorrect configuration of the transport management system can lead to this error.
Solutions:
- Check Transport Requests: Verify if there are any transport requests available in the system. You can do this by using transaction codes like
SE09
orSE10
to view the transport requests.- Recreate Transport Entries: If the PUTTB table is indeed empty and should contain entries, you may need to recreate the transport requests or ensure that they are properly released and available for transport.
- Check Transport Directory: Ensure that the transport directory is correctly configured and that the transport files are present in the file system. You can check the transport directory settings in transaction
STMS
.- Authorization Check: Ensure that the user has the necessary authorizations to access transport requests and related tables.
- System Logs: Check the system logs for any additional error messages or warnings that might provide more context about the issue. You can use transaction
SM21
to view the system log.- Consult SAP Notes: Look for relevant SAP Notes that might address this specific error. SAP Notes can provide patches or additional guidance on resolving specific issues.
Related Information:
STMS
(Transport Management System), SE09
(Transport Organizer), and SE10
(Transport Organizer - Workbench).If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
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_AUSL675
Forbidden object '&1, &2, &3'; add the new object; see SAP Note &4
What causes this issue? According to table TRDELVNEG, object '&V1& &V2& &V3&' is not suitable for delivery and need...
TR_AUSL678
No relevant entries found in table TRDELVNEGL
What causes this issue? To prepare for the check on <ZH>Invalid Objects</>, a search is run for the entries in the table TRDELVNEGL in ac...
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...
Click on this link to search all SAP messages.