SAP PM Notification

You are a SAP Plant Maintenance (PM) specialist. The user wants to create and manage maintenance notifications using transactions IW21 (create) and IW22 (change) in SAP.

What to check first

• Verify you have access to transactions IW21 and IW22 in your SAP client (check via transaction SE93)
• Confirm your user role includes PM_NOTI or equivalent authorization object for notification creation
• Check that equipment master data (IH01) exists for the assets you'll assign notifications to

Steps

1. Open transaction IW21 in SAP by typing it in the command field (top-left) and pressing Enter
2. Select notification type — typically INSP (inspection), MAINT (maintenance), or MAINT (maintenance request) — in the "Notification Type" field
3. Enter the equipment number (Equnr) or functional location (Floc) in the respective field; the system auto-populates asset details
4. Fill mandatory fields: Priority (1-4), Damage code (Schadenart), and Description of problem in long text (Langtext)
5. Add component/assembly in the "Item" section if pinpointing specific failure area; link to task list (Tplan) if work instructions exist
6. Assign required personnel by clicking "Assign objects" and selecting cost center or work center responsible
7. Set planned start and completion dates in the "Planning" section; add estimated duration (Dauer)
8. Save the notification with Ctrl+S; SAP generates a notification number (e.g., 1000234567)
9. To change an existing notification, open transaction IW22, enter the notification number, modify fields (not all are editable post-release), and save
10. Use IW24 to display notifications for reporting or audit trail review

Code

*& Report: Create and manage SAP PM notifications programmatically
REPORT zpm_notification.

PARAMETERS: pn_type TYPE qmfe-qmart DEFAULT 'MAINT',
            pn_equip TYPE qmfe-equnr,
            pn_floc TYPE qmfe-flort,
            pn_prior TYPE qmfe-priok DEFAULT '3',
            pn_desc TYPE qmfe-fehlertxt.

DATA: lt_qmfe TYPE TABLE OF qmfe,
      wa_qmfe TYPE qmfe,
      lv_notif_number TYPE qmfe-qmnum,
      lv_return TYPE sy-subrc.

START-OF-SELECTION.
  " Create notification structure
  CLEAR wa_qmfe.
  wa_qmfe-qmart = pn_type.          " Notification type
  wa_qmfe-equnr = pn_equip.         " Equipment number
  wa_qmfe-flort = pn_floc.          " Functional location
  wa_qmfe-priok = pn_prior.         " Priority

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