SAP Function Modules

comments icon Comments

FOPC_PRINT_REPORT_PROXY_CALL SAP Function module







FOPC_PRINT_REPORT_PROXY_CALL 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 FOPC_PRINT_REPORT_PROXY_CALL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FOPC_PRINT
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM FOPC_PRINT_REPORT_PROXY_CALL - FOPC PRINT REPORT PROXY CALL 





CALL FUNCTION 'FOPC_PRINT_REPORT_PROXY_CALL' "
  EXPORTING
    i_report_input =            " xstring       GUID in 'CHAR' Format in Uppercase
*   i_print_type = SPACE        " fopc_btc_attachment_type  BTC Reports - Attachment for Background Report
    is_printing_info =          " xstring       BTC Reports - Info Relevant for Printing Reports
  IMPORTING
    e_done =                    " xfeld         Checkbox
    e_report_output =           " xstring
    e_print_output =            " xstring
    .  "  FOPC_PRINT_REPORT_PROXY_CALL

ABAP code example for Function Module FOPC_PRINT_REPORT_PROXY_CALL





The ABAP code below is a full code listing to execute function module FOPC_PRINT_REPORT_PROXY_CALL 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_e_done    TYPE XFELD
,
ld_e_report_output    TYPE XSTRING
,
ld_e_print_output    TYPE XSTRING
.




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

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

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

CALL FUNCTION 'FOPC_PRINT_REPORT_PROXY_CALL'
  EXPORTING
    i_report_input =             ld_i_report_input
*   i_print_type =               ld_i_print_type
    is_printing_info =           ld_is_printing_info
  IMPORTING
    e_done =                     ld_e_done
    e_report_output =            ld_e_report_output
    e_print_output =             ld_e_print_output
    .  "  FOPC_PRINT_REPORT_PROXY_CALL

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_e_done  TYPE XFELD ,
ld_i_report_input  TYPE XSTRING ,
ld_e_report_output  TYPE XSTRING ,
ld_i_print_type  TYPE FOPC_BTC_ATTACHMENT_TYPE ,
ld_e_print_output  TYPE XSTRING ,
ld_is_printing_info  TYPE XSTRING .




ld_i_report_input = 'Check type of data required'.
ld_i_print_type = 'Check type of data required'.
ld_is_printing_info = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FOPC_PRINT_REPORT_PROXY_CALL or its description.


   
 

FOPC_PRINT_REPORT_PROXY_CALL - 
FOPC_ORM_TRANSFER - Transfer ORM
FOPC_ORM - Transfer ORM
FOPC_MODIFY_SIGNOFF_ADD - 
FOPC_MODIFY_SIGNOFF - 
FOPC_ISSUE_RANGE_BUILD -