SAP BUDGET_TEXT_GET Function Module for Get Budget Text









BUDGET_TEXT_GET is a standard budget text get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Budget Text processing and below is the pattern details for this FM, 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 budget text get FM, simply by entering the name BUDGET_TEXT_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function BUDGET_TEXT_GET 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 'BUDGET_TEXT_GET'"Get Budget Text
EXPORTING
* I_T_ADDRESS_DIMPART = "Table with FM account assignments
* I_GRANT_NBR = "Grant
I_APPLIC = "Application
I_FM_AREA = "Financial Management Area
I_BUDCAT = "Budget category
I_VERSION = "Budget version
I_FISCYEAR = "Fiscal Year
I_BUDTYPE = "Budget Type
* I_S_ADDRESS_DIMTABS = "Select options for dimensions
* I_ADDRESS_OBJNR = "Object number for FM budgeting and AVC

IMPORTING
E_FMBUDTXT = "Budget texts register

TABLES
* E_T_VFMBUDTXT = "Generated Table for View V_FMBUDTXT

EXCEPTIONS
NO_SUCCESFUL_SELECTION = 1
.



IMPORTING Parameters details for BUDGET_TEXT_GET

I_T_ADDRESS_DIMPART - Table with FM account assignments

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

I_GRANT_NBR - Grant

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

I_APPLIC - Application

Data type: BUKU_APPLIC
Optional: No
Call by Reference: Yes

I_FM_AREA - Financial Management Area

Data type: FIKRS
Optional: No
Call by Reference: Yes

I_BUDCAT - Budget category

Data type: BUKU_BUDCAT
Optional: No
Call by Reference: Yes

I_VERSION - Budget version

Data type: BUKU_VERSION
Optional: No
Call by Reference: Yes

I_FISCYEAR - Fiscal Year

Data type: BUKU_FISCYEAR
Optional: No
Call by Reference: Yes

I_BUDTYPE - Budget Type

Data type: BUKU_BUDTYPE
Optional: No
Call by Reference: Yes

I_S_ADDRESS_DIMTABS - Select options for dimensions

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

I_ADDRESS_OBJNR - Object number for FM budgeting and AVC

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

EXPORTING Parameters details for BUDGET_TEXT_GET

E_FMBUDTXT - Budget texts register

Data type: FMBUDTXT
Optional: No
Call by Reference: Yes

TABLES Parameters details for BUDGET_TEXT_GET

E_T_VFMBUDTXT - Generated Table for View V_FMBUDTXT

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

EXCEPTIONS details

NO_SUCCESFUL_SELECTION - The selection returns no values

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUDGET_TEXT_GET 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_e_fmbudtxt  TYPE FMBUDTXT, "   
lt_e_t_vfmbudtxt  TYPE STANDARD TABLE OF V_FMBUDTXT, "   
lv_i_t_address_dimpart  TYPE FMKU_T_DIMPART, "   
lv_no_succesful_selection  TYPE FMKU_T_DIMPART, "   
lv_i_grant_nbr  TYPE GM_GRANT_NBR, "   
lv_i_applic  TYPE BUKU_APPLIC, "   
lv_i_fm_area  TYPE FIKRS, "   
lv_i_budcat  TYPE BUKU_BUDCAT, "   
lv_i_version  TYPE BUKU_VERSION, "   
lv_i_fiscyear  TYPE BUKU_FISCYEAR, "   
lv_i_budtype  TYPE BUKU_BUDTYPE, "   
lv_i_s_address_dimtabs  TYPE FMBS_S_DIMSELTABS, "   
lv_i_address_objnr  TYPE BUBAS_OBJNR. "   

  CALL FUNCTION 'BUDGET_TEXT_GET'  "Get Budget Text
    EXPORTING
         I_T_ADDRESS_DIMPART = lv_i_t_address_dimpart
         I_GRANT_NBR = lv_i_grant_nbr
         I_APPLIC = lv_i_applic
         I_FM_AREA = lv_i_fm_area
         I_BUDCAT = lv_i_budcat
         I_VERSION = lv_i_version
         I_FISCYEAR = lv_i_fiscyear
         I_BUDTYPE = lv_i_budtype
         I_S_ADDRESS_DIMTABS = lv_i_s_address_dimtabs
         I_ADDRESS_OBJNR = lv_i_address_objnr
    IMPORTING
         E_FMBUDTXT = lv_e_fmbudtxt
    TABLES
         E_T_VFMBUDTXT = lt_e_t_vfmbudtxt
    EXCEPTIONS
        NO_SUCCESFUL_SELECTION = 1
. " BUDGET_TEXT_GET




ABAP code using 7.40 inline data declarations to call FM BUDGET_TEXT_GET

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



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!