SAP CMOR_T160M_READ Function Module for NOTRANSL: Lesen der Tabelle T160M (Nachrichtensteuerung)









CMOR_T160M_READ is a standard cmor t160m read 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: Lesen der Tabelle T160M (Nachrichtensteuerung) 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 cmor t160m read FM, simply by entering the name CMOR_T160M_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CMOR_T160M_READ 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 'CMOR_T160M_READ'"NOTRANSL: Lesen der Tabelle T160M (Nachrichtensteuerung)
EXPORTING
I_ARBGB = "Application area
I_MSGNR = "Message Number
* I_MSGVS = '00' "Message control version: Purchasing/Sales

IMPORTING
E_MSGTP = "System message category, purchasing

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for CMOR_T160M_READ

I_ARBGB - Application area

Data type: T160M-ARBGB
Optional: No
Call by Reference: Yes

I_MSGNR - Message Number

Data type: T160M-MSGNR
Optional: No
Call by Reference: Yes

I_MSGVS - Message control version: Purchasing/Sales

Data type: T160M-MSGVS
Default: '00'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CMOR_T160M_READ

E_MSGTP - System message category, purchasing

Data type: T160M-MSGTP
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CMOR_T160M_READ 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_msgtp  TYPE T160M-MSGTP, "   
lv_i_arbgb  TYPE T160M-ARBGB, "   
lv_not_found  TYPE T160M, "   
lv_i_msgnr  TYPE T160M-MSGNR, "   
lv_i_msgvs  TYPE T160M-MSGVS. "   '00'

  CALL FUNCTION 'CMOR_T160M_READ'  "NOTRANSL: Lesen der Tabelle T160M (Nachrichtensteuerung)
    EXPORTING
         I_ARBGB = lv_i_arbgb
         I_MSGNR = lv_i_msgnr
         I_MSGVS = lv_i_msgvs
    IMPORTING
         E_MSGTP = lv_e_msgtp
    EXCEPTIONS
        NOT_FOUND = 1
. " CMOR_T160M_READ




ABAP code using 7.40 inline data declarations to call FM CMOR_T160M_READ

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 MSGTP FROM T160M INTO @DATA(ld_e_msgtp).
 
"SELECT single ARBGB FROM T160M INTO @DATA(ld_i_arbgb).
 
 
"SELECT single MSGNR FROM T160M INTO @DATA(ld_i_msgnr).
 
"SELECT single MSGVS FROM T160M INTO @DATA(ld_i_msgvs).
DATA(ld_i_msgvs) = '00'.
 


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!