Transporting Application Forms 

Use

An application form consists of different, independent, transportable (sub)objects. The individual objects each have a different transport behavior.

Transport Behavior of the Objects

Object Type	Transport Object (R3TR)	Client-Independent	Object Catalog Entry (TADIR)
Application form	EFOM	NO	NO
SAPscript form	FORM	NO	YES
Smart Form	SSFO	YES	YES
PDF-based form/form interface	SFPF / SFPI	YES	YES
SAPscript text	TEXT	NO	NO
User includes	PROG	YES	YES
Generated function group	(FUGR)	(NO)	$TMP (LOCAL)

An application form has only been correctly transported if all subcomponents have also been transported.

Features

You have two options for transporting application forms. The option you choose depends on the system setting of the client in which the application form is developed or maintained.

·        Automatic transport
If the setting Recording of Client-Dependent Customizing is active, each time you change a client-dependent object (for example, application form or SAPscript text), an entry is created in a Print Workbench transport request for the object concerned. The system requests this entry before the change. The client-independent objects are entered in transport requests as standard provided you have assigned them to transportable packages.
Exception: The SAPscript is client-dependent, but has a cross-client object catalog entry.

·        Manual transport
You carry out a manual transport in the following cases if the recording of client-specific Customizing is not active in the client in which you are developing the application form, and/or you want to place the application form, including subcomponents, in a transport request. Proceed as follows:

...

                            a.      Choose Print Workbench ® Application Form ® Transport.

                            b.      In the subsequent dialog box, select the subobjects to be transported.

                            c.      Specify a transport request and choose Continue.

When it releases the transport request, the system checks the application form specified and if necessary, reactivates it. If errors occur, the release is terminated. You can analyze the corresponding messages in the transport log for the request. During the import into the target system, the transported application forms are also activated. If an application form cannot be activated, a corresponding error entry is updated in the transport log of the request.