SAP FMAVC_GET_FILTER_SETTINGS_BUD Function Module for Determine filter settings for FM budget values (AVC)

Search SAP Function Modules

FMAVC_GET_FILTER_SETTINGS_BUD is a standard fmavc get filter settings bud SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine filter settings for FM budget values (AVC) 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 fmavc get filter settings bud FM, simply by entering the name FMAVC_GET_FILTER_SETTINGS_BUD into the relevant SAP transaction such as SE37 or SE38.

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

Function FMAVC_GET_FILTER_SETTINGS_BUD 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 'FMAVC_GET_FILTER_SETTINGS_BUD'"Determine filter settings for FM budget values (AVC)
  EXPORTING
   I_ALDNR =  "Availability ledger
   I_ARCTY =  "Record Type
   I_FM_AREA =  "Financial management area
   I_FISCYEAR =  "Fiscal year
*  I_FUND =  "Fund
*  I_FLG_BYPASS_BUFFER = ' ' "Flag: By-pass local buffer
*  I_FLG_TAKE_DEFAULT = 'X' "Flag: Take default values

 IMPORTING
   E_S_FILTER_HEADER =  "AVC filter settings for FM budget values: header entries
   E_T_VALBUD_TYPE =  "Value type - Budget type

EXCEPTIONS
   ERROR_FILTER_DATA = 1 

.

IMPORTING Parameters details for FMAVC_GET_FILTER_SETTINGS_BUD

I_ALDNR - Availability ledger

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

I_ARCTY - Record Type

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

I_FM_AREA - Financial management area

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

I_FISCYEAR - Fiscal year

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

I_FUND - Fund

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

I_FLG_BYPASS_BUFFER - Flag: By-pass local buffer

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: Yes

I_FLG_TAKE_DEFAULT - Flag: Take default values

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

EXPORTING Parameters details for FMAVC_GET_FILTER_SETTINGS_BUD

E_S_FILTER_HEADER - AVC filter settings for FM budget values: header entries

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

E_T_VALBUD_TYPE - Value type - Budget type

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

EXCEPTIONS details

ERROR_FILTER_DATA - Table entry either missing or inconsistent

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

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

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