← ClaudeAtlas

sap-software-downloadlisted

Find, qualify and download SAP software from the SAP for Me Software Center — Support Packages, kernel and patches, installation media, add-ons — and build a correct SP import queue. Resolves a component (e.g. "ST-PI 740") to exact filenames, object keys, sizes, SHA-256 checksums, the required SPAM/SAINT level and the EPS .PAT name via the Software Center's OData service, then covers where files go and how to verify them. Downloads are scriptable with X.509 client-certificate auth. For add-ons it walks the INSTALLATION vs EXCHANGE-UPGRADE tree. Use for "download a support package", "which SP is latest", "get the kernel SAR", "SP queue from SP28 to latest", "software center", "automate SAP downloads", "SAPCAR extract", "EPS/in", "SAINT installation package".
adam0thman/sap-basis-ops · ★ 0 · Data & Documents · score 72
Install: claude install-skill adam0thman/sap-basis-ops
# SAP Software Download (SAP for Me Software Center) Getting the *right* file is most of this job. A Basis download is only correct when four things line up: the **component + release**, the **patch/SP level**, the **platform** (OS + DB + Unicode, for kernel), and the **prerequisites** (SPAM/SAINT level, minimum SAP_BASIS, mandatory co-imports). This skill resolves all four before anything is fetched. > **Guardrail — the whole workflow is automatable, with the right credential.** > - Search, metadata **and the file download itself** work end-to-end without a browser, using > **X.509 client-certificate authentication** (§5). Verified: 7 support packages fetched unattended, > all SHA-256 verified against the service. **[V]** > - **Authentication method decides everything.** A *browser session* download redirects into interactive > SAML and needs a human (the account picker alone blocks it). A *client certificate* completes the same > SAML chain non-interactively. Same URL, different outcome — see §5. > - **Never guess a filename or an SP level.** Resolve it from the service (§2) and quote the object key. > - **Verify the SHA-256 before importing, always** (§5). The service publishes it; there is no excuse for > discovering a truncated `.SAR` during `IMPORT_PROPER`. > - **Check the component's release-strategy Note and known-issue Notes before building a queue** (§4) — > locked packages and mandatory co-imports are announced there, not in the file list. > - **Add-o