Customizing the General Notification

Use

When customizing an Internal Service Request (ISR) , the main step, which should be performed first, consists of settings for the General Notification .The General Notification corresponds to the business object on which internal service requests are based.

You should not need to define your own notification types when you create your own change requests. You can use the notification types we deliver for your own change requests.

If, however, you do want to set up a customer-specific notification type, see the comprehensive documentation in the Internal Service Request cookbook in the SAP Service Marketplace under service.sap.com/isr.

Process Flow

When you set up a notification type, the following detailed steps are necessary:

Define Notification Types

You find the relevant IMG activity in the SAP Implementation Guide by choosing Cross-Application ComponentsNotificationNotification CreationNotification TypeDefine Notification Types .

The notification type characterizes the General Notification and groups together some definitions for processing change requests. Later, you must assign each form to a notification type.

For change requests we deliver the notification types 56 ( PCR with Approval) and 57 ( PCR without Approval) , which you can also use for your own personnel change requests.

If you create your own notification type, define it on the detail screen with the notification origin General Notification .

Assign Number Range to Notification Types

You find the relevant IMG activity in the SAP Implementation Guide by choosing Cross-Application ComponentsNotificationNotification CreationNotification TypeDefine Number Ranges .

When assigning number ranges to notification types you define notification numbers under which change requests are saved in the system. To create a new number range group for change requests, choose Maintain Groups and then GroupInsert . In the resulting dialog box, enter a name for a new number range group (for example, Personnel Change Requests ) and specify the number range interval.

Even if you are only using or testing the change requests we deliver, you must check the that the standard notification types 56 and 57 are assigned to number ranges, and assign them if necessary.

Regardless of whether you create your own notification types or use SAP notification types, you must ensure that the notification types you use are assigned to valid number ranges. To assign notification types to valid number ranges, do the following (here using notification types 56 and 57 as an example):

To create a new number range group for change requests, choose Maintain Groups and then GroupInsert . In the resulting dialog box, enter a name for a new number range group (for example, Personnel Change Requests ) and specify the number range interval. You only need to perform this step if the existing number ranges in your system are not suitable for use with personnel change requests.

To assign notification types 56 and 57(or your own notification types) to the new group, select notification types 56 and 57 on the overview screen Maintain Number Range Groups . To do this, first position the cursor on notification type 56 and then choose Select Element in the status bar. Do the same for notification type 57. Then select the checkbox for the newly generated number range group and choose Assign Element Group from the status bar. In this way notification types 56 and 57 are assigned to the newly defined number range group.

Define Partner Functions

You find the relevant IMG activity in the SAP Implementation Guide by choosing Cross-Application ComponentsNotificationNotification CreationPartnerDefine Partner Determination Procedure .

Several roles are involved in the business process related to change requests. These roles include the manager as the author of the change request, an approver, and the personnel administrator whose task is to finish processing the request and process data in the HR system. In addition, a contact person can also be involved who is available to answer technical questions (for example, workflow problems). To depict the described process we deliver the following partner functions in the standard:

Partner Functions for Change Request Forms:

Partner Functions

Description

A0

Author

PC

Personnel Administrator

§G

Approver

§A

Contact Person

If your process needs more functions, you can create them under Partner Functions .

Definition of Partner Determination Procedure

You find the relevant IMG activity in the SAP Implementation Guide by choosing Cross-Application ComponentsNotificationNotification CreationPartnerDefine Partner Determination Procedure .

Partner determination procedures group together individual partner functions. If you have created your own partner functions, you must also define your own partner determination procedure. Only then can you assign the partner functions to the notification type.

We deliver the partner determination procedure SPCR for change requests. The partner functions listed under 3 are contained in it.

Assign Partner Determination Procedure to Notification Type

You can find the relevant Customizing activity in the SAP Implementation Guide, under C ross-Application ComponentsNotificationNotification CreationPartnersDefine Partner Determination Procedure , substep Assign Partner Determination Procedure to Notification Type.

In the example, we have assigned the partner determination procedure SPCR to the notification types 56 and 57. If you have defined your own notification types or partner functions and partner determination procedure, use this Customizing step to assign your partner determination procedure to a notification type.

Assign Partner Functions to Notification Type

You can find the relevant Customizing activity in the SAP Implementation Guide, under C ross-Application ComponentsNotificationNotification CreationPartnersDefine Partner Determination Procedures , substep Assign Partner Functions to Notification Type.

When you have assigned the partner determination procedure to notification types, the partner functions are available in Customizing for the notification type. Partner functions are used to give the generic roles of the Internal Service Request a semantic specific to the change requests. For the notification types of the change requests ( 56 and 57) the following are defined as standard:

ISR Function

Partner

Author

A0 (Author)

Person responsible

PC (Personnel administrator)

Approver

§G (Approver)

The Approver is only needed for notification types for which the Approval Required indicator is set. In the standard Customizing delivered for change requests, the partner function Approver (§G) is assigned to the ISR function Approver in notification type 56 ( Personnel Change Request with Approval ) .

Determine Screen Layout for Request Processing

You can find the relevant Customizing activity in the SAP Implementation Guide, under C ross-Application ComponentsNotification.Overview of Notification Type.

Various settings for the screen layout for the administrator transaction (IQS22) are assigned to the notification type. In this step, make settings for the screen template of your notification type.

We deliver the following settings as standard for notification types 56 and 57.

Screen Areas in Notification Header: H700 (Header General Notification)

Screen Structure for Extended View: 10\TAB01 (Overview) and 10\TAB18 (Form)

Screen Structure for Simplified View: Screen Area 1: 030 (Subject and Long Text)

Long Text Formatting:

We deliver the following settings as standard:

Log Row

When the author of the request enters a comment in the form, the system inserts a log row with information about who generated the comment.

No Text Change

Comments that have been entered and saved can no longer be changed.