FTR_PARTNER_GET_TEXT SAP Function module - Text Description of Business Partner (Variable Role, Default: TR Partner

FTR_PARTNER_GET_TEXT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FTR_PARTNER_GET_TEXT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FTR_REUSE_PARTNER
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FTR_PARTNER_GET_TEXT - FTR PARTNER GET TEXT

CALL FUNCTION 'FTR_PARTNER_GET_TEXT' "Text Description of Business Partner (Variable Role, Default: TR Partner)
  EXPORTING
*   pi_companycode = SPACE      " bukrs         Company Code
    pi_partner_id =             " tb_kontrh     Counterparty
*   pi_partner_role = 'TR0151'  " c             Rolle (ist die alte TR-Partner Rolle)
*   pi_flg_check = SPACE        " boole_d       Existenzprüfung durchführen? (X=ja, else=nein)
  IMPORTING
    pe_partner_text =           " tb_xkontrh    Name and Address of Business Partner
  EXCEPTIONS
    PARTNER_NOT_FOUND = 1       "               Partner Not Found
    PARTNER_ROLE_NOT_FOUND = 2  "               Partner in Rolle nicht gefunden
    .  "  FTR_PARTNER_GET_TEXT

ABAP code example for Function Module FTR_PARTNER_GET_TEXT

The ABAP code below is a full code listing to execute function module FTR_PARTNER_GET_TEXT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_pe_partner_text  
 
 TYPE TB_XKONTRH
.


DATA(ld_pi_companycode) = 'Check type of data required'.

DATA(ld_pi_partner_id) = 'Check type of data required'.

DATA(ld_pi_partner_role) = 'Check type of data required'.

DATA(ld_pi_flg_check) = 'Check type of data required'.
.

CALL FUNCTION 'FTR_PARTNER_GET_TEXT'
  EXPORTING
*   pi_companycode =             ld_pi_companycode
    pi_partner_id =              ld_pi_partner_id
*   pi_partner_role =            ld_pi_partner_role
*   pi_flg_check =               ld_pi_flg_check
  IMPORTING
    pe_partner_text =            ld_pe_partner_text
  EXCEPTIONS
    PARTNER_NOT_FOUND =          1
    PARTNER_ROLE_NOT_FOUND =     2
    .  "  FTR_PARTNER_GET_TEXT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_pe_partner_text
 
 TYPE TB_XKONTRH ,
ld_pi_companycode
 
 TYPE BUKRS ,
ld_pi_partner_id
 
 TYPE TB_KONTRH ,
ld_pi_partner_role
 
 TYPE C ,
ld_pi_flg_check
 
 TYPE BOOLE_D .


ld_pi_companycode = 'Check type of data required'.
ld_pi_partner_id = 'Check type of data required'.
ld_pi_partner_role = 'Check type of data required'.
ld_pi_flg_check = 'Check type of data required'.