SAP SD_COND_VARA_ACTIVE_TEST Function Module for
SD_COND_VARA_ACTIVE_TEST is a standard sd cond vara active test SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sd cond vara active test FM, simply by entering the name SD_COND_VARA_ACTIVE_TEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: V13F
Program Name: SAPLV13F
Main Program: SAPLV13F
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_COND_VARA_ACTIVE_TEST 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 'SD_COND_VARA_ACTIVE_TEST'".
EXPORTING
ABTYP_I = "Agreement category
KAPPL_I = "Application
KVEWE_I = "Usage
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for SD_COND_VARA_ACTIVE_TEST
ABTYP_I - Agreement category
Data type: T672-ABTYPOptional: No
Call by Reference: No ( called with pass by value option)
KAPPL_I - Application
Data type: T681A-KAPPLOptional: No
Call by Reference: No ( called with pass by value option)
KVEWE_I - Usage
Data type: T681V-KVEWEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_COND_VARA_ACTIVE_TEST 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_error | TYPE STRING, " | |||
| lv_abtyp_i | TYPE T672-ABTYP, " | |||
| lv_kappl_i | TYPE T681A-KAPPL, " | |||
| lv_kvewe_i | TYPE T681V-KVEWE. " |
|   CALL FUNCTION 'SD_COND_VARA_ACTIVE_TEST' " |
| EXPORTING | ||
| ABTYP_I | = lv_abtyp_i | |
| KAPPL_I | = lv_kappl_i | |
| KVEWE_I | = lv_kvewe_i | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " SD_COND_VARA_ACTIVE_TEST | ||
ABAP code using 7.40 inline data declarations to call FM SD_COND_VARA_ACTIVE_TEST
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 ABTYP FROM T672 INTO @DATA(ld_abtyp_i). | ||||
| "SELECT single KAPPL FROM T681A INTO @DATA(ld_kappl_i). | ||||
| "SELECT single KVEWE FROM T681V INTO @DATA(ld_kvewe_i). | ||||
Search for further information about these or an SAP related objects