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 - Change and Transport System
Message number: 166
Message text: Key description contains old default
A key definition was processed that was defined according to an
outdated description rule. An area was defined by specifying a FROM
field and a TO field.
The old specifications were:
Object : "&V1&"
Table : "&V2&"
FROM field : "&V3&"
TO field : "&V4&"
Specifying intervals with upper and lower limits to define key
ranges can have undesired effects and/or cause errors, as the decision
as to whether a given key lies in the interval depends on the codepage
used.
You must enter a new definition to replace the old one.
List generic areas to define key ranges.
Delete the entry and add the appropriate generic description lines.
Example: old: from Y to ZZZ
should be replaced by
new: Y*
and Z*
Therefore, in this example, the one old line is replaced by two new
ones.
<ZH>Example of error case:</>
Range: XX* to YY*
Permissible on ASCII computers: e.g. keys "Z1234", "Z9*"
Permissible on EDCDIC computers: e.g. keys "Y1234", "Y9*"
The permissible ranges on the two types of computers are mutually
exclusive; when such a key is actually permitted, this is due to
coincidence more than anything else.
In contrast, configured key specifications, such as
A* to X* ,
are not critical, as no special characters and/or numeric values
could be involved in a codepage.
Error message extract from SAP system. Copyright SAP SE.
TR166
- Key description contains old default ?The SAP error message TR166 ("Key description contains old default") typically occurs in the context of transport requests in SAP systems. This error indicates that there is a mismatch or inconsistency in the transport request's key description, often due to changes in the system or configuration that have not been properly updated in the transport request.
Cause:
- Old Default Values: The transport request may contain references to old default values that have been changed in the system. This can happen if the configuration or development objects have been modified after the transport request was created.
- Inconsistent Transport Request: If the transport request was not properly updated or if there were changes in the system that were not reflected in the transport request, it can lead to this error.
- Manual Changes: Manual changes to the transport request or its objects can also lead to inconsistencies.
Solution:
- Check Transport Request: Review the transport request to identify any inconsistencies. You can do this by using transaction code SE09 or SE10 to display the transport request and its objects.
- Update Key Descriptions: If you find that the key descriptions are outdated, you may need to update them to reflect the current configuration or development objects.
- Recreate Transport Request: If the transport request is too inconsistent or complex to fix, consider creating a new transport request and moving the necessary objects into it.
- Transport Organizer: Use the Transport Organizer to check for any inconsistencies and resolve them. You can also use the "Check" function in the Transport Organizer to identify issues.
- Consult Documentation: Refer to SAP documentation or notes related to transport management for any specific guidance on handling this error.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR165
Key description is not generic
What causes this issue? A fully qualified table key was entered. A key field of the table specified does not have a character format. In this case, t...
TR164
Caution when entering 'from-to' range
Important for entry of 'from-to ranges': code-page-specific entries Unintended faulty effects may be produced when you enter intervals with...
TR167
Describe the key generically
What causes this issue? A fully qualified key was entered. However, only key areas for name reservations - i.e. generic key descriptions - are possi...
TR168
TRESC can be edited at SAP only
What causes this issue? The table for allocated name ranges (TRESC) cannot be maintained in a client system. The data can only be displayed because i...
Click on this link to search all SAP messages.