SAP QEEO_DATA_CHANGED Function Module for NOTRANSL: Datenänderungen an Change Manager melden









QEEO_DATA_CHANGED is a standard qeeo data 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: Datenänderungen an Change Manager melden 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 qeeo data changed FM, simply by entering the name QEEO_DATA_CHANGED into the relevant SAP transaction such as SE37 or SE38.

Function Group: QEEO
Program Name: SAPLQEEO
Main Program: SAPLQEEO
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function QEEO_DATA_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 'QEEO_DATA_CHANGED'"NOTRANSL: Datenänderungen an Change Manager melden
EXPORTING
I_CHANGE_TYPE = "
I_CHANGE_KEY = "Change Type Keys for QE Subjects (Framework)
.



IMPORTING Parameters details for QEEO_DATA_CHANGED

I_CHANGE_TYPE -

Data type:
Optional: No
Call by Reference: Yes

I_CHANGE_KEY - Change Type Keys for QE Subjects (Framework)

Data type: QECHNGKEY
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for QEEO_DATA_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_i_change_type  TYPE STRING, "   
lv_i_change_key  TYPE QECHNGKEY. "   

  CALL FUNCTION 'QEEO_DATA_CHANGED'  "NOTRANSL: Datenänderungen an Change Manager melden
    EXPORTING
         I_CHANGE_TYPE = lv_i_change_type
         I_CHANGE_KEY = lv_i_change_key
. " QEEO_DATA_CHANGED




ABAP code using 7.40 inline data declarations to call FM QEEO_DATA_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



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!