SAP FTBP_READ_ADDRESS_DATA Function Module for Business Partner: Read Address Data and Formatted Address









FTBP_READ_ADDRESS_DATA is a standard ftbp read address data 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 Address Data and Formatted Address 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 address data FM, simply by entering the name FTBP_READ_ADDRESS_DATA 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_ADDRESS_DATA 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_ADDRESS_DATA'"Business Partner: Read Address Data and Formatted Address
  EXPORTING
   I_PARTNER =  "Business Partner
*  I_ADR_KIND = ' ' "
*  I_ADDRNUMBER =  "
*  I_DATE =  "Datum zur Auswahl der Adresse
*  I_OPERATION = ' ' "Activity for BP Address Determination
*  I_XMEMORY =  "
*  I_XWA =  "

 IMPORTING
   E_BUS020_EXT =  "BP: Addresses with Addr. Data (Read)
   E_BUT021_FS =  "BP: Address Usage With Validity Data
   E_SMTP_ADDR =  "Internet Mail (SMTP) Address
   E_TTX_NUMBER =  "Teletex Number
   E_TLX_NUMBER =  "Telex Number
   E_ADURI_ADDR =  "Internet Mail (SMTP) Address
   E_STND_INSTEAD =  "Kennzeichen: Standardadresse statt angeforderter Adresse selektiert

TABLES
*  T_ADTEL =  "Telephone number data transfer structure (centr.addr.admin)
*  T_ADFAX =  "Transfer structure for fax numbers (central address admin.)
*  T_ADSMTP =  "SMTP Addresses Data Transfer Structure (Bus. Addr. Services)
*  T_ADURI =  "URI Address Transfer Structure (Business Address Services)
*  T_ADTLX =  "Telex Number Data Transfer Structure (Bus. Addr. Services)
*  T_ADTTX =  "Teletex Number Data Transfer Structure (BAS)

EXCEPTIONS
   ADDRESS = 1    PARTNER = 2    NO_ADDRESS = 3
.



IMPORTING Parameters details for FTBP_READ_ADDRESS_DATA

I_PARTNER - Business Partner

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

I_ADR_KIND -

Data type: TB009-ADR_KIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ADDRNUMBER -

Data type: BUS020_EXT-ADDRNUMBER
Optional: Yes
Call by Reference: Yes

I_DATE - Datum zur Auswahl der Adresse

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

I_OPERATION - Activity for BP Address Determination

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

I_XMEMORY -

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

I_XWA -

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

EXPORTING Parameters details for FTBP_READ_ADDRESS_DATA

E_BUS020_EXT - BP: Addresses with Addr. Data (Read)

Data type: BUS020_EXT
Optional: No
Call by Reference: Yes

E_BUT021_FS - BP: Address Usage With Validity Data

Data type: BUT021_FS
Optional: No
Call by Reference: Yes

E_SMTP_ADDR - Internet Mail (SMTP) Address

Data type: AD_SMTPADR
Optional: No
Call by Reference: Yes

E_TTX_NUMBER - Teletex Number

Data type: AD_TTXNMBR
Optional: No
Call by Reference: Yes

E_TLX_NUMBER - Telex Number

Data type: AD_TLXNMBR
Optional: No
Call by Reference: Yes

E_ADURI_ADDR - Internet Mail (SMTP) Address

Data type: AD_URI
Optional: No
Call by Reference: Yes

E_STND_INSTEAD - Kennzeichen: Standardadresse statt angeforderter Adresse selektiert

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

TABLES Parameters details for FTBP_READ_ADDRESS_DATA

T_ADTEL - Telephone number data transfer structure (centr.addr.admin)

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

T_ADFAX - Transfer structure for fax numbers (central address admin.)

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

T_ADSMTP - SMTP Addresses Data Transfer Structure (Bus. Addr. Services)

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

T_ADURI - URI Address Transfer Structure (Business Address Services)

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

T_ADTLX - Telex Number Data Transfer Structure (Bus. Addr. Services)

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

T_ADTTX - Teletex Number Data Transfer Structure (BAS)

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

EXCEPTIONS details

ADDRESS - Adresse nicht vorhanden oder zugeordnet

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

PARTNER - Partner does not exist

Data type:
Optional: No
Call by Reference: Yes

NO_ADDRESS - Obsolete

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FTBP_READ_ADDRESS_DATA 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_address  TYPE STRING, "   
lt_t_adtel  TYPE STANDARD TABLE OF ADTEL, "   
lv_i_partner  TYPE BUT000-PARTNER, "   
lv_e_bus020_ext  TYPE BUS020_EXT, "   
lv_partner  TYPE BUS020_EXT, "   
lt_t_adfax  TYPE STANDARD TABLE OF ADFAX, "   
lv_i_adr_kind  TYPE TB009-ADR_KIND, "   SPACE
lv_e_but021_fs  TYPE BUT021_FS, "   
lt_t_adsmtp  TYPE STANDARD TABLE OF ADSMTP, "   
lv_no_address  TYPE ADSMTP, "   
lv_e_smtp_addr  TYPE AD_SMTPADR, "   
lv_i_addrnumber  TYPE BUS020_EXT-ADDRNUMBER, "   
lv_i_date  TYPE SY-DATUM, "   
lt_t_aduri  TYPE STANDARD TABLE OF ADURI, "   
lv_e_ttx_number  TYPE AD_TTXNMBR, "   
lt_t_adtlx  TYPE STANDARD TABLE OF ADTLX, "   
lv_i_operation  TYPE BU_OPERATION, "   SPACE
lv_e_tlx_number  TYPE AD_TLXNMBR, "   
lt_t_adttx  TYPE STANDARD TABLE OF ADTTX, "   
lv_i_xmemory  TYPE BOOLE-BOOLE, "   
lv_e_aduri_addr  TYPE AD_URI, "   
lv_i_xwa  TYPE BOOLE-BOOLE, "   
lv_e_stnd_instead  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FTBP_READ_ADDRESS_DATA'  "Business Partner: Read Address Data and Formatted Address
    EXPORTING
         I_PARTNER = lv_i_partner
         I_ADR_KIND = lv_i_adr_kind
         I_ADDRNUMBER = lv_i_addrnumber
         I_DATE = lv_i_date
         I_OPERATION = lv_i_operation
         I_XMEMORY = lv_i_xmemory
         I_XWA = lv_i_xwa
    IMPORTING
         E_BUS020_EXT = lv_e_bus020_ext
         E_BUT021_FS = lv_e_but021_fs
         E_SMTP_ADDR = lv_e_smtp_addr
         E_TTX_NUMBER = lv_e_ttx_number
         E_TLX_NUMBER = lv_e_tlx_number
         E_ADURI_ADDR = lv_e_aduri_addr
         E_STND_INSTEAD = lv_e_stnd_instead
    TABLES
         T_ADTEL = lt_t_adtel
         T_ADFAX = lt_t_adfax
         T_ADSMTP = lt_t_adsmtp
         T_ADURI = lt_t_aduri
         T_ADTLX = lt_t_adtlx
         T_ADTTX = lt_t_adttx
    EXCEPTIONS
        ADDRESS = 1
        PARTNER = 2
        NO_ADDRESS = 3
. " FTBP_READ_ADDRESS_DATA




ABAP code using 7.40 inline data declarations to call FM FTBP_READ_ADDRESS_DATA

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 ADR_KIND FROM TB009 INTO @DATA(ld_i_adr_kind).
DATA(ld_i_adr_kind) = ' '.
 
 
 
 
 
"SELECT single ADDRNUMBER FROM BUS020_EXT INTO @DATA(ld_i_addrnumber).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date).
 
 
 
 
DATA(ld_i_operation) = ' '.
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_stnd_instead).
 


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!