SAP SALP_CLASS_AGGREG_GET Function Module for









SALP_CLASS_AGGREG_GET is a standard salp class aggreg get 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 salp class aggreg get FM, simply by entering the name SALP_CLASS_AGGREG_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function SALP_CLASS_AGGREG_GET 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 'SALP_CLASS_AGGREG_GET'"
  EXPORTING
   MTSYSID =  "
   MTECLASS =  "Alert: monitoring type class (perf., single msg.,...)
   GRANULARITY =  "
   FIRSTDAY =  "
   LASTDAY =  "
   TYPE_FLAG =  "
*  SFTPLYKEY =  "
*  FRCSTKEY =  "
*  ESTIMATE_FLAG =  "Single-character flag

 IMPORTING
   SHOW_DATA =  "

EXCEPTIONS
   WRONG_TYPE_FLAG = 1    EMPTY_DATA = 2    WRONG_GRAN = 3    SFT_POL_NOT_FOUND = 4
.



IMPORTING Parameters details for SALP_CLASS_AGGREG_GET

MTSYSID -

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

MTECLASS - Alert: monitoring type class (perf., single msg.,...)

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

GRANULARITY -

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

FIRSTDAY -

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

LASTDAY -

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

TYPE_FLAG -

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

SFTPLYKEY -

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

FRCSTKEY -

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

ESTIMATE_FLAG - Single-character flag

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

EXPORTING Parameters details for SALP_CLASS_AGGREG_GET

SHOW_DATA -

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

EXCEPTIONS details

WRONG_TYPE_FLAG -

Data type:
Optional: No
Call by Reference: Yes

EMPTY_DATA -

Data type:
Optional: No
Call by Reference: Yes

WRONG_GRAN -

Data type:
Optional: No
Call by Reference: Yes

SFT_POL_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SALP_CLASS_AGGREG_GET 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_mtsysid  TYPE SYSYSID, "   
lv_show_data  TYPE ALRVARCONT, "   
lv_wrong_type_flag  TYPE ALRVARCONT, "   
lv_mteclass  TYPE ALPERFOB-MTECLASS, "   
lv_empty_data  TYPE ALPERFOB, "   
lv_wrong_gran  TYPE ALPERFOB, "   
lv_granularity  TYPE ALPDBRTYP, "   
lv_firstday  TYPE ALDATE, "   
lv_sft_pol_not_found  TYPE ALDATE, "   
lv_lastday  TYPE ALDATE, "   
lv_type_flag  TYPE CHAR1, "   
lv_sftplykey  TYPE ALPFPOLKEY, "   
lv_frcstkey  TYPE ALPFPOLKEY, "   
lv_estimate_flag  TYPE CHAR1. "   

  CALL FUNCTION 'SALP_CLASS_AGGREG_GET'  "
    EXPORTING
         MTSYSID = lv_mtsysid
         MTECLASS = lv_mteclass
         GRANULARITY = lv_granularity
         FIRSTDAY = lv_firstday
         LASTDAY = lv_lastday
         TYPE_FLAG = lv_type_flag
         SFTPLYKEY = lv_sftplykey
         FRCSTKEY = lv_frcstkey
         ESTIMATE_FLAG = lv_estimate_flag
    IMPORTING
         SHOW_DATA = lv_show_data
    EXCEPTIONS
        WRONG_TYPE_FLAG = 1
        EMPTY_DATA = 2
        WRONG_GRAN = 3
        SFT_POL_NOT_FOUND = 4
. " SALP_CLASS_AGGREG_GET




ABAP code using 7.40 inline data declarations to call FM SALP_CLASS_AGGREG_GET

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 MTECLASS FROM ALPERFOB INTO @DATA(ld_mteclass).
 
 
 
 
 
 
 
 
 
 
 


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!