sap-support-caselisted

Raise an SAP support case (incident) properly — earn it first by exhausting the supported remedies, route it to the right component using SAP's own routing KBAs rather than the component name the error text happens to print, gather the IDs SAP will ask for (correlation ID, formation/job ID, troubleshooting key), set an honest priority against SAP's published definitions, and get the subject and description right BEFORE submitting — the case wizard buries them in an early step and will happily submit a stale description written before you fixed half the problem. Covers the multi-step case wizard's navigation traps, the business-impact fields that unlock at High, the troubleshooting key as a customer consent decision, and what to do when a case goes out wrong. Use this whenever raising, drafting, routing or correcting an SAP case or incident, and for "raise an SAP ticket", "open a case with SAP", "create SAP incident", "which component should I use", "case priority high or medium", "SAP wants a correlation ID",
adam0thman/sap-basis-ops · ★ 0 · AI & Automation · score 72

Install: claude install-skill adam0thman/sap-basis-ops

# Raising an SAP support case **Field-derived.** Built from a live BTP/Joule case raised on a customer landscape — including the mistakes made while raising it. Marks: **[F]** observed in the field, **[V]** verified against SAP documentation, **[G]** cited but not read in full. > ## The one-line version > > **A case is a claim that SAP's product is at fault.** Everything before submitting is about earning > the right to make that claim — and everything in the form is about making it **routable** and > **honest**. Most bounced cases fail one of those two, not both. --- ## 1. Earn it — most "SAP bugs" are configuration Before you open the form, three gates. On the field case, **the first one dissolved the original problem entirely**. **[F]** ### Gate 1 — has the *supported automation* been tried? A subscription failed twice with a hard error code, and a case looked justified. Then the **booster** (SAP's own guided automation) completed it first try. Cause: the manual attempts used the **wrong application and plan**; the booster picked the right pair. **[F]** | | Application | Plan | Result | |---|---|---|---| | Manual attempts ×2 | `<app>-ias` | `default` | **Failed** | | Booster | `<app>` | `foundation` | **Succeeded, first try** | **No product defect existed.** A case would have consumed SAP's time and the customer's, and been closed as configuration. > **Generalise it:** if SAP ships a booster, a guided procedure, a wizard, or a "recommended > configuration" path f