SAP HRFPM_F4_OBJID_REQUEST Function Module for
HRFPM_F4_OBJID_REQUEST is a standard hrfpm f4 objid request 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 hrfpm f4 objid request FM, simply by entering the name HRFPM_F4_OBJID_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRFPM_F4_HELP_BUDGET
Program Name: SAPLHRFPM_F4_HELP_BUDGET
Main Program: SAPLHRFPM_F4_HELP_BUDGET
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRFPM_F4_OBJID_REQUEST 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 'HRFPM_F4_OBJID_REQUEST'".
EXPORTING
PLVAR = "
* OTYPE = ' ' "
* SEARK = '*' "
* DYNPRO_REPID = ' ' "
* DYNPRO_DYNNR = ' ' "
* DYNPRO_SEARKFIELD = ' ' "
* SEARK_BEGDA = SY-DATUM "
* SEARK_ENDDA = SY-DATUM "
* IV_CONTEXT_AD_HOC = ABAP_FALSE "
IMPORTING
SEL_OBJECT = "
SEL_OBJID = "
TABLES
* SEL_OBJECTS = "
IMPORTING Parameters details for HRFPM_F4_OBJID_REQUEST
PLVAR -
Data type: PLOGI-PLVAROptional: No
Call by Reference: No ( called with pass by value option)
OTYPE -
Data type: PLOGI-OTYPEDefault: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)
SEARK -
Data type: PPMAC-SEARKDefault: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DYNPRO_REPID -
Data type: SY-REPIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DYNPRO_DYNNR -
Data type: SY-DYNNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DYNPRO_SEARKFIELD -
Data type: DYNPREAD-FIELDNAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SEARK_BEGDA -
Data type: WPLOG-BEGDADefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
SEARK_ENDDA -
Data type: WPLOG-ENDDADefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONTEXT_AD_HOC -
Data type: BOOLE_DDefault: ABAP_FALSE
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for HRFPM_F4_OBJID_REQUEST
SEL_OBJECT -
Data type: OBJECOptional: No
Call by Reference: Yes
SEL_OBJID -
Data type: OBJEC-OBJIDOptional: No
Call by Reference: Yes
TABLES Parameters details for HRFPM_F4_OBJID_REQUEST
SEL_OBJECTS -
Data type: OBJECOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for HRFPM_F4_OBJID_REQUEST 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_plvar | TYPE PLOGI-PLVAR, " | |||
| lv_sel_object | TYPE OBJEC, " | |||
| lt_sel_objects | TYPE STANDARD TABLE OF OBJEC, " | |||
| lv_otype | TYPE PLOGI-OTYPE, " SPACE | |||
| lv_sel_objid | TYPE OBJEC-OBJID, " | |||
| lv_seark | TYPE PPMAC-SEARK, " '*' | |||
| lv_dynpro_repid | TYPE SY-REPID, " SPACE | |||
| lv_dynpro_dynnr | TYPE SY-DYNNR, " SPACE | |||
| lv_dynpro_searkfield | TYPE DYNPREAD-FIELDNAME, " SPACE | |||
| lv_seark_begda | TYPE WPLOG-BEGDA, " SY-DATUM | |||
| lv_seark_endda | TYPE WPLOG-ENDDA, " SY-DATUM | |||
| lv_iv_context_ad_hoc | TYPE BOOLE_D. " ABAP_FALSE |
|   CALL FUNCTION 'HRFPM_F4_OBJID_REQUEST' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| OTYPE | = lv_otype | |
| SEARK | = lv_seark | |
| DYNPRO_REPID | = lv_dynpro_repid | |
| DYNPRO_DYNNR | = lv_dynpro_dynnr | |
| DYNPRO_SEARKFIELD | = lv_dynpro_searkfield | |
| SEARK_BEGDA | = lv_seark_begda | |
| SEARK_ENDDA | = lv_seark_endda | |
| IV_CONTEXT_AD_HOC | = lv_iv_context_ad_hoc | |
| IMPORTING | ||
| SEL_OBJECT | = lv_sel_object | |
| SEL_OBJID | = lv_sel_objid | |
| TABLES | ||
| SEL_OBJECTS | = lt_sel_objects | |
| . " HRFPM_F4_OBJID_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM HRFPM_F4_OBJID_REQUEST
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 PLOGI INTO @DATA(ld_plvar). | ||||
| "SELECT single OTYPE FROM PLOGI INTO @DATA(ld_otype). | ||||
| DATA(ld_otype) | = ' '. | |||
| "SELECT single OBJID FROM OBJEC INTO @DATA(ld_sel_objid). | ||||
| "SELECT single SEARK FROM PPMAC INTO @DATA(ld_seark). | ||||
| DATA(ld_seark) | = '*'. | |||
| "SELECT single REPID FROM SY INTO @DATA(ld_dynpro_repid). | ||||
| DATA(ld_dynpro_repid) | = ' '. | |||
| "SELECT single DYNNR FROM SY INTO @DATA(ld_dynpro_dynnr). | ||||
| DATA(ld_dynpro_dynnr) | = ' '. | |||
| "SELECT single FIELDNAME FROM DYNPREAD INTO @DATA(ld_dynpro_searkfield). | ||||
| DATA(ld_dynpro_searkfield) | = ' '. | |||
| "SELECT single BEGDA FROM WPLOG INTO @DATA(ld_seark_begda). | ||||
| DATA(ld_seark_begda) | = SY-DATUM. | |||
| "SELECT single ENDDA FROM WPLOG INTO @DATA(ld_seark_endda). | ||||
| DATA(ld_seark_endda) | = SY-DATUM. | |||
| DATA(ld_iv_context_ad_hoc) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects