SAP LXE_TS_API_OBJECT_CHANGED3 Function Module for Check if an object has changed since a specified timestamp

Search SAP Function Modules

LXE_TS_API_OBJECT_CHANGED3 is a standard lxe ts api object changed3 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if an object has changed since a specified timestamp 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 lxe ts api object changed3 FM, simply by entering the name LXE_TS_API_OBJECT_CHANGED3 into the relevant SAP transaction such as SE37 or SE38.

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

Function LXE_TS_API_OBJECT_CHANGED3 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 'LXE_TS_API_OBJECT_CHANGED3'"Check if an object has changed since a specified timestamp
  EXPORTING
   TRANSAREA =  "Translation Area
   OBJNAME3 =  "Text
   LANGUAGE =  "ISO Language ID
   TIMESTAMP =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

 IMPORTING
   CHANGED =  "Single-Character Flag

EXCEPTIONS
   UNAUTHORIZED = 1    UNKNOWN_TRANS_AREA = 2    UNSUPPORTED_TRANS_AREA_TYPE = 3    UNKNOWN_LANGUAGE = 4    OBJECT_NOT_FOUND = 5    LOCKED = 6 

.

IMPORTING Parameters details for LXE_TS_API_OBJECT_CHANGED3

TRANSAREA - Translation Area

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

OBJNAME3 - Text

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

LANGUAGE - ISO Language ID

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

TIMESTAMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

EXPORTING Parameters details for LXE_TS_API_OBJECT_CHANGED3

CHANGED - Single-Character Flag

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

EXCEPTIONS details

UNAUTHORIZED - Unauthorized

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_TRANS_AREA - Unknown translation area

Data type:
Optional: No
Call by Reference: Yes

UNSUPPORTED_TRANS_AREA_TYPE - Unsupported translation area type

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_LANGUAGE - Unknown language

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_FOUND - Object was not found

Data type:
Optional: No
Call by Reference: Yes

LOCKED - Operation is currently locked

Data type:
Optional: No
Call by Reference: Yes

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

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