SAP BSP_BUFFER Function Module for

Search SAP Function Modules

BSP_BUFFER is a standard bsp buffer 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 bsp buffer FM, simply by entering the name BSP_BUFFER into the relevant SAP transaction such as SE37 or SE38.

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

Function BSP_BUFFER 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 'BSP_BUFFER'"
  EXPORTING
*  I_FISC_YEAR =  "
*  I_FM_AREA =  "
*  I_F_INDEX =  "
*  I_USE_MTHD_FILL =  "
*  I_USE_MTHD_GET =  "
*  I_USE_MTHD_CHECK =  "
*  I_USE_MTHD_DEL =  "
*  I_FLG_ALL =  "

 IMPORTING
   E_T_BUDGET_OBJECTS =  "

CHANGING
*  C_T_INDEX =  "

TABLES
*  T_RANGE_FIPEX =  "
*  T_RANGE_FICTR =  "
*  T_RANGE_FONDS =  "

EXCEPTIONS
   NOT_IN_BUFFER = 1 

.

IMPORTING Parameters details for BSP_BUFFER

I_FISC_YEAR -

Data type: FM01UD-GJAHR
Optional: Yes
Call by Reference: Yes

I_FM_AREA -

Data type: FM01UD-FIKRS
Optional: Yes
Call by Reference: Yes

I_F_INDEX -

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

I_USE_MTHD_FILL -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

I_USE_MTHD_GET -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

I_USE_MTHD_CHECK -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

I_USE_MTHD_DEL -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

I_FLG_ALL -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BSP_BUFFER

E_T_BUDGET_OBJECTS -

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

CHANGING Parameters details for BSP_BUFFER

C_T_INDEX -

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

TABLES Parameters details for BSP_BUFFER

T_RANGE_FIPEX -

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

T_RANGE_FICTR -

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

T_RANGE_FONDS -

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

EXCEPTIONS details

NOT_IN_BUFFER -

Data type:
Optional: No
Call by Reference: Yes

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

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