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

Function HRFPM_BUDGET_PROVIDE 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_PROVIDE'".
EXPORTING
PLVAR = "
OBJID = "
BEGDA = "
ENDDA = "
STATUS = "
FCODE = "
* FIN_OTYPE = "Object Type
* FIN_OBJID = "Object ID
EXCEPTIONS
NOT_FOUND = 1 CANCEL = 2 KACTIV_ERROR = 3 ENQUEUE_ERROR = 4 NO_EXPENDITURE_TYPE = 5 ACTIVE_INTEGRATION = 6
IMPORTING Parameters details for HRFPM_BUDGET_PROVIDE
PLVAR -
Data type: P1000-PLVAROptional: No
Call by Reference: No ( called with pass by value option)
OBJID -
Data type: P1000-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
BEGDA -
Data type: P1000-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
ENDDA -
Data type: P1000-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
STATUS -
Data type: P1000-ISTATOptional: No
Call by Reference: No ( called with pass by value option)
FCODE -
Data type: T77FC-FCODEOptional: No
Call by Reference: No ( called with pass by value option)
FIN_OTYPE - Object Type
Data type: OTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
FIN_OBJID - Object ID
Data type: OBJEKTIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
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)
KACTIV_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_EXPENDITURE_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTIVE_INTEGRATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRFPM_BUDGET_PROVIDE 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, " | |||
| lv_not_found | TYPE P1000, " | |||
| lv_objid | TYPE P1000-OBJID, " | |||
| lv_cancel | TYPE P1000, " | |||
| lv_begda | TYPE P1000-BEGDA, " | |||
| lv_kactiv_error | TYPE P1000, " | |||
| lv_endda | TYPE P1000-ENDDA, " | |||
| lv_enqueue_error | TYPE P1000, " | |||
| lv_status | TYPE P1000-ISTAT, " | |||
| lv_no_expenditure_type | TYPE P1000, " | |||
| lv_fcode | TYPE T77FC-FCODE, " | |||
| lv_active_integration | TYPE T77FC, " | |||
| lv_fin_otype | TYPE OTYPE, " | |||
| lv_fin_objid | TYPE OBJEKTID. " |
|   CALL FUNCTION 'HRFPM_BUDGET_PROVIDE' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| OBJID | = lv_objid | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| STATUS | = lv_status | |
| FCODE | = lv_fcode | |
| FIN_OTYPE | = lv_fin_otype | |
| FIN_OBJID | = lv_fin_objid | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| CANCEL = 2 | ||
| KACTIV_ERROR = 3 | ||
| ENQUEUE_ERROR = 4 | ||
| NO_EXPENDITURE_TYPE = 5 | ||
| ACTIVE_INTEGRATION = 6 | ||
| . " HRFPM_BUDGET_PROVIDE | ||
ABAP code using 7.40 inline data declarations to call FM HRFPM_BUDGET_PROVIDE
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_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_status). | ||||
| "SELECT single FCODE FROM T77FC INTO @DATA(ld_fcode). | ||||
Search for further information about these or an SAP related objects