SAP DNO_EDIT_NOTIFICATION Function Module for









DNO_EDIT_NOTIFICATION is a standard dno edit notification 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 dno edit notification FM, simply by entering the name DNO_EDIT_NOTIFICATION into the relevant SAP transaction such as SE37 or SE38.

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



Function DNO_EDIT_NOTIFICATION 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 'DNO_EDIT_NOTIFICATION'"
EXPORTING
GUID = "GUID Notification
* AKTTYP = 'DI' "Activity Category

EXCEPTIONS
NOTIFIC_NOT_EXISTS = 1 ACTIVIT_NOT_ALLOWED = 2 NOTIFIC_ENQUEUED_BY_USER = 3 NOTIFIC_ENQUEUED_BY_PROC = 4
.



IMPORTING Parameters details for DNO_EDIT_NOTIFICATION

GUID - GUID Notification

Data type: DNOD_NOTIF-GUIDH
Optional: No
Call by Reference: Yes

AKTTYP - Activity Category

Data type: DNOC_SUBSCR-AKTTYP
Default: 'DI'
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOTIFIC_NOT_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

ACTIVIT_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

NOTIFIC_ENQUEUED_BY_USER -

Data type:
Optional: No
Call by Reference: Yes

NOTIFIC_ENQUEUED_BY_PROC -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DNO_EDIT_NOTIFICATION 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_guid  TYPE DNOD_NOTIF-GUIDH, "   
lv_notific_not_exists  TYPE DNOD_NOTIF, "   
lv_akttyp  TYPE DNOC_SUBSCR-AKTTYP, "   'DI'
lv_activit_not_allowed  TYPE DNOC_SUBSCR, "   
lv_notific_enqueued_by_user  TYPE DNOC_SUBSCR, "   
lv_notific_enqueued_by_proc  TYPE DNOC_SUBSCR. "   

  CALL FUNCTION 'DNO_EDIT_NOTIFICATION'  "
    EXPORTING
         GUID = lv_guid
         AKTTYP = lv_akttyp
    EXCEPTIONS
        NOTIFIC_NOT_EXISTS = 1
        ACTIVIT_NOT_ALLOWED = 2
        NOTIFIC_ENQUEUED_BY_USER = 3
        NOTIFIC_ENQUEUED_BY_PROC = 4
. " DNO_EDIT_NOTIFICATION




ABAP code using 7.40 inline data declarations to call FM DNO_EDIT_NOTIFICATION

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 GUIDH FROM DNOD_NOTIF INTO @DATA(ld_guid).
 
 
"SELECT single AKTTYP FROM DNOC_SUBSCR INTO @DATA(ld_akttyp).
DATA(ld_akttyp) = 'DI'.
 
 
 
 


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!