SAP HRFPM_BUDGET_OBJID_REQUEST Function Module for

Search SAP Function Modules

HRFPM_BUDGET_OBJID_REQUEST is a standard hrfpm 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 hrfpm budget objid request FM, simply by entering the name HRFPM_BUDGET_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_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 'HRFPM_BUDGET_OBJID_REQUEST'"
  EXPORTING
   PLVAR =  "Plan Variant
*  SHOW_HHM = 'X' "
*  OTYPE =  "Object Type
*  OBJID =  "Object ID
*  BEGDA =  "Start Date
*  ENDDA =  "End Date
*  ISTAT =  "Planning Status
*  SHOW_PURPOSE =  "
*  USE_RESTRICT_TAB =  "General Flag
*  BUTYP =  "

 IMPORTING
   RETURN_OBJID =  "Object ID

TABLES
*  RESTRICT_TAB =  "Restriction for structure search

EXCEPTIONS
   OCX_SEARCH_NOT_ACTIVE = 1    CANCEL = 2    NOTHING_FOUND = 3    PROCESSING_ERROR = 4 

.

IMPORTING Parameters details for HRFPM_BUDGET_OBJID_REQUEST

PLVAR - Plan Variant

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

SHOW_HHM -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

OTYPE - Object Type

Data type: P1000-OTYPE
Optional: Yes
Call by Reference: Yes

OBJID - Object ID

Data type: P1000-OBJID
Optional: Yes
Call by Reference: Yes

BEGDA - Start Date

Data type: P1000-BEGDA
Optional: Yes
Call by Reference: Yes

ENDDA - End Date

Data type: P1000-ENDDA
Optional: Yes
Call by Reference: Yes

ISTAT - Planning Status

Data type: P1000-ISTAT
Optional: Yes
Call by Reference: Yes

SHOW_PURPOSE -

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

USE_RESTRICT_TAB - General Flag

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

BUTYP -

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

EXPORTING Parameters details for HRFPM_BUDGET_OBJID_REQUEST

RETURN_OBJID - Object ID

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

TABLES Parameters details for HRFPM_BUDGET_OBJID_REQUEST

RESTRICT_TAB - Restriction for structure search

Data type: PMRESTRICT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OCX_SEARCH_NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANCEL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOTHING_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PROCESSING_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

ABAP code using 7.40 inline data declarations to call FM HRFPM_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.

Search for further information about these or an SAP related objects