sap-api-policy

Featured

Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.

API & Backend 414 stars 113 forks Updated 4 days ago GPL-3.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
87
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# SAP API Policy — Evidence Assessment Assess whether an SAP API usage scenario appears aligned with the **SAP API Policy v.4.2026a** (and its FAQ v1.2, May 2026) by gathering evidence from official SAP sources and the user's own facts, then producing a conservative, sourced technical assessment. ## When to Use Use this skill for a single SAP interface assessment, an architecture decision involving SAP APIs, or a batch inventory that needs evidence-based policy triage. Route purely legal, contractual, commercial, or roadmap questions to the appropriate SAP or customer owner. ## Quick Start 1. Capture the product, deployment, interface, consumer, data direction, volume, and intended use. 2. Gather current official evidence for publication status, documented use, and applicable controls. 3. Apply the workflow below and record evidence separately from inference. 4. Return one assessment category, one confidence level, residual risks, and concrete SAP questions. ## The one rule that defines this skill **Never present the result as legal advice, contractual advice, or a final/definitive SAP compliance decision.** Only SAP, the applicable contract, or SAP support/account/legal channels can give a binding answer for a specific customer landscape. This is not a hedge you can drop to sound more helpful — SAP itself declines to publish a binary "compliant / not compliant" decision matrix (FAQ Q49), so a confident yes/no would misrepresent what is knowable. Your job is to get as ...

Details

Author
secondsky
Repository
secondsky/sap-skills
Created
9 months ago
Last Updated
4 days ago
Language
JavaScript
License
GPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Featured

sap-api-style

This skill provides comprehensive guidance for documenting SAP APIs following the SAP API Style Guide standards. It should be used when creating or reviewing API documentation for REST, OData, Java, JavaScript, .NET, or C/C++ APIs. The skill covers naming conventions, documentation comments, OpenAPI specifications, quality checklists, deprecation policies, and manual documentation templates. It ensures consistency with SAP API Business Hub standards and industry best practices. Keywords: SAP API, REST, OData, OpenAPI, Swagger, Javadoc, JSDoc, XML documentation, API Business Hub, API naming, API deprecation, x-sap-stateInfo, Entity Data Model, EDM, documentation tags, API quality, API templates

414 Updated 4 days ago
secondsky
API & Backend Listed

sap-api-policy

SAP API Management policy design and governance — security, traffic, mediation, lifecycle

0 Updated 3 weeks ago
williamcorrea23
Data & Documents Listed

sap-api-advisor

Natural-language SAP API discovery over RFC (no GUI): turn a goal like "create a sales order" or "post a goods movement" into a ranked, trap-annotated, paste-ready shortlist of BAPIs / function modules / classes — with released state (S/4), interface + documentation for the top candidates, the team's known traps inlined, and a ready-to-paste CALL FUNCTION snippet. Reads the BAPI catalog (BAPI_MONITOR_GETLIST), TFDIR/TFTIT name+text, SEOCLASS, ARS_W_API_STATE (S/4 released state), FUPARAREF/FUNCT + DOCU_GET. HARD rule: it never test-calls a candidate — snippets are text only. Read-only; deploys nothing. Use for: "which BAPI/FM for X", find an API, is this BAPI released, API to create/read/post <object>, discover function module, released API S/4. `successor` (released→sanctioned replacement) is phase 2; `scan` is phase 3. Prerequisites: an RFC-capable connection profile (/sap-login). No dev-init, no GUI.

7 Updated today
sapdev-ai