SAP SRT_MONI_GET_PROCESSORID_INFO Function Module for Gets the metadata for the processor ID









SRT_MONI_GET_PROCESSORID_INFO is a standard srt moni get processorid info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets the metadata for the processor ID processing and below is the pattern details for this FM, 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 srt moni get processorid info FM, simply by entering the name SRT_MONI_GET_PROCESSORID_INFO into the relevant SAP transaction such as SE37 or SE38.

Function Group: SRT_TRACING_LOGGING
Program Name: SAPLSRT_TRACING_LOGGING
Main Program: SAPLSRT_TRACING_LOGGING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SRT_MONI_GET_PROCESSORID_INFO 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 'SRT_MONI_GET_PROCESSORID_INFO'"Gets the metadata for the processor ID
EXPORTING
I_PROCESSOR_ID = "SOAP Runtime Processor Unit ID

IMPORTING
E_DISPLAY_NAME = "Display Name for Meta Data Components
E_DESCRIPTION = "Description for Meta Data Components

EXCEPTIONS
TECHNICAL_EXCEPTION = 1
.



IMPORTING Parameters details for SRT_MONI_GET_PROCESSORID_INFO

I_PROCESSOR_ID - SOAP Runtime Processor Unit ID

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

EXPORTING Parameters details for SRT_MONI_GET_PROCESSORID_INFO

E_DISPLAY_NAME - Display Name for Meta Data Components

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

E_DESCRIPTION - Description for Meta Data Components

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

EXCEPTIONS details

TECHNICAL_EXCEPTION - Technical problem

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SRT_MONI_GET_PROCESSORID_INFO 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_e_display_name  TYPE SRT_MONI_DISPLAY_NAME, "   
lv_i_processor_id  TYPE SRT_MONI_PROC_ID, "   
lv_technical_exception  TYPE SRT_MONI_PROC_ID, "   
lv_e_description  TYPE SRT_MONI_DESCRIPTION. "   

  CALL FUNCTION 'SRT_MONI_GET_PROCESSORID_INFO'  "Gets the metadata for the processor ID
    EXPORTING
         I_PROCESSOR_ID = lv_i_processor_id
    IMPORTING
         E_DISPLAY_NAME = lv_e_display_name
         E_DESCRIPTION = lv_e_description
    EXCEPTIONS
        TECHNICAL_EXCEPTION = 1
. " SRT_MONI_GET_PROCESSORID_INFO




ABAP code using 7.40 inline data declarations to call FM SRT_MONI_GET_PROCESSORID_INFO

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.

 
 
 
 


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!