S_TCC_INTERNAL_OBJSTATUS SAP Function module - TCC internal: Object Status

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

Associated Function Group: S_LMCFG_SERVICES
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM S_TCC_INTERNAL_OBJSTATUS - S TCC INTERNAL OBJSTATUS

CALL FUNCTION 'S_TCC_INTERNAL_OBJSTATUS' "TCC internal: Object Status
  EXPORTING
*   ip_action = 'R'             " char1         C=Create, D=Delete, R=Read
    ip_objtype =                " trobjtype     Object Type
    ip_objname =                " char30        Object Name
*   ip_validity = 3600          " i             Validity of new entry in seconds
  IMPORTING
    ep_status =                 " char1         A=Active, Space=Inactive
* TABLES
*   return =                    " bapiret2      Return Parameter
    .  "  S_TCC_INTERNAL_OBJSTATUS

ABAP code example for Function Module S_TCC_INTERNAL_OBJSTATUS

The ABAP code below is a full code listing to execute function module S_TCC_INTERNAL_OBJSTATUS 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_ep_status  
 
 TYPE CHAR1
,
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.


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

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

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

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

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'S_TCC_INTERNAL_OBJSTATUS'
  EXPORTING
*   ip_action =                  ld_ip_action
    ip_objtype =                 ld_ip_objtype
    ip_objname =                 ld_ip_objname
*   ip_validity =                ld_ip_validity
  IMPORTING
    ep_status =                  ld_ep_status
* TABLES
*   return =                     it_return
    .  "  S_TCC_INTERNAL_OBJSTATUS

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_ep_status
 
 TYPE CHAR1 ,
ld_ip_action
 
 TYPE CHAR1 ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_ip_objtype
 
 TYPE TROBJTYPE ,
ld_ip_objname
 
 TYPE CHAR30 ,
ld_ip_validity
 
 TYPE I .


ld_ip_action = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_return to it_return.
ld_ip_objtype = 'Check type of data required'.
ld_ip_objname = 'Check type of data required'.
ld_ip_validity = 'Check type of data required'.