SAP HRIQ_CHECK_VALID_INFT_OBJ_BAPI Function Module for

Search SAP Function Modules

HRIQ_CHECK_VALID_INFT_OBJ_BAPI is a standard hriq check valid inft obj bapi 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 check valid inft obj bapi FM, simply by entering the name HRIQ_CHECK_VALID_INFT_OBJ_BAPI 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_CHECK_VALID_INFT_OBJ_BAPI 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_CHECK_VALID_INFT_OBJ_BAPI'"
  EXPORTING
   IV_PLVAR =  "
   IV_OTYPE =  "
   IV_OBJID =  "
   IV_ISTAT =  "
   IV_INFTY =  "
*  IV_FIELD_FOR_BEGDA = 'BEGDA'  '#EC NOTEXT "
*  IV_FIELD_FOR_ENDDA = 'ENDDA' '#EC NOTEXT "
*  IS_PIQPPPAR =  "

 IMPORTING
   EV_OBJEC_BEGDA =  "
   EV_OBJEC_ENDDA =  "
   ET_RETURN =  "

CHANGING
   CV_INFTY_BEGDA =  "
   CV_INFTY_ENDDA =  "

.

IMPORTING Parameters details for HRIQ_CHECK_VALID_INFT_OBJ_BAPI

IV_PLVAR -

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

IV_OTYPE -

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

IV_OBJID -

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

IV_ISTAT -

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

IV_INFTY -

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

IV_FIELD_FOR_BEGDA -

Data type: BAPIRET2-FIELD
Default: 'BEGDA' '#EC NOTEXT
Optional: Yes
Call by Reference: Yes

IV_FIELD_FOR_ENDDA -

Data type: BAPIRET2-FIELD
Default: 'ENDDA' '#EC NOTEXT
Optional: Yes
Call by Reference: Yes

IS_PIQPPPAR -

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

EXPORTING Parameters details for HRIQ_CHECK_VALID_INFT_OBJ_BAPI

EV_OBJEC_BEGDA -

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

EV_OBJEC_ENDDA -

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

ET_RETURN -

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

CHANGING Parameters details for HRIQ_CHECK_VALID_INFT_OBJ_BAPI

CV_INFTY_BEGDA -

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

CV_INFTY_ENDDA -

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

Copy and paste ABAP code example for HRIQ_CHECK_VALID_INFT_OBJ_BAPI 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.

ABAP code using 7.40 inline data declarations to call FM HRIQ_CHECK_VALID_INFT_OBJ_BAPI

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.

Search for further information about these or an SAP related objects