SAP OM_IS_DEPENDENCY_CHANGED Function Module for NOTRANSL: Aussage, ob Beziehungswissen geändert wurde
OM_IS_DEPENDENCY_CHANGED is a standard om is dependency changed 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: Aussage, ob Beziehungswissen 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 om is dependency changed FM, simply by entering the name OM_IS_DEPENDENCY_CHANGED into the relevant SAP transaction such as SE37 or SE38.
Function Group: OM_ENTRY
Program Name: SAPLOM_ENTRY
Main Program: SAPLOM_ENTRY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OM_IS_DEPENDENCY_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 'OM_IS_DEPENDENCY_CHANGED'"NOTRANSL: Aussage, ob Beziehungswissen geändert wurde.
EXPORTING
NODE = "Node Name
EXCEPTIONS
NOT_FOUND = 1 NO_CHANGES = 2 CHANGES = 3
IMPORTING Parameters details for OM_IS_DEPENDENCY_CHANGED
NODE - Node Name
Data type: COCOM_PNAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Do(es) not exist
Data type:Optional: No
Call by Reference: Yes
NO_CHANGES - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
CHANGES - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OM_IS_DEPENDENCY_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_node | TYPE COCOM_PNAME, " | |||
| lv_not_found | TYPE COCOM_PNAME, " | |||
| lv_no_changes | TYPE COCOM_PNAME, " | |||
| lv_changes | TYPE COCOM_PNAME. " |
|   CALL FUNCTION 'OM_IS_DEPENDENCY_CHANGED' "NOTRANSL: Aussage, ob Beziehungswissen geändert wurde |
| EXPORTING | ||
| NODE | = lv_node | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NO_CHANGES = 2 | ||
| CHANGES = 3 | ||
| . " OM_IS_DEPENDENCY_CHANGED | ||
ABAP code using 7.40 inline data declarations to call FM OM_IS_DEPENDENCY_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