SAP GET_COVERAGE_FOR_OBJECT_LIST Function Module for









GET_COVERAGE_FOR_OBJECT_LIST is a standard get coverage for object list 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 get coverage for object list FM, simply by entering the name GET_COVERAGE_FOR_OBJECT_LIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCV_EVALUATION_REMOTE
Program Name: SAPLSCV_EVALUATION_REMOTE
Main Program: SAPLSCV_EVALUATION_REMOTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:



Function GET_COVERAGE_FOR_OBJECT_LIST 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 'GET_COVERAGE_FOR_OBJECT_LIST'"
EXPORTING
I_TESTKEY = "
I_OBJECT_DIRECTORY_ELEMENTS = "
* I_WITH_BRANCH_COVERAGE = ' ' "
* I_WITH_PROCEDURE_COVERAGE = ' ' "
* I_WITH_STATEMENT_COVERAGE = 'X' "

IMPORTING
E_COVERAGE_RESULTS = "

EXCEPTIONS
EXECUTION_ERROR = 1 NO_AUTHORIZATION = 2 NO_COVERAGE_TYPE_CHOSEN = 3 TESTKEY_DOES_NOT_EXIST = 4
.



IMPORTING Parameters details for GET_COVERAGE_FOR_OBJECT_LIST

I_TESTKEY -

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

I_OBJECT_DIRECTORY_ELEMENTS -

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

I_WITH_BRANCH_COVERAGE -

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

I_WITH_PROCEDURE_COVERAGE -

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

I_WITH_STATEMENT_COVERAGE -

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

EXPORTING Parameters details for GET_COVERAGE_FOR_OBJECT_LIST

E_COVERAGE_RESULTS -

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

EXCEPTIONS details

EXECUTION_ERROR -

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

NO_AUTHORIZATION -

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

NO_COVERAGE_TYPE_CHOSEN -

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

TESTKEY_DOES_NOT_EXIST -

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

Copy and paste ABAP code example for GET_COVERAGE_FOR_OBJECT_LIST 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_i_testkey  TYPE CVA_TESTK, "   
lv_execution_error  TYPE CVA_TESTK, "   
lv_e_coverage_results  TYPE CVT_COVERAGE_RESULT_R3TRS, "   
lv_no_authorization  TYPE CVT_COVERAGE_RESULT_R3TRS, "   
lv_i_object_directory_elements  TYPE CVT_OBJECT_DIRECTORY_ELEMENTS, "   
lv_i_with_branch_coverage  TYPE BOOLE_D, "   SPACE
lv_no_coverage_type_chosen  TYPE BOOLE_D, "   
lv_testkey_does_not_exist  TYPE BOOLE_D, "   
lv_i_with_procedure_coverage  TYPE BOOLE_D, "   SPACE
lv_i_with_statement_coverage  TYPE BOOLE_D. "   'X'

  CALL FUNCTION 'GET_COVERAGE_FOR_OBJECT_LIST'  "
    EXPORTING
         I_TESTKEY = lv_i_testkey
         I_OBJECT_DIRECTORY_ELEMENTS = lv_i_object_directory_elements
         I_WITH_BRANCH_COVERAGE = lv_i_with_branch_coverage
         I_WITH_PROCEDURE_COVERAGE = lv_i_with_procedure_coverage
         I_WITH_STATEMENT_COVERAGE = lv_i_with_statement_coverage
    IMPORTING
         E_COVERAGE_RESULTS = lv_e_coverage_results
    EXCEPTIONS
        EXECUTION_ERROR = 1
        NO_AUTHORIZATION = 2
        NO_COVERAGE_TYPE_CHOSEN = 3
        TESTKEY_DOES_NOT_EXIST = 4
. " GET_COVERAGE_FOR_OBJECT_LIST




ABAP code using 7.40 inline data declarations to call FM GET_COVERAGE_FOR_OBJECT_LIST

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.

 
 
 
 
 
DATA(ld_i_with_branch_coverage) = ' '.
 
 
 
DATA(ld_i_with_procedure_coverage) = ' '.
 
DATA(ld_i_with_statement_coverage) = '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!