SAP HRIQ_ST_OBJID2PARTNER_BAPI Function Module for
HRIQ_ST_OBJID2PARTNER_BAPI is a standard hriq st objid2partner 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 st objid2partner bapi FM, simply by entering the name HRIQ_ST_OBJID2PARTNER_BAPI into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00STUDENTNUMBER2
Program Name: SAPLHRPIQ00STUDENTNUMBER2
Main Program: SAPLHRPIQ00STUDENTNUMBER2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRIQ_ST_OBJID2PARTNER_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_ST_OBJID2PARTNER_BAPI'".
EXPORTING
PLANVERSION = "
OBJECTID = "
IMPORTING
EV_PARTNER = "
ET_RETURN = "
IMPORTING Parameters details for HRIQ_ST_OBJID2PARTNER_BAPI
PLANVERSION -
Data type: BAPISTUDENT_HEAD-PLVAROptional: No
Call by Reference: Yes
OBJECTID -
Data type: BAPISTUDENT_HEAD-OBJIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HRIQ_ST_OBJID2PARTNER_BAPI
EV_PARTNER -
Data type: BAPISTUDENT_HEAD-PARTNEROptional: No
Call by Reference: Yes
ET_RETURN -
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRIQ_ST_OBJID2PARTNER_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.| DATA: | ||||
| lv_ev_partner | TYPE BAPISTUDENT_HEAD-PARTNER, " | |||
| lv_planversion | TYPE BAPISTUDENT_HEAD-PLVAR, " | |||
| lv_objectid | TYPE BAPISTUDENT_HEAD-OBJID, " | |||
| lv_et_return | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'HRIQ_ST_OBJID2PARTNER_BAPI' " |
| EXPORTING | ||
| PLANVERSION | = lv_planversion | |
| OBJECTID | = lv_objectid | |
| IMPORTING | ||
| EV_PARTNER | = lv_ev_partner | |
| ET_RETURN | = lv_et_return | |
| . " HRIQ_ST_OBJID2PARTNER_BAPI | ||
ABAP code using 7.40 inline data declarations to call FM HRIQ_ST_OBJID2PARTNER_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.| "SELECT single PARTNER FROM BAPISTUDENT_HEAD INTO @DATA(ld_ev_partner). | ||||
| "SELECT single PLVAR FROM BAPISTUDENT_HEAD INTO @DATA(ld_planversion). | ||||
| "SELECT single OBJID FROM BAPISTUDENT_HEAD INTO @DATA(ld_objectid). | ||||
Search for further information about these or an SAP related objects