Delivering and Translating Form Objects

Delivery

The Form Interface and Form Template form objects are standalone development objects. The system creates an entry for each form object in the TADIR table. The corresponding transport objects are:

For form interfaces: SFPI (R3TR SFPI <name>)
For form templates: SFPF (R3TR SFPF <name>)

The system creates the TADIR entries and transport objects with the help of the Transport Organizer. The Transport Organizer distributes the form objects to other systems. Local objects are not included in this process. You assign the package when you create a form object.

Note Form objects are cross-client.

Translation

Form objects are integrated into the translation process for development objects. The transport objects SFPF and SFPI are known to the translation tools (transaction SE63) and are included in the relevant worklists. The following form template texts are translation-relevant:

Descriptions (short texts) of the nodes
Texts in the form layout that you created in the Form Builder with Adobe LiveCycle Designer

Caution If you want to translate older form templates, you must call the layout in edit mode and save it again. If you do not change the layout, you must delete the template cache so that the changed translation takes effect. To delete the template cache, call the report FP_PDF_TEST_26 before testing the form.

Note The original language of the texts of a form template corresponds to the logon language when the form templates were created.

More information:

Defining the Layout of a Form Template

Translating PDF-Based Forms in the documentation for transaction SE63

Standard Forms

SAP delivers standard forms for various uses. If you want to adapt standard forms to company-specific requirements, create copies and link them to the applications. This prevents your form template from being overwritten by the system in the event of an update.