Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-CIC (Application Component) Interaction Center WinClient⤷
INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
| ID | OLIAOQN0 | Define Notification Types |
| Transaction Code | S_ALR_87001131 | IMG Activity: OLIAOQN0 |
| Created on | 19981222 | |
| Customizing Attributes | OLIAOQN0 | Define notification types |
| Customizing Activity | OLIAOQN0 | Define Notification Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CA-NCT |
In this step, you define notification types.
Each notification type references a notification category and an origin. Notifications have the category predefined on the basis of the origin.
You can define notification types for the following origins:
- Maintenance Notification
- General maintenance notification
- Malfunction report
- Activity report
- Service Notification
- Problem notification
- Activity report (Service)
- General notification (Service)
- Quality Notification
- Customer complaint
- Complaint against vendor
- Internal problem notification
- SAP notification to SAP Support Line
- Claim
- Claim on customer or vendor
- Claim by customer or vendor
- General Notification
- General notification
The origin requires a suitable screen control in the notification transactions.
Comprehensive controls are linked to the notification type. Due to the wide range of functions that are covered by these controls, they are dealt with in separate sections of the Implementation Guide.
Standard Settings
You use the notification type to define the use for the notification.
Certain notification types are preset in the standard system.
Notification type $$ is reserved for the SAP online service (OSS).
Recommendation
If you want to define your own notification types, start with the preset notification types contained in the standard system as templates.
Identify the criteria according to which you want to differentiate your notification types. The following are a guide:
- Origin
This differentiation allows appropriate screen controls and is therefore required. - Organizational units, departments or process steps, in which the notification originated, or to which the notification relates.
- Control parameters that are assigned to the notification type.
This additional differentiation allows different scenarios in notification processing and is therefore advisable.
Activities
Identify which notification types are to be used in your company and define their parameters:
- Origin
- Catalog profile
(You can also define the catalog profile in the view "Catalogs and Catalog Profiles for the Notification Type")
You also define:
- Whether the notification number is to be displayed immediately.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | 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 | CA-NCT | 0 | HLA0006831 | Creating Quality Notifications |
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 |
| V_TQ80_M | V - View | SM30 | IH-MELDUNG | Notification Types |
History
| Last changed by/on | SAP | 20000131 |
| SAP Release Created in |
