Hierarchy

⤷

⤷

IMG Activity
ID | FCC_BADI_NOTIF_SCE | BAdI: Custom Notification Scenarios |
Transaction Code | S_FC8_75000020 | (empty) |
Created on | 20111124 | |
Customizing Attributes | FCC_BADI_NOTIF_SCE | BAdI: Custom Notification Scenarios |
Customizing Activity | FCC_BADI_NOTIF_SCE | BAdI: Custom Notification Scenarios |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FCC_BADI_NOTIFICATION_SCENARIO |
Use
This Business Add-In (BAdI) is used in the Financial Closing cockpit Add-On (CA-GTF-FCC) component. You can use this BAdI to define custom notification scenarios. When the conditions for triggering a custom notification scenario for a task are met, the system sends an email to the responsible agent and the processor of the task. The BAdI is called when the triggering conditions are met and when the system clears the flags for sent notifications.
This BAdI definition contains the following methods:
- Set Notifications Triggered by User Action (GET_NOTI_SCENARIOS_BY_ACTION)
You can use this BAdI method to define the user actions that trigger custom notification scenarios. You can define only actions whose results are immediate and do not require saving. These actions include manually changing task status, executing tasks, and locking tasks. Actions such as changing task processors and deleting tasks are not supported because they need to be saved.
- Set Notifications Triggered by Background Scan (GET_NOTI_SCENARIOS_BACKGROUND)
You can use this BAdI method to define the background conditions that trigger custom notification scenarios. Background conditions are those that do not require user action. For example, you can specify that notifications should be sent three hours before the planned start time of a task.
- Clear Flags in FCC_NOT_SENTLOG for Sent Notifications (GET_NOTI_SENTLOG_FLAGS)
You can use this BAdI method to clear the flags for sent notifications. The system flags an email notification after the notification is sent. Before sending a notification, the system checks whether the notification is already flagged. If the notification is already flagged, the system does not send the notification again. This BAdI method is useful when you want to send a notification more than once, for example at intervals after the planned start time of a task.
Requirements
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20120202 |
SAP Release Created in | 100 |