SAP FTBU_CONV_TPZ2 Function Module for Conversion: Conversion Customizing for Groupings
FTBU_CONV_TPZ2 is a standard ftbu conv tpz2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion: Conversion Customizing for Groupings 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 ftbu conv tpz2 FM, simply by entering the name FTBU_CONV_TPZ2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTBU_CONV_CUST
Program Name: SAPLFTBU_CONV_CUST
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTBU_CONV_TPZ2 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 'FTBU_CONV_TPZ2'"Conversion: Conversion Customizing for Groupings.
EXPORTING
* I_GROUP_ID = "Business Partner Grouping (TR BP)
* I_BU_GROUP = "Business Partner Grouping (CBP)
* I_CHECK = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* I_CONVERT = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
IMPORTING
E_BU_GROUP = "Business Partner Grouping (CBP)
E_GROUP_ID = "Business Partner Grouping (TR BP)
E_TB001 = "BP Groupings (CBP)
E_STPZ2_ZGP = "Business Partner: Customizing BP Grouping (TR BP)
EXCEPTIONS
NO_ENTRY = 1 NO_UCUST = 2
IMPORTING Parameters details for FTBU_CONV_TPZ2
I_GROUP_ID - Business Partner Grouping (TR BP)
Data type: BP_GRP_IDOptional: Yes
Call by Reference: Yes
I_BU_GROUP - Business Partner Grouping (CBP)
Data type: TPZ2-BU_GROUPOptional: Yes
Call by Reference: Yes
I_CHECK - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_CONVERT - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FTBU_CONV_TPZ2
E_BU_GROUP - Business Partner Grouping (CBP)
Data type: TB001-BU_GROUPOptional: No
Call by Reference: Yes
E_GROUP_ID - Business Partner Grouping (TR BP)
Data type: BP_GRP_IDOptional: No
Call by Reference: Yes
E_TB001 - BP Groupings (CBP)
Data type: TB001Optional: No
Call by Reference: Yes
E_STPZ2_ZGP - Business Partner: Customizing BP Grouping (TR BP)
Data type: STPZ2_ZGPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_UCUST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTBU_CONV_TPZ2 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_no_entry | TYPE STRING, " | |||
| lv_e_bu_group | TYPE TB001-BU_GROUP, " | |||
| lv_i_group_id | TYPE BP_GRP_ID, " | |||
| lv_no_ucust | TYPE BP_GRP_ID, " | |||
| lv_e_group_id | TYPE BP_GRP_ID, " | |||
| lv_i_bu_group | TYPE TPZ2-BU_GROUP, " | |||
| lv_e_tb001 | TYPE TB001, " | |||
| lv_i_check | TYPE BOOLE-BOOLE, " | |||
| lv_i_convert | TYPE BOOLE-BOOLE, " | |||
| lv_e_stpz2_zgp | TYPE STPZ2_ZGP. " |
|   CALL FUNCTION 'FTBU_CONV_TPZ2' "Conversion: Conversion Customizing for Groupings |
| EXPORTING | ||
| I_GROUP_ID | = lv_i_group_id | |
| I_BU_GROUP | = lv_i_bu_group | |
| I_CHECK | = lv_i_check | |
| I_CONVERT | = lv_i_convert | |
| IMPORTING | ||
| E_BU_GROUP | = lv_e_bu_group | |
| E_GROUP_ID | = lv_e_group_id | |
| E_TB001 | = lv_e_tb001 | |
| E_STPZ2_ZGP | = lv_e_stpz2_zgp | |
| EXCEPTIONS | ||
| NO_ENTRY = 1 | ||
| NO_UCUST = 2 | ||
| . " FTBU_CONV_TPZ2 | ||
ABAP code using 7.40 inline data declarations to call FM FTBU_CONV_TPZ2
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_e_bu_group). | ||||
| "SELECT single BU_GROUP FROM TPZ2 INTO @DATA(ld_i_bu_group). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_convert). | ||||
Search for further information about these or an SAP related objects