sap-compliance-docslisted

# SAP Compliance, Certification & Usage-Rights Documents Auditors, procurement and security reviews all ask the same question in different words: *"prove this SAP service is certified / covered / licensed."* The answer is always **a specific document**, and the work is knowing which one and where it lives. > **Guardrail — this skill FINDS documents. It does not interpret them.** > - **Never assert an entitlement, licence position, or compliance status from memory.** Produce the > document reference and quote it. If no document is found, say so. > - **Never give legal, contractual or audit advice.** Certification scope, contract terms and audit > sufficiency are decisions for the customer's legal/compliance function and their **SAP account > executive / Customer Success Partner** — route them there explicitly. > - **Licence questions go to SAP.** Usage rights (§6) summarise a published page; anything contested, > partner-specific, or money-adjacent goes to the account executive or SAP Order Management. > - **Certificates are scoped and dated.** A certificate covering *SAP Enterprise Management* does **not** > automatically cover every SAP product you run. Always check the **Statement of Applicability (SoA)** > version and the **assessment period** — §2. > - **Public vs entitled.** Some documents are public; others require sign-in and an entitlement. Don't > promise a customer a document you haven't confirmed they can obtain — §3. Verification legend: **[V]** v