SAP RS_HDSYS_CALL_TC_VARIANT Function Module for External: Call Transaction With Variant









RS_HDSYS_CALL_TC_VARIANT is a standard rs hdsys call tc variant SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for External: Call Transaction With Variant 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 rs hdsys call tc variant FM, simply by entering the name RS_HDSYS_CALL_TC_VARIANT into the relevant SAP transaction such as SE37 or SE38.

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



Function RS_HDSYS_CALL_TC_VARIANT 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 'RS_HDSYS_CALL_TC_VARIANT'"External: Call Transaction With Variant
EXPORTING
TCODE = "
* RESET_AFTER_CALL_TC = "
* VTCODE = "
* VARIANT = "Variant Name
* I_FLAG_CLIENT_INDEPENDENT = "Cross-client variant
* CALL_MODE = 'X' "
* AUTHORITY_CHECK = 'X' "
* VARIANT_CHECK = 'X' "
* NO_EXPORT = "
* I_FLAG_SKIP_FIRST_SCREEN = "

EXCEPTIONS
NO_VARIANT = 1 NO_AUTHORITY_TCODE = 2
.



IMPORTING Parameters details for RS_HDSYS_CALL_TC_VARIANT

TCODE -

Data type: SHDFV-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

RESET_AFTER_CALL_TC -

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

VTCODE -

Data type: SHDFV-TCODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

VARIANT - Variant Name

Data type: SHDFV-TCVARIANT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLAG_CLIENT_INDEPENDENT - Cross-client variant

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

CALL_MODE -

Data type: AS4FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUTHORITY_CHECK -

Data type: AS4FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VARIANT_CHECK -

Data type: AS4FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_EXPORT -

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

I_FLAG_SKIP_FIRST_SCREEN -

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

EXCEPTIONS details

NO_VARIANT - Variant does not exist

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

NO_AUTHORITY_TCODE -

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

Copy and paste ABAP code example for RS_HDSYS_CALL_TC_VARIANT 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_tcode  TYPE SHDFV-TCODE, "   
lv_no_variant  TYPE SHDFV, "   
lv_reset_after_call_tc  TYPE AS4FLAG, "   
lv_vtcode  TYPE SHDFV-TCODE, "   
lv_no_authority_tcode  TYPE SHDFV, "   
lv_variant  TYPE SHDFV-TCVARIANT, "   
lv_i_flag_client_independent  TYPE AS4FLAG, "   
lv_call_mode  TYPE AS4FLAG, "   'X'
lv_authority_check  TYPE AS4FLAG, "   'X'
lv_variant_check  TYPE AS4FLAG, "   'X'
lv_no_export  TYPE AS4FLAG, "   
lv_i_flag_skip_first_screen  TYPE AS4FLAG. "   

  CALL FUNCTION 'RS_HDSYS_CALL_TC_VARIANT'  "External: Call Transaction With Variant
    EXPORTING
         TCODE = lv_tcode
         RESET_AFTER_CALL_TC = lv_reset_after_call_tc
         VTCODE = lv_vtcode
         VARIANT = lv_variant
         I_FLAG_CLIENT_INDEPENDENT = lv_i_flag_client_independent
         CALL_MODE = lv_call_mode
         AUTHORITY_CHECK = lv_authority_check
         VARIANT_CHECK = lv_variant_check
         NO_EXPORT = lv_no_export
         I_FLAG_SKIP_FIRST_SCREEN = lv_i_flag_skip_first_screen
    EXCEPTIONS
        NO_VARIANT = 1
        NO_AUTHORITY_TCODE = 2
. " RS_HDSYS_CALL_TC_VARIANT




ABAP code using 7.40 inline data declarations to call FM RS_HDSYS_CALL_TC_VARIANT

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 TCODE FROM SHDFV INTO @DATA(ld_tcode).
 
 
 
"SELECT single TCODE FROM SHDFV INTO @DATA(ld_vtcode).
 
 
"SELECT single TCVARIANT FROM SHDFV INTO @DATA(ld_variant).
 
 
DATA(ld_call_mode) = 'X'.
 
DATA(ld_authority_check) = 'X'.
 
DATA(ld_variant_check) = 'X'.
 
 
 


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!