SAP Function Modules

GRPC_API_REPORT_OVS SAP Function module - OVS filling for reporting







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

Associated Function Group: GRPC_API_REPORT
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM GRPC_API_REPORT_OVS - GRPC API REPORT OVS





CALL FUNCTION 'GRPC_API_REPORT_OVS' "OVS filling for reporting
  EXPORTING
*   i_session_id =              " grpc_api_session_id  GRPC unique session ID
*   i_search_pattern =          " grpc_api_search_pattern  Search pattern for the Query APIs
    i_entity_id =               " grpc_api_entity_id  GRPC ID of the entity
    i_sel_screen = 'R'          " grpc_rep_sel_screen  Report: Selection screen
*   is_selection_rep =          " grpc_s_rep_selection  Search condition
*   i_regulation_id =           " grpc_api_object_id  GRPC ID of the individual object
  IMPORTING
    e_return_code =             " int4          Natural number
  TABLES
*   et_message =                " bapirettab    Table with BAPI Return Information
    et_ovs_values =             " grpc_t_f4help  Table of F4 Help
    .  "  GRPC_API_REPORT_OVS

ABAP code example for Function Module GRPC_API_REPORT_OVS





The ABAP code below is a full code listing to execute function module GRPC_API_REPORT_OVS 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_return_code  TYPE INT4 ,
it_et_message  TYPE STANDARD TABLE OF BAPIRETTAB,"TABLES PARAM
wa_et_message  LIKE LINE OF it_et_message ,
it_et_ovs_values  TYPE STANDARD TABLE OF GRPC_T_F4HELP,"TABLES PARAM
wa_et_ovs_values  LIKE LINE OF it_et_ovs_values .

DATA(ld_i_session_id) = 'Check type of data required'.
DATA(ld_i_search_pattern) = 'Check type of data required'.
DATA(ld_i_entity_id) = 'Check type of data required'.
DATA(ld_i_sel_screen) = 'Check type of data required'.
DATA(ld_is_selection_rep) = 'Check type of data required'.
DATA(ld_i_regulation_id) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_message to it_et_message.

"populate fields of struture and append to itab
append wa_et_ovs_values to it_et_ovs_values. . CALL FUNCTION 'GRPC_API_REPORT_OVS' EXPORTING * i_session_id = ld_i_session_id * i_search_pattern = ld_i_search_pattern i_entity_id = ld_i_entity_id i_sel_screen = ld_i_sel_screen * is_selection_rep = ld_is_selection_rep * i_regulation_id = ld_i_regulation_id IMPORTING e_return_code = ld_e_return_code TABLES * et_message = it_et_message et_ovs_values = it_et_ovs_values . " GRPC_API_REPORT_OVS
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_return_code  TYPE INT4 ,
ld_i_session_id  TYPE GRPC_API_SESSION_ID ,
it_et_message  TYPE STANDARD TABLE OF BAPIRETTAB ,
wa_et_message  LIKE LINE OF it_et_message,
ld_i_search_pattern  TYPE GRPC_API_SEARCH_PATTERN ,
it_et_ovs_values  TYPE STANDARD TABLE OF GRPC_T_F4HELP ,
wa_et_ovs_values  LIKE LINE OF it_et_ovs_values,
ld_i_entity_id  TYPE GRPC_API_ENTITY_ID ,
ld_i_sel_screen  TYPE GRPC_REP_SEL_SCREEN ,
ld_is_selection_rep  TYPE GRPC_S_REP_SELECTION ,
ld_i_regulation_id  TYPE GRPC_API_OBJECT_ID .

ld_i_session_id = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
ld_i_search_pattern = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_ovs_values to it_et_ovs_values.
ld_i_entity_id = 'Check type of data required'.
ld_i_sel_screen = 'Check type of data required'.
ld_is_selection_rep = 'Check type of data required'.
ld_i_regulation_id = '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 GRPC_API_REPORT_OVS or its description.