SAP BUP_BUFFER_GET_BASIS Function Module for
BUP_BUFFER_GET_BASIS is a standard bup buffer get basis 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 basis FM, simply by entering the name BUP_BUFFER_GET_BASIS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUPA_SELECT
Program Name: SAPLBUPA_SELECT
Main Program: SAPLBUPA_SELECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUP_BUFFER_GET_BASIS 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_BASIS'".
EXPORTING
I_PARTNER = "
* I_VALDT = '00000000' "
IMPORTING
E_BUT000_STAT = "
E_BUT100_STAT = "
E_BUT020_STAT = "
E_BUT021_FS_STAT = "
E_BUT000 = "
TABLES
* T_BUT020 = "
* T_BUT021_FS = "
* T_BUT100 = "
* T_BUT000 = "
* T_BUT000_TD = "
IMPORTING Parameters details for BUP_BUFFER_GET_BASIS
I_PARTNER -
Data type: BU_PARTNEROptional: No
Call by Reference: Yes
I_VALDT -
Data type: SY-DATLODefault: '00000000'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BUP_BUFFER_GET_BASIS
E_BUT000_STAT -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_BUT100_STAT -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_BUT020_STAT -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_BUT021_FS_STAT -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_BUT000 -
Data type: BUT000Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BUP_BUFFER_GET_BASIS
T_BUT020 -
Data type: BUT020Optional: Yes
Call by Reference: Yes
T_BUT021_FS -
Data type: BUT021_FSOptional: Yes
Call by Reference: Yes
T_BUT100 -
Data type: BUT100Optional: Yes
Call by Reference: Yes
T_BUT000 -
Data type: BUT000Optional: Yes
Call by Reference: Yes
T_BUT000_TD -
Data type: BUT000_TDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BUP_BUFFER_GET_BASIS 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: | ||||
| lt_t_but020 | TYPE STANDARD TABLE OF BUT020, " | |||
| lv_i_partner | TYPE BU_PARTNER, " | |||
| lv_e_but000_stat | TYPE BOOLE-BOOLE, " | |||
| lv_i_valdt | TYPE SY-DATLO, " '00000000' | |||
| lt_t_but021_fs | TYPE STANDARD TABLE OF BUT021_FS, " | |||
| lv_e_but100_stat | TYPE BOOLE-BOOLE, " | |||
| lt_t_but100 | TYPE STANDARD TABLE OF BUT100, " | |||
| lv_e_but020_stat | TYPE BOOLE-BOOLE, " | |||
| lt_t_but000 | TYPE STANDARD TABLE OF BUT000, " | |||
| lv_e_but021_fs_stat | TYPE BOOLE-BOOLE, " | |||
| lv_e_but000 | TYPE BUT000, " | |||
| lt_t_but000_td | TYPE STANDARD TABLE OF BUT000_TD. " |
|   CALL FUNCTION 'BUP_BUFFER_GET_BASIS' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_VALDT | = lv_i_valdt | |
| IMPORTING | ||
| E_BUT000_STAT | = lv_e_but000_stat | |
| E_BUT100_STAT | = lv_e_but100_stat | |
| E_BUT020_STAT | = lv_e_but020_stat | |
| E_BUT021_FS_STAT | = lv_e_but021_fs_stat | |
| E_BUT000 | = lv_e_but000 | |
| TABLES | ||
| T_BUT020 | = lt_t_but020 | |
| T_BUT021_FS | = lt_t_but021_fs | |
| T_BUT100 | = lt_t_but100 | |
| T_BUT000 | = lt_t_but000 | |
| T_BUT000_TD | = lt_t_but000_td | |
| . " BUP_BUFFER_GET_BASIS | ||
ABAP code using 7.40 inline data declarations to call FM BUP_BUFFER_GET_BASIS
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 BOOLE FROM BOOLE INTO @DATA(ld_e_but000_stat). | ||||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt). | ||||
| DATA(ld_i_valdt) | = '00000000'. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_but100_stat). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_but020_stat). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_but021_fs_stat). | ||||
Search for further information about these or an SAP related objects