SAP Function Modules

PUT_CHECK_NAME_CLASS SAP Function module







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

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


Pattern for FM PUT_CHECK_NAME_CLASS - PUT CHECK NAME CLASS





CALL FUNCTION 'PUT_CHECK_NAME_CLASS' "
  EXPORTING
    wi_object =                 " tadir-object  TADIR OBJECT TYPE (for example: PROG/TABL/..)
    wi_objname =                " tadir-obj_name  TADIR OBJECT NAME (for example: )
    wi_pgmid =                  " tadir-pgmid   TADIR Object pgmID (for example: R3TR/..)
  IMPORTING
    we_name_class =             " gsugi_pa-w_tadir  S = SAP- / C = customer name range /' ' = general, open
    .  "  PUT_CHECK_NAME_CLASS

ABAP code example for Function Module PUT_CHECK_NAME_CLASS





The ABAP code below is a full code listing to execute function module PUT_CHECK_NAME_CLASS 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_we_name_class  TYPE GSUGI_PA-W_TADIR .


SELECT single OBJECT
FROM TADIR
INTO @DATA(ld_wi_object).


SELECT single OBJ_NAME
FROM TADIR
INTO @DATA(ld_wi_objname).


SELECT single PGMID
FROM TADIR
INTO @DATA(ld_wi_pgmid).
. CALL FUNCTION 'PUT_CHECK_NAME_CLASS' EXPORTING wi_object = ld_wi_object wi_objname = ld_wi_objname wi_pgmid = ld_wi_pgmid IMPORTING we_name_class = ld_we_name_class . " PUT_CHECK_NAME_CLASS
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_we_name_class  TYPE GSUGI_PA-W_TADIR ,
ld_wi_object  TYPE TADIR-OBJECT ,
ld_wi_objname  TYPE TADIR-OBJ_NAME ,
ld_wi_pgmid  TYPE TADIR-PGMID .


SELECT single OBJECT
FROM TADIR
INTO ld_wi_object.


SELECT single OBJ_NAME
FROM TADIR
INTO ld_wi_objname.


SELECT single PGMID
FROM TADIR
INTO ld_wi_pgmid.

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 PUT_CHECK_NAME_CLASS or its description.