HRIQ_BAPI_EXTENSION_GET SAP Function module

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

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

Pattern for FM HRIQ_BAPI_EXTENSION_GET - HRIQ BAPI EXTENSION GET

CALL FUNCTION 'HRIQ_BAPI_EXTENSION_GET' "
  EXPORTING
    iv_bapi_te_name =           " bapiparex-structure
*   iv_bapi_te_namex =          " bapiparex-structure
    iv_objid =                  " wplog-objid
    iv_plvar =                  " wplog-plvar
    iv_otype =                  " wplog-otype
*   iv_subty =                  " wplog-subty
    it_extension =              " bapiparex_t
*   iv_message_store = 'X'      " piqflag
*   iv_log_handle =             " cl_hrpiq00_errorhandler
  IMPORTING
    es_bapi_te_data =           " bapiparex
    es_bapi_te_datax =          " bapiparex
    et_return =                 " bapiret2_t
    ev_found =                  " piqflag
    .  "  HRIQ_BAPI_EXTENSION_GET

ABAP code example for Function Module HRIQ_BAPI_EXTENSION_GET

The ABAP code below is a full code listing to execute function module HRIQ_BAPI_EXTENSION_GET 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_es_bapi_te_data  
 
 TYPE BAPIPAREX
,
ld_es_bapi_te_datax  
 
 TYPE BAPIPAREX
,
ld_et_return  
 
 TYPE BAPIRET2_T
,
ld_ev_found  
 
 TYPE PIQFLAG
.



DATA(ld_iv_bapi_te_name) = some text here


DATA(ld_iv_bapi_te_namex) = some text here


DATA(ld_iv_objid) = Check type of data required


DATA(ld_iv_plvar) = some text here


DATA(ld_iv_otype) = some text here


DATA(ld_iv_subty) = some text here

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

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

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

CALL FUNCTION 'HRIQ_BAPI_EXTENSION_GET'
  EXPORTING
    iv_bapi_te_name =            ld_iv_bapi_te_name
*   iv_bapi_te_namex =           ld_iv_bapi_te_namex
    iv_objid =                   ld_iv_objid
    iv_plvar =                   ld_iv_plvar
    iv_otype =                   ld_iv_otype
*   iv_subty =                   ld_iv_subty
    it_extension =               ld_it_extension
*   iv_message_store =           ld_iv_message_store
*   iv_log_handle =              ld_iv_log_handle
  IMPORTING
    es_bapi_te_data =            ld_es_bapi_te_data
    es_bapi_te_datax =           ld_es_bapi_te_datax
    et_return =                  ld_et_return
    ev_found =                   ld_ev_found
    .  "  HRIQ_BAPI_EXTENSION_GET

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_es_bapi_te_data
 
 TYPE BAPIPAREX ,
ld_iv_bapi_te_name
 
 TYPE BAPIPAREX-STRUCTURE ,
ld_es_bapi_te_datax
 
 TYPE BAPIPAREX ,
ld_iv_bapi_te_namex
 
 TYPE BAPIPAREX-STRUCTURE ,
ld_et_return
 
 TYPE BAPIRET2_T ,
ld_iv_objid
 
 TYPE WPLOG-OBJID ,
ld_ev_found
 
 TYPE PIQFLAG ,
ld_iv_plvar
 
 TYPE WPLOG-PLVAR ,
ld_iv_otype
 
 TYPE WPLOG-OTYPE ,
ld_iv_subty
 
 TYPE WPLOG-SUBTY ,
ld_it_extension
 
 TYPE BAPIPAREX_T ,
ld_iv_message_store
 
 TYPE PIQFLAG ,
ld_iv_log_handle
 
 TYPE CL_HRPIQ00_ERRORHANDLER .



ld_iv_bapi_te_name = some text here

ld_iv_bapi_te_namex = some text here

ld_iv_objid = Check type of data required

ld_iv_plvar = some text here

ld_iv_otype = some text here

ld_iv_subty = some text here
ld_it_extension = 'Check type of data required'.
ld_iv_message_store = 'Check type of data required'.
ld_iv_log_handle = 'Check type of data required'.