Where-used list incorrect for includes

[] [] [] [] [] [] [] []

  1. Where-used list incorrect after renaming methodsSymptom 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...
  2. 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....
  3. 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...
  4. 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...
  5. 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...
  6. 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...
  7. BWA 7.00: Incorrect result for some FEMS queriesSymptom You encounter incorrect results for a BW query using FEMS logic Other terms BIA, BWA, Accelerator, wrong data, different result Reason and Prerequisites Prerequisites: SAP NetWeaver BW Accelerator Revision 51 or...
  8. BWA 7.00: Incorrect result for some FEMS queriesSymptom You encounter incorrect results for a BW query using FEMS logic Other terms BIA, BWA, Accelerator, wrong data, different result Reason and Prerequisites Prerequisites: SAP NetWeaver BW Accelerator Revision 51 or...

Symptom

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 advance correction or import the specified Support Package.
To generate the where-used list index, you must rerun the SAPRSEUB report after you implement the advance correction. Schedule the report in the background. See Note 28022.
For Release 6.20, note the following procedure for implementing the advance correction:
For Support Package level 55 and higher, class attributes and method interfaces are implemented automatically by the Note Assistant. For Support Packages lower than 55, class attributes and method interfaces must be created or changed in the class builder before transferring the sources. To do this, proceed as follows:
1. Implement the advance correction, but do not activate it.2. Proceed as follows: Call transaction SE24 (Class Builder) and change the following objects:Go to the ‘Attributes’ tab page.Create the following class attributes:
TABLE_WBCROSSI_RAHMEN Static Attribute Private Type WBCROSST
TABLE_WBCROSSI_INCLUDES Static Attribute Private Type WBCROSST
INSERT_INCLUDE Static Attribute Private Type CHAR1
ALL_PROGRAMS Static Attribute Private Type PROGRAMTAB
Change the reference type of the attribute TABLE_WBCROSSI to TY_WBCROSSI_TAB.

Navigate to the ‘Methods’ tab pageCreate the following methods with the relevant interfaces. The method type is ‘Static Method’ and visibility is ‘Private’.
Method CHECK_DELETE_WBCROSSI
Import parameters P_DELETE_WA type WBCROSSI and Changingparameter P_DELETE_TABLE type WBCROSST .
Method SELECT_WBCROSSI_INCLUDES (no parameters)
Method SELECT_WBCROSSI_MASTER
Import parameter P_PROGRAM_TAB Type PROGRAMTABChange the typing of the P_WBCROSSI parameter of the GET_INDEX to TY_WBCROSSI_TAB method.3. Save and activate the CL_WB_CROSSREFERENCE class.

For Release 6.40, proceed as follows to implement the advance correction:
1. First of all, create the WBACTINDEX table in the system. To do this, call transaction SE11 and enter the ‘WBACTINDEX’ name in the ‘Database table’ field. Choose the ‘Create’ function.
Enter the following values:
Package: SEUIX
Delivery class of the table: ‘S’ = ‘System table, maint only by SAP, change = modification’.
Data Browser/Table View Maint: Data Browser/Table View Maint:
‘Display/Maintenance Allowed with Restrictions’.
Data class: SSRC
Size category: 0
Buffering not allowed
Enhancement Category: Can be enhanced (character-type)
The short description of the table is ‘Update Programs for Navigation Index’. Create the PROGNAME field with the corresponding PROGNAME data element. Select the ‘Key’ and ‘Initial Values’ checkboxes for this field.2. Activate the table.3. Now implement the advance corrections for Release 6.40.
Important: Do not activate all objects yet. First of all, activate the function module: REPS_OBJECT_ACTIVATE separately. To do this, proceed as follows: If the dialog box for activating all objects is displayed when you implement the note, enter a parallel mode and activate the REPS_OBJECT_ACTIVATE function module. Confirm the activation when you implement the note.

For Release 7.00, note the following procedure for implementing the advance correction:
Copy the advance correction for Release 7.00.
Important: Do not activate all objects yet. First of all, activate the function module: REPS_OBJECT_ACTIVATE separately. After you have successfully activated the function module, you can activate all the other objects.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment