SAP FLBPC_VEND_READ_TBC001 Function Module for Business Partner: Assignment Grouping Account Group
FLBPC_VEND_READ_TBC001 is a standard flbpc vend read tbc001 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: Assignment Grouping Account Group 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 flbpc vend read tbc001 FM, simply by entering the name FLBPC_VEND_READ_TBC001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FLBPC_CUST_READ
Program Name: SAPLFLBPC_CUST_READ
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FLBPC_VEND_READ_TBC001 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 'FLBPC_VEND_READ_TBC001'"Business Partner: Assignment Grouping Account Group.
EXPORTING
I_BU_GROUP = "Business Partner Grouping
IMPORTING
E_TBC001 = "Business Partner: Assignment Grouping Account Group
IMPORTING Parameters details for FLBPC_VEND_READ_TBC001
I_BU_GROUP - Business Partner Grouping
Data type: TB001-BU_GROUPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FLBPC_VEND_READ_TBC001
E_TBC001 - Business Partner: Assignment Grouping Account Group
Data type: TBCS001Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FLBPC_VEND_READ_TBC001 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_tbc001 | TYPE TBCS001, " | |||
| lv_i_bu_group | TYPE TB001-BU_GROUP. " |
|   CALL FUNCTION 'FLBPC_VEND_READ_TBC001' "Business Partner: Assignment Grouping Account Group |
| EXPORTING | ||
| I_BU_GROUP | = lv_i_bu_group | |
| IMPORTING | ||
| E_TBC001 | = lv_e_tbc001 | |
| . " FLBPC_VEND_READ_TBC001 | ||
ABAP code using 7.40 inline data declarations to call FM FLBPC_VEND_READ_TBC001
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 BU_GROUP FROM TB001 INTO @DATA(ld_i_bu_group). | ||||
Search for further information about these or an SAP related objects