Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PE-LSO-TM (Application Component) Training Management⤷
LSO_IMG (Package) SAP Learning Solution - IMG
IMG Activity
| ID | HR_LSO_M1C8D1E21A1 | Define Notification Group |
| Transaction Code | S_AEN_10000565 | (empty) |
| Created on | 20050310 | |
| Customizing Attributes | HR_LSO_M1C8D1E21A1 | Define Notification Group |
| Customizing Activity | HR_LSO_M1C8D1E21A1PO | Define Notification Group |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HR_LSO_M1C8D1E21A1 |
Use
In this IMG activity, you specify notification groups for request-based correspondence. By doing so, you group activities that should be treated in the same way in request-based correspondence. For each notification group, you can set up the following activities, either generally at the level of the delivery method or in more detail at the level of the course type or the course.
Activities to be mapped per notification group:
Question Activity per notification group
By what Business process (request-based)
To whom Recipient role (role-based)
What Correspondence type from the Correspondence Tool
How Output medium
When Automatic processing
Correspondence requests are based on business processes in Training Management. For this reason, you first define notification groups and, in doing so, you specify for which business processes of Training Management request-based correspondence should be carried out:
- You specify for which Training Management business processes request-based correspondence should be triggered automatically by the system.
- You specify in which situations request-based correspondence should be triggered manually.
In the following IMG activities, you specify how request-based correspondence should react.
Requirements
You want to use request-based correspondence and you have set the HRLSO CRPSP switch to X.
Standard settings
If you use the predefined notification groups from the standard system, you do not need to work through this IMG activity.
Activities
You can use the notification groups from the standanrd system or create your own customer groups.
To create customer notification groups:
- In the Notification Groups view, enter the required details. This includes:
- ID of the notification group (note the customer namespace.)
- Description of the notification group
- You enter a class for context preparation. This class must implement the interface IF_LSO_CRP_CONTEXT_PREP. The class specifies how the correspondence request is filled with application data. Recommendation: Enter the class CL_LSO_CRP_CONTEXT_PARTIC from the standard system. You only need to implement and enter a customer class in exceptional cases.
- In the Notification Groups view, select a line and in the Allowed Relationships view, enter the allowed object types and relationships. For example, the notification group participation confirmation is linked with the delivery method curriculum and the relationship is participated in by.
In this way, you determine what application data is selected during manual output.
You can also (indirectly) define notification groups for manual correspondence that only have objects but no relationships.
- In the Triggering Event view, define the business processes in Training Management for which request-based correspondence should be triggered automatically. To do so, assign a notification group to the relevant logical function code (activity). SAP predefines and sets the logical function codes.
When you create customer notification groups, note the following:
- Steps 2 and 3 are linked from a content point of view. The entries must be consistent with one another.
- Set up customer notification groups in such a way that only business processes of the same type are defined. In step 2, for example, you should not mix different business processes, in other words, do not combine participation bookings and prebookings in the same notification group, nor participation bookings and resource reservations in one group.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | HR_LSO_M1C8D1E21A1 | 0 | KP70000007 | Day-to-Day Activities |
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 |
| VC_LSOCRPNOTFGRP | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20050310 |
| SAP Release Created in | 600 |
