WCGZ_WCMOBJ_STATUS_CHECK SAP Function module

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

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

Pattern for FM WCGZ_WCMOBJ_STATUS_CHECK - WCGZ WCMOBJ STATUS CHECK

CALL FUNCTION 'WCGZ_WCMOBJ_STATUS_CHECK' "
  EXPORTING
    i_iwerk =                   " iwerk         Planning Plant
    i_objart =                  " wceobjart     Object Type
    i_objtyp =                  " wcetyp        Subobject Type
    i_objnr =                   " j_objnr       Object Number
    i_aktyp =                   " aktyp         Activity Type in the Transaction
    i_info =                    " wceinfo       Boolean Value: Message Can Be Output
    i_status =                  " j_status      Status
  IMPORTING
    e_return_value =            " sysubrc       Return Value
  EXCEPTIONS
    ERROR = 1                   "
    .  "  WCGZ_WCMOBJ_STATUS_CHECK

ABAP code example for Function Module WCGZ_WCMOBJ_STATUS_CHECK

The ABAP code below is a full code listing to execute function module WCGZ_WCMOBJ_STATUS_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_e_return_value  
 
 TYPE SYSUBRC
.


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

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

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

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

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

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

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

CALL FUNCTION 'WCGZ_WCMOBJ_STATUS_CHECK'
  EXPORTING
    i_iwerk =                    ld_i_iwerk
    i_objart =                   ld_i_objart
    i_objtyp =                   ld_i_objtyp
    i_objnr =                    ld_i_objnr
    i_aktyp =                    ld_i_aktyp
    i_info =                     ld_i_info
    i_status =                   ld_i_status
  IMPORTING
    e_return_value =             ld_e_return_value
  EXCEPTIONS
    ERROR =                      1
    .  "  WCGZ_WCMOBJ_STATUS_CHECK

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_return_value
 
 TYPE SYSUBRC ,
ld_i_iwerk
 
 TYPE IWERK ,
ld_i_objart
 
 TYPE WCEOBJART ,
ld_i_objtyp
 
 TYPE WCETYP ,
ld_i_objnr
 
 TYPE J_OBJNR ,
ld_i_aktyp
 
 TYPE AKTYP ,
ld_i_info
 
 TYPE WCEINFO ,
ld_i_status
 
 TYPE J_STATUS .


ld_i_iwerk = 'Check type of data required'.
ld_i_objart = 'Check type of data required'.
ld_i_objtyp = 'Check type of data required'.
ld_i_objnr = 'Check type of data required'.
ld_i_aktyp = 'Check type of data required'.
ld_i_info = 'Check type of data required'.
ld_i_status = 'Check type of data required'.