SAP FTBP_READ_ZGP_TO_TRGP Function Module for Business Partner: Determines CBP Number from Partner and Vice Versa









FTBP_READ_ZGP_TO_TRGP is a standard ftbp read zgp to trgp 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: Determines CBP Number from Partner and Vice Versa 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 zgp to trgp FM, simply by entering the name FTBP_READ_ZGP_TO_TRGP into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTBU_CONV_PARALLEL
Program Name: SAPLFTBU_CONV_PARALLEL
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FTBP_READ_ZGP_TO_TRGP 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_ZGP_TO_TRGP'"Business Partner: Determines CBP Number from Partner and Vice Versa
EXPORTING
* I_PARTNER = "CBP Number
* I_PARTNR = "TR BP Number
* I_TAB = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* I_CONVERT = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

IMPORTING
E_PARTNR = "TR BP Number
E_PARTNER = "CBP Number

TABLES
* R_PARTNER = "Ranges Structure for Partner Number
* R_PARTNER_ZGP = "Ranges Structure for Partner Number

EXCEPTIONS
NO_ZGP = 1 NO_TRGP = 2
.



IMPORTING Parameters details for FTBP_READ_ZGP_TO_TRGP

I_PARTNER - CBP Number

Data type: BP000-PARTNER
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARTNR - TR BP Number

Data type: BP000-PARTNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TAB - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

I_CONVERT - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FTBP_READ_ZGP_TO_TRGP

E_PARTNR - TR BP Number

Data type: BP000-PARTNR
Optional: No
Call by Reference: Yes

E_PARTNER - CBP Number

Data type: BUT000-PARTNER
Optional: No
Call by Reference: Yes

TABLES Parameters details for FTBP_READ_ZGP_TO_TRGP

R_PARTNER - Ranges Structure for Partner Number

Data type: BPAR_PART1
Optional: Yes
Call by Reference: Yes

R_PARTNER_ZGP - Ranges Structure for Partner Number

Data type: BPAR_PART1
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_ZGP -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_TRGP -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FTBP_READ_ZGP_TO_TRGP 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_zgp  TYPE STRING, "   
lv_e_partnr  TYPE BP000-PARTNR, "   
lv_i_partner  TYPE BP000-PARTNER, "   
lt_r_partner  TYPE STANDARD TABLE OF BPAR_PART1, "   
lv_no_trgp  TYPE BPAR_PART1, "   
lv_i_partnr  TYPE BP000-PARTNR, "   
lv_e_partner  TYPE BUT000-PARTNER, "   
lt_r_partner_zgp  TYPE STANDARD TABLE OF BPAR_PART1, "   
lv_i_tab  TYPE BOOLE-BOOLE, "   
lv_i_convert  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FTBP_READ_ZGP_TO_TRGP'  "Business Partner: Determines CBP Number from Partner and Vice Versa
    EXPORTING
         I_PARTNER = lv_i_partner
         I_PARTNR = lv_i_partnr
         I_TAB = lv_i_tab
         I_CONVERT = lv_i_convert
    IMPORTING
         E_PARTNR = lv_e_partnr
         E_PARTNER = lv_e_partner
    TABLES
         R_PARTNER = lt_r_partner
         R_PARTNER_ZGP = lt_r_partner_zgp
    EXCEPTIONS
        NO_ZGP = 1
        NO_TRGP = 2
. " FTBP_READ_ZGP_TO_TRGP




ABAP code using 7.40 inline data declarations to call FM FTBP_READ_ZGP_TO_TRGP

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 PARTNR FROM BP000 INTO @DATA(ld_e_partnr).
 
"SELECT single PARTNER FROM BP000 INTO @DATA(ld_i_partner).
 
 
 
"SELECT single PARTNR FROM BP000 INTO @DATA(ld_i_partnr).
 
"SELECT single PARTNER FROM BUT000 INTO @DATA(ld_e_partner).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_tab).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_convert).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!