SAP PERFORMANCE_VALIDATE Function Module for









PERFORMANCE_VALIDATE is a standard performance validate 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 performance validate FM, simply by entering the name PERFORMANCE_VALIDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PERF_TRA_DIA
Program Name: SAPLPERF_TRA_DIA
Main Program: SAPLPERF_TRA_DIA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PERFORMANCE_VALIDATE 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 'PERFORMANCE_VALIDATE'"
  EXPORTING
   P_LOGID =  "
*  P_PERFTEST_TEXT1 =  "
*  P_PERFTEST_TEXT2 =  "
*  P_START_TIME =  "
*  P_START_DATE =  "
*  P_END_TIME =  "
*  P_END_DATE =  "
*  P_VALIDATION_TYPE =  "

 IMPORTING
   P_MAIN_TEST_INFO =  "
   P_ERROR =  "

TABLES
*  T_PERF_DATA =  "
*  T_LOGBOOK =  "
*  T_CHKLIST =  "
*  T_ADD_TEST_INFO =  "
.



IMPORTING Parameters details for PERFORMANCE_VALIDATE

P_LOGID -

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

P_PERFTEST_TEXT1 -

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

P_PERFTEST_TEXT2 -

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

P_START_TIME -

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

P_START_DATE -

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

P_END_TIME -

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

P_END_DATE -

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

P_VALIDATION_TYPE -

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

EXPORTING Parameters details for PERFORMANCE_VALIDATE

P_MAIN_TEST_INFO -

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

P_ERROR -

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

TABLES Parameters details for PERFORMANCE_VALIDATE

T_PERF_DATA -

Data type: AMSUR
Optional: Yes
Call by Reference: Yes

T_LOGBOOK -

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

T_CHKLIST -

Data type: STRACKLIST
Optional: Yes
Call by Reference: Yes

T_ADD_TEST_INFO -

Data type: ADD_TEST_INFO
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for PERFORMANCE_VALIDATE 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_p_logid  TYPE REFID1, "   
lt_t_perf_data  TYPE STANDARD TABLE OF AMSUR, "   
lv_p_main_test_info  TYPE MAIN_TEST_INFO, "   
lv_p_error  TYPE XFELD, "   
lt_t_logbook  TYPE STANDARD TABLE OF STRACPRO_D, "   
lv_p_perftest_text1  TYPE PROTIDTEXT, "   
lt_t_chklist  TYPE STANDARD TABLE OF STRACKLIST, "   
lv_p_perftest_text2  TYPE PROTIDTEXT, "   
lv_p_start_time  TYPE TSTARTDATE, "   
lt_t_add_test_info  TYPE STANDARD TABLE OF ADD_TEST_INFO, "   
lv_p_start_date  TYPE TSTARTTIME, "   
lv_p_end_time  TYPE TENDDATE, "   
lv_p_end_date  TYPE TENDTIME, "   
lv_p_validation_type  TYPE ADD_TEST_INFO. "   

  CALL FUNCTION 'PERFORMANCE_VALIDATE'  "
    EXPORTING
         P_LOGID = lv_p_logid
         P_PERFTEST_TEXT1 = lv_p_perftest_text1
         P_PERFTEST_TEXT2 = lv_p_perftest_text2
         P_START_TIME = lv_p_start_time
         P_START_DATE = lv_p_start_date
         P_END_TIME = lv_p_end_time
         P_END_DATE = lv_p_end_date
         P_VALIDATION_TYPE = lv_p_validation_type
    IMPORTING
         P_MAIN_TEST_INFO = lv_p_main_test_info
         P_ERROR = lv_p_error
    TABLES
         T_PERF_DATA = lt_t_perf_data
         T_LOGBOOK = lt_t_logbook
         T_CHKLIST = lt_t_chklist
         T_ADD_TEST_INFO = lt_t_add_test_info
. " PERFORMANCE_VALIDATE




ABAP code using 7.40 inline data declarations to call FM PERFORMANCE_VALIDATE

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!