RHCT_OBJECT_CHECK_LEAF SAP Function module

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

Associated Function Group: RHCT
Released Date: . .
Processing type: Normal fucntion module

Pattern for FM RHCT_OBJECT_CHECK_LEAF - RHCT OBJECT CHECK LEAF

CALL FUNCTION 'RHCT_OBJECT_CHECK_LEAF' "
  EXPORTING
    sel_object =                " hrhctobjc     Object type / object ID
*   cat_plvar =                 " objec-plvar   Plan version
    cat_type =                  " t77oc-cattp   Catalog category from table T77OC
*   sel_begda = SY-DATUM        " objec-begda   Start of the analysis period
*   sel_endda = SY-DATUM        " objec-endda   End of the analysis period
*   sel_svect = '1'             " gdstr-svect
  IMPORTING
    leaf =                      " hrhctrefer-flag  'X': Object is sheet
  EXCEPTIONS
    OBJECT_NOT_VALID = 1        "               Object cannot be checked
    .  "  RHCT_OBJECT_CHECK_LEAF

ABAP code example for Function Module RHCT_OBJECT_CHECK_LEAF

The ABAP code below is a full code listing to execute function module RHCT_OBJECT_CHECK_LEAF 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_leaf  
 
 TYPE HRHCTREFER-FLAG
.


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


DATA(ld_cat_plvar) = some text here
 

SELECT single CATTP 
  FROM T77OC 
  INTO @DATA(ld_cat_type).



DATA(ld_sel_begda) = 20210129


DATA(ld_sel_endda) = 20210129


DATA(ld_sel_svect) = some text here
.

CALL FUNCTION 'RHCT_OBJECT_CHECK_LEAF'
  EXPORTING
    sel_object =                 ld_sel_object
*   cat_plvar =                  ld_cat_plvar
    cat_type =                   ld_cat_type
*   sel_begda =                  ld_sel_begda
*   sel_endda =                  ld_sel_endda
*   sel_svect =                  ld_sel_svect
  IMPORTING
    leaf =                       ld_leaf
  EXCEPTIONS
    OBJECT_NOT_VALID =           1
    .  "  RHCT_OBJECT_CHECK_LEAF

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_leaf
 
 TYPE HRHCTREFER-FLAG ,
ld_sel_object
 
 TYPE HRHCTOBJC ,
ld_cat_plvar
 
 TYPE OBJEC-PLVAR ,
ld_cat_type
 
 TYPE T77OC-CATTP ,
ld_sel_begda
 
 TYPE OBJEC-BEGDA ,
ld_sel_endda
 
 TYPE OBJEC-ENDDA ,
ld_sel_svect
 
 TYPE GDSTR-SVECT .


ld_sel_object = 'Check type of data required'.

ld_cat_plvar = some text here

SELECT single CATTP 
  FROM T77OC 
  INTO ld_cat_type.


ld_sel_begda = 20210129

ld_sel_endda = 20210129

ld_sel_svect = some text here