FLM Transport Wizard

Transporting forms  in FLM 295 SP2 and above.

The Form Transport Wizard can be found in SPRO -> IMG -> Cross-Application Components -> General Application Components -> Forms Lifecycle Manager -> Tools -> Form Transport Wizard

For FLM 295 SP3 be sure to apply FLM Note: 0124

The form transport wizard will guide you through the process of moving a form definition and FLM Customer Code configuration through your SAP landscape.

Note: number ranges and the FLM customer code must be setup in each receiving system before transporting. If FLM is being used on more than one SAP Client on the same Instance the number range interval should be <CLIENT>0000000 - <CLIENT>9999999 (e.g. 8110000000 - 8119999999) for transparency.

FLM 295 SP2 now supports transporting the central configuration between clients and systems.

The wizard now supports 6 different scenarios.

1) Client-to-client

This is used when FLM is configured on multiple clients on the same SAP instance.  If different FLM customer codes are used in each client, then the system will copy the ABAP code associated with each client into a separate business logic class which allows for a clear separation between the clients.  If each client has the same FLM customer code, then each client shares the ABAP business logic and hence the separation between the clients is limited.

2) System-to-system  (default)

The standard scenario for moving a form from Development through to Quality and Production.

After the Wizard there may be some additional entries and objects that also need to be transported:

  • From 295 SP3 on MIME types referenced in .HTML templates (Images, Stylesheets, Javascripts) can be transported by adding them to a transport when the they are uploaded in the FLM Form Resources img activity.
    • MIME Objects can also be added to transports by opening transaction SE80->BSP Application /FLM/PORTAL_MIMES, then right clicking on the MIME object then selecting Other Functions->Write Transport Entry
    • If the objects is assigned to package $TMP the package will need to be changed first via ‘Change Package Assignment”. The appropriate package is likely ZFLM_FORM_CLASSES.
  • This is also moved in the "Central configuration system-to-system" scenario.
    • Javascript Snippets can be transported by attaching table /FLM/JS_VARS with key <CLNT><CUSTOMER_CODE>*
  • Javascript Dynamic Variables can be transported by adding the snippets class.
    • To find the associated class looked for <Cusotmer_Code><Form type: JXXX> in table /FLM/FTYPE_CLASS
  • SAP Standard Texts (SO10) can be manually added to transports when they are created/edited or by using report RSTXTTRAN.
    • Run report RSTXTTRAN and enter "Text key - name" with the UPPER CASE wildcard search.
      • Form specific texts should start with /FLM/<CUSTOMER_CODE>_<FTYPE>*
      • Global texts should start with /FLM/<CUSTOMER_CODE>*
    • Select the required texts and hit enter to confirm
    • Click the new "Trsfr text to corr." button and choose the relevant transport.

3) Export form package

Only used when exporting a form definition to be sent to a 3rd party for support (for example).

4) Import form package

Used to import a form definition into the new FLM system that was exported in the previous Form Wizard option.  This mechanism can only be used to import Form Definitions into development systems.

5) Central configuration client-to-client

This moves all customizing that is specific to a customer code such as the global list of form actions and statuses between clients on a system. Certain installation specific customizing (eg content server configuration) is not included here, but is transported using the standard SAP mechanism.

  • The System Specific Settings can be transported by attaching table /FLM/DNS_SUB with key <CLNT>*
  • When transporting to a fresh client you must first add an entry in "Link Data Types" before it will be recognized by the Transport Wizard.

6) Central configuration system-to-system

This moves all customizing that is specific to a customer code such as the global list of form actions and statuses between systems. Certain installation specific customizing (eg content server configuration) is not included here, but is transported using the standard SAP mechanism.

  • The System Specific Settings can be added by attaching table /FLM/DNS_SUB with key <CLNT>*
  • Adding the Customer Code level user-exits class to the transport:
    • Identify the class by inspecting the /FLM/FTYPE_CLASSES table where the CCODE = <Customer_Code> and FTYPE = <Customer_Code> entry.
    • On the transport add Program ID: R3TR, Object: CLAS and Object Name: <Class Name> example: /FLM/0001 or ZFLM_0001.

Software Component Vector

When importing transports into the target system the Software Component Vector will show that the Component FLM:Cust=<Customer Code> is not installed. This error can be ignored. The SAPCOMPONENT object is used by the FLM Wizards to manage transports and does not have any impact outside of the FLM software.

Transporting forms in FLM 295 SP1

Note: number ranges and the FLM customer code must be setup in each receiving system before transporting. If FLM is being used on more than one SAP Client on the same Instance the number range interval should be <CLIENT>0000000 - <CLIENT>9999999 (e.g. 8110000000 - 8119999999) for transparency.

As of 295 SP1 the Form Wizard also transports Web Services. However, some manual activation of those services must still be performed on the receiving system. See the Using Web Services page for more details.

Form Wizard

During the initial Form Wizard run the system builds and allocates one workbench and one customizing request to each form type.  During regular development and customizing no further pop-ups are sent to the user. 

Manually Creating Transports

If your system is locked so all new transports must originate from Solution Manager you will receive an error here indicating that the requests cannot be created. This will not prevent your proceeding and you will be able to select any transport you want to use in the Form Transport Wizard. If you'd like the Form Transport Wizard to automatically find your Customizing and Workbench transports add Request Attributes of type 'SAPCOMPONENT' with values of 'FLM:Cust = <Customer Code> and Form = <Form Type>'.

 

Form Transport Wizard

SP1 delivers a new tool, the 'Form Transport Wizard'. 

When the form type is ready for transport, the user then executes the new Form Transport Wizard, which collects all of the necessary objects and adds them to the two existing requests.  These can then be released and transported to the target system using regular SAP tools.

In order to then continue with the next set of changes, the user simpy runs the original Form Wizard again which will generate and initialize a new pair of requests, including an incremented sequence number.

Note// Any Z or Y objects that aren't on other transports will need to be manually added.

Transport and Migration Tasks Consolidated

The new Form Transport Wizard has 4 modes of operation:

  1. client-to-client
  2. system-to-system
  3. system-to-external
  4. external-to-system

Options 3) and 4) are direct replacements for the form package export and import transactions, which have therefore been removed from the FLM IMG.

 

Transporting forms in FLM 295.

Note// you must have configured number ranges and the FLM customer master in each receiving system beforehand.

In FLM 295 onwards Forms are transport through a system landscape using the normal STMS method of releasing and importing Workbench and Customizing Requests.

 

Transporting forms in FLM 290 and below.

Note// you must have configured number ranges and the FLM customer master in each receiving system beforehand.

After the initial installation of the software and the customer code configuration has been done, release and migrate all FLM customizing and workbench transports through the landscape.

For subsequent forms there are 3 aspects to doing transports: customizing, workbench and form templates.   If STMS is correctly set up, when you execute the form wizard you will be asked for 1 customizing request and 1 workbench request.   We recommend strongly that you start a 2 new corrections for each new form type and make sure that you add any subsequent customizing or workbench changes onto the same two transports.

Transporting form templates using download/upload

To transport the form templates you use the import/export mechanism provided, which creates an external file:

/spro/cross-apps/general app functions/flm/interactive forms/setup forms/migrating form packages/import form package

/spro/cross-apps/general app functions/flm/interactive forms/setup forms/migrating form packages/export form package

Do not choose to add either business logic or posting adapters to your file for transporting forms between local systems, as these components are transported via the normal SAP tp mechanism.

A logging transaction keeps track of what you are doing:

        /spro/cross-apps/general app functions/flm/interactive forms/setup forms/execute FLM transport log

You can do the transports and the import/export in any order.

Export packages including the business logic and/or the posting adapters are only used for sending requests to your support company, or when downloading existing forms from this website to use as a starting point for your own developments.

Transporting form templates using transports

This mechanism is not recommended as creating manual transports is error prone and transporting erroneous transports into productive systems could result in data loss. 

Notes on adding final form template to a transport request (not automatically added at this version of FLM): 

 

1)      Transaction OAC0 (oh-ay-see-zero).  This shows that the name of the content repository is normally 'ZFLM0001' and the name of the content table is /FLM/SDOKCONT1.

 

This table will store all the form templates (and the form data).

 

2)      Transaction SE10.   You need one customizing transport and one workbench transport.

 

3)      Manually add these entries to the customizing transport:

 

Object

Table

Keys

Example

R3TR TABU

/FLM/FTYPE     

<MANDT><CCODE><FTYPE>*       

020INFHRLV*

R3TR TABU

/FLM/FDD_SF  

<MANDT><CCODE><FTYPE>*       

020INFHRLV*

R3R TABU

/FLM/FDD_FLD

<MANDT><CCODE><FTYPE>*       

020INFHRLV*

 

4)      Manually add these entries to the workbench transport:

 

Object

Table

Keys 

Example

R3TR TABU

/FLM/SDOKCONT1

IN<CCODE>-<FTYPE>-<LANG>-<VERS>

ININF-HRLV-E-00

R3TR TABU

/FLM/SDOKCONT1

IR<CCODE>-<FTYPE>-<LANG>-<VERS><19 spaces>*

IRINF-HRLV-E-00 *

MOST IMPORTANT -  DO NOT FORGET THE 19 SPACES AND THE * ON THE IR LINE

 

 

5)      Release and transport these through the landscape as normal

 

Transporting the FLM Central Configuration

  • Use SE09 to create a new Customizing Request and name it “<ccode> FLM Central Config”  where e.g. <ccode> = ACL
  • Double click on the new transport task and go into change mode (Ctrl+F1)
  • Under the “Program ID” column always enter R3TR and under “Object Type” enter TABU
  • Enter each table name in turn as the “Object Name” and the table keys as below all starting with the source SAP client number
  • In the example below we are creating a transport from client 200 for customer code ACL
/FLM/CCODE 200ACL
/FLM/DNS_SUB 200*
/FLM/FACT 200ACL*
/FLM/FACTT 200EACL*
/FLM/FCAT 200ACL*
/FLM/FSTAT 200ACL*
/FLM/FSTATT 200EACL*
/FLM/JS_VARS 200ACL*

 

Importing a .flm package from another system (all FLM versions).

Import the package into your DEV system using this transaction

/spro/cross-apps/general app functions/flm/interactive forms/setup forms/migrating form packages/import form package

Execute the form wizard to add the necessary objects to corrections, 1 customizing and 1 workbench (again always use new transports for each form type).  You must also download the form to the desktop and then upload it back into the system using the import form template transaction - this last step necessary to add the encoding type to a customizing transport (there's no need to actually modify inside Designer if you have no need to).

Also go into the template look and feel transaction (if no entries exist, go into the form statuses table in the 'Initialize Customer Code' section of the IMG and click the 'Propagate New Status' button), form routing table, form types configuration, escalations and reminders, email setting, FPE valid statuses, FPE control and add the entries onto the same customizing correction.