SAP HRIQ_BAPI_INFTY_INSERT Function Module for









HRIQ_BAPI_INFTY_INSERT is a standard hriq bapi infty insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for hriq bapi infty insert FM, simply by entering the name HRIQ_BAPI_INFTY_INSERT into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRPIQ00BAPISERVICE
Program Name: SAPLHRPIQ00BAPISERVICE
Main Program: SAPLHRPIQ00BAPISERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HRIQ_BAPI_INFTY_INSERT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'HRIQ_BAPI_INFTY_INSERT'"
EXPORTING
IV_PLVAR = "
* IS_BAPI_TE_DATA = "
* IV_MESSAGE_STORE = 'X' "
* IV_TESTRUN = ' ' "
* IV_LOG_HANDLE = "
IV_OBJID = "
IV_BEGDA = "
IV_ENDDA = "
IV_OTYPE = "
IV_INFTY = "
* IV_COUNTER = "
IS_BAPI_DATA = "
IV_BAPI_STRU = "

IMPORTING
ET_RETURN = "
.



IMPORTING Parameters details for HRIQ_BAPI_INFTY_INSERT

IV_PLVAR -

Data type: PLOG-PLVAR
Optional: No
Call by Reference: Yes

IS_BAPI_TE_DATA -

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

IV_MESSAGE_STORE -

Data type: PIQFLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_TESTRUN -

Data type: TESTRUN
Default: ' '
Optional: Yes
Call by Reference: Yes

IV_LOG_HANDLE -

Data type: CL_HRPIQ00_ERRORHANDLER
Optional: Yes
Call by Reference: Yes

IV_OBJID -

Data type: PLOG-OBJID
Optional: No
Call by Reference: Yes

IV_BEGDA -

Data type: PLOG-BEGDA
Optional: No
Call by Reference: Yes

IV_ENDDA -

Data type: PLOG-ENDDA
Optional: No
Call by Reference: Yes

IV_OTYPE -

Data type: PLOG-OTYPE
Optional: No
Call by Reference: Yes

IV_INFTY -

Data type: PLOG-INFTY
Optional: No
Call by Reference: Yes

IV_COUNTER -

Data type: I
Optional: Yes
Call by Reference: Yes

IS_BAPI_DATA -

Data type:
Optional: No
Call by Reference: Yes

IV_BAPI_STRU -

Data type: STRUKNAME
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for HRIQ_BAPI_INFTY_INSERT

ET_RETURN -

Data type: BAPIRET2_T
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRIQ_BAPI_INFTY_INSERT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_iv_plvar  TYPE PLOG-PLVAR, "   
lv_et_return  TYPE BAPIRET2_T, "   
lv_is_bapi_te_data  TYPE BAPIPAREX, "   
lv_iv_message_store  TYPE PIQFLAG, "   'X'
lv_iv_testrun  TYPE TESTRUN, "   ' '
lv_iv_log_handle  TYPE CL_HRPIQ00_ERRORHANDLER, "   
lv_iv_objid  TYPE PLOG-OBJID, "   
lv_iv_begda  TYPE PLOG-BEGDA, "   
lv_iv_endda  TYPE PLOG-ENDDA, "   
lv_iv_otype  TYPE PLOG-OTYPE, "   
lv_iv_infty  TYPE PLOG-INFTY, "   
lv_iv_counter  TYPE I, "   
lv_is_bapi_data  TYPE I, "   
lv_iv_bapi_stru  TYPE STRUKNAME. "   

  CALL FUNCTION 'HRIQ_BAPI_INFTY_INSERT'  "
    EXPORTING
         IV_PLVAR = lv_iv_plvar
         IS_BAPI_TE_DATA = lv_is_bapi_te_data
         IV_MESSAGE_STORE = lv_iv_message_store
         IV_TESTRUN = lv_iv_testrun
         IV_LOG_HANDLE = lv_iv_log_handle
         IV_OBJID = lv_iv_objid
         IV_BEGDA = lv_iv_begda
         IV_ENDDA = lv_iv_endda
         IV_OTYPE = lv_iv_otype
         IV_INFTY = lv_iv_infty
         IV_COUNTER = lv_iv_counter
         IS_BAPI_DATA = lv_is_bapi_data
         IV_BAPI_STRU = lv_iv_bapi_stru
    IMPORTING
         ET_RETURN = lv_et_return
. " HRIQ_BAPI_INFTY_INSERT




ABAP code using 7.40 inline data declarations to call FM HRIQ_BAPI_INFTY_INSERT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single PLVAR FROM PLOG INTO @DATA(ld_iv_plvar).
 
 
 
DATA(ld_iv_message_store) = 'X'.
 
DATA(ld_iv_testrun) = ' '.
 
 
"SELECT single OBJID FROM PLOG INTO @DATA(ld_iv_objid).
 
"SELECT single BEGDA FROM PLOG INTO @DATA(ld_iv_begda).
 
"SELECT single ENDDA FROM PLOG INTO @DATA(ld_iv_endda).
 
"SELECT single OTYPE FROM PLOG INTO @DATA(ld_iv_otype).
 
"SELECT single INFTY FROM PLOG INTO @DATA(ld_iv_infty).
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!