SAP SD_MESSAGE_LOG_MSGTY_GET Function Module for NOTRANSL: Ermittelt durch Customizing gewünschte Änderung des message Typs

Search SAP Function Modules

SD_MESSAGE_LOG_MSGTY_GET is a standard sd message log msgty get 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: Ermittelt durch Customizing gewünschte Änderung des message Typs 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 sd message log msgty get FM, simply by entering the name SD_MESSAGE_LOG_MSGTY_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_MESSAGE_LOG_MSGTY_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 'SD_MESSAGE_LOG_MSGTY_GET'"NOTRANSL: Ermittelt durch Customizing gewünschte Änderung des message Typs
  EXPORTING
   IV_MSGVS =  "Message version for T160M control
   IV_MSGID =  "Messages, Message Class
   IV_MSGNO =  "Messages, Message Number
   IS_MHPAR =  "Internally Used Key for Controllable Error Messages

 IMPORTING
   EV_MSGTY =  "ABAP System Field: Message Type

EXCEPTIONS
   NO_RECORD_FOUND = 1 

.

IMPORTING Parameters details for SD_MESSAGE_LOG_MSGTY_GET

IV_MSGVS - Message version for T160M control

Data type: V50AGL-MSGVS
Optional: No
Call by Reference: Yes

IV_MSGID - Messages, Message Class

Data type: VBFS-MSGID
Optional: No
Call by Reference: Yes

IV_MSGNO - Messages, Message Number

Data type: VBFS-MSGNO
Optional: No
Call by Reference: Yes

IS_MHPAR - Internally Used Key for Controllable Error Messages

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

EXPORTING Parameters details for SD_MESSAGE_LOG_MSGTY_GET

EV_MSGTY - ABAP System Field: Message Type

Data type: SY-MSGTY
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_RECORD_FOUND -

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

Copy and paste ABAP code example for SD_MESSAGE_LOG_MSGTY_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.

ABAP code using 7.40 inline data declarations to call FM SD_MESSAGE_LOG_MSGTY_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.

Search for further information about these or an SAP related objects