SAP ECATT_OBJ_CHANGED Function Module for
ECATT_OBJ_CHANGED is a standard ecatt obj changed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ecatt obj changed FM, simply by entering the name ECATT_OBJ_CHANGED into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECATT_API
Program Name: SAPLECATT_API
Main Program: SAPLECATT_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ECATT_OBJ_CHANGED 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 'ECATT_OBJ_CHANGED'".
EXPORTING
IS_KEY = "
IMPORTING
E_CHANGED = "
E_MAINTAIN_MODE = "
TABLES
RETURN = "
IMPORTING Parameters details for ECATT_OBJ_CHANGED
IS_KEY -
Data type: ETAPI_OBJOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ECATT_OBJ_CHANGED
E_CHANGED -
Data type: ETONOFFOptional: No
Call by Reference: No ( called with pass by value option)
E_MAINTAIN_MODE -
Data type: ETOBJ_MODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ECATT_OBJ_CHANGED
RETURN -
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ECATT_OBJ_CHANGED 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_is_key | TYPE ETAPI_OBJ, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_e_changed | TYPE ETONOFF, " | |||
| lv_e_maintain_mode | TYPE ETOBJ_MODE. " |
|   CALL FUNCTION 'ECATT_OBJ_CHANGED' " |
| EXPORTING | ||
| IS_KEY | = lv_is_key | |
| IMPORTING | ||
| E_CHANGED | = lv_e_changed | |
| E_MAINTAIN_MODE | = lv_e_maintain_mode | |
| TABLES | ||
| RETURN | = lt_return | |
| . " ECATT_OBJ_CHANGED | ||
ABAP code using 7.40 inline data declarations to call FM ECATT_OBJ_CHANGED
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