function module 'FPCOMP_FORM_START' is displaying usage error

[Former Member]

Hi ,

i have developed a webdynpro application, which calls a adobe form.

it is working fine in quality and development system ,but in production system it is dumping.

The is the error message can be seen below .i debugged and found it is failing in function module FPCOMP_FORM_START and sy-subrc = 1.

i debugged inside this function module , it is sending error message in PERFORM check_form_start.

Error message from ST22.

Exception 'CX_FPM_EXCEPTION' was raised, but it was not caught anywhere along

  the

call hierarchy.

Since exceptions represent error situations, and this error was not

adequately responded to, ABAP program 'CL_FPM_MESSAGE_MANAGER========CP' had

  to be terminated.

FORM check_form_start.

   IF fpstat-is_opened = abap_false.

     PERFORM reset_status.

     MESSAGE ID 'FPRUNX' TYPE 'E' NUMBER '102' RAISING usage_error.

   ENDIF.

   IF fpstat-is_started = abap_true.

     PERFORM reset_status.

     MESSAGE ID 'FPRUNX' TYPE 'E' NUMBER '103' RAISING usage_error.

   ENDIF.

   fpstat-is_started = abap_true.

ENDFORM.                    "check_form_start

source code extract

"Check if the original exception contains text

   lv_additional_text_trucated = lv_short_text(20).

   CONCATENATE lv_additional_text_trucated '...' INTO lv_additional_text_trucated SEPARATED BY space RESPECTING BLANKS.

   DATA: lv_original_text_length TYPE i.

   lv_original_text_length = STRLEN( lv_additional_text_trucated ).

   lv_original_text = text-011.

   CONCATENATE lv_additional_text lv_original_text lv_additional_text_trucated INTO lv_additional_text SEPARATED BY SPACE RESPECTING BLANKS.

   IF lv_original_text_length EQ 0.

     lv_original_text = text-012.

     CONCATENATE lv_additional_text lv_original_text INTO lv_additional_text RESPECTING BLANKS SEPARATED BY SPACE .

   ENDIF.

   CLEAR: lv_log_message.

   CONCATENATE if_fpm_message_manager=>gc_logpoint_raise_exception sy-timlo into lv_log_message RESPECTING BLANKS.

   ASSERT ID fpm_runtime_messages

      SUBKEY lv_log_message

     "SUBKEY if_fpm_message_manager=>gc_logpoint_raise_exception

     FIELDS

       text-006 'RAISE_CX_ROOT_EXCEPTION'

       text-001 lv_short_text

       text-002 lv_long_text

       text-003 lv_program_name

       text-004 lv_include_name

       text-005 lv_line_number

       text-007 lv_additional_text

     CONDITION lv_assert_exception = abap_false.

>>>   RAISE EXCEPTION TYPE cx_fpm_exception

     EXPORTING

       textid = cx_fpm_exception=>report_free_text

       previous = io_exception

       gc_text_1 = lv_additional_text

       .

[Former Member]

When you called the FM, you didn't specify the exceptions.

Rob

[Former Member]

Issue resolved.

i had provided a printer name which was not available in production system.

wa_outputparams-dest = 'FORMS'