SAP FTR_PARTNER_GET_ADDRESS_PRINT Function Module for Business Partner: Read Address Data and Formatted Address
FTR_PARTNER_GET_ADDRESS_PRINT is a standard ftr partner get address print 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 ftr partner get address print FM, simply by entering the name FTR_PARTNER_GET_ADDRESS_PRINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_REUSE_PARTNER
Program Name: SAPLFTR_REUSE_PARTNER
Main Program: SAPLFTR_REUSE_PARTNER
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_PARTNER_GET_ADDRESS_PRINT 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 'FTR_PARTNER_GET_ADDRESS_PRINT'"Business Partner: Read Address Data and Formatted Address.
EXPORTING
PI_PARTNER_ID = "Partner
* PI_PARTNER_ROLE = ' ' "Rolle (bzw. Rollentyp)
* PI_ADDR_KIND = ' ' "Address type
* PI_COMPANYCODE = ' ' "Buchungskreis (MUSS-Feld für Authority, sonst KANN)
* PI_SENDER_COUNTRY = ' ' "Sender country for address formatting
* PI_DATE = SY-DATUM "Date and Time, Current (Application Server) Date
* PI_COUNT_LINES = 5 "Number of lines in address
IMPORTING
PE_ADDRESS = "Address
PE_BUS020_EXT = "SAP-GP: Adressen mit Adressdaten
PE_BUT021_FS = "SAP-GP: zeitabhängige Adressverwendungen
PE_TRPARTNER_ADDREF = "alte TRGP-Struktur: Adresse+Kommunikation
PE_TRPARTNER_ADDR = "alte TRGP-Struktur: Adresse
PE_ADDRESS_PRINTFORM = "Formatted address (maximum 10 lines)
PE_ADDRESS_SHORT_FORM = "One-line short form of formatted address
PE_ADDRESS_SHORT_FORM_S = "One-line short form of formatted address
PE_ADDRESS_DATA_CARRIER = "Short form of the formatted address for the data medium
PE_ADDRESS_DATA_CARRIER_0 = "Short form of the formatted address for the data medium
PE_NUMBER_OF_USED_LINES = "Number of lines in address
PE_GNRL_DATA1 = "BP: General Data I (Read)
PE_ORG_DATA = "Treasury Attributes Organization
EXCEPTIONS
PARTNER_NOT_FOUND = 1 PARTNER_ROLE_NOT_FOUND = 2 PARTNER_NOT_RELEASED = 3 PARTNER_TO_BE_DELETED = 4 PARTNER_ADDRESS_NOT_FOUND = 5
IMPORTING Parameters details for FTR_PARTNER_GET_ADDRESS_PRINT
PI_PARTNER_ID - Partner
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
PI_PARTNER_ROLE - Rolle (bzw. Rollentyp)
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_ADDR_KIND - Address type
Data type: BU_ADRKINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_COMPANYCODE - Buchungskreis (MUSS-Feld für Authority, sonst KANN)
Data type: BUKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_SENDER_COUNTRY - Sender country for address formatting
Data type: AD_CTRY_FRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_DATE - Date and Time, Current (Application Server) Date
Data type: SYDATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_COUNT_LINES - Number of lines in address
Data type: ANZEIDefault: 5
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTR_PARTNER_GET_ADDRESS_PRINT
PE_ADDRESS - Address
Data type: ADRSOptional: No
Call by Reference: Yes
PE_BUS020_EXT - SAP-GP: Adressen mit Adressdaten
Data type: BUS020_EXTOptional: No
Call by Reference: Yes
PE_BUT021_FS - SAP-GP: zeitabhängige Adressverwendungen
Data type: BUT021_FSOptional: No
Call by Reference: Yes
PE_TRPARTNER_ADDREF - alte TRGP-Struktur: Adresse+Kommunikation
Data type: BPDADREFOptional: No
Call by Reference: Yes
PE_TRPARTNER_ADDR - alte TRGP-Struktur: Adresse
Data type: BPDADROptional: No
Call by Reference: Yes
PE_ADDRESS_PRINTFORM - Formatted address (maximum 10 lines)
Data type: ADRS_PRINTOptional: No
Call by Reference: Yes
PE_ADDRESS_SHORT_FORM - One-line short form of formatted address
Data type: SZAD_FIELD-ADDR_SHORTOptional: No
Call by Reference: Yes
PE_ADDRESS_SHORT_FORM_S - One-line short form of formatted address
Data type: SZAD_FIELD-ADDR_SHORTOptional: No
Call by Reference: Yes
PE_ADDRESS_DATA_CARRIER - Short form of the formatted address for the data medium
Data type: SZAD_FIELD-ADDR_DCOptional: No
Call by Reference: Yes
PE_ADDRESS_DATA_CARRIER_0 - Short form of the formatted address for the data medium
Data type: SZAD_FIELD-ADDR_DCOptional: No
Call by Reference: Yes
PE_NUMBER_OF_USED_LINES - Number of lines in address
Data type: ADRS-ANZZLOptional: No
Call by Reference: Yes
PE_GNRL_DATA1 - BP: General Data I (Read)
Data type: BUS000Optional: No
Call by Reference: Yes
PE_ORG_DATA - Treasury Attributes Organization
Data type: BP001Optional: No
Call by Reference: Yes
EXCEPTIONS details
PARTNER_NOT_FOUND - Partner is not available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_ROLE_NOT_FOUND - Partner ist nicht in der Rolle vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_NOT_RELEASED - Partner is not released
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_TO_BE_DELETED - Partner ist zum Löschen vorgemerkt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_ADDRESS_NOT_FOUND - zum Partner ist keine Adresse vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_PARTNER_GET_ADDRESS_PRINT 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_pe_address | TYPE ADRS, " | |||
| lv_pi_partner_id | TYPE BU_PARTNER, " | |||
| lv_partner_not_found | TYPE BU_PARTNER, " | |||
| lv_pe_bus020_ext | TYPE BUS020_EXT, " | |||
| lv_pe_but021_fs | TYPE BUT021_FS, " | |||
| lv_pe_trpartner_addref | TYPE BPDADREF, " | |||
| lv_pe_trpartner_addr | TYPE BPDADR, " | |||
| lv_pi_partner_role | TYPE C, " SPACE | |||
| lv_pe_address_printform | TYPE ADRS_PRINT, " | |||
| lv_partner_role_not_found | TYPE ADRS_PRINT, " | |||
| lv_pi_addr_kind | TYPE BU_ADRKIND, " SPACE | |||
| lv_partner_not_released | TYPE BU_ADRKIND, " | |||
| lv_pe_address_short_form | TYPE SZAD_FIELD-ADDR_SHORT, " | |||
| lv_pi_companycode | TYPE BUKRS, " SPACE | |||
| lv_partner_to_be_deleted | TYPE BUKRS, " | |||
| lv_pe_address_short_form_s | TYPE SZAD_FIELD-ADDR_SHORT, " | |||
| lv_pi_sender_country | TYPE AD_CTRY_FR, " SPACE | |||
| lv_pe_address_data_carrier | TYPE SZAD_FIELD-ADDR_DC, " | |||
| lv_partner_address_not_found | TYPE SZAD_FIELD, " | |||
| lv_pi_date | TYPE SYDATUM, " SY-DATUM | |||
| lv_pe_address_data_carrier_0 | TYPE SZAD_FIELD-ADDR_DC, " | |||
| lv_pi_count_lines | TYPE ANZEI, " 5 | |||
| lv_pe_number_of_used_lines | TYPE ADRS-ANZZL, " | |||
| lv_pe_gnrl_data1 | TYPE BUS000, " | |||
| lv_pe_org_data | TYPE BP001. " |
|   CALL FUNCTION 'FTR_PARTNER_GET_ADDRESS_PRINT' "Business Partner: Read Address Data and Formatted Address |
| EXPORTING | ||
| PI_PARTNER_ID | = lv_pi_partner_id | |
| PI_PARTNER_ROLE | = lv_pi_partner_role | |
| PI_ADDR_KIND | = lv_pi_addr_kind | |
| PI_COMPANYCODE | = lv_pi_companycode | |
| PI_SENDER_COUNTRY | = lv_pi_sender_country | |
| PI_DATE | = lv_pi_date | |
| PI_COUNT_LINES | = lv_pi_count_lines | |
| IMPORTING | ||
| PE_ADDRESS | = lv_pe_address | |
| PE_BUS020_EXT | = lv_pe_bus020_ext | |
| PE_BUT021_FS | = lv_pe_but021_fs | |
| PE_TRPARTNER_ADDREF | = lv_pe_trpartner_addref | |
| PE_TRPARTNER_ADDR | = lv_pe_trpartner_addr | |
| PE_ADDRESS_PRINTFORM | = lv_pe_address_printform | |
| PE_ADDRESS_SHORT_FORM | = lv_pe_address_short_form | |
| PE_ADDRESS_SHORT_FORM_S | = lv_pe_address_short_form_s | |
| PE_ADDRESS_DATA_CARRIER | = lv_pe_address_data_carrier | |
| PE_ADDRESS_DATA_CARRIER_0 | = lv_pe_address_data_carrier_0 | |
| PE_NUMBER_OF_USED_LINES | = lv_pe_number_of_used_lines | |
| PE_GNRL_DATA1 | = lv_pe_gnrl_data1 | |
| PE_ORG_DATA | = lv_pe_org_data | |
| EXCEPTIONS | ||
| PARTNER_NOT_FOUND = 1 | ||
| PARTNER_ROLE_NOT_FOUND = 2 | ||
| PARTNER_NOT_RELEASED = 3 | ||
| PARTNER_TO_BE_DELETED = 4 | ||
| PARTNER_ADDRESS_NOT_FOUND = 5 | ||
| . " FTR_PARTNER_GET_ADDRESS_PRINT | ||
ABAP code using 7.40 inline data declarations to call FM FTR_PARTNER_GET_ADDRESS_PRINT
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.| DATA(ld_pi_partner_role) | = ' '. | |||
| DATA(ld_pi_addr_kind) | = ' '. | |||
| "SELECT single ADDR_SHORT FROM SZAD_FIELD INTO @DATA(ld_pe_address_short_form). | ||||
| DATA(ld_pi_companycode) | = ' '. | |||
| "SELECT single ADDR_SHORT FROM SZAD_FIELD INTO @DATA(ld_pe_address_short_form_s). | ||||
| DATA(ld_pi_sender_country) | = ' '. | |||
| "SELECT single ADDR_DC FROM SZAD_FIELD INTO @DATA(ld_pe_address_data_carrier). | ||||
| DATA(ld_pi_date) | = SY-DATUM. | |||
| "SELECT single ADDR_DC FROM SZAD_FIELD INTO @DATA(ld_pe_address_data_carrier_0). | ||||
| DATA(ld_pi_count_lines) | = 5. | |||
| "SELECT single ANZZL FROM ADRS INTO @DATA(ld_pe_number_of_used_lines). | ||||
Search for further information about these or an SAP related objects