/PACG/ECM_NOTIF - Notification Configuration for Checklist
- proaxia
This transaction has been created based on: /PACG/ECM_CLCTN - Notification tasks parameters for checklist. The purpose of this redesign was to enhance user experience by creating a view cluster and refining condition creation. To avoid data duplication, please make sure to maintain data only in one of the mentioned transactions.
Manage notifications and notification tasks based on checklist instance values.
Checklist template for notifications
Enter a checklist template ID and template version.
Notification actions configuration
Enter a custom name for a ‘notification action’. Such action defines a type of a notification to be created [Typ] and whether a notification should be closed [Close notification].
Close notification
Yes | Close notification. |
|---|---|
No | Do not close notification. |
Field value for notification closure | Close notification if the value in a specified position of a checklist instance [PosNotClo] is equal to the value entered in [Field value for notif. closure] |
Notifications can be completed only if all tasks are closed. If an open task is found, the notification remains open, too.
Position numbers of checklist elements can be checked in table /PACG/ECM_CLTTP.
Notification task actions configuration
Enter a custom name for a ‘notification task action’. Such action defines:
a task code [Code] and code group [TkCodeGp] of a notification task to be created
whether the notification task should be closed [Close task]:
If [Close task] is set to ‘checklist value’, the tasks are closed only if a specified checklist position [Task close pos] contains value entered in [Task close checklist field value]
source of task start/end time [Start time indication/End time indicator]:
System date/time
Checklist creation in SAP
Checklist value - value entered in checklist position specified in [Start pos.] and [End posnr]
Operation start/end date
Short text source [Short text pos.]
Long text source [Long text position]
Notification actions and tasks
Define a pair of notification actions and notification task actions for which a set of conditions is specified later in 'Notification conditions'. If these conditions are met, the actions will be carried out.
Notification conditions
Enter a checklist position number and values (or a range of values) which must be found in this position of checklist instance. If they’re found, actions defined in the previous steps will be carried out.
Example - generate a notification and a task notification based on checklist instance values
1. Enter a template ID and a template version.
If checklist template 373 version 1 is assigned to an activity/service call then…
2. Define a notification-related action for the specified template.
Action ACTION_NAME creates a new notification of type Y2.
3. Define a task-related action for the specified template.
Action TASK_ACTION generates a task of code group PM1 and code 1.
4. Group notification tasks and notification actions.
5. Define conditions for notifications.
Condition n. 1 – If position 4 of the checklist 373, v.1 is equal to 10, execute notification and notification task actions.
6. Create a checklist instance. Fill the positions in a way which meets the conditions defined above.
7. Navigate to IW33 and notice that a new notification has been created. Its type reflects the one defined in the customizing view (Notification Actions Configuration). Notification tasks are also created, of the type defined in Notification Task Actions Configuration.
Example - lacking settings
Example - close notification
Follow all the steps from the first example with one exception - ‘Close notification’ set to ‘yes’ in Notification Actions Configuration.
Notification has been created and its status is NOCO (completed).
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.