Basis Errors and Solutions

Where-used list incorrect after renaming methods

July 16, 2009 at 10:12 am

[incorrect] [incorrect string] [incorrect version] [list] [login incorrect] [methods] [refactoring] [renaming] [where-used]

1. Where-used list incorrect for includesSymptom The where-used list for includes does not find all usage locations. Other terms WBCROSSI, SE38, where-used list Reason and Prerequisites This problem is caused by a program error. Solution Implement the...
2. NR: Number from incorrect year is usedSymptom You create an interval in a year-dependent number range, and an interval for a later year already existed before. For the interval that already existed before, a buffer was created in...
3. SP_CALL_GET returns incorrect values when called second timeSymptom If you call SP_CALL_GET twice in succession, the second time it is called, a leading zero is truncated in the return parameter CALLSTATE-PARTY. For example: After the first call of the...
4. TROYMICR: Incorrect print output with 701/711/720 kernelSymptom When printing with device type TROYMICR, the printer commands for the printer initialization are not sent correctly and thus check printing with the Troy printer fails. Other terms TROYMICR Reason and...
5. Incorrect matches when using find_next( )Symptom If you use anchor characters, the methods find_next( ) and replace_next( ) of class cl_abap_matcher find additional, incorrect matches. Other terms Regular expressions, beginning of line, cl_abap_regex, match, regex, regexp Reason...
6. Incorrect format when printing listsSymptom The system uses an incorrect format when printing ABAP lists: In the print dialog, the system proposes a format for an output device, which is not defined for the relevant device...
7. OS07: Display incorrect OS log after refreshSymptom When you display the operating system log via transaction OS07, the incorrect OS log is displayed after you refresh the display. The error only occurs if a server is selected in...
8. Job refers to incorrect spool requestSymptom You want to display the spool request for a job step in transaction SM37. However, the system displays a spool request that does not seem to correspond to the relevant job....

Symptom

The navigation index is incorrect after you rename methods.
The system does not find the new method in the where-used list.
Other terms

Where-used list, renaming methods, refactoring
Reason and Prerequisites

This error occurs only if you first insert and then inactively save the new method name for the usage locations, and you then rename the method itself.
Solution

Implement the advance correction or import the relevant Support Package.

Permalink