Symptom
BAdI BADI_QQM_NOTIF_EVENT_SAVE_CLD is not called when saving quality notification.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Implement custom logic with app "Custom Logic" to populate the supplier name in a custom field in quality notification type Q2 Supplier complaint.
- Test the custom logic in app "Custom Logic".
- Create or change a quality notification in app "Manage Quality Notification" or "Change Quality Notification".
- Observe that the custom field is not filled with the supplier name.
Cause
There is a misunderstanding about notification category and type. It is mentioned in documentation that "You can only use this BAdI for notification category 02 (Quality Notification). The BAdI is only triggered if QMTYP = 02 (quality notification)". For quality notification, the notification category is set as "02 Quality Notification" by default. And the filter parameter is related with notification type - "Key that enables notifications to be differentiated and grouped according to notification category, notification origin, and other criteria".
Resolution
The issue is caused by incorrect filter settings in the custom logic. The filter parameter NOTIFICATION_TYPE was set to "02", but it should be "Q2" according to the notification type definition and drop-down entries.
Keywords
Quality Notifications, Custom Logic, BADI_QQM_NOTIF_EVENT_SAVE_CLD, Supplier Complaint, NOTIFICATION_TYPE, Filter Parameter, Custom Field. , KBA , QM-QN-2CL , Quality Notifications (Public Cloud) , Problem
SAP Knowledge Base Article - Public