SAP FTBP_READ_KNB1 Function Module for Business Partner: Read FI Customer Data (Company Code)
FTBP_READ_KNB1 is a standard ftbp read knb1 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 FI Customer Data (Company Code) 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 knb1 FM, simply by entering the name FTBP_READ_KNB1 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_KNB1 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_KNB1'"Business Partner: Read FI Customer Data (Company Code).
EXPORTING
* I_PARTNER = "
* I_CUSTOMER = "
* I_BUKRS = "
* I_CUSTOMER_TO_PARTNER = "
* I_XMEMORY = "
* I_XWA = "
* I_DATE = SY-DATUM "
IMPORTING
E_KNB1 = "
TABLES
* T_KNB1 = "
EXCEPTIONS
CUSTOMER_NOT_FOUND = 1 NO_CONNECTION = 2
IMPORTING Parameters details for FTBP_READ_KNB1
I_PARTNER -
Data type: BUT000-PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_CUSTOMER -
Data type: KNB1-KUNNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: KNB1-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CUSTOMER_TO_PARTNER -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XMEMORY -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XWA -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FTBP_READ_KNB1
E_KNB1 -
Data type: KNB1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FTBP_READ_KNB1
T_KNB1 -
Data type: KNB1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CUSTOMER_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CONNECTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTBP_READ_KNB1 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_knb1 | TYPE KNB1, " | |||
| lt_t_knb1 | TYPE STANDARD TABLE OF KNB1, " | |||
| lv_i_partner | TYPE BUT000-PARTNER, " | |||
| lv_customer_not_found | TYPE BUT000, " | |||
| lv_i_customer | TYPE KNB1-KUNNR, " | |||
| lv_no_connection | TYPE KNB1, " | |||
| lv_i_bukrs | TYPE KNB1-BUKRS, " | |||
| lv_i_customer_to_partner | TYPE BOOLE-BOOLE, " | |||
| lv_i_xmemory | TYPE BOOLE-BOOLE, " | |||
| lv_i_xwa | TYPE BOOLE-BOOLE, " | |||
| lv_i_date | TYPE SY-DATUM. " SY-DATUM |
|   CALL FUNCTION 'FTBP_READ_KNB1' "Business Partner: Read FI Customer Data (Company Code) |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_CUSTOMER | = lv_i_customer | |
| I_BUKRS | = lv_i_bukrs | |
| I_CUSTOMER_TO_PARTNER | = lv_i_customer_to_partner | |
| I_XMEMORY | = lv_i_xmemory | |
| I_XWA | = lv_i_xwa | |
| I_DATE | = lv_i_date | |
| IMPORTING | ||
| E_KNB1 | = lv_e_knb1 | |
| TABLES | ||
| T_KNB1 | = lt_t_knb1 | |
| EXCEPTIONS | ||
| CUSTOMER_NOT_FOUND = 1 | ||
| NO_CONNECTION = 2 | ||
| . " FTBP_READ_KNB1 | ||
ABAP code using 7.40 inline data declarations to call FM FTBP_READ_KNB1
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). | ||||
| "SELECT single KUNNR FROM KNB1 INTO @DATA(ld_i_customer). | ||||
| "SELECT single BUKRS FROM KNB1 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_customer_to_partner). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_date). | ||||
| DATA(ld_i_date) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects