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: TK - Transport Organizer
Message number: 368
Message text: Cannot display where-used list
Currently it is not possible to branch to the where-used list.
The process is cancelled.
Try to generate the where-used list for the object in the appropriate
editor or the Repository Information System.
Error message extract from SAP system. Copyright SAP SE.
TK368
- Cannot display where-used list ?The SAP error message TK368 "Cannot display where-used list" typically occurs when a user attempts to view the where-used list for a particular object (like a material, BOM, or routing) but the system is unable to retrieve the necessary data. This can happen for several reasons. Here are some common causes, potential solutions, and related information:
Causes:
- Authorization Issues: The user may not have the necessary authorizations to view the where-used list for the specified object.
- Object Not Found: The object for which the where-used list is being requested may not exist or may have been deleted.
- Data Inconsistencies: There may be inconsistencies or corruption in the database that prevent the where-used list from being generated.
- Technical Issues: There could be technical issues with the SAP system, such as problems with the database or application server.
- Missing Configuration: The necessary configuration for the where-used list functionality may not be set up correctly in the system.
Solutions:
- Check Authorizations: Ensure that the user has the appropriate authorizations to access the where-used list for the object in question. This can be done by checking the user's roles and authorizations in the SAP system.
- Verify Object Existence: Confirm that the object for which the where-used list is being requested actually exists in the system. You can do this by trying to access the object directly.
- Database Consistency Check: Run database consistency checks to identify and resolve any inconsistencies. This may involve using transaction codes like SE14 (Database Utility) or SE11 (Data Dictionary).
- Technical Support: If the issue persists, it may be necessary to contact your SAP Basis team or technical support to investigate any underlying technical issues with the system.
- Configuration Review: Review the configuration settings related to the where-used list functionality to ensure everything is set up correctly.
Related Information:
If the problem continues after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.
Get instant SAP help. Sign up for our Free Essentials Plan.
TK367
Objects in SAP namespace cannot be included in local packages
What causes this issue? Objects in the SAP name range cannot be created in a local package ($, T packages).System Response The function terminates.H...
TK366
Object already exists globally in system &
What causes this issue? The object already exists globally in the SAP system &V1&.System Response The function terminates.How to fix this er...
TK369
Call only for objects of SAP partners (J in the first position)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TK370
Namespace conflict between object &1 and target package &3
What causes this issue? You want to place the object &V1& in a request (relocation with package change) or edit it. During this there was a n...
Click on this link to search all SAP messages.