Basis Errors and Solutions

Incorrect format when printing lists

July 22, 2009 at 8:32 pm

[01] [128] [834] [=] [dialog] [FORMAT] [incorrect] [incorrect integer] [incorrect string] [login incorrect] [l_rc] [Mail] [Message] [no] [Package] [Print] [SAPconnect] [SAPLSPRI] [send] [SMTP] [Support] [XS]

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...
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...
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...
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...
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....
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...
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 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 type.In the background, the system generates a spool request that cannot be printed because the format is not defined for the relevant device type. If “Print immediately” is set as the time of printing, the relevant output request receives the status incorrect (Format cannot be read).
Other terms

SAPLSPRI, print dialog
SAPconnect, SMTP, send mail
Message XS 834
Support Package 01, no format, l_rc = 128

Reason and Prerequisites

The following reasons for the error are currently known:
A user-defined specification was defined in the print dialog for the format.A cross-user and report-dependent specification was defined for the format using the program RSPRIPARADMIN.In the print program, a format is directly transferred to the function module GET_PRINT_PARAMETERS as the parameter LAYOUT.

At runtime, the format is not defined for the device type of the current output device.

Solution

In the dialog, the system displays message PT 002 on the print screen:
Format “Z_XX_YY” not defined for printer “DEST”
You then have the following options:
1. Replace the format in the print dialog with another format that is suitable.2. Adjust your user-defined specification for the format accordingly, or delete your user-defined specification. To do this, choose “Properties” and then “Specifications” in the print dialog.3. Adjust the cross-user specification for the format accordingly using the program RSPRIPARADMIN, or delete the cross-user specification.

If you are not in the dialog, use the attached correction instructions. Alternatively, import the relevant Support Package. As a result, the system checks whether the combination of output device and format that was determined at runtime is valid. If the system recognizes an invalid format, it uses the most suitable format for further processing to avoid subsequent terminations.