Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MSE (Application Component) Mobile Service⤷
IWOC (Package) Application Development R/3 Work Order Cycle
IMG Activity
| ID | IQS0_NOTIF_TYPE_CHAN | BAdI: Checks for Extended Change of Notification Type |
| Transaction Code | S_EBS_44000290 | (empty) |
| Created on | 20101130 | |
| Customizing Attributes | IQS0_NOTIF_TYPE_CHAN | BAdI: Checks for Extended Change of Notification Type |
| Customizing Activity | IQS0_NOTIF_TYPE_CHAN | BAdI: Checks for Extended Change of Notification Type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_IQS0_NOTIF_TYPE_CHANGE |
Use
This Business Add-In (BAdI) is used in the Quality Notifications component (QM-QN).
The BAdI contains the following methods:
- EXECUTE_ADD_CHECKS
You can use this BAdI method to execute additional enterprise-specific checks following a change of notification type. For example, changes of notification type that are generally allowed can be prohibited under certain circumstances, such as for specific customers or materials.
The BAdI method is called in two places:
- With the filter value "original notification type" when you start the function Change Notification Type using the respective pushbutton
- With the filter values "original notification type" and "target notification type" when you select the required target notification type from the selection list
- EXECUTE_TYPE_CHANGE
You can use this BAdI method to determine which notification data is to be deleted or retained when the notification type is changed. The default setting is that all notification data is retained when the notification type is changed.
Requirements
In Customizing for Quality Management under Define Allowed Changes of Notification Type, you have specified which notification types can be changed to which other notification types. The original notification type and the target notification type are used as filter values for the BAdI.
Standard settings
In the standard system, there is no activated BAdI implementation.
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20101130 |
| SAP Release Created in | 606 |
