CUPAX_GET_TOKEN SAP Function module

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

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

Pattern for FM CUPAX_GET_TOKEN - CUPAX GET TOKEN

CALL FUNCTION 'CUPAX_GET_TOKEN' "
  EXPORTING
    col =                       "               Offset in header of the editor buffer
  IMPORTING
    dlm =                       "               Type of the token limit (PARSI_TOKENS)
    ln =                        "               Length of the token
    type_p =                    "
  TABLES
    parsd_source =              " pars_text     Editor buffer
  EXCEPTIONS
    ILLEGAL_CHARACTER = 1       "               Invalid character in the token
    INTERNAL_ERROR = 2          "
    TOKEN_TOO_LONG = 3          "               Token longer than planned
    UNBALANCED_QUOTES = 4       "               Quotes not in pairs
    .  "  CUPAX_GET_TOKEN

ABAP code example for Function Module CUPAX_GET_TOKEN

The ABAP code below is a full code listing to execute function module CUPAX_GET_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_dlm  
 
 TYPE STRING
,
ld_ln  
 
 TYPE STRING
,
ld_type_p  
 
 TYPE STRING
,
it_parsd_source  
 
 TYPE STANDARD TABLE OF PARS_TEXT,"TABLES PARAM
wa_parsd_source
 
 LIKE LINE OF it_parsd_source
.


DATA(ld_col) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_parsd_source to it_parsd_source.
.

CALL FUNCTION 'CUPAX_GET_TOKEN'
  EXPORTING
    col =                        ld_col
  IMPORTING
    dlm =                        ld_dlm
    ln =                         ld_ln
    type_p =                     ld_type_p
  TABLES
    parsd_source =               it_parsd_source
  EXCEPTIONS
    ILLEGAL_CHARACTER =          1
    INTERNAL_ERROR =             2
    TOKEN_TOO_LONG =             3
    UNBALANCED_QUOTES =          4
    .  "  CUPAX_GET_TOKEN

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_dlm
 
 TYPE STRING ,
ld_col
 
 TYPE STRING ,
it_parsd_source
 
 TYPE STANDARD TABLE OF PARS_TEXT ,
wa_parsd_source
 
 LIKE LINE OF it_parsd_source,
ld_ln
 
 TYPE STRING ,
ld_type_p
 
 TYPE STRING .


ld_col = 'some text here'. 

"populate fields of struture and append to itab
append wa_parsd_source to it_parsd_source.