Ansicht
Dokumentation

RSBCS_CONVERT_OTF_FOR_UNICODE - BCS: Conversion of OTF documents before a Unicode conversion

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Purpose

Documents of form processing type OTF are created system-specifically. If these documents are stored in the database, (for example, if they are sent by e-mail or fax using Business Communication Services (BCS)), they can no longer be displayed or resent after Unicode conversion. If existing OTF documents are still needed after Unicode conversion, they can be converted to PDF format before the Unicode conversion using the existing RSBCS_CONVERT_OTF_FOR_UNICODE report.

This report also enables you to replace OTF documents in another system. The documents are converted into a PDF in the source system and transferred by RFC to the target system. There, the content of the OTF document is replaced by the PDF. This enables OTF documents from a system already converted to Unicode to be replaced by documents converted into PDF from a non-Unicode system.

Source system and target system must be identical, that is, the OTF document keys must be the same in both systems. If the OTF cannot be found in the target system, the documents cannot be replaced.

Integration

Prerequisites

Features

Selection

On the selection screen of the report the OTF document can be selected according to different criteria.

You can enter an RFC destination for the target system in the "Remote Office Destination" field. If this field is not set, the conversion is done locally.

Standard Variants

Output

If the "Detailed Output" option is not selected, only the number of documents and the number of possible errors is displayed. Otherwise the report displays a results list with all selected documents. In test mode, a double-click on an entry can display the OTF document, or in the productive run the PDF document. Documents are only saved as PDF if test mode is not selected.

Example

Fill RESBD Structure from EBP Component Structure   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2064 Date: 20240601 Time: 062142     sap01-206 ( 52 ms )