SAP MS_READ_CHANGE_LIMIT Function Module for NOTRANSL: Liest ob erwarteter Wert geändert wurde









MS_READ_CHANGE_LIMIT is a standard ms read change limit 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: Liest ob erwarteter Wert geändert wurde 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 ms read change limit FM, simply by entering the name MS_READ_CHANGE_LIMIT into the relevant SAP transaction such as SE37 or SE38.

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



Function MS_READ_CHANGE_LIMIT 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 'MS_READ_CHANGE_LIMIT'"NOTRANSL: Liest ob erwarteter Wert geändert wurde
EXPORTING
I_PACKNO = "Package number

IMPORTING
DRUCK = "
.



IMPORTING Parameters details for MS_READ_CHANGE_LIMIT

I_PACKNO - Package number

Data type: ESUH-PACKNO
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for MS_READ_CHANGE_LIMIT

DRUCK -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MS_READ_CHANGE_LIMIT 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_druck  TYPE STRING, "   
lv_i_packno  TYPE ESUH-PACKNO. "   

  CALL FUNCTION 'MS_READ_CHANGE_LIMIT'  "NOTRANSL: Liest ob erwarteter Wert geändert wurde
    EXPORTING
         I_PACKNO = lv_i_packno
    IMPORTING
         DRUCK = lv_druck
. " MS_READ_CHANGE_LIMIT




ABAP code using 7.40 inline data declarations to call FM MS_READ_CHANGE_LIMIT

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 PACKNO FROM ESUH INTO @DATA(ld_i_packno).
 


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!