SAP SALI_PERF_REPORT_VALUE Function Module for









SALI_PERF_REPORT_VALUE is a standard sali perf report value 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 sali perf report value FM, simply by entering the name SALI_PERF_REPORT_VALUE into the relevant SAP transaction such as SE37 or SE38.

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



Function SALI_PERF_REPORT_VALUE 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 'SALI_PERF_REPORT_VALUE'"
EXPORTING
TOTAL_OF_REPORTED_VALUES = "
* NUMBER_OF_REPORTED_VALUES = 1 "
* REPORTEDBY = "

IMPORTING
DETAILED_ERROR_TEXT = "

CHANGING
TID = "

EXCEPTIONS
INVALID_TID = 1 WRONG_TYPECLASS = 2 INVALID_PARAMETERS = 3 COMMUNICATION_FAILURE = 4 OTHER_PROBLEM = 5 WRONG_SEGMENT = 6 INTERNAL_FAILURE_SALS = 7
.



IMPORTING Parameters details for SALI_PERF_REPORT_VALUE

TOTAL_OF_REPORTED_VALUES -

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

NUMBER_OF_REPORTED_VALUES -

Data type: ALPERFRVAL-NUMOFEVENT
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

REPORTEDBY -

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

EXPORTING Parameters details for SALI_PERF_REPORT_VALUE

DETAILED_ERROR_TEXT -

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

CHANGING Parameters details for SALI_PERF_REPORT_VALUE

TID -

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

EXCEPTIONS details

INVALID_TID -

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

WRONG_TYPECLASS -

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

INVALID_PARAMETERS - Invalid parameter

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

COMMUNICATION_FAILURE -

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

OTHER_PROBLEM -

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

WRONG_SEGMENT -

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

INTERNAL_FAILURE_SALS -

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

Copy and paste ABAP code example for SALI_PERF_REPORT_VALUE 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_tid  TYPE ALGLOBTID, "   
lv_invalid_tid  TYPE ALGLOBTID, "   
lv_detailed_error_text  TYPE STRING, "   
lv_total_of_reported_values  TYPE ALPERFRVAL-NEWPVALSUM, "   
lv_wrong_typeclass  TYPE ALPERFRVAL, "   
lv_number_of_reported_values  TYPE ALPERFRVAL-NUMOFEVENT, "   1
lv_reportedby  TYPE C, "   
lv_invalid_parameters  TYPE C, "   
lv_communication_failure  TYPE C, "   
lv_other_problem  TYPE C, "   
lv_wrong_segment  TYPE C, "   
lv_internal_failure_sals  TYPE C. "   

  CALL FUNCTION 'SALI_PERF_REPORT_VALUE'  "
    EXPORTING
         TOTAL_OF_REPORTED_VALUES = lv_total_of_reported_values
         NUMBER_OF_REPORTED_VALUES = lv_number_of_reported_values
         REPORTEDBY = lv_reportedby
    IMPORTING
         DETAILED_ERROR_TEXT = lv_detailed_error_text
    CHANGING
         TID = lv_tid
    EXCEPTIONS
        INVALID_TID = 1
        WRONG_TYPECLASS = 2
        INVALID_PARAMETERS = 3
        COMMUNICATION_FAILURE = 4
        OTHER_PROBLEM = 5
        WRONG_SEGMENT = 6
        INTERNAL_FAILURE_SALS = 7
. " SALI_PERF_REPORT_VALUE




ABAP code using 7.40 inline data declarations to call FM SALI_PERF_REPORT_VALUE

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 NEWPVALSUM FROM ALPERFRVAL INTO @DATA(ld_total_of_reported_values).
 
 
"SELECT single NUMOFEVENT FROM ALPERFRVAL INTO @DATA(ld_number_of_reported_values).
DATA(ld_number_of_reported_values) = 1.
 
 
 
 
 
 
 


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!