SAP FSBP_DBREAD_BUS020_EXT Function Module for
FSBP_DBREAD_BUS020_EXT is a standard fsbp dbread bus020 ext 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 fsbp dbread bus020 ext FM, simply by entering the name FSBP_DBREAD_BUS020_EXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FSBP_DBREAD
Program Name: SAPLFSBP_DBREAD
Main Program: SAPLFSBP_DBREAD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FSBP_DBREAD_BUS020_EXT 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 'FSBP_DBREAD_BUS020_EXT'".
EXPORTING
* I_PARTNER = "Business Partner Number
* I_ADDRNR = "Address Number
* I_OPERATION = "
* I_DATE = "Date and time, local date of user
* I_DB = "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING
E_BUT000 = "BP: General data I
E_ADDRESS = "BP: Addresses with Addr. Data (Read)
E_STND_INSTEAD = "
TABLES
* T_ADDRESS = "BP: Addresses with Addr. Data (Read)
EXCEPTIONS
PARTNER_NOT_FOUND = 1 ADDRESS_NOT_FOUND = 2
IMPORTING Parameters details for FSBP_DBREAD_BUS020_EXT
I_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_ADDRNR - Address Number
Data type: AD_ADDRNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OPERATION -
Data type: BU_OPERATIONOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE - Date and time, local date of user
Data type: SY-DATLOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DB - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FSBP_DBREAD_BUS020_EXT
E_BUT000 - BP: General data I
Data type: BUT000Optional: No
Call by Reference: No ( called with pass by value option)
E_ADDRESS - BP: Addresses with Addr. Data (Read)
Data type: BUS020_EXTOptional: No
Call by Reference: No ( called with pass by value option)
E_STND_INSTEAD -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FSBP_DBREAD_BUS020_EXT
T_ADDRESS - BP: Addresses with Addr. Data (Read)
Data type: BUS020_EXTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
PARTNER_NOT_FOUND - Partner Not Found
Data type:Optional: No
Call by Reference: Yes
ADDRESS_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FSBP_DBREAD_BUS020_EXT 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_but000 | TYPE BUT000, " | |||
| lv_i_partner | TYPE BU_PARTNER, " | |||
| lt_t_address | TYPE STANDARD TABLE OF BUS020_EXT, " | |||
| lv_partner_not_found | TYPE BUS020_EXT, " | |||
| lv_i_addrnr | TYPE AD_ADDRNUM, " | |||
| lv_e_address | TYPE BUS020_EXT, " | |||
| lv_address_not_found | TYPE BUS020_EXT, " | |||
| lv_i_operation | TYPE BU_OPERATION, " | |||
| lv_e_stnd_instead | TYPE BOOLE-BOOLE, " | |||
| lv_i_date | TYPE SY-DATLO, " | |||
| lv_i_db | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'FSBP_DBREAD_BUS020_EXT' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_ADDRNR | = lv_i_addrnr | |
| I_OPERATION | = lv_i_operation | |
| I_DATE | = lv_i_date | |
| I_DB | = lv_i_db | |
| IMPORTING | ||
| E_BUT000 | = lv_e_but000 | |
| E_ADDRESS | = lv_e_address | |
| E_STND_INSTEAD | = lv_e_stnd_instead | |
| TABLES | ||
| T_ADDRESS | = lt_t_address | |
| EXCEPTIONS | ||
| PARTNER_NOT_FOUND = 1 | ||
| ADDRESS_NOT_FOUND = 2 | ||
| . " FSBP_DBREAD_BUS020_EXT | ||
ABAP code using 7.40 inline data declarations to call FM FSBP_DBREAD_BUS020_EXT
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_stnd_instead). | ||||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_date). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_db). | ||||
Search for further information about these or an SAP related objects