Configuration of subcription in IT Service management
Subscription of Incidents are necessary for everyone who want to get notifications to a business transaction when the status of this transaction is updated. It is possible as well to perform a subscription to an existing subscription that is not created by you.
The following technical article describes how to configure a subscription for Incidents in SAP Solution Manager 7.2. that everybody who is interested in, get informed of any changes made in the Incident.
Before we can start to configure the subscription for Incidents, some general settings needs to be done in SAP Solution Manager 7.2.
In transaction SFW5 the following switch needs to be activated.
In transaction MW_MODE the middleware needs to be switch to “On”.
Enable local link for subscription:
For creating a general subscription for Incidents or display some existing subscriptions, the logical link needs to be enabled in the business role where you use the IT Service Management functionality – usually a copy from the standard business role SOLMANPRO. It is done in transaction SPRO.
The link CT-NF-CR and CT-NF-SR are set to visible in the work center “Service Operation”.
Define number ranges for the subscription:
Number ranges can be defined in transaction SNUM. The standard can be used.
Specific settings for the subscription
The following chapter describes customer specific settings for the subscription in the SAP Solution Manager 7.2.
Creation of mail form templates:
Two mail form templates needs to be created. One template that the subscriber is informed, that a subscription was created/deleted. And one template which is send to the subscriber after a status was changed in the incident. This is done in transaction SM_CRM in the standard business role SOLMANPRO -> Service Operations -> Create Mail Forms
A mail form could look like this.
“Action” in the subject fields means created or deleted of a subscription.
The 2nd mail form could look like the following.
In the system settings for the notification framework in transaction SPRO the following entries needs to be maintained.
DIRECT_SENDING means: A Mail is send automatically after status change of the incident
SENDER_EMAIL: This is the default sender address, e.g. email@example.com
MFORM_FOR_NF_DOC_CHANGES: This is the mail form template which is send after clicking the button “Subscribe/Unsubscribe” in the incident ->This value can only be maintained after a mail form template was created in SM_CRM.
Define conditions of processing of a subscription:
The following entry must be exist in transaction SPRO and the attributes and the translation needs to be checked as well.
This channel needs to be checked in transaction SPRO.
Processing of subscribers:
The following entries needs to be checked in transaction SPRO.
Defaults of direct subscribing:
The following entry needs to be created for the customer incident transaction type in transaction SPRO.
Validity days means, that a subscription is active for 40 days. You can choose another number of days.
In the dialog structure the “Channels” needs to be checked and the following entry needs to bei entered. This mail form is sent after a status changes in the incident.
Scheduling background job:
A background job is needed for sending the mails.
Schedule report CRM_NF_CORE_QOUT_PROCESSING in transaction SM36 as a job with the following parameters:
Channel Type = E-Mail
Business Object Type = BUS2000223
The variant/parameter Z_SUBSCRIBE is created in transaction SE38
The configuration of a subscription for Incidents is useful if you like to be informed for other incidents where you are not assigned to. With this configuration steps your are able to perform the mandatory settings for using subscription in the IT Service Management process and learned how to use it.
If you have any questions or input, please feel free to comment and share!