SAP Basis Tech Supports

Symptom
After a Unicode migration, OTF documents that were created in the non-Unicode environment are no longer displayed or converted. The following symptoms may occur:
When you send data, the send process terminates in CONVERT_OTF when the system attempts to convert the OTF into a PDF.You can no longer display OTF documents from SOST or SBWP.

Reason and Prerequisites
OTF documents are linked to one system. They exist in binary in the system code page and can no longer be used after the system code page is converted.
Solution
For technical reasons, OTF documents that were created in a non-Unicode environment can no longer be used in a Unicode environment. You cannot create them again AFTER the Unicode migration.
To avoid this problem, the OTF document must be converted to another format in the non-Unicode environment. Here are some possible options for doing this:
Send the document by e-mail with the target format PDF or PS in SAPconnect administrationPrint the document to a file on the front end