SAP TRINT_GTABKEY_CHK_CASCADE Function Module for check whether sw comp can be cascaded









TRINT_GTABKEY_CHK_CASCADE is a standard trint gtabkey chk cascade SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for check whether sw comp can be cascaded processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for trint gtabkey chk cascade FM, simply by entering the name TRINT_GTABKEY_CHK_CASCADE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SGTA
Program Name: SAPLSGTA
Main Program: SAPLSGTA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TRINT_GTABKEY_CHK_CASCADE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'TRINT_GTABKEY_CHK_CASCADE'"check whether sw comp can be cascaded
EXPORTING
IV_CDLVUNIT = "
IV_CRELEASE = "
IV_CHECK_ALSO = "

CHANGING
CV_RC = "

EXCEPTIONS
WRONG_CALL = 1
.



IMPORTING Parameters details for TRINT_GTABKEY_CHK_CASCADE

IV_CDLVUNIT -

Data type: DLVUNIT
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CRELEASE -

Data type: SAPRELEASE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CHECK_ALSO -

Data type: CGKGROUP
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for TRINT_GTABKEY_CHK_CASCADE

CV_RC -

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TRINT_GTABKEY_CHK_CASCADE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_cv_rc  TYPE SY-SUBRC, "   
lv_wrong_call  TYPE SY, "   
lv_iv_cdlvunit  TYPE DLVUNIT, "   
lv_iv_crelease  TYPE SAPRELEASE, "   
lv_iv_check_also  TYPE CGKGROUP. "   

  CALL FUNCTION 'TRINT_GTABKEY_CHK_CASCADE'  "check whether sw comp can be cascaded
    EXPORTING
         IV_CDLVUNIT = lv_iv_cdlvunit
         IV_CRELEASE = lv_iv_crelease
         IV_CHECK_ALSO = lv_iv_check_also
    CHANGING
         CV_RC = lv_cv_rc
    EXCEPTIONS
        WRONG_CALL = 1
. " TRINT_GTABKEY_CHK_CASCADE




ABAP code using 7.40 inline data declarations to call FM TRINT_GTABKEY_CHK_CASCADE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single SUBRC FROM SY INTO @DATA(ld_cv_rc).
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!