SAP JIT18_SET_DEFAULT_VARIANT Function Module for NOTRANSL: Setzen der Defaultvariante für JIT6/JIT7









JIT18_SET_DEFAULT_VARIANT is a standard jit18 set default 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: Setzen der Defaultvariante für JIT6/JIT7 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 jit18 set default variant FM, simply by entering the name JIT18_SET_DEFAULT_VARIANT into the relevant SAP transaction such as SE37 or SE38.

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



Function JIT18_SET_DEFAULT_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 'JIT18_SET_DEFAULT_VARIANT'"NOTRANSL: Setzen der Defaultvariante für JIT6/JIT7
EXPORTING
TCVARIANT_IV = "Transaction variant

EXCEPTIONS
NO_UPDATE_POSSIBLE = 1
.



IMPORTING Parameters details for JIT18_SET_DEFAULT_VARIANT

TCVARIANT_IV - Transaction variant

Data type: TCVARIANT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_UPDATE_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JIT18_SET_DEFAULT_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_tcvariant_iv  TYPE TCVARIANT, "   
lv_no_update_possible  TYPE TCVARIANT. "   

  CALL FUNCTION 'JIT18_SET_DEFAULT_VARIANT'  "NOTRANSL: Setzen der Defaultvariante für JIT6/JIT7
    EXPORTING
         TCVARIANT_IV = lv_tcvariant_iv
    EXCEPTIONS
        NO_UPDATE_POSSIBLE = 1
. " JIT18_SET_DEFAULT_VARIANT




ABAP code using 7.40 inline data declarations to call FM JIT18_SET_DEFAULT_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.

 
 


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!