Basis Errors and Solutions

NR: Number from incorrect year is used

July 14, 2009 at 5:54 am

[incorrect] [incorrect string] [incorrect version] [login incorrect] [main] [Memory] [NUMBER_RANGE_API_THNOCALL] [NUMBER_RANGE_UPDATE_CLOSE] [SNRO] [SNUM] [ThNoCall]

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...
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...
ST02/ST03N: Values displayed in incorrect columnsSymptom 1. In transaction ST02, the system displays the value for the maximum heap memory consumption in the column “In Mem [KB]” instead of in the column “MaxUse [KB]“. 2. In the...
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...
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...
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...
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...
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...

Symptom

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 the main memory because numbers were already used from the interval. If a number from the newly created interval is requested, the system uses a number from the buffer and does not use a number from the newly created interval.
Other terms

SNUM, SNRO, NUMBER_RANGE_UPDATE_CLOSE, ThNoCall, main memory, NUMBER_RANGE_API_THNOCALL
Reason and Prerequisites

During the creation process, the buffer is reset only for the year of the new interval, all the other buffers are retained. If a number is requested, the system uses a number from the outdated buffer.
Solution

Implement the corrections using the Note Assistant or import the relevant Support Package.

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 700 From SAPKB70002 |
————————————————————————
Create a dialog text:
1. Call transaction SE61.
Document class: Dialog Text
Choose a language.
Dialog text: TRANSPORT
Choose “Create”.
2. Copy the following text:
In the target system, all intervals of the selected number range object are deleted first, so that only the exported intervals remain after the import. The number levels are imported with the value that they have at the time of the export.
For year-dependent intervals or number range objects that are buffered in the main memory, the buffers in the target system are not reset by the transport. Use transaction SM56 to manually perform this for the number range object.
Dependent tables are not transported or converted.
3. Save and activate your changes.