SAP MD_GET_EXCEPTIONS_RFC Function Module for NOTRANSL: Ausnahememeldungen für Alert-Monitor holen









MD_GET_EXCEPTIONS_RFC is a standard md get exceptions rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ausnahememeldungen für Alert-Monitor holen 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 md get exceptions rfc FM, simply by entering the name MD_GET_EXCEPTIONS_RFC into the relevant SAP transaction such as SE37 or SE38.

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



Function MD_GET_EXCEPTIONS_RFC 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 'MD_GET_EXCEPTIONS_RFC'"NOTRANSL: Ausnahememeldungen für Alert-Monitor holen
EXPORTING
USER = "SAP System, User Logon Name
LANGU = "SAP System, Current Language
VIEW = "Key for planning result view

TABLES
I_MDAM = "Structure for Exception Messages in Alert Monitor

EXCEPTIONS
VIEW_NOT_FOUND = 1
.



IMPORTING Parameters details for MD_GET_EXCEPTIONS_RFC

USER - SAP System, User Logon Name

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

LANGU - SAP System, Current Language

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

VIEW - Key for planning result view

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

TABLES Parameters details for MD_GET_EXCEPTIONS_RFC

I_MDAM - Structure for Exception Messages in Alert Monitor

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

EXCEPTIONS details

VIEW_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MD_GET_EXCEPTIONS_RFC 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_user  TYPE SY-UNAME, "   
lt_i_mdam  TYPE STANDARD TABLE OF MDAM, "   
lv_view_not_found  TYPE MDAM, "   
lv_langu  TYPE SY-LANGU, "   
lv_view  TYPE MDDMAP-VIEWN. "   

  CALL FUNCTION 'MD_GET_EXCEPTIONS_RFC'  "NOTRANSL: Ausnahememeldungen für Alert-Monitor holen
    EXPORTING
         USER = lv_user
         LANGU = lv_langu
         VIEW = lv_view
    TABLES
         I_MDAM = lt_i_mdam
    EXCEPTIONS
        VIEW_NOT_FOUND = 1
. " MD_GET_EXCEPTIONS_RFC




ABAP code using 7.40 inline data declarations to call FM MD_GET_EXCEPTIONS_RFC

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 UNAME FROM SY INTO @DATA(ld_user).
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
 
"SELECT single VIEWN FROM MDDMAP INTO @DATA(ld_view).
 


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!