Incorrect matches when using find_next( )

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

  1. 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...
  2. 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...
  3. 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...
  4. 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...
  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. 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....
  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

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 and Prerequisites

If the methods find_next( ) and replace_next( ) are called several times, the anchor characters ^, \A, \b, and \< may match incorrectly after the first match has been found.
For example:
CREATE OBJECT regex EXPORTING pattern = '^-+a+'.
matcher = regex->create_matcher( text = ‘–aa–aa–aab–’ ).
Here, only a match at offset 0 would be correct; however, due to the error, multiple calls of matcher->find_next( ) also return matches at offsets 4 and 8.
Solution

If the error description above applies to your situation, install the current version of the ABAP kernel. For the lowest patch level for the relevant release, see the section “Support Package patch level”.
(Patch text: ‘fixed anchor handling in find_next( )’)
Check SAP Service Marketplace to see whether the patch is already available for your platform, and apply it in accordance with Note 19466.

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

Leave a Comment