SAP FTBP_READ_PARTNER_F4 Function Module for









FTBP_READ_PARTNER_F4 is a standard ftbp read partner f4 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 partner f4 FM, simply by entering the name FTBP_READ_PARTNER_F4 into the relevant SAP transaction such as SE37 or SE38.

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



Function FTBP_READ_PARTNER_F4 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_PARTNER_F4'"
EXPORTING
* I_SELOPT = "
* I_ROLE = "
* IT_ROLE = "
* I_MAXHITS = 200 "
* I_TIMEOUT = 5 "
* I_RLTYP = "BDT: Object Part
* I_SEARCH = ' ' "
* IT_RLTYP = "
* I_XMAIN = ' ' "
* I_ACTION = '01' "BDT activity
* I_CLEAR_FIELDS = ' ' "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

IMPORTING
E_PARTNER = "

EXCEPTIONS
PARTNER_NOT_FOUND = 1
.



IMPORTING Parameters details for FTBP_READ_PARTNER_F4

I_SELOPT -

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

I_ROLE -

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

IT_ROLE -

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

I_MAXHITS -

Data type: I
Default: 200
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TIMEOUT -

Data type: I
Default: 5
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RLTYP - BDT: Object Part

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

I_SEARCH -

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_RLTYP -

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

I_XMAIN -

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ACTION - BDT activity

Data type: TBZ0M-ACTION
Default: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)

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

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FTBP_READ_PARTNER_F4

E_PARTNER -

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

EXCEPTIONS details

PARTNER_NOT_FOUND -

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

Copy and paste ABAP code example for FTBP_READ_PARTNER_F4 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_i_selopt  TYPE BUSSRCH_SELOPT_T, "   
lv_e_partner  TYPE BUT000-PARTNER, "   
lv_partner_not_found  TYPE BUT000, "   
lv_i_role  TYPE BU_PARTNERROLE, "   
lv_it_role  TYPE FSBP_BUP_PARTNERROLES_TTY, "   
lv_i_maxhits  TYPE I, "   200
lv_i_timeout  TYPE I, "   5
lv_i_rltyp  TYPE BUT100-RLTYP, "   
lv_i_search  TYPE BOOLE-BOOLE, "   ' '
lv_it_rltyp  TYPE BU_BUS0RLTYP_T, "   
lv_i_xmain  TYPE BOOLE-BOOLE, "   ' '
lv_i_action  TYPE TBZ0M-ACTION, "   '01'
lv_i_clear_fields  TYPE BOOLE-BOOLE. "   ' '

  CALL FUNCTION 'FTBP_READ_PARTNER_F4'  "
    EXPORTING
         I_SELOPT = lv_i_selopt
         I_ROLE = lv_i_role
         IT_ROLE = lv_it_role
         I_MAXHITS = lv_i_maxhits
         I_TIMEOUT = lv_i_timeout
         I_RLTYP = lv_i_rltyp
         I_SEARCH = lv_i_search
         IT_RLTYP = lv_it_rltyp
         I_XMAIN = lv_i_xmain
         I_ACTION = lv_i_action
         I_CLEAR_FIELDS = lv_i_clear_fields
    IMPORTING
         E_PARTNER = lv_e_partner
    EXCEPTIONS
        PARTNER_NOT_FOUND = 1
. " FTBP_READ_PARTNER_F4




ABAP code using 7.40 inline data declarations to call FM FTBP_READ_PARTNER_F4

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_e_partner).
 
 
 
 
DATA(ld_i_maxhits) = 200.
 
DATA(ld_i_timeout) = 5.
 
"SELECT single RLTYP FROM BUT100 INTO @DATA(ld_i_rltyp).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_search).
DATA(ld_i_search) = ' '.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmain).
DATA(ld_i_xmain) = ' '.
 
"SELECT single ACTION FROM TBZ0M INTO @DATA(ld_i_action).
DATA(ld_i_action) = '01'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_clear_fields).
DATA(ld_i_clear_fields) = ' '.
 


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!