FTR_PARTNER_DISPLAY_DATA SAP Function module - Display a Business Partner

FTR_PARTNER_DISPLAY_DATA 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_DISPLAY_DATA 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_DISPLAY_DATA - FTR PARTNER DISPLAY DATA

CALL FUNCTION 'FTR_PARTNER_DISPLAY_DATA' "Display a Business Partner
  EXPORTING
    pi_partner_id =             " tb_kunnr      Partner
*   pi_partner_role = 'TR0151'  " c             Rolle (bzw. Rollentyp)
*   pi_validity_date = '00000000'  " sy-datlo   Gültigkeitsdatum von Rolle/Rollentyp
*   pi_companycode = SPACE      " bukrs         Company Code
  EXCEPTIONS
    PARTNER_NOT_FOUND = 1       "               Partner does not exist
    PARTNER_ROLE_NOT_FOUND = 2  "               Partnerrolle nicht vorhanden
    .  "  FTR_PARTNER_DISPLAY_DATA

ABAP code example for Function Module FTR_PARTNER_DISPLAY_DATA

The ABAP code below is a full code listing to execute function module FTR_PARTNER_DISPLAY_DATA 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_pi_partner_id) = 'Check type of data required'.

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

DATA(ld_pi_validity_date) = '20210129'.

DATA(ld_pi_companycode) = '20210129'.
.

CALL FUNCTION 'FTR_PARTNER_DISPLAY_DATA'
  EXPORTING
    pi_partner_id =              ld_pi_partner_id
*   pi_partner_role =            ld_pi_partner_role
*   pi_validity_date =           ld_pi_validity_date
*   pi_companycode =             ld_pi_companycode
  EXCEPTIONS
    PARTNER_NOT_FOUND =          1
    PARTNER_ROLE_NOT_FOUND =     2
    .  "  FTR_PARTNER_DISPLAY_DATA

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_pi_partner_id
 
 TYPE TB_KUNNR ,
ld_pi_partner_role
 
 TYPE C ,
ld_pi_validity_date
 
 TYPE SY-DATLO ,
ld_pi_companycode
 
 TYPE BUKRS .


ld_pi_partner_id = '20210129'.
ld_pi_partner_role = '20210129'.
ld_pi_validity_date = '20210129'.
ld_pi_companycode = '20210129'.