SAP PERFORMANCE_PROT_GET_DATA_2 Function Module for









PERFORMANCE_PROT_GET_DATA_2 is a standard performance prot get data 2 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 prot get data 2 FM, simply by entering the name PERFORMANCE_PROT_GET_DATA_2 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 + BasXML supported
Update:



Function PERFORMANCE_PROT_GET_DATA_2 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_PROT_GET_DATA_2'"
  EXPORTING
*  P_PROCGUID =  "
*  P_DARK_CALL = ' ' "
*  P_READ_CHECKLIST = ' ' "

 IMPORTING
   P_MAIN_TEST_INFO =  "
   P_ERROR =  "

TABLES
*  T_PERF_DATA =  "
*  T_AMASUR =  "
*  T_AMESISTA =  "
*  T_CHECKLIST =  "
*  T_CHECKLIST_2 =  "
*  T_LOGBOOK =  "

EXCEPTIONS
   NO_DATA = 1    NO_TEXT = 2    NO_DATA_SUM = 3    NO_GUID = 4
.



IMPORTING Parameters details for PERFORMANCE_PROT_GET_DATA_2

P_PROCGUID -

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

P_DARK_CALL -

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

P_READ_CHECKLIST -

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

EXPORTING Parameters details for PERFORMANCE_PROT_GET_DATA_2

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_PROT_GET_DATA_2

T_PERF_DATA -

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

T_AMASUR -

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

T_AMESISTA -

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

T_CHECKLIST -

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

T_CHECKLIST_2 -

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

T_LOGBOOK -

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

EXCEPTIONS details

NO_DATA -

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

NO_TEXT -

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

NO_DATA_SUM -

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

NO_GUID -

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

Copy and paste ABAP code example for PERFORMANCE_PROT_GET_DATA_2 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_no_data  TYPE STRING, "   
lv_p_procguid  TYPE PROCGUID, "   
lt_t_perf_data  TYPE STANDARD TABLE OF AMSUR, "   
lv_p_main_test_info  TYPE MAIN_TEST_INFO, "   
lv_no_text  TYPE MAIN_TEST_INFO, "   
lv_p_error  TYPE XFELD, "   
lt_t_amasur  TYPE STANDARD TABLE OF AMASUR, "   
lv_p_dark_call  TYPE XFELD, "   ' '
lt_t_amesista  TYPE STANDARD TABLE OF AMESISTA, "   
lv_no_data_sum  TYPE AMESISTA, "   
lv_p_read_checklist  TYPE XFELD, "   ' '
lv_no_guid  TYPE XFELD, "   
lt_t_checklist  TYPE STANDARD TABLE OF STRACKLIST, "   
lt_t_checklist_2  TYPE STANDARD TABLE OF STRACKLIST, "   
lt_t_logbook  TYPE STANDARD TABLE OF STRACPRO_D. "   

  CALL FUNCTION 'PERFORMANCE_PROT_GET_DATA_2'  "
    EXPORTING
         P_PROCGUID = lv_p_procguid
         P_DARK_CALL = lv_p_dark_call
         P_READ_CHECKLIST = lv_p_read_checklist
    IMPORTING
         P_MAIN_TEST_INFO = lv_p_main_test_info
         P_ERROR = lv_p_error
    TABLES
         T_PERF_DATA = lt_t_perf_data
         T_AMASUR = lt_t_amasur
         T_AMESISTA = lt_t_amesista
         T_CHECKLIST = lt_t_checklist
         T_CHECKLIST_2 = lt_t_checklist_2
         T_LOGBOOK = lt_t_logbook
    EXCEPTIONS
        NO_DATA = 1
        NO_TEXT = 2
        NO_DATA_SUM = 3
        NO_GUID = 4
. " PERFORMANCE_PROT_GET_DATA_2




ABAP code using 7.40 inline data declarations to call FM PERFORMANCE_PROT_GET_DATA_2

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_p_dark_call) = ' '.
 
 
 
DATA(ld_p_read_checklist) = ' '.
 
 
 
 
 


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!