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

Function RH_PM_BUDGET_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 'RH_PM_BUDGET_OBJID_REQUEST'".
EXPORTING
PLVAR = "
* SHOW_HHM = 'X' "
* OTYPE = "
* OBJID = "
* BEGDA = "
* ENDDA = "
* ISTAT = "
* SHOW_PURPOSE = "
* USE_RESTRICT_TAB = "
* BUTYP = "
IMPORTING
RETURN_OBJID = "
TABLES
* RESTRICT_TAB = "
EXCEPTIONS
OCX_SEARCH_NOT_ACTIVE = 1 CANCEL = 2 NOTHING_FOUND = 3 PROCESSING_ERROR = 4
IMPORTING Parameters details for RH_PM_BUDGET_OBJID_REQUEST
PLVAR -
Data type: P1000-PLVAROptional: No
Call by Reference: Yes
SHOW_HHM -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
OTYPE -
Data type: P1000-OTYPEOptional: Yes
Call by Reference: Yes
OBJID -
Data type: P1000-OBJIDOptional: Yes
Call by Reference: Yes
BEGDA -
Data type: P1000-BEGDAOptional: Yes
Call by Reference: Yes
ENDDA -
Data type: P1000-ENDDAOptional: Yes
Call by Reference: Yes
ISTAT -
Data type: P1000-ISTATOptional: Yes
Call by Reference: Yes
SHOW_PURPOSE -
Data type: FLAGOptional: Yes
Call by Reference: Yes
USE_RESTRICT_TAB -
Data type: FLAGOptional: Yes
Call by Reference: Yes
BUTYP -
Data type: BUTYPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RH_PM_BUDGET_OBJID_REQUEST
RETURN_OBJID -
Data type: P1000-OBJIDOptional: No
Call by Reference: Yes
TABLES Parameters details for RH_PM_BUDGET_OBJID_REQUEST
RESTRICT_TAB -
Data type: PMRESTRICTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
OCX_SEARCH_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
CANCEL -
Data type:Optional: No
Call by Reference: Yes
NOTHING_FOUND -
Data type:Optional: No
Call by Reference: Yes
PROCESSING_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RH_PM_BUDGET_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 P1000-PLVAR, " | |||
| lt_restrict_tab | TYPE STANDARD TABLE OF PMRESTRICT, " | |||
| lv_return_objid | TYPE P1000-OBJID, " | |||
| lv_ocx_search_not_active | TYPE P1000, " | |||
| lv_show_hhm | TYPE FLAG, " 'X' | |||
| lv_otype | TYPE P1000-OTYPE, " | |||
| lv_cancel | TYPE P1000, " | |||
| lv_objid | TYPE P1000-OBJID, " | |||
| lv_nothing_found | TYPE P1000, " | |||
| lv_begda | TYPE P1000-BEGDA, " | |||
| lv_processing_error | TYPE P1000, " | |||
| lv_endda | TYPE P1000-ENDDA, " | |||
| lv_istat | TYPE P1000-ISTAT, " | |||
| lv_show_purpose | TYPE FLAG, " | |||
| lv_use_restrict_tab | TYPE FLAG, " | |||
| lv_butyp | TYPE BUTYP. " |
|   CALL FUNCTION 'RH_PM_BUDGET_OBJID_REQUEST' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| SHOW_HHM | = lv_show_hhm | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| ISTAT | = lv_istat | |
| SHOW_PURPOSE | = lv_show_purpose | |
| USE_RESTRICT_TAB | = lv_use_restrict_tab | |
| BUTYP | = lv_butyp | |
| IMPORTING | ||
| RETURN_OBJID | = lv_return_objid | |
| TABLES | ||
| RESTRICT_TAB | = lt_restrict_tab | |
| EXCEPTIONS | ||
| OCX_SEARCH_NOT_ACTIVE = 1 | ||
| CANCEL = 2 | ||
| NOTHING_FOUND = 3 | ||
| PROCESSING_ERROR = 4 | ||
| . " RH_PM_BUDGET_OBJID_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM RH_PM_BUDGET_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 P1000 INTO @DATA(ld_plvar). | ||||
| "SELECT single OBJID FROM P1000 INTO @DATA(ld_return_objid). | ||||
| DATA(ld_show_hhm) | = 'X'. | |||
| "SELECT single OTYPE FROM P1000 INTO @DATA(ld_otype). | ||||
| "SELECT single OBJID FROM P1000 INTO @DATA(ld_objid). | ||||
| "SELECT single BEGDA FROM P1000 INTO @DATA(ld_begda). | ||||
| "SELECT single ENDDA FROM P1000 INTO @DATA(ld_endda). | ||||
| "SELECT single ISTAT FROM P1000 INTO @DATA(ld_istat). | ||||
Search for further information about these or an SAP related objects