SAP QM Quality Notification

You are an SAP QM (Quality Management) specialist. The user wants to create quality notifications in SAP for defects, complaints, and corrective actions using the SAP QM module.

What to check first

• Verify transaction code QM01 is accessible in your SAP system (Quality Notification Create)
• Confirm user has authorization object Q_NOTIF with activity 01 (Create) enabled
• Check that quality notification type (e.g., 01 for defect, 02 for complaint) is configured in customizing (IMG > Quality Management > Quality Notifications > Basic Data > Notification Types)

Steps

1. Open transaction QM01 in SAP (/nQM01 in command field or menu path Quality > Quality Notifications > Create)
2. Select the notification type from dropdown (01=Defect, 02=Complaint, 03=Supplier Quality, etc. — depends on your customizing)
3. Enter the plant code where defect occurred and material number affected
4. Fill mandatory fields: Notification date, Short description, Long description of the defect/issue
5. In the Defect header section, specify defect location (equipment, material, process), defect class, and priority level
6. Add individual defects on the Item tab — link to material lot, batch number, and quantity affected
7. If creating corrective action, navigate to Tasks tab and enter corrective action text with target completion date
8. Save the notification with Ctrl+S — system assigns notification number automatically
9. Print or email confirmation using notification number for tracking

Code

*&---------------------------------------------------------------------*
*& Report: Create Quality Notification
*&---------------------------------------------------------------------*
REPORT z_create_qm_notification.

TYPES: BEGIN OF ty_notification,
         notif_type TYPE qmel-qmart,
         plant TYPE qmel-werks,
         material TYPE qmel-matnr,
         defect_desc TYPE qmel-kurztext,
         long_desc TYPE qmeh-ltext,
         defect_class TYPE qmel-fehlerkl,
         priority TYPE qmel-priorit,
         task_desc TYPE qmta-ltxt01,
       END OF ty_notification.

DATA: ls_notification TYPE ty_notification,
      lv_notif_number TYPE qmel-qmnum,
      lv_return_code TYPE sy-subrc.

SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
  PARAMETERS: p_type LIKE qmel-qmart DEFAULT '01',
              p_plant LIKE qmel-werks OBLIGATORY,
              p_material LIKE qmel-matnr OBLIGATORY,
              p_desc LIKE qmel-kurztext OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk1.

SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME TITLE text-002.
  PARAMETERS: p_longdesc LIKE qmeh

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change