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: 827
Message text: &1 unconvertible entries (with old syntax) found
A relevant transport object could not be determined for entries found
with the old syntax in the lock key table. The corresponding lock keys
with the new syntax could therefore not be determined. The lock keys
are no longer locking any objects and have therefore been deleted from
the lock key table.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The deleted lock key entries can be displayed by increasing the
expansion level in the log display.
Error message extract from SAP system. Copyright SAP SE.
TK827
- &1 unconvertible entries (with old syntax) found ?The SAP error message TK827 indicates that there are unconvertible entries in the system, specifically related to the use of old syntax in the context of transport requests or customizing settings. This error typically arises when there are inconsistencies or issues with the transport directory or when trying to convert old transport requests to a new format.
Cause:
- Old Syntax: The error is primarily caused by the presence of transport requests or customizing entries that are still using an outdated syntax that the system can no longer interpret correctly.
- Transport Directory Issues: There may be issues with the transport directory or inconsistencies in the transport logs.
- System Upgrade: If the system has been upgraded, some old entries may not be compatible with the new version.
- Missing or Corrupted Data: There could be missing or corrupted data in the transport requests.
Solution:
- Check Transport Requests: Review the transport requests that are causing the issue. You can use transaction code
SE01
orSE09
to analyze the transport requests.- Convert Old Syntax: If possible, convert the old syntax entries to the new format. This may involve manually editing the entries or using specific SAP tools designed for this purpose.
- Delete or Correct Entries: If certain entries are no longer needed or are corrupted, consider deleting them or correcting the data.
- Use Transport Management System (TMS): Ensure that the Transport Management System is properly configured and functioning. You may need to re-import or re-export transport requests.
- Check for Notes: Look for SAP Notes related to this error message. SAP frequently releases notes that provide fixes or workarounds for known issues.
- Consult SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex transport issues.
Related Information:
SE01
, SE09
, SE10
, and STMS
for managing transport requests and analyzing issues.By following these steps, you should be able to identify the cause of the TK827 error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
TK826
&1 lock key entries deleted successfully
What causes this issue? &V1& obsolete or invalid lock keys were deleted successfully from the lock key table at database level.System Respons...
TK825
Error: Could not delete lock key entries
What causes this issue? An error occurred when obsolete or invalid lock key entries were deleted at database level. This is caused by internal proble...
TK828
&1 lock keys with errors (with incorrect length) deleted
What causes this issue? Entries satisfying neither the old nor the new syntax were found in the lock key table. These faulty entries are no longer lo...
TK829
Contents of lock key table at start of adjustment:
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
Click on this link to search all SAP messages.