SAP Function Modules

K_EP_TEXTNAME_INPUT SAP Function module







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

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


Pattern for FM K_EP_TEXTNAME_INPUT - K EP TEXTNAME INPUT





CALL FUNCTION 'K_EP_TEXTNAME_INPUT' "
  EXPORTING
*   i_applclass = 'KS'          " applclass
    i_text_name =               " rtxtname
    i_text_type =               " rtxttype
*   i_text_langu = SY-LANGU     " spras
*   i_input_language_only =     " flag
  IMPORTING
    e_applclass =               " applclass
    e_text_name =               " rtxtname
    e_text_type =               " rtxttype
    e_text_langu =              " spras
  EXCEPTIONS
    INPUT_CANCELED = 1          "
    .  "  K_EP_TEXTNAME_INPUT

ABAP code example for Function Module K_EP_TEXTNAME_INPUT





The ABAP code below is a full code listing to execute function module K_EP_TEXTNAME_INPUT 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_applclass  TYPE APPLCLASS ,
ld_e_text_name  TYPE RTXTNAME ,
ld_e_text_type  TYPE RTXTTYPE ,
ld_e_text_langu  TYPE SPRAS .

DATA(ld_i_applclass) = 'Check type of data required'.
DATA(ld_i_text_name) = 'Check type of data required'.
DATA(ld_i_text_type) = 'Check type of data required'.
DATA(ld_i_text_langu) = 'Check type of data required'.
DATA(ld_i_input_language_only) = 'Check type of data required'. . CALL FUNCTION 'K_EP_TEXTNAME_INPUT' EXPORTING * i_applclass = ld_i_applclass i_text_name = ld_i_text_name i_text_type = ld_i_text_type * i_text_langu = ld_i_text_langu * i_input_language_only = ld_i_input_language_only IMPORTING e_applclass = ld_e_applclass e_text_name = ld_e_text_name e_text_type = ld_e_text_type e_text_langu = ld_e_text_langu EXCEPTIONS INPUT_CANCELED = 1 . " K_EP_TEXTNAME_INPUT
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_e_applclass  TYPE APPLCLASS ,
ld_i_applclass  TYPE APPLCLASS ,
ld_e_text_name  TYPE RTXTNAME ,
ld_i_text_name  TYPE RTXTNAME ,
ld_e_text_type  TYPE RTXTTYPE ,
ld_i_text_type  TYPE RTXTTYPE ,
ld_e_text_langu  TYPE SPRAS ,
ld_i_text_langu  TYPE SPRAS ,
ld_i_input_language_only  TYPE FLAG .

ld_i_applclass = 'Check type of data required'.
ld_i_text_name = 'Check type of data required'.
ld_i_text_type = 'Check type of data required'.
ld_i_text_langu = 'Check type of data required'.
ld_i_input_language_only = '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 K_EP_TEXTNAME_INPUT or its description.