RTP_US_API_GET_DESCRIPTIONS SAP Function module - Obtains the descriptions of the plan type, bank area etc

RTP_US_API_GET_DESCRIPTIONS 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 RTP_US_API_GET_DESCRIPTIONS into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM RTP_US_API_GET_DESCRIPTIONS - RTP US API GET DESCRIPTIONS

CALL FUNCTION 'RTP_US_API_GET_DESCRIPTIONS' "Obtains the descriptions of the plan type, bank area etc
  EXPORTING
    i_str_accountholder =       " but000        BP: General data I
    i_type_code =               " rtp_us_plan-type_code  Type code for a retirement plan
    i_bkkrs =                   " rtp_us_plan-bkkrs  Bank Area
  IMPORTING
    e_name =                    " irtp_us_plan_report-name  Full name of business partner
    e_type_description =        " trtp_us_plantypt-description  Description of the retirement plan type
    e_bkkrs =                   " tbkk01t-t_bkkrs  Description bank area
    .  "  RTP_US_API_GET_DESCRIPTIONS

ABAP code example for Function Module RTP_US_API_GET_DESCRIPTIONS

The ABAP code below is a full code listing to execute function module RTP_US_API_GET_DESCRIPTIONS 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_e_name  
 
 TYPE IRTP_US_PLAN_REPORT-NAME
,
ld_e_type_description  
 
 TYPE TRTP_US_PLANTYPT-DESCRIPTION
,
ld_e_bkkrs  
 
 TYPE TBKK01T-T_BKKRS
.


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

SELECT single TYPE_CODE 
  FROM RTP_US_PLAN 
  INTO @DATA(ld_i_type_code).

 

SELECT single BKKRS 
  FROM RTP_US_PLAN 
  INTO @DATA(ld_i_bkkrs).

.

CALL FUNCTION 'RTP_US_API_GET_DESCRIPTIONS'
  EXPORTING
    i_str_accountholder =        ld_i_str_accountholder
    i_type_code =                ld_i_type_code
    i_bkkrs =                    ld_i_bkkrs
  IMPORTING
    e_name =                     ld_e_name
    e_type_description =         ld_e_type_description
    e_bkkrs =                    ld_e_bkkrs
    .  "  RTP_US_API_GET_DESCRIPTIONS

IF SY-SUBRC EQ 0.
  "All OK
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_e_name
 
 TYPE IRTP_US_PLAN_REPORT-NAME ,
ld_i_str_accountholder
 
 TYPE BUT000 ,
ld_e_type_description
 
 TYPE TRTP_US_PLANTYPT-DESCRIPTION ,
ld_i_type_code
 
 TYPE RTP_US_PLAN-TYPE_CODE ,
ld_e_bkkrs
 
 TYPE TBKK01T-T_BKKRS ,
ld_i_bkkrs
 
 TYPE RTP_US_PLAN-BKKRS .


ld_i_str_accountholder = 'Check type of data required'.

SELECT single TYPE_CODE 
  FROM RTP_US_PLAN 
  INTO ld_i_type_code.


SELECT single BKKRS 
  FROM RTP_US_PLAN 
  INTO ld_i_bkkrs.