SAP Function Modules

RKE_PLAN_LONG_TEXT SAP Function module







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

Associated Function Group: KEP1
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM RKE_PLAN_LONG_TEXT - RKE PLAN LONG TEXT





CALL FUNCTION 'RKE_PLAN_LONG_TEXT' "
  EXPORTING
    i_erkrs =                   " tkebb-erkrs
*   i_pa_type = '1'             " ceddb-pa_type
    i_ce0 =                     "
*   i_display = 'X'             " c
*   i_mode = '1'                " c
  IMPORTING
    e_subrc =                   " sy-subrc
    e_commit =                  " c
    .  "  RKE_PLAN_LONG_TEXT

ABAP code example for Function Module RKE_PLAN_LONG_TEXT





The ABAP code below is a full code listing to execute function module RKE_PLAN_LONG_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_e_subrc  TYPE SY-SUBRC ,
ld_e_commit  TYPE C .


SELECT single ERKRS
FROM TKEBB
INTO @DATA(ld_i_erkrs).


DATA(ld_i_pa_type) = some text here
DATA(ld_i_ce0) = 'some text here'.
DATA(ld_i_display) = 'Check type of data required'.
DATA(ld_i_mode) = 'Check type of data required'. . CALL FUNCTION 'RKE_PLAN_LONG_TEXT' EXPORTING i_erkrs = ld_i_erkrs * i_pa_type = ld_i_pa_type i_ce0 = ld_i_ce0 * i_display = ld_i_display * i_mode = ld_i_mode IMPORTING e_subrc = ld_e_subrc e_commit = ld_e_commit . " RKE_PLAN_LONG_TEXT
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_subrc  TYPE SY-SUBRC ,
ld_i_erkrs  TYPE TKEBB-ERKRS ,
ld_e_commit  TYPE C ,
ld_i_pa_type  TYPE CEDDB-PA_TYPE ,
ld_i_ce0  TYPE STRING ,
ld_i_display  TYPE C ,
ld_i_mode  TYPE C .


SELECT single ERKRS
FROM TKEBB
INTO ld_i_erkrs.


ld_i_pa_type = some text here
ld_i_ce0 = 'some text here'.
ld_i_display = 'Check type of data required'.
ld_i_mode = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name RKE_PLAN_LONG_TEXT or its description.