SAP BUP_BUFFER_GET Function Module for

Search SAP Function Modules

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

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

Function BUP_BUFFER_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 'BUP_BUFFER_GET'"
  EXPORTING
   I_PARTNER =  "Business Partner Number
*  I_VALDT = '00000000' "Validity Date

 IMPORTING
   E_BUT000_STAT =  "
   E_BUT100_STAT =  "
   E_BUT0CC_STAT =  "
   E_BUT0BK_STAT =  "
   E_BUT020_STAT =  "
   E_BUT021_FS_STAT =  "
   E_BUT000 =  "BP: General data I

TABLES
*  T_BUT0BK =  "BP: Bank details
*  T_BUT0CC =  "BP: Payment Cards
*  T_BUT020 =  "BP: Addresses
*  T_BUT021_FS =  "Time-Dependent Address Usage
*  T_BUT100 =  "BP: Roles
*  T_BUT000 =  "
*  T_BUT000_TD =  "

.

IMPORTING Parameters details for BUP_BUFFER_GET

I_PARTNER - Business Partner Number

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

I_VALDT - Validity Date

Data type: SY-DATLO
Default: '00000000'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BUP_BUFFER_GET

E_BUT000_STAT -

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

E_BUT100_STAT -

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

E_BUT0CC_STAT -

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

E_BUT0BK_STAT -

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

E_BUT020_STAT -

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

E_BUT021_FS_STAT -

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

E_BUT000 - BP: General data I

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

TABLES Parameters details for BUP_BUFFER_GET

T_BUT0BK - BP: Bank details

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

T_BUT0CC - BP: Payment Cards

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

T_BUT020 - BP: Addresses

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

T_BUT021_FS - Time-Dependent Address Usage

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

T_BUT100 - BP: Roles

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

T_BUT000 -

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

T_BUT000_TD -

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

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

ABAP code using 7.40 inline data declarations to call FM BUP_BUFFER_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