SAP HRIQ_RFC_BAPI_BASIC_CHECK Function Module for CM: Standardprüfung/Sperre zu Beginn eines GETDETAIL oder CHANGE BAPIs









HRIQ_RFC_BAPI_BASIC_CHECK is a standard hriq rfc bapi basic check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CM: Standardprüfung/Sperre zu Beginn eines GETDETAIL oder CHANGE BAPIs processing and below is the pattern details for this FM, 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 rfc bapi basic check FM, simply by entering the name HRIQ_RFC_BAPI_BASIC_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRPIQ00SELFSERVICE_RFC
Program Name: SAPLHRPIQ00SELFSERVICE_RFC
Main Program: SAPLHRPIQ00SELFSERVICE_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function HRIQ_RFC_BAPI_BASIC_CHECK 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_RFC_BAPI_BASIC_CHECK'"CM: Standardprüfung/Sperre zu Beginn eines GETDETAIL oder CHANGE BAPIs
EXPORTING
IV_OTYPE = "
IV_OBJID = "
* IV_CHECK_KEYDATE = 'X' "
* IV_TESTRUN = "

IMPORTING
EV_OBJEC_BEGDA = "
EV_OBJEC_ENDDA = "
EV_MATNR = "
ET_RETURN = "

CHANGING
* CV_PLVAR = "
* CV_ISTAT = "
* CV_KEYDATE = "
.



IMPORTING Parameters details for HRIQ_RFC_BAPI_BASIC_CHECK

IV_OTYPE -

Data type: OBJEC-OTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_OBJID -

Data type: OBJEC-OBJID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CHECK_KEYDATE -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TESTRUN -

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HRIQ_RFC_BAPI_BASIC_CHECK

EV_OBJEC_BEGDA -

Data type: OBJEC-BEGDA
Optional: No
Call by Reference: No ( called with pass by value option)

EV_OBJEC_ENDDA -

Data type: OBJEC-ENDDA
Optional: No
Call by Reference: No ( called with pass by value option)

EV_MATNR -

Data type: PIQSTUDENT12
Optional: No
Call by Reference: No ( called with pass by value option)

ET_RETURN -

Data type: BAPIRET2_T
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for HRIQ_RFC_BAPI_BASIC_CHECK

CV_PLVAR -

Data type: OBJEC-PLVAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

CV_ISTAT -

Data type: OBJEC-ISTAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

CV_KEYDATE -

Data type: D
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HRIQ_RFC_BAPI_BASIC_CHECK 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_cv_plvar  TYPE OBJEC-PLVAR, "   
lv_iv_otype  TYPE OBJEC-OTYPE, "   
lv_ev_objec_begda  TYPE OBJEC-BEGDA, "   
lv_cv_istat  TYPE OBJEC-ISTAT, "   
lv_iv_objid  TYPE OBJEC-OBJID, "   
lv_ev_objec_endda  TYPE OBJEC-ENDDA, "   
lv_ev_matnr  TYPE PIQSTUDENT12, "   
lv_cv_keydate  TYPE D, "   
lv_iv_check_keydate  TYPE XFELD, "   'X'
lv_et_return  TYPE BAPIRET2_T, "   
lv_iv_testrun  TYPE XFELD. "   

  CALL FUNCTION 'HRIQ_RFC_BAPI_BASIC_CHECK'  "CM: Standardprüfung/Sperre zu Beginn eines GETDETAIL oder CHANGE BAPIs
    EXPORTING
         IV_OTYPE = lv_iv_otype
         IV_OBJID = lv_iv_objid
         IV_CHECK_KEYDATE = lv_iv_check_keydate
         IV_TESTRUN = lv_iv_testrun
    IMPORTING
         EV_OBJEC_BEGDA = lv_ev_objec_begda
         EV_OBJEC_ENDDA = lv_ev_objec_endda
         EV_MATNR = lv_ev_matnr
         ET_RETURN = lv_et_return
    CHANGING
         CV_PLVAR = lv_cv_plvar
         CV_ISTAT = lv_cv_istat
         CV_KEYDATE = lv_cv_keydate
. " HRIQ_RFC_BAPI_BASIC_CHECK




ABAP code using 7.40 inline data declarations to call FM HRIQ_RFC_BAPI_BASIC_CHECK

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 OBJEC INTO @DATA(ld_cv_plvar).
 
"SELECT single OTYPE FROM OBJEC INTO @DATA(ld_iv_otype).
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_ev_objec_begda).
 
"SELECT single ISTAT FROM OBJEC INTO @DATA(ld_cv_istat).
 
"SELECT single OBJID FROM OBJEC INTO @DATA(ld_iv_objid).
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_ev_objec_endda).
 
 
 
DATA(ld_iv_check_keydate) = 'X'.
 
 
 


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!