SAP HRIQ_EVOBJINST_RFC_GET_LIST Function Module for
HRIQ_EVOBJINST_RFC_GET_LIST is a standard hriq evobjinst rfc get list 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 evobjinst rfc get list FM, simply by entering the name HRIQ_EVOBJINST_RFC_GET_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00EVALOBJINST_RFC
Program Name: SAPLHRPIQ00EVALOBJINST_RFC
Main Program: SAPLHRPIQ00EVALOBJINST_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function HRIQ_EVOBJINST_RFC_GET_LIST 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_EVOBJINST_RFC_GET_LIST'".
EXPORTING
IV_EVOB_PLVAR = "
* IV_KEYDATE = SY-DATUM "
* IV_LANGU = SY-LANGU "
IV_EVOB_OBJID = "
* IV_ACAD_YEAR = "
* IV_ACAD_PERIOD = "
* IV_OFFERNO = "
* IV_EVENT_OBJID = "
* IV_EXAMMODE = "
* IV_EXAMORGTYPE = "
* IV_READ_TEXT = "
TABLES
* ET_EVOBOFFER = "
* ET_EVOBOFFER_RFC = "
* ET_EVOBOFFER2 = "
* ET_EVOBOFFER3 = "
* ET_MESSAGE = "
IMPORTING Parameters details for HRIQ_EVOBJINST_RFC_GET_LIST
IV_EVOB_PLVAR -
Data type: PLVAROptional: No
Call by Reference: No ( called with pass by value option)
IV_KEYDATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LANGU -
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_EVOB_OBJID -
Data type: PIQEVOB_OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_ACAD_YEAR -
Data type: PIQPERYROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ACAD_PERIOD -
Data type: PIQPERIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OFFERNO -
Data type: PIQEVOBOFFNOOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EVENT_OBJID -
Data type: PIQEXAMEVENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EXAMMODE -
Data type: PIQEXAMMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EXAMORGTYPE -
Data type: PIQEXAMORGTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_TEXT -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HRIQ_EVOBJINST_RFC_GET_LIST
ET_EVOBOFFER -
Data type: PIQEVOBOFFER_TOptional: Yes
Call by Reference: Yes
ET_EVOBOFFER_RFC -
Data type: PIQEVOBOFFER_RFC_TOptional: Yes
Call by Reference: Yes
ET_EVOBOFFER2 -
Data type: PIQEVOBOFFER2_TOptional: Yes
Call by Reference: Yes
ET_EVOBOFFER3 -
Data type: PIQEVOBOFFER3_TOptional: Yes
Call by Reference: Yes
ET_MESSAGE -
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for HRIQ_EVOBJINST_RFC_GET_LIST 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: | ||||
| lt_et_evoboffer | TYPE STANDARD TABLE OF PIQEVOBOFFER_T, " | |||
| lv_iv_evob_plvar | TYPE PLVAR, " | |||
| lv_iv_keydate | TYPE SY-DATUM, " SY-DATUM | |||
| lv_iv_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_iv_evob_objid | TYPE PIQEVOB_OBJID, " | |||
| lt_et_evoboffer_rfc | TYPE STANDARD TABLE OF PIQEVOBOFFER_RFC_T, " | |||
| lv_iv_acad_year | TYPE PIQPERYR, " | |||
| lt_et_evoboffer2 | TYPE STANDARD TABLE OF PIQEVOBOFFER2_T, " | |||
| lt_et_evoboffer3 | TYPE STANDARD TABLE OF PIQEVOBOFFER3_T, " | |||
| lv_iv_acad_period | TYPE PIQPERID, " | |||
| lt_et_message | TYPE STANDARD TABLE OF BAPIRET2_T, " | |||
| lv_iv_offerno | TYPE PIQEVOBOFFNO, " | |||
| lv_iv_event_objid | TYPE PIQEXAMEVENT, " | |||
| lv_iv_exammode | TYPE PIQEXAMMODE, " | |||
| lv_iv_examorgtype | TYPE PIQEXAMORGTYPE, " | |||
| lv_iv_read_text | TYPE FLAG. " |
|   CALL FUNCTION 'HRIQ_EVOBJINST_RFC_GET_LIST' " |
| EXPORTING | ||
| IV_EVOB_PLVAR | = lv_iv_evob_plvar | |
| IV_KEYDATE | = lv_iv_keydate | |
| IV_LANGU | = lv_iv_langu | |
| IV_EVOB_OBJID | = lv_iv_evob_objid | |
| IV_ACAD_YEAR | = lv_iv_acad_year | |
| IV_ACAD_PERIOD | = lv_iv_acad_period | |
| IV_OFFERNO | = lv_iv_offerno | |
| IV_EVENT_OBJID | = lv_iv_event_objid | |
| IV_EXAMMODE | = lv_iv_exammode | |
| IV_EXAMORGTYPE | = lv_iv_examorgtype | |
| IV_READ_TEXT | = lv_iv_read_text | |
| TABLES | ||
| ET_EVOBOFFER | = lt_et_evoboffer | |
| ET_EVOBOFFER_RFC | = lt_et_evoboffer_rfc | |
| ET_EVOBOFFER2 | = lt_et_evoboffer2 | |
| ET_EVOBOFFER3 | = lt_et_evoboffer3 | |
| ET_MESSAGE | = lt_et_message | |
| . " HRIQ_EVOBJINST_RFC_GET_LIST | ||
ABAP code using 7.40 inline data declarations to call FM HRIQ_EVOBJINST_RFC_GET_LIST
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 DATUM FROM SY INTO @DATA(ld_iv_keydate). | ||||
| DATA(ld_iv_keydate) | = SY-DATUM. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_iv_langu). | ||||
| DATA(ld_iv_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects