SAP FTBP_READ_BP001 Function Module for Business Partner: Read General FS Attributes (BP001)
FTBP_READ_BP001 is a standard ftbp read bp001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Business Partner: Read General FS Attributes (BP001) 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 ftbp read bp001 FM, simply by entering the name FTBP_READ_BP001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTBP_READ
Program Name: SAPLFTBP_READ
Main Program: SAPLFTBP_READ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTBP_READ_BP001 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 'FTBP_READ_BP001'"Business Partner: Read General FS Attributes (BP001).
EXPORTING
I_PARTNER = "Partner
* I_RELEASE = ' ' "Freigabe des Partner prüfen
* I_READ_FROM_DB = ' ' "Lesen immer von der Datenbank
* I_DATE = SY-DATUM "
* I_XMEMORY = ' ' "'X' heißt erst im Memory lesen
* I_XWA = ' ' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
IMPORTING
E_BP001 = "
EXCEPTIONS
PARTNER = 1 PARTNER_NOT_RELEASED = 2 WRONG_PARAMETERS = 3 DATA_FOR_DATA_NOT_ACT = 4
IMPORTING Parameters details for FTBP_READ_BP001
I_PARTNER - Partner
Data type: BUT000-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
I_RELEASE - Freigabe des Partner prüfen
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_READ_FROM_DB - Lesen immer von der Datenbank
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XMEMORY - 'X' heißt erst im Memory lesen
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XWA - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTBP_READ_BP001
E_BP001 -
Data type: BP001Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARTNER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_NOT_RELEASED - Partner is not released
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_PARAMETERS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_FOR_DATA_NOT_ACT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTBP_READ_BP001 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_bp001 | TYPE BP001, " | |||
| lv_partner | TYPE BP001, " | |||
| lv_i_partner | TYPE BUT000-PARTNER, " | |||
| lv_i_release | TYPE BUT000, " SPACE | |||
| lv_partner_not_released | TYPE BUT000, " | |||
| lv_i_read_from_db | TYPE BUT000, " SPACE | |||
| lv_wrong_parameters | TYPE BUT000, " | |||
| lv_i_date | TYPE SY-DATUM, " SY-DATUM | |||
| lv_data_for_data_not_act | TYPE SY, " | |||
| lv_i_xmemory | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_xwa | TYPE BOOLE-BOOLE. " SPACE |
|   CALL FUNCTION 'FTBP_READ_BP001' "Business Partner: Read General FS Attributes (BP001) |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_RELEASE | = lv_i_release | |
| I_READ_FROM_DB | = lv_i_read_from_db | |
| I_DATE | = lv_i_date | |
| I_XMEMORY | = lv_i_xmemory | |
| I_XWA | = lv_i_xwa | |
| IMPORTING | ||
| E_BP001 | = lv_e_bp001 | |
| EXCEPTIONS | ||
| PARTNER = 1 | ||
| PARTNER_NOT_RELEASED = 2 | ||
| WRONG_PARAMETERS = 3 | ||
| DATA_FOR_DATA_NOT_ACT = 4 | ||
| . " FTBP_READ_BP001 | ||
ABAP code using 7.40 inline data declarations to call FM FTBP_READ_BP001
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 PARTNER FROM BUT000 INTO @DATA(ld_i_partner). | ||||
| DATA(ld_i_release) | = ' '. | |||
| DATA(ld_i_read_from_db) | = ' '. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_date). | ||||
| DATA(ld_i_date) | = SY-DATUM. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory). | ||||
| DATA(ld_i_xmemory) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa). | ||||
| DATA(ld_i_xwa) | = ' '. | |||
Search for further information about these or an SAP related objects