SAP RH_PM_BUDGET_CREATE Function Module for









RH_PM_BUDGET_CREATE is a standard rh pm budget create 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 create FM, simply by entering the name RH_PM_BUDGET_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHB1
Program Name: SAPLRHB1
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RH_PM_BUDGET_CREATE 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_CREATE'"
  EXPORTING
   PLVAR =  "
*  FINYR =  "
*  INTEGRATED =  "
*  BSTAT = '1' "
   OTYPE =  "
   OBJID =  "
   BEGDA =  "
   ENDDA =  "
*  STATUS = '1' "
   REL_OTYPE =  "
   REL_OBJID =  "
*  VTASK = 'B' "

 IMPORTING
   OBJID =  "
   E_BEGDA =  "
   E_ENDDA =  "

EXCEPTIONS
   CANCEL = 1    NO_INSERT = 2    NO_AUTH = 3
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLRHB1_001 User-Defined Modification of 'Overall Budget' Menu
EXIT_SAPLRHB1_002 User-Defined Enhancement of 'Overall Budget' Menu
EXIT_SAPLRHB1_003 User-Defined Enhancement of 'Overall Budget' Menu
EXIT_SAPLRHB1_004 User-Defined Enhancement of 'Overall Budget' List

IMPORTING Parameters details for RH_PM_BUDGET_CREATE

PLVAR -

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

FINYR -

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

INTEGRATED -

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

BSTAT -

Data type: P1500-BSTAT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OTYPE -

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

OBJID -

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

BEGDA -

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

ENDDA -

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

STATUS -

Data type: P1000-ISTAT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

REL_OTYPE -

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

REL_OBJID -

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

VTASK -

Data type: HRRHAP-VTASK
Default: 'B'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RH_PM_BUDGET_CREATE

OBJID -

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

E_BEGDA -

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

E_ENDDA -

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

EXCEPTIONS details

CANCEL -

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

NO_INSERT -

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

NO_AUTH -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RH_PM_BUDGET_CREATE 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_objid  TYPE P1000-OBJID, "   
lv_plvar  TYPE P1000-PLVAR, "   
lv_cancel  TYPE P1000, "   
lv_finyr  TYPE T7PM9-FINYR, "   
lv_integrated  TYPE P1000-HISTO, "   
lv_bstat  TYPE P1500-BSTAT, "   '1'
lv_otype  TYPE P1000-OTYPE, "   
lv_e_begda  TYPE P1000-BEGDA, "   
lv_no_insert  TYPE P1000, "   
lv_objid  TYPE P1000-OBJID, "   
lv_e_endda  TYPE P1000-ENDDA, "   
lv_no_auth  TYPE P1000, "   
lv_begda  TYPE P1000-BEGDA, "   
lv_endda  TYPE P1000-ENDDA, "   
lv_status  TYPE P1000-ISTAT, "   '1'
lv_rel_otype  TYPE P1000-OTYPE, "   
lv_rel_objid  TYPE P1000-OBJID, "   
lv_vtask  TYPE HRRHAP-VTASK. "   'B'

  CALL FUNCTION 'RH_PM_BUDGET_CREATE'  "
    EXPORTING
         PLVAR = lv_plvar
         FINYR = lv_finyr
         INTEGRATED = lv_integrated
         BSTAT = lv_bstat
         OTYPE = lv_otype
         OBJID = lv_objid
         BEGDA = lv_begda
         ENDDA = lv_endda
         STATUS = lv_status
         REL_OTYPE = lv_rel_otype
         REL_OBJID = lv_rel_objid
         VTASK = lv_vtask
    IMPORTING
         OBJID = lv_objid
         E_BEGDA = lv_e_begda
         E_ENDDA = lv_e_endda
    EXCEPTIONS
        CANCEL = 1
        NO_INSERT = 2
        NO_AUTH = 3
. " RH_PM_BUDGET_CREATE




ABAP code using 7.40 inline data declarations to call FM RH_PM_BUDGET_CREATE

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 OBJID FROM P1000 INTO @DATA(ld_objid).
 
"SELECT single PLVAR FROM P1000 INTO @DATA(ld_plvar).
 
 
"SELECT single FINYR FROM T7PM9 INTO @DATA(ld_finyr).
 
"SELECT single HISTO FROM P1000 INTO @DATA(ld_integrated).
 
"SELECT single BSTAT FROM P1500 INTO @DATA(ld_bstat).
DATA(ld_bstat) = '1'.
 
"SELECT single OTYPE FROM P1000 INTO @DATA(ld_otype).
 
"SELECT single BEGDA FROM P1000 INTO @DATA(ld_e_begda).
 
 
"SELECT single OBJID FROM P1000 INTO @DATA(ld_objid).
 
"SELECT single ENDDA FROM P1000 INTO @DATA(ld_e_endda).
 
 
"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).
DATA(ld_status) = '1'.
 
"SELECT single OTYPE FROM P1000 INTO @DATA(ld_rel_otype).
 
"SELECT single OBJID FROM P1000 INTO @DATA(ld_rel_objid).
 
"SELECT single VTASK FROM HRRHAP INTO @DATA(ld_vtask).
DATA(ld_vtask) = 'B'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!