SAP Basis Tech Supports

Symptom

After a Unicode conversion, you encounter the following problems with spool requests that were created before the conversion:
The display of ABAP lists in transaction SP01 is moved, and control characters are displayed.A CONVT_NO_NUMBER dump occurs in the SAPLSTXW program during the graphic display of SAPscript documents.During printing, the spool work process terminates in the is_microfiche_normal kernel function (rspoget2).During the PDF conversion of OTF spool requests, the error ‘OTF end command // missing in OTF data’ occurs.During the PDF conversion of ABAP lists, the ASSIGN_TYPE_ILLEGAL_CAST dump occurs in the SAPLSTXW program.Similar errors occur when you send spool lists from transaction SP01, depending on the SAPconnect setting.

Reason and Prerequisites

All of these problems only concern the spool requests that were created BEFORE the conversion.

Solution

ABAP list requests can be converted in the Unicode system using the UMG_CONVERT_SPOOL report. For more information, see Note 901004.
Unfortunately, OTF requests (smart forms and SAPscript) cannot be converted.
Unfortunately, there is no general solution for correcting the specified problems AFTER the conversion.
To avoid the problems from the very start, execute one or more of the following steps PRIOR TO the conversion:
Printing the requestsArchiving the ABAP listsDownloading the ABAP listsConverting the requests to PDF with the RSTXPDFT4 reportSending the requests by e-mail