SAP OSS Notes

999712 SAP OSS Note - PDF conversion for Unicode








SAP OSS Note 999712 version 0012 contains details of a know issue related to PDF conversion for Unicode . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 999712 Details:





When does this problem occur



How can I convert SAPscript or Smart Forms documents that were created


with Unicode device types into PDF format?



Cause of the problem and Pre-requisites



With Release 710 (or 620/640/700 with the Support Packages specified


below), the existing PDF Converter (function module CONVERT_OTF)

for SAPscript and Smart Forms is enhanced so that PDF documents can be


created in Unicode systems and correctly reproduce a mixture of

 languages.




The prerequisites for using the Unicode Converter are as follows:
An SAP Unicode system Release 620 or higher
The Support Packages specified below for Release 620, 640, 700
The kernel patches from Note 873239
Truetype fonts installed with the RSTXPDF2UC report. The Unicode-PDF
Converter inserts the fonts into the PDF where necessary. A guide

 to installing the fonts is attached to this note. (No fonts are


required for Chinese/Japanese/Korean.)

The OTF data to be converted must have been created with a cascading


fonts Unicode device type (such as ZSWINCF, see Note 906031) or w

ith the new PDF device type PDFUC attached to this note. As of Release


710, this device type PDFUC is available in the standard system

.


Alternatively, you can also use Unicode PCL5 device types LEXUTF8,
HPUTF8, RC001U18 or RC001V18. In this case, in Report RSTXPDF3, the

 option


CASC_UC_DEVTYPES
must be activated. However, LEXUTF8, HPUTF8, RC001U18 or RC001V18 are
not recommended for PDF conversion because the ANDALE font can

not be correctly reproduced in the PDF.




Solution instructions



For PDFUC to work in Releases 620-700, you require at least the


following Support Package level:

Support Package required for 620: Support Package 61.


Support Package required for 640: Support Package 20.
Support Package required for 700: Support Package 11.




The device type PDFUC is delivered in Releases 620, 640, 700, 701 and
702 in the more recent Support Packages defined in the note.



Description of problem



CONVERT_OTF, PDFUC


Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 999712 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 999712 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 999712 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 999712 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)