How To Fix TR166 - Key description contains old default

TR166 - Overview

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 166

• Message text: Key description contains old default

What causes this issue?

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.

System Response

You must enter a new definition to replace the old one.

How to fix this error?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 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.