Hierarchy
FCCO (Software Component) Financial Closing Cockpit 200⤷
CA-GTF-FCC (Application Component) Financial Closing cockpit Add-on⤷
FCC_CLOSING (Package) Financial Closing Cockpit - SAPGUI and backend
IMG Activity
| ID | FCC_BADI_NOTIF | BAdI: Customize Notifications |
| Transaction Code | S_FC8_75000019 | (empty) |
| Created on | 20111124 | |
| Customizing Attributes | FCC_BADI_NOTIF | BAdI: Customize Notifications |
| Customizing Activity | FCC_BADI_NOTIF | BAdI: Customize Notifications |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FCC_BADI_NOTIFICATION |
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 customize how email notifications are sent.
This BAdI definition contains the following methods:
- Set Additional Users for Notifications (GET_EXTRA_USERS_4_NOTIFICATION)
You can use this BAdI method to specify a list of additional users defined as email recipients of notifications. An additional user is someone other than the responsible agent or the processor of a task, including someone not using the Financial Closing cockpit. You can specify whether you want to send, carbon copy (Cc), or blind carbon copy (Bcc) each user the email notifications.
- Set Start Time and Frequency for Reminder Notifications (GET_FREQUENCY_4_REMINDER_SCEN)
You can use this BAdI method to specify the start time and the frequency for sending reminder notifications. You can use the notifications to remind email recipients that a task is about to start or about to end. If you specify the ED_FREQUENCY_IN_MINUTES export parameter as zero, the system sends the notification only once.
- Set Excluded Notification Scenarios for Tasks (GET_EXCLUDED_SCENARIOS_OF_TASK)
You can use this BAdI method to specify the notification scenarios you want to exclude from sending email notifications for. You get task details in the IS_TASK import parameter. You specify the scenarios you want to exclude from sending email notifications for in the ET_SCENARIOS export parameter.
- Set Email Subject (GET_EMAIL_SUBJECT)
You can use this BAdI method to customize the subject of email notifications. This allows you to include information specific to a task in the email subject, for example, the task name, so that you can see what task an email is sent for without having to check the email body. Note that an email subject must be no longer than 50 characters; any characters beyond that are cut off in the sent emails.
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
You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the Implementation Example Classes section.
The following example implementations are available:
- CL_FCC_BADI_NOTIFICATION_IMPL
You can use this example implementation to experiment with sending, carbon copying (Cc), and blind carbon copying (Bcc) users email notifications according to the importing parameters, such as scenario type.
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 |
