SCSMBK_MDATA_TRANSL_TOKEN SAP Function module

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

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

Pattern for FM SCSMBK_MDATA_TRANSL_TOKEN - SCSMBK MDATA TRANSL TOKEN

CALL FUNCTION 'SCSMBK_MDATA_TRANSL_TOKEN' "
  EXPORTING
*   namespace =                 " csmobjnm      Object name in CCMS Repository
*   scheme = SCHEME_BC          " csmsmntc
    class =                     " csmclass      CCMS Class Names
    token =                     " csmtoken      Property of CCMS Repository class
*   requested_language =        " sy-langu      SAP R/3 System, Current Language
  IMPORTING
    trans_text =                " csmtoken      Property of CCMS Repository class
    trans_text_long =           " text132       Text (length 132)
    .  "  SCSMBK_MDATA_TRANSL_TOKEN

ABAP code example for Function Module SCSMBK_MDATA_TRANSL_TOKEN

The ABAP code below is a full code listing to execute function module SCSMBK_MDATA_TRANSL_TOKEN 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_trans_text  
 
 TYPE CSMTOKEN
,
ld_trans_text_long  
 
 TYPE TEXT132
.


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

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

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

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

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

CALL FUNCTION 'SCSMBK_MDATA_TRANSL_TOKEN'
  EXPORTING
*   namespace =                  ld_namespace
*   scheme =                     ld_scheme
    class =                      ld_class
    token =                      ld_token
*   requested_language =         ld_requested_language
  IMPORTING
    trans_text =                 ld_trans_text
    trans_text_long =            ld_trans_text_long
    .  "  SCSMBK_MDATA_TRANSL_TOKEN

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_trans_text
 
 TYPE CSMTOKEN ,
ld_namespace
 
 TYPE CSMOBJNM ,
ld_trans_text_long
 
 TYPE TEXT132 ,
ld_scheme
 
 TYPE CSMSMNTC ,
ld_class
 
 TYPE CSMCLASS ,
ld_token
 
 TYPE CSMTOKEN ,
ld_requested_language
 
 TYPE SY-LANGU .


ld_namespace = 'Check type of data required'.
ld_scheme = 'Check type of data required'.
ld_class = 'Check type of data required'.
ld_token = 'Check type of data required'.
ld_requested_language = 'Check type of data required'.