SAP JIT10_GET_VARIANT Function Module for NOTRANSL: Ermitteln der Variante für den Benutzer und die Transaktion
JIT10_GET_VARIANT is a standard jit10 get 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 NOTRANSL: Ermitteln der Variante für den Benutzer und die Transaktion 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 jit10 get variant FM, simply by entering the name JIT10_GET_VARIANT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JIT10
Program Name: SAPLJIT10
Main Program: SAPLJIT10
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JIT10_GET_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 'JIT10_GET_VARIANT'"NOTRANSL: Ermitteln der Variante für den Benutzer und die Transaktion.
IMPORTING
AZVAR_EV = "Display Variant in JIT Cockpit
CHANGING
* UNAME_CV = SY-UNAME "User name
TCODE_CV = "Transaction Code
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLJIT10_001 JIT-Cockpit - Display Component List in HTML Format
EXIT_SAPLJIT10_002 JIT: Customer-Exit for Triggering Workflow by the Signal Monitor
EXPORTING Parameters details for JIT10_GET_VARIANT
AZVAR_EV - Display Variant in JIT Cockpit
Data type: JITTC0-AZVAROptional: No
Call by Reference: Yes
CHANGING Parameters details for JIT10_GET_VARIANT
UNAME_CV - User name
Data type: JITTC0-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
TCODE_CV - Transaction Code
Data type: JITTC0-TCODEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JIT10_GET_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_azvar_ev | TYPE JITTC0-AZVAR, " | |||
| lv_uname_cv | TYPE JITTC0-UNAME, " SY-UNAME | |||
| lv_tcode_cv | TYPE JITTC0-TCODE. " |
|   CALL FUNCTION 'JIT10_GET_VARIANT' "NOTRANSL: Ermitteln der Variante für den Benutzer und die Transaktion |
| IMPORTING | ||
| AZVAR_EV | = lv_azvar_ev | |
| CHANGING | ||
| UNAME_CV | = lv_uname_cv | |
| TCODE_CV | = lv_tcode_cv | |
| . " JIT10_GET_VARIANT | ||
ABAP code using 7.40 inline data declarations to call FM JIT10_GET_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 AZVAR FROM JITTC0 INTO @DATA(ld_azvar_ev). | ||||
| "SELECT single UNAME FROM JITTC0 INTO @DATA(ld_uname_cv). | ||||
| DATA(ld_uname_cv) | = SY-UNAME. | |||
| "SELECT single TCODE FROM JITTC0 INTO @DATA(ld_tcode_cv). | ||||
Search for further information about these or an SAP related objects