Hierarchy

⤷

⤷

⤷

IMG Activity
ID | OLQU_BADI_MS | Business Add-In When Saving Notification Data |
Transaction Code | S_AL0_96000720 | (empty) |
Created on | 20020117 | |
Customizing Attributes | OLQU_BADI_MS | Business Add-In When Saving Notification Data |
Customizing Activity | OLQU_BADI_MS | Business Add-In When Saving Notification Data |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | NOTIF_EVENT_SAVE |
Use
This Business Add-In can be used for any notification type (maintenance notification, QM notification, CS notification, claim, or general notification)
Using this Business Add-In, notification data can be changed when the notification is saved. These changes are dependent on the notification type. You can also use this Business Add-In when the saving of the notification is triggered directly by calling the function module IQS1_POST_NOTIFICATION, and not using the dialog transaction. You can, for example, use this Business Add-In for defects recording in mySAP PLM Quality Management.
The following notification data is available in the Business Add-In implementation:
VIQMEL Notification header data
T365 Processing mode AKTYP ( A = Add, C = Change, D = Display)
TQ80 Notification type
IWQMFE Item data (defect data)
IWQMSM Tasks
IWQMMA Activities
IWQMUR Causes for item
You can return the following with changes to the calling program:
VIQMEL Notification header data
IWQMFE Item data (defect data)
IWQMSM Tasks
IWQMMA Activities
IWQMUR Causes for item
Requirements
The notification type serves as the filter variable.
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20020117 |
SAP Release Created in | 470 |