Hierarchy

⤷

⤷

IMG Activity
ID | /GRCPI/GRACVNOTIFYMS | Maintain Text for Custom Notification Messages (Plug-In) |
Transaction Code | /GRCPI/13000004 | (empty) |
Created on | 20111103 | |
Customizing Attributes | /GRCPI/GRACVNOTIFYMS | Maintain Text for Custom Notification Messages (Plug-In) |
Customizing Activity | /GRCPI/GRACVNOTIFYMS | Maintain Text for Custom Notification Messages (Plug-In) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /GRCPI/GRACVNOTIFYMS_DOC |
Use
In this Customizing activity, you can use transaction SE61 to create and maintain docu objects, which contain the text for the message body of superuser access notifications. The application allows you to send notification e-mails to controller roles when users log onto the plug-Iin system to perform firefighting activities.
Note: You use this Customizing activity only if you want to create and maintain custom notification messages. If you want to use the default notification messages delivered with the application, do not use this activity.
Requirements
- You have decided which variables to include in the docu object.
Make sure you use only variables that are valid for superuser maintenance. - In the Customizing activity, Maintain Custom Notification Messages for Superuser Access (Plug-In), you have maintained the structure for the notification messages, such as subject, message class, and so on.
Standard settings
The process to maintain and use custom notifications consists of the following procedures:
- In the Customizing activity, Maintain Custom Notification Messages, structure the notification messages, such as subject, message class, and so on.
- Create and maintain the docu objects.( See Activities below.)
Activities
To maintain the docu object:
- In the Document Class field, select General Text.
- In the Name field, enter the name for the docu object.
- Choose Create.
- Maintain the message text and variables as needed.
- Save the entry.
For the superuser access process, these are the valid variables you can use in the message text:
- RECIPIENT
- FFOBJECT
- CONNECTOR
- REASON_CODE
- FF_USER
- OWNER
- LOG_TIME
- REASON_CODE_DESCN
- ACTIVITY
Example
The following is an example of text from the default docu. object: /GRCPI/GRIA_SPM_NOTIFICATION.
Dear %RECIPIENT%,
The login notification details for the Firefighter ID %FFOBJECT% in system %CONNECTOR% using Reason code '%REASON_CODE%' is as follows :
Firefighter: %FF_USER%
Owner: %OWNER%
Date & Time: %LOG_TIME%
Reason code: %REASON_CODE_DESCN%
Activity: %ACTIVITY%
Kind Regards,
Access Control Administrator
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMGDUMMY | D - Dummy object | SE61 |
History
Last changed by/on | SAP | 20111103 |
SAP Release Created in | V1100_700 |