Message E FPRUNX 001 cannot be processed in plugin mode HTTP

Question

Hi,
I am getting an error when i execute BSP application error is as follows.
Exception Class     CX_SY_MESSAGE_IN_PLUGIN_MODE
Error Name     
Program     Z_GET_BOOKING_FORM_NET========CP
Include     Z_GET_BOOKING_FORM_NET========CM001
ABAP Class     Z_GET_BOOKING_FORM_NET
Method     DO_REQUEST
Line     74
Long text     -*
coding in the method is as follows
method DO_REQUEST.
*CALL METHOD SUPER->DO_REQUEST
  runtime->server->response->delete_header_field( name = 'Expires' ).
  runtime->server->response->delete_header_field( name = 'Pragma' ).
  DATA: l_name TYPE funcname.
  TRY.
      CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
        EXPORTING
          i_name     = 'Z_CUST_FLIGHT_BOOKING_GEBO'
        IMPORTING
          e_funcname = l_name
        EXCEPTIONS
          OTHERS     = 0.
    CATCH cx_fp_api_repository.                         "#EC NO_HANDLER
    CATCH cx_fp_api_usage.                              "#EC NO_HANDLER
    CATCH cx_fp_api_internal.                           "#EC NO_HANDLER
  ENDTRY.
  DATA: l_outputparams TYPE sfpoutputparams.
*Start Form Processing.
  l_outputparams-getpdf = 'X'.
  CALL FUNCTION 'FP_JOB_OPEN'
    CHANGING
      ie_outputparams = l_outputparams
    EXCEPTIONS
      cancel          = 1
      usage_error     = 2
      system_error    = 3
      internal_error  = 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.
Add a call to the Formu2019s function module. Notice the
settings on fp_docparams that allow for the generation
of an Interactive form Without these settings the form
will be generated as standard print form. Hint: Get the
form functional moduleu2019s generated name by testing it in
transaction SFP, and then use the Pattern wizard to insert
the function callin your code.
  DATA: fp_docparams TYPE sfpdocparams,
        reservedonly TYPE bapisbodat-reserved,
        booking_data TYPE bapisbonew,
        fp_result    TYPE fpformoutput.
  fp_docparams-fillable = 'X'.
  fp_docparams-langu = sy-langu.
  CALL FUNCTION l_name
    EXPORTING
      /1bcdwb/docparams  = fp_docparams
      reserved           = reservedonly
      booking_data       = booking_data
    IMPORTING
      /1bcdwb/formoutput = fp_result
    EXCEPTIONS
      usage_error        = 1
      system_error       = 2
      internal_error     = 3
      OTHERS             = 4.
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.
Get the returned PDF, and store it in a
fpformoutput-pdf type variable.
  DATA: pdf TYPE fpformoutput-pdf.
_  pdf = fp_result-pdf._
*Close the form processing session by calling the
*FP_JOB_CLOSE function.
  CALL FUNCTION 'FP_JOB_CLOSE'
    EXCEPTIONS
      usage_error    = 1
      system_error   = 2
      internal_error = 3
      OTHERS         = 4.
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.
Set the content type to be of u201Capplication/pdfu201D. This way,
the client will know what kind of format the response is,
and will start the adobe reader to display it.
  CALL METHOD response->set_content_type
    EXPORTING
      content_type = 'application/pdf'.
*Put the PDF into the response.
  CALL METHOD response->set_data
    EXPORTING
      data = pdf.
endmethod.
error is in the line 74 in this coding line 74 is
  pdf = fp_result-pdf.
Can any one suggest me some solutions.
Thanks,
Nethaji.

Answer 1

Hi,
I'm facing the same problem.
I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
FP_GET_LAST_ADS_TRACE return following:
Begin operation:
Render, elapsed time = 16 ms.
#   End operation: Render, elapsed time = 89 ms.
#   Begin operation: UsageRights, elapsed time = 89 ms.
#   End operation: UsageRights, elapsed time = 97 ms.#
...and the error string of FP_GET_LAST_ADS_ERRSTR is:
ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
Any idea what the problem might be?