SAP SALP_GET_DATA_FROM_PERFDB Function Module for









SALP_GET_DATA_FROM_PERFDB is a standard salp get data from perfdb 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 get data from perfdb FM, simply by entering the name SALP_GET_DATA_FROM_PERFDB 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_GET_DATA_FROM_PERFDB 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_GET_DATA_FROM_PERFDB'"
  EXPORTING
   TID =  "Alert: global TID as key (w/o INDEX fields)
*  TRY_REMOTE = ' ' "Single-Character Flag
*  REMOTE_ONLY = ' ' "Single-Character Flag
   OUT_FIRSTDAY =  "Alert: date
   OUT_LASTDAY =  "Alert: date
   OUT_RECTYPE =  "Montoring infra. perf.DB record type
*  XDAY_X = '10' "Natural Number
*  SFTNAME =  "Monitoring architecture: Performance database schema key
*  CALNAME =  "Monitoring architecture: Performance database schema key
*  OUT_TIMEZONE =  "Time Zone
*  NO_NULL = 'X' "Single-Character Flag

TABLES
   OUT_TAB =  "Structure of Output Table for PerfDB Reading

EXCEPTIONS
   NO_DATA_IN_PERFDB = 1    NO_RFC_DESTINATION = 2
.



IMPORTING Parameters details for SALP_GET_DATA_FROM_PERFDB

TID - Alert: global TID as key (w/o INDEX fields)

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

TRY_REMOTE - Single-Character Flag

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

REMOTE_ONLY - Single-Character Flag

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

OUT_FIRSTDAY - Alert: date

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

OUT_LASTDAY - Alert: date

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

OUT_RECTYPE - Montoring infra. perf.DB record type

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

XDAY_X - Natural Number

Data type: INT4
Default: '10'
Optional: Yes
Call by Reference: Yes

SFTNAME - Monitoring architecture: Performance database schema key

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

CALNAME - Monitoring architecture: Performance database schema key

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

OUT_TIMEZONE - Time Zone

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

NO_NULL - Single-Character Flag

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

TABLES Parameters details for SALP_GET_DATA_FROM_PERFDB

OUT_TAB - Structure of Output Table for PerfDB Reading

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

EXCEPTIONS details

NO_DATA_IN_PERFDB -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_DESTINATION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SALP_GET_DATA_FROM_PERFDB 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 ALTIDKEY, "   
lt_out_tab  TYPE STANDARD TABLE OF ALPF_OUTTAB_STR, "   
lv_no_data_in_perfdb  TYPE ALPF_OUTTAB_STR, "   
lv_try_remote  TYPE CHAR1, "   ' '
lv_remote_only  TYPE CHAR1, "   ' '
lv_out_firstday  TYPE ALDATE, "   
lv_no_rfc_destination  TYPE ALDATE, "   
lv_out_lastday  TYPE ALDATE, "   
lv_out_rectype  TYPE ALPDBRTYP, "   
lv_xday_x  TYPE INT4, "   '10'
lv_sftname  TYPE ALPFPOLKEY, "   
lv_calname  TYPE ALPFPOLKEY, "   
lv_out_timezone  TYPE TIMEZONE, "   
lv_no_null  TYPE CHAR1. "   'X'

  CALL FUNCTION 'SALP_GET_DATA_FROM_PERFDB'  "
    EXPORTING
         TID = lv_tid
         TRY_REMOTE = lv_try_remote
         REMOTE_ONLY = lv_remote_only
         OUT_FIRSTDAY = lv_out_firstday
         OUT_LASTDAY = lv_out_lastday
         OUT_RECTYPE = lv_out_rectype
         XDAY_X = lv_xday_x
         SFTNAME = lv_sftname
         CALNAME = lv_calname
         OUT_TIMEZONE = lv_out_timezone
         NO_NULL = lv_no_null
    TABLES
         OUT_TAB = lt_out_tab
    EXCEPTIONS
        NO_DATA_IN_PERFDB = 1
        NO_RFC_DESTINATION = 2
. " SALP_GET_DATA_FROM_PERFDB




ABAP code using 7.40 inline data declarations to call FM SALP_GET_DATA_FROM_PERFDB

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_try_remote) = ' '.
 
DATA(ld_remote_only) = ' '.
 
 
 
 
 
DATA(ld_xday_x) = '10'.
 
 
 
 
DATA(ld_no_null) = 'X'.
 


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!