SAP Function Modules

SEO_TYPE_EXISTENCE_CHECK SAP Function module







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

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


Pattern for FM SEO_TYPE_EXISTENCE_CHECK - SEO TYPE EXISTENCE CHECK





CALL FUNCTION 'SEO_TYPE_EXISTENCE_CHECK' "
  EXPORTING
*   cifkey =                    " seoclskey
    typkey =                    " seocmpkey
  IMPORTING
    deleted =                   " seox_boolean  Deleted
  EXCEPTIONS
    CLIF_NOT_EXISTING = 1       "
    NOT_SPECIFIED = 2           "
    NOT_EXISTING = 3            "
    IS_ATTRIBUTE = 4            "
    IS_METHOD = 5               "
    IS_EVENT = 6                "
    NO_TEXT = 7                 "
    INCONSISTENT = 8            "
    .  "  SEO_TYPE_EXISTENCE_CHECK

ABAP code example for Function Module SEO_TYPE_EXISTENCE_CHECK





The ABAP code below is a full code listing to execute function module SEO_TYPE_EXISTENCE_CHECK 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_deleted  TYPE SEOX_BOOLEAN .

DATA(ld_cifkey) = 'Check type of data required'.
DATA(ld_typkey) = 'Check type of data required'. . CALL FUNCTION 'SEO_TYPE_EXISTENCE_CHECK' EXPORTING * cifkey = ld_cifkey typkey = ld_typkey IMPORTING deleted = ld_deleted EXCEPTIONS CLIF_NOT_EXISTING = 1 NOT_SPECIFIED = 2 NOT_EXISTING = 3 IS_ATTRIBUTE = 4 IS_METHOD = 5 IS_EVENT = 6 NO_TEXT = 7 INCONSISTENT = 8 . " SEO_TYPE_EXISTENCE_CHECK
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 ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 8. "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_deleted  TYPE SEOX_BOOLEAN ,
ld_cifkey  TYPE SEOCLSKEY ,
ld_typkey  TYPE SEOCMPKEY .

ld_cifkey = 'Check type of data required'.
ld_typkey = '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 SEO_TYPE_EXISTENCE_CHECK or its description.