Entering content frame

Background documentation Delivery and Translation Locate the document in its SAP Library structure

Transport Object

The interface and form (context and layout) of a PDF-based form are separate development objects. An entry is created in the TADIR (object directory) table for each interface and each form. The corresponding transport objects are as follows:

·        SFPF for the form (R3TR SFPF <name>)

·        SFPI for the interface (R3TR SFPI <name>)

The system uses the Transport Organizer in the usual way to create the TADIR entries or transport objects and their attributes. The Transport Organizer distributes the interfaces and forms to other systems. Local objects are not included in this process. You assign a package to an interface or form when you create it.

 

Cross-Client Objects

The interfaces and forms for PDF-based forms are cross-client objects.

 

Translating Texts

PDF-based forms are integrated in the same translation process as other development objects; this means that the SFPF and SFPI transport objects are recognized by the translation tools (transaction SE63) and are included in the relevant worklists. The translation-relevant texts in a PDF-based form are as follows:

·        Descriptions of the nodes

·        Texts in the layout of the PDF-based form that you created in the Form Builder with Adobe Designer

The node descriptions are translated in the same way as other system short texts.

You use Adobe Designer to translate the texts in the layout. The translation tool calls Adobe Designer automatically. To do this, the system creates a copy of the original layout, in which you can translate the texts.

 

Original Language

When you create a PDF-based form, the system specifies the logon language as the original language. You create the form and all its language-specific parts (such as texts and meanings) in the original language.

 

Standard Forms

Different applications in the SAP system use different standard PDF forms. If you want to adapt these forms to your own requirements, copy the standard form, make your changes to this copy only, and then link it to the application. (The system does not log any modifications to the standard form.) In this way, your customer-specific changes are not lost when an updated version of the standard form is imported in an upgrade.

 

Leaving content frame