SAP SALP_AGGREG_MIN2DAY Function Module for
SALP_AGGREG_MIN2DAY is a standard salp aggreg min2day 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 aggreg min2day FM, simply by entering the name SALP_AGGREG_MIN2DAY 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_AGGREG_MIN2DAY 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_AGGREG_MIN2DAY'".
EXPORTING
IN_TID = "Alert: global TID as key (w/o INDEX fields)
* ALLOW_RECURSIVE_CALL = ' ' "Single-Character Flag
IN_RECTYPE = "Montoring infra. perf.DB record type
FIRSTDAY = "Alert: date
LASTDAY = "Alert: date
* SCHEMENAME = '' "Monitoring architecture: Performance database schema key
* SFTNAME = '' "Monitoring architecture: Performance database schema key
* OUT_TIMEZONE = '' "Time Zone
* LOADTABLE = 'X' "Single-Character Flag
* USED_FLAG = ' ' "Single-Character Flag
IMPORTING
OUT_DATA = "Mon. Arch.: PerfDB Cluster for Day Average of ONE Day
OUT_STATUS = "Monitoring infra. perf DB record status
TABLES
* PERFDB_DATA = "Shortened ALPERFDB Structure (Without Cluster)
EXCEPTIONS
WRONG_RECTYPE = 1
IMPORTING Parameters details for SALP_AGGREG_MIN2DAY
IN_TID - Alert: global TID as key (w/o INDEX fields)
Data type: ALTIDKEYOptional: No
Call by Reference: No ( called with pass by value option)
ALLOW_RECURSIVE_CALL - Single-Character Flag
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IN_RECTYPE - Montoring infra. perf.DB record type
Data type: ALPDBRTYPOptional: No
Call by Reference: No ( called with pass by value option)
FIRSTDAY - Alert: date
Data type: ALDATEOptional: No
Call by Reference: No ( called with pass by value option)
LASTDAY - Alert: date
Data type: ALDATEOptional: No
Call by Reference: No ( called with pass by value option)
SCHEMENAME - Monitoring architecture: Performance database schema key
Data type: ALPFPOLKEYDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
SFTNAME - Monitoring architecture: Performance database schema key
Data type: ALPFPOLKEYDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
OUT_TIMEZONE - Time Zone
Data type: TIMEZONEDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOADTABLE - Single-Character Flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
USED_FLAG - Single-Character Flag
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SALP_AGGREG_MIN2DAY
OUT_DATA - Mon. Arch.: PerfDB Cluster for Day Average of ONE Day
Data type: ALPERFCL_DOptional: No
Call by Reference: Yes
OUT_STATUS - Monitoring infra. perf DB record status
Data type: ALPDBRSTATOptional: No
Call by Reference: Yes
TABLES Parameters details for SALP_AGGREG_MIN2DAY
PERFDB_DATA - Shortened ALPERFDB Structure (Without Cluster)
Data type: ALPERFDBOCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_RECTYPE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SALP_AGGREG_MIN2DAY 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_in_tid | TYPE ALTIDKEY, " | |||
| lv_out_data | TYPE ALPERFCL_D, " | |||
| lt_perfdb_data | TYPE STANDARD TABLE OF ALPERFDBOC, " | |||
| lv_wrong_rectype | TYPE ALPERFDBOC, " | |||
| lv_allow_recursive_call | TYPE CHAR1, " ' ' | |||
| lv_in_rectype | TYPE ALPDBRTYP, " | |||
| lv_out_status | TYPE ALPDBRSTAT, " | |||
| lv_firstday | TYPE ALDATE, " | |||
| lv_lastday | TYPE ALDATE, " | |||
| lv_schemename | TYPE ALPFPOLKEY, " '' | |||
| lv_sftname | TYPE ALPFPOLKEY, " '' | |||
| lv_out_timezone | TYPE TIMEZONE, " '' | |||
| lv_loadtable | TYPE CHAR1, " 'X' | |||
| lv_used_flag | TYPE CHAR1. " ' ' |
|   CALL FUNCTION 'SALP_AGGREG_MIN2DAY' " |
| EXPORTING | ||
| IN_TID | = lv_in_tid | |
| ALLOW_RECURSIVE_CALL | = lv_allow_recursive_call | |
| IN_RECTYPE | = lv_in_rectype | |
| FIRSTDAY | = lv_firstday | |
| LASTDAY | = lv_lastday | |
| SCHEMENAME | = lv_schemename | |
| SFTNAME | = lv_sftname | |
| OUT_TIMEZONE | = lv_out_timezone | |
| LOADTABLE | = lv_loadtable | |
| USED_FLAG | = lv_used_flag | |
| IMPORTING | ||
| OUT_DATA | = lv_out_data | |
| OUT_STATUS | = lv_out_status | |
| TABLES | ||
| PERFDB_DATA | = lt_perfdb_data | |
| EXCEPTIONS | ||
| WRONG_RECTYPE = 1 | ||
| . " SALP_AGGREG_MIN2DAY | ||
ABAP code using 7.40 inline data declarations to call FM SALP_AGGREG_MIN2DAY
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_allow_recursive_call) | = ' '. | |||
| DATA(ld_schemename) | = ''. | |||
| DATA(ld_sftname) | = ''. | |||
| DATA(ld_out_timezone) | = ''. | |||
| DATA(ld_loadtable) | = 'X'. | |||
| DATA(ld_used_flag) | = ' '. | |||
Search for further information about these or an SAP related objects