Transporting smartforms

[Former Member]

Hi All,

When we transport a smart form, from source system to target system, will the FM associated with it get transported.

If the FM doesnt get transported then when will the FM get generated for the smart form in the target system?

Regards,

Arjun

[Former Member · Accepted solution]

use fm.

Whenever a smart form is activated function module is generated. This FM returns the name of the generated function module.

CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'

EXPORTING

formname = 'GIVE YOUR SMART FORM NAME'

• VARIANT = ' '

• DIRECT_CALL = ' '

IMPORTING

fm_name = v_form_name

EXCEPTIONS

no_form = 1

no_function_module = 2

OTHERS = 3 .

*---- Function Module to call the Smart Form -

---

*step 1 - go to ur smart form

*step2 - take environment

*step3-take function module name

*copy that unique number.

*step4 -come back to ur driver program.

*step5 - place ur cursur here. take patter,.give that unique number.

*at that time u will get the below code.

*step6 - rename that unique number with 'v_form_name' in the code generated by pattern.

CALL FUNCTION v_form_name

EXPORTING

• ARCHIVE_INDEX =

• ARCHIVE_PARAMETERS =

control_parameters = p_control_parameters

• MAIL_APPL_OBJ =

• MAIL_RECIPIENT =

• MAIL_SENDER =

output_options = p_output_options

user_settings = ' '

• ARCHIVE_INDEX_TAB =

• IMPORTING

• DOCUMENT_OUTPUT_INFO =

• JOB_OUTPUT_INFO =

• JOB_OUTPUT_OPTIONS =

EXCEPTIONS

formatting_error = 1

internal_error = 2

send_error = 3

user_canceled = 4

OTHERS = 5

.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

When the form is activated, the system automatically generates an internal name for the function module. The function module SSF_FUNCTION_MODULE_NAME is used to derive the name of the generated function module. This internal name is stored in the variable FM_NAME in the coding. In this function the form name has to be passed as the export parameter.

The second call is to the function FN_NAME. The import and export parameters of the function module must be specified in the form interface.

The generated function module is thus called and populated with the corresponding data from the application

[Former Member · Accepted solution]

Hi Kishan,

This procedure if fine to find out the FM name is system.

But my question is will this FM also gets transported,say when we transport the smart form from development environment to the UAT environment.

If the FM doesnt get transported then,at what time will the FM get generated at the UAT system.

[Former Member · Accepted solution]

no it is genrated fm ,it may be diffrent name in another server.

When the form is activated, the system automatically generates an internal name for the function module. The function module SSF_FUNCTION_MODULE_NAME is used to derive the name of the generated function module. This internal name is stored in the variable FM_NAME in the coding. In this function the form name has to be passed as the export parameter.

The second call is to the function FN_NAME. The import and export parameters of the function module must be specified in the form interface.

The generated function module is thus called and populated with the corresponding data from the application

[Former Member · Accepted solution]

Thank you for the answer.

So is it like when we transport a smart form the FM will be automaticlly generated in the target system.So there is no need for us to separately activate it in taget system.

[Former Member · Accepted solution]

ya if u r using this fm then there is no need to activate it againin target system .

but if u r using genrated fm than u have to because it is not automaticaly genrated in target system and privious genrated fm only belongs to dev client .

so it is recomondate always use ssf* fm for smartforms.