SAP ME_CHECK_T160M Function Module for Reading table T160M - returning return codes via exeptions

Search SAP Function Modules

ME_CHECK_T160M is a standard me check t160m SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reading table T160M - returning return codes via exeptions 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 me check t160m FM, simply by entering the name ME_CHECK_T160M into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_CHECK_T160M 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 'ME_CHECK_T160M'"Reading table T160M - returning return codes via exeptions
  EXPORTING
   I_ARBGB =  "Application area
   I_MSGNR =  "Message number
*  I_MSGVS = '00' "Version from the user master
*  I_MSGTP_DEFAULT = 'W' "

EXCEPTIONS
   ERROR = 1    NOTHING = 2    WARNING = 3    SUCCESS = 4    POPUP = 5    INFORMATION = 6 

.

IMPORTING Parameters details for ME_CHECK_T160M

I_ARBGB - Application area

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

I_MSGNR - Message number

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

I_MSGVS - Version from the user master

Data type: T160M-MSGVS
Default: '00'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGTP_DEFAULT -

Data type: T160M-MSGTP
Default: 'W'
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR - Message should be sent as an error

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

NOTHING - Message should not be sent

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

WARNING - Message should be sent as a warnin

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

SUCCESS -

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

POPUP -

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

INFORMATION -

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

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

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