SAP DFS_PM_NOTIFICATION_CREATE Function Module for PM Notification Create in Update Task
DFS_PM_NOTIFICATION_CREATE is a standard dfs pm notification create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PM Notification Create in Update Task 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 dfs pm notification create FM, simply by entering the name DFS_PM_NOTIFICATION_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DFS_PM_NOTIFICATION
Program Name: SAPLDFS_PM_NOTIFICATION
Main Program: SAPLDFS_PM_NOTIFICATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DFS_PM_NOTIFICATION_CREATE 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 'DFS_PM_NOTIFICATION_CREATE'"PM Notification Create in Update Task.
EXPORTING
IV_NOTIFICATION = "Notification Number
* IV_NOTIF_TYPE = "Notification Type
* IS_NOTIF_HEADER = "BAPI Service Notification Header for creation
* IV_SYNC_RFC_DESTINATION = "Logical destination (specified in function call)
* IS_GEODATA = "Coordination Data in the Maintenance Notification
IV_CREATE_NOTIF = "Boolean Variables (X=true, space=false)
IV_CREATE_TEXT = "Boolean Variables (X=true, space=false)
IV_SET_TECH_STAT = "Boolean Variables (X=true, space=false)
IMPORTING
ES_NOTIF_HEADER_EXPORT = "BAPI Service Notification Header
TABLES
* IT_NOTITEM = "Notification item for creation
* IT_STATUS_OBJ = "Status Object Information
* ET_RETURN = "Return Parameter
* IT_EXTENSIONIN = "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
* IT_NOTIFCAUS = "Notification causes for creation
* IT_NOTIFACTV = "Notification activity for creation
* IT_NOTIFTASK = "Notification task for creation
* IT_NOTIFPARTNR = "Partners for creation/change
* IT_LONGTEXTS = "Notification long text
* IT_NOTIF_LTEXT = "DFS PM Object Long Texts
* IT_NOTIFSTATUS = "DFS PM Notification Status
* IT_OBJECT_STAT = "Individual Object Status Information
IMPORTING Parameters details for DFS_PM_NOTIFICATION_CREATE
IV_NOTIFICATION - Notification Number
Data type: BAPI2080_NOTHDRE-NOTIF_NOOptional: No
Call by Reference: No ( called with pass by value option)
IV_NOTIF_TYPE - Notification Type
Data type: BAPI2080-NOTIF_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_NOTIF_HEADER - BAPI Service Notification Header for creation
Data type: BAPI2080_NOTHDRIOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SYNC_RFC_DESTINATION - Logical destination (specified in function call)
Data type: RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_GEODATA - Coordination Data in the Maintenance Notification
Data type: /ISDFPS/QMTPORTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CREATE_NOTIF - Boolean Variables (X=true, space=false)
Data type: BOOLEAN_FLGOptional: No
Call by Reference: No ( called with pass by value option)
IV_CREATE_TEXT - Boolean Variables (X=true, space=false)
Data type: BOOLEAN_FLGOptional: No
Call by Reference: No ( called with pass by value option)
IV_SET_TECH_STAT - Boolean Variables (X=true, space=false)
Data type: BOOLEAN_FLGOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DFS_PM_NOTIFICATION_CREATE
ES_NOTIF_HEADER_EXPORT - BAPI Service Notification Header
Data type: BAPI2080_NOTHDREOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DFS_PM_NOTIFICATION_CREATE
IT_NOTITEM - Notification item for creation
Data type: BAPI2080_NOTITEMIOptional: Yes
Call by Reference: Yes
IT_STATUS_OBJ - Status Object Information
Data type: DFS_STAT_OBJ_INFO_SOptional: Yes
Call by Reference: Yes
ET_RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
IT_EXTENSIONIN - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
IT_NOTIFCAUS - Notification causes for creation
Data type: BAPI2080_NOTCAUSIOptional: Yes
Call by Reference: Yes
IT_NOTIFACTV - Notification activity for creation
Data type: BAPI2080_NOTACTVIOptional: Yes
Call by Reference: Yes
IT_NOTIFTASK - Notification task for creation
Data type: BAPI2080_NOTTASKIOptional: Yes
Call by Reference: Yes
IT_NOTIFPARTNR - Partners for creation/change
Data type: BAPI2080_NOTPARTNRIOptional: Yes
Call by Reference: Yes
IT_LONGTEXTS - Notification long text
Data type: BAPI2080_NOTFULLTXTIOptional: Yes
Call by Reference: Yes
IT_NOTIF_LTEXT - DFS PM Object Long Texts
Data type: DFS_PM_LONGTEXT_TTOptional: Yes
Call by Reference: Yes
IT_NOTIFSTATUS - DFS PM Notification Status
Data type: DFS_PM_NOTIF_STATUS_SOptional: Yes
Call by Reference: Yes
IT_OBJECT_STAT - Individual Object Status Information
Data type: DFS_OBJ_STAT_INFO_SOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DFS_PM_NOTIFICATION_CREATE 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: | ||||
| lt_it_notitem | TYPE STANDARD TABLE OF BAPI2080_NOTITEMI, " | |||
| lv_iv_notification | TYPE BAPI2080_NOTHDRE-NOTIF_NO, " | |||
| lv_es_notif_header_export | TYPE BAPI2080_NOTHDRE, " | |||
| lt_it_status_obj | TYPE STANDARD TABLE OF DFS_STAT_OBJ_INFO_S, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_it_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_it_notifcaus | TYPE STANDARD TABLE OF BAPI2080_NOTCAUSI, " | |||
| lv_iv_notif_type | TYPE BAPI2080-NOTIF_TYPE, " | |||
| lt_it_notifactv | TYPE STANDARD TABLE OF BAPI2080_NOTACTVI, " | |||
| lv_is_notif_header | TYPE BAPI2080_NOTHDRI, " | |||
| lt_it_notiftask | TYPE STANDARD TABLE OF BAPI2080_NOTTASKI, " | |||
| lv_iv_sync_rfc_destination | TYPE RFCDEST, " | |||
| lv_is_geodata | TYPE /ISDFPS/QMTPORT, " | |||
| lt_it_notifpartnr | TYPE STANDARD TABLE OF BAPI2080_NOTPARTNRI, " | |||
| lt_it_longtexts | TYPE STANDARD TABLE OF BAPI2080_NOTFULLTXTI, " | |||
| lv_iv_create_notif | TYPE BOOLEAN_FLG, " | |||
| lt_it_notif_ltext | TYPE STANDARD TABLE OF DFS_PM_LONGTEXT_TT, " | |||
| lv_iv_create_text | TYPE BOOLEAN_FLG, " | |||
| lt_it_notifstatus | TYPE STANDARD TABLE OF DFS_PM_NOTIF_STATUS_S, " | |||
| lv_iv_set_tech_stat | TYPE BOOLEAN_FLG, " | |||
| lt_it_object_stat | TYPE STANDARD TABLE OF DFS_OBJ_STAT_INFO_S. " |
|   CALL FUNCTION 'DFS_PM_NOTIFICATION_CREATE' "PM Notification Create in Update Task |
| EXPORTING | ||
| IV_NOTIFICATION | = lv_iv_notification | |
| IV_NOTIF_TYPE | = lv_iv_notif_type | |
| IS_NOTIF_HEADER | = lv_is_notif_header | |
| IV_SYNC_RFC_DESTINATION | = lv_iv_sync_rfc_destination | |
| IS_GEODATA | = lv_is_geodata | |
| IV_CREATE_NOTIF | = lv_iv_create_notif | |
| IV_CREATE_TEXT | = lv_iv_create_text | |
| IV_SET_TECH_STAT | = lv_iv_set_tech_stat | |
| IMPORTING | ||
| ES_NOTIF_HEADER_EXPORT | = lv_es_notif_header_export | |
| TABLES | ||
| IT_NOTITEM | = lt_it_notitem | |
| IT_STATUS_OBJ | = lt_it_status_obj | |
| ET_RETURN | = lt_et_return | |
| IT_EXTENSIONIN | = lt_it_extensionin | |
| IT_NOTIFCAUS | = lt_it_notifcaus | |
| IT_NOTIFACTV | = lt_it_notifactv | |
| IT_NOTIFTASK | = lt_it_notiftask | |
| IT_NOTIFPARTNR | = lt_it_notifpartnr | |
| IT_LONGTEXTS | = lt_it_longtexts | |
| IT_NOTIF_LTEXT | = lt_it_notif_ltext | |
| IT_NOTIFSTATUS | = lt_it_notifstatus | |
| IT_OBJECT_STAT | = lt_it_object_stat | |
| . " DFS_PM_NOTIFICATION_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM DFS_PM_NOTIFICATION_CREATE
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 NOTIF_NO FROM BAPI2080_NOTHDRE INTO @DATA(ld_iv_notification). | ||||
| "SELECT single NOTIF_TYPE FROM BAPI2080 INTO @DATA(ld_iv_notif_type). | ||||
Search for further information about these or an SAP related objects