RESTful Adapter for SAP PO

Efficient Integration and Development of REST APIs with SAP Process Orchestration and the Open API Standard

The KaTe RESTful Adapter significantly reduces development times and operational costs when creating or utilizing REST APIs based on the Open API Standard with SAP Process Orchestration.

The RESTful Adapter for SAP Integration Suite is the logical successor of our RESTful adapter for SAP Process Orchestration. Any API built on PO is simply runnable on BTP without big migration efforts.

Start building and integrating APIs with a clear path forward to a possible BTP migration.

Development Benefits:

• Quick and Efficient: The solution significantly reduces development effort for building & translating type safe data structures from JSON to XML and vice versa, routing of calls, enforcement of http status codes down to a few simple click through steps.
• Re-use developments: Allows re-use of existing ESR data types and interfaces for Open APIs with a few clicks.
• Works with established Toolset: Use established frameworks that are here to stay in S4 and BTP with minimal effort. ABAP Classes (ABAP Proxies) can simply get generated from Open API definitions, IDOCs/RFCs or other interfaces can be re-used as Open API with a few clicks
• Easy Migration to BTP: Transitioning of Open APIs built by this approach are 1:1 migratable from SAP Process Orchestration to SAP Integration Suite (±1-2 minutes per API).
• State-of-the-Art API Standards: Supports OpenAPI 3.x and Swagger 2.0 for comprehensive API descriptions in sender and receiver channels.

Security Benefits:

• Protection Against Unauthorized Access: Blocks non-compliant API calls.
• Flexible API Authorization: Supports to integrate own Identity management solutions via JWT/OpenID/Oauth2 and established standards like NTLM, custom tokens.

Business Benefits:

• Cost Savings: Reduces development costs by shortening development times and utilizing existing skills.
• Sustainable Investments: Reuse ESR content as Open APIs to preserve existing investments.
• No Complex Custom Development: Avoids time-consuming custom programming.
• Free trial: Test before you buy with a free trial for Proof of Concepts.

Use Cases:

API-First Development: Bridging Old and New Worlds

Software development is increasingly shifting to mobile platforms, hyperscalers, or container environments, all of which leverage the Open API Standard for API management, security (JWT, OAuth2), and automation.

The KaTe RESTful Adapter facilitates seamless SAP integration with API-first strategies from non-SAP ecosystems—whether on SAP BTP, hyperscalers like AWS, Azure, or GCP, or in containerized development environments.

Open APIs in regulated industries

Regulated industries such as telecommunications (TMF), banking (Open Banking), or utilities (market data exchange) require standardized Open APIs for data exchange. Our approach significantly reduces the development and operational costs of such APIs while leveraging existing developer skills and requiring minimal investment.

The KaTe RESTful Adapter maximizes the efficiency and security of your API integrations, protects existing investments, and builds seamless bridges between SAP and modern API standards. With this future-proof solution, you are well-equipped to meet the increasing demands of integrating advanced technologies and driving your digital transformation forward—enhancing your SAP landscape to its full potential

Use OData within established architectures

SAP has strongly committed to OData, which can be described via Open API definitions. However, challenges often arise in hybrid environments or API management solutions:

• SAP Specifics: Clients need to manage XCSRF tokens or deal with SAP-specific attributes in OData definitions.
• Internal Links: API management solutions may return responses with internal links, creating security risks and hindering OData clients from working directly.

The KaTe RESTful Adapter resolves these issues efficiently: Links are automatically rewritten to frontend URLs, and XCSRF tokens are handled automatically.