BBP_OUTPUT_PRINT SAP Function module

BBP_OUTPUT_PRINT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BBP_OUTPUT_PRINT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BBP_OUTPUT
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BBP_OUTPUT_PRINT - BBP OUTPUT PRINT

CALL FUNCTION 'BBP_OUTPUT_PRINT' "
  EXPORTING
    is_control_parameters =     " ssfctrlop
    is_output_options =         " ssfcompop
    it_attachment =             " bbpt_pds_att_t
*   iv_commit =                 " xfeld
  IMPORTING
    ev_archdone =               " tdarcdone
    ev_output_done =            " tdoutdone
    et_message =                " bbpt_tr_error
  CHANGING
    is_form_attachment =        " bbps_forms_output
    .  "  BBP_OUTPUT_PRINT

ABAP code example for Function Module BBP_OUTPUT_PRINT

The ABAP code below is a full code listing to execute function module BBP_OUTPUT_PRINT including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_ev_archdone  
 
 TYPE TDARCDONE
,
ld_ev_output_done  
 
 TYPE TDOUTDONE
,
ld_et_message  
 
 TYPE BBPT_TR_ERROR
.


DATA(ld_is_form_attachment) = 'Check type of data required'.

DATA(ld_is_control_parameters) = 'Check type of data required'.

DATA(ld_is_output_options) = 'Check type of data required'.

DATA(ld_it_attachment) = 'Check type of data required'.

DATA(ld_iv_commit) = 'Check type of data required'.
.

CALL FUNCTION 'BBP_OUTPUT_PRINT'
  EXPORTING
    is_control_parameters =      ld_is_control_parameters
    is_output_options =          ld_is_output_options
    it_attachment =              ld_it_attachment
*   iv_commit =                  ld_iv_commit
  IMPORTING
    ev_archdone =                ld_ev_archdone
    ev_output_done =             ld_ev_output_done
    et_message =                 ld_et_message
  CHANGING
    is_form_attachment =         ld_is_form_attachment
    .  "  BBP_OUTPUT_PRINT

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_is_form_attachment
 
 TYPE BBPS_FORMS_OUTPUT ,
ld_ev_archdone
 
 TYPE TDARCDONE ,
ld_is_control_parameters
 
 TYPE SSFCTRLOP ,
ld_ev_output_done
 
 TYPE TDOUTDONE ,
ld_is_output_options
 
 TYPE SSFCOMPOP ,
ld_et_message
 
 TYPE BBPT_TR_ERROR ,
ld_it_attachment
 
 TYPE BBPT_PDS_ATT_T ,
ld_iv_commit
 
 TYPE XFELD .


ld_is_form_attachment = 'Check type of data required'.
ld_is_control_parameters = 'Check type of data required'.
ld_is_output_options = 'Check type of data required'.
ld_it_attachment = 'Check type of data required'.
ld_iv_commit = 'Check type of data required'.