SAP user group slams 'uncertainty' in ERP giant's API policy

2026-04-30 · Source: The Register: Enterprise Technology News and Analysis · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning · Depth: Intermediate, quick

Summary

An influential SAP user group, DSAG, has criticized SAP's recently updated API policy, stating it introduces significant uncertainty for customers and partners. The new policy, published last week, restricts users to building with APIs "within the limits of SAP-endorsed architectures, data services, or service-specific pathways" and references an API Hub for approved interfaces. DSAG chairman Jens Hungershausen highlighted that SAP's approved list is poorly managed and that the ability for SAP to revoke API whitelisting creates substantial ambiguity. This lack of clarity, particularly concerning which of the numerous SAP function modules are permissible APIs, risks deterring customers from adopting new innovations, including AI solutions, that integrate with SAP systems. SAP, in response to earlier criticism, stated the updates aim to support secure, reliable, and equitable use of shared enterprise platforms amid growing automation and AI-driven access.

Key takeaway

For CTOs and AI Architects evaluating new integrations with SAP systems, the current API policy uncertainty poses a significant risk to project timelines and innovation adoption. You should carefully review SAP's API Hub and DSAG's forthcoming FAQs to understand permissible integration pathways before committing resources to new AI or automation initiatives that rely on SAP APIs, mitigating potential future roadblocks.

Key insights

Unclear API policies can hinder innovation and adoption of new technologies like AI within enterprise ecosystems.

Principles

• API policies must be clear and consistently managed.
• Uncertainty deters innovation and new project adoption.

In practice

• Regularly update and manage API whitelists.
• Provide clear guidelines for API usage.

Topics

• SAP API Policy
• DSAG User Group
• ERP Systems
• AI Integration
• Vendor Lock-in

Best for: CTO, VP of Engineering/Data, AI Architect, Tech Journalist, Director of AI/ML, Software Engineer

Related on AIssential

• SAP Is Attempting To Become The Gatekeeper Of Enterprise AI — CIOs Should Push Back — SAP's new API policy restricts third-party AI access and data extraction, establishing metered pathways and a 2027 pricing cliff.
• AI Adoption Outpaces Safety Policies, Leaving Organizations Exposed — Rapid AI adoption without adequate safety policies creates significant organizational cybersecurity and privacy risks.
• How do companies decide between building AI models in-house or using APIs? — Companies face a critical build vs. buy decision for AI models.
• Took Me a Few Days to Get This Right: The Integration Gauntlet (SAP Build & Destinations) — Integrating custom APIs with SAP Build requires navigating specific OpenAPI versioning, action limits, and a centralized authentication model.
• FDEs & The Enterprise AI Adoption Wedge — The problem is not the AI model's capability, but enterprise integration and adoption challenges.
• SAP Is Targeting The AI Data Control Plane — SAP's acquisitions of Dremio and Prior Labs aim to establish SAP BDC as the enterprise AI data control plane.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The Register: Enterprise Technology News and Analysis.