Hierarchy
GRCFND_A (Software Component) GRC Foundation ABAP⤷
GRC (Application Component) Governance, Risk and Compliance⤷
GRFN_DOCUMENTS (Package) Documents
IMG Activity
| ID | GRACTXTNOTIFYMSGC | Maintain Text for Custom Notification Messages |
| Transaction Code | S_GF1_13000163 | (empty) |
| Created on | 20101210 | |
| Customizing Attributes | GRACTXTNOTIFYMSGC | Maintain Text for Custom Notification Messages |
| Customizing Activity | GRACTXTNOTIFYMSGC | Maintain Text for Custom Notification Messages |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | GRACTXTNOTIFYMSGC_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 the notifications.
The application allows you to send notification e-mails to recipients triggered by specific workflow events. For example, send a notification to the requestor when their request is completed.
You use this Customizing activity only if you want to create and maintain custom docu objects. If you want to use the default notifications delivered with the application, do not use this activity.
Process
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.)
- In the Customizing activity, Maintain MSMP Workflows, maintain the notification templates and variables. The notification template is the object in MSMP workflow that consists of the message class and docu object. The variables are parts of the message body that can be replaced with specific information at runtime. For example, REQUESTOR_NAME, is replaced with the requestor's actual name.
- In the Customizing activity, Maintain MSMP Workflows, maintain the Notification Settings for stage level in the Maintain Paths phase. This sets the events that trigger the relevant notification
Requirements
- You have decided which variables to include in the docu object.
The variables are valid only for specific process types and templates. For more information, see the Customizing activity, Maintain MSMP Workflows > Variables and Templates. - In the Customizing activity, Maintain Custom Notification Messages, you have maintained the structure for the notification messages, such as subject, message class, and so on.
Standard settings
If you choose not to customize the message text or notification behavior, the application uses the default delivered message classes and document objects. The default delivered system view is GRFNVNOTIFYMSG and the associated database tables are GRFNNOTIFYMSG and GRFNNOTIFYMSGT.
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.
The following templates are valid for all process types:
- APPROVED
- REJECTED
- ESCALATION
- NEW WORK ITEM
The following tables list the delivered process types and the valid variables for each:
Process Type Variable
SAP_GRAC_AR APPROVED_BY
FIRST_NAME
LAST_NAME
LINK_APPROVE_REJECT
LINK_GET_APPROVERS
LINK_GET_REQ_STATUS
PATH
PROVISIONING
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
SUBMISSION
USER_ID
Process Type Variable
SAP_GRAC_CNTLASGN APPROVED_BY
FIRST_NAME
LAST_NAME
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
Process Type Variable
SAP_GRAC_FIREFIGHT_LOG_REPORT APPROVED_BY
FIRST_NAME
LAST_NAME
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
USER_ID
Process Type Variable
SAP_GRAC_FUNC_APPR APPROVED_BY
FIRST_NAME
LAST_NAME
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
Process Type Variable
SAP_GRAC_MIT_CONTROL_MAINT APPROVED_BY
FIRST_NAME
LAST_NAME
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
Process Type Variable
SAP_GRAC_RISK_APPR APPROVED_BY
FIRST_NAME
LAST_NAME
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
Process Type Variable
SAP_GRAC_RISK_REVIEW APPROVED_BY
ATTACHMENT_REPORT
CO_ORDINATOR
FIRST_NAME
LAST_NAME
LINK_GET_APPROVERS
LINK_GET_REQ_STATUS
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
SENDER
STAGE
USER_ID
Process Type Variable
SAP_GRAC_ROLE_APPR APPROVED_BY
FIRST_NAME
LAST_NAME
LINK_APPROVE_REJECT
LINK_GET_ROLE_STATUS
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
ROLE_NAME
SENDER
STAGE
Process Type Variable
SAP_GRAC_ROLE_ASGN_REVIEW APPROVED_BY
ATTACHMENT_REPORT
CO_ORDINATOR
FIRST_NAME
LAST_NAME
LINK_GET_APPROVERS
LINK_GET_REQ_STATUS
PATH
REQNO
REQUESTER_NAME
REQUEST_TYPE
REVIEWER
SENDER
STAGE
USER_ID
Example
The following is an example of text from the docu. Object GRAC_MSMP_AR_APPROVED:
Dear %REQUESTER_NAME%,
Your request number : %REQNO% has been approved.
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 | 20101210 |
| SAP Release Created in | V1000 |
