ABAP Proxy generation support with SAP Integration Suite

Introduction

ABAP Proxies are one of the most widely used integration technologies in SAP landscapes. For years, they have been central to PI/PO-based integrations. Now, with the availability of ABAP Proxy support in SAP Integration Suite, customers can extend this capability to the cloud, accelerating their migration from PI/PO to Integration Suite. This closes an important gap for organizations transitioning from SAP Process Integration (PI/PO) to SAP Integration Suite .

This blog provides a technical overview and step-by-step setup guide for enabling generation of ABAP Proxies with Integration Suite.

What Are ABAP Proxies?

• ABAP Proxies are generated classes in the SAP ABAP system based on service interfaces defined in the Enterprise Service Repository (ESR).

• They allow ABAP developers to call or expose services without dealing with low-level communication protocols.

• Proxies are commonly used for synchronous/asynchronous service calls, typically via SOAP adapters in PI/PO.

Why ABAP Proxy Support in SAP Integration Suite Matters?

Until recently, ABAP proxies were heavily tied to on-premise PI/PO middleware. With many customers moving their integration to the cloud, there was a strong demand for equivalent support in Integration Suite.

Key benefits of the new support include:

• Cloud-first Enablement – Seamlessly connect SAP backends to Integration Suite using proxies.
• Reuse of Existing Investments – No need to redesign all integration scenarios; existing service interfaces can still be leveraged.
• Simplified Migration from PI/PO – Reduces the complexity of moving from legacy middleware to cloud-based integration.
• Standardized Integration – Continue using ESR artifacts and ABAP proxies as standardized communication interfaces.

Prerequisites

• SAP Integration Suite tenant is active.
• Connectivity between SAP backend and Integration Suite (HTTPS) is enabled.
• Certificates (for mutual TLS if required) are exchanged.
• Service interface meant for proxy generation must already be present/imported inside an Integration Package of the SAP Integration Suite tenant
• You've a user with the role AuthGroup_IntegrationDeveloper assigned.

Connectivity between SAP backend and Integration Suite

For ABAP Proxy to Integration Suite, the standard practice is to configure an SM59 destination of type G.

SM59 Destination Configuration (Type G) :

Configuration Steps in SM59 (Type G)

Go to Transaction SM59

Choose HTTP Connections to External Server.

Create a new destination or Open the existing Destination with name SAP_PROXY_ESR

Technical Settings

• Target Host: The host name of Integration Suite tenant(Navigate to BTP Cockpit Instances and Subscriptions < your instance for Service Process Integration Runtime with api Plan> View Credentials (in JSON format) and copy the url(without https://) Note : Do not use the clientId and client secret from the Service Key instance

• Service No.: 443 (for HTTPS).
• Path Prefix: Enter the following : /rest/api/v1/workspace/sproxy

[画像:radhika_javvaji_2-1762196381518.png]

Logon & Security

• Choose Basic Authentication
• Enter the credentials of the Technical user with role AuthGroup_IntegrationDeveloper assigned and created with Default Identity Provider
• Security Options
  • Select SSL Active
  • Import CPI’s Server certificate into transaction STRUST (SSL Client → Standard).
  • Assign it to the relevant SSL Client PSE so that HTTPS trust is established

radhika_javvaji_3-1762196593671.png

• Save the changes and Perform Connection Test. Successful Connection Test result in HTTP 200 Ok Response .

radhika_javvaji_0-1762194984633.png

Procedure to Generate ABAP Proxy

• Log into the SAP ABAP backend system (ECC or S/4HANA).
• Run transaction SPROXY.
  • This transaction allows browsing and generating proxies from Service Interfaces present in the Integration Suite tenant that is configured in SM59 destination(SAP_PROXY_ESR)
  • In the Enterprise Service Browser view, navigate to Source --> ESR --> SWCs to see the list of Integration Packages that contain atleast one of the proxy relevant artifacts(Datatypes,(Fault)Message Types,Service Interfaces) are listed.
  • Locate the Integration Package containing the desired Service Interface (Inbound or Outbound).
  • Drill down to Service Provider or Service Consumer.(Namespaces -->Choose the desire namespace -->Object Types)
  • Choose the Inbound (server proxy) or Outbound (client proxy) interface.
  • Right-click the selected Service Provider or Consumer → choose Generate.
  • Proxy Generation Wizard opens. Provide:
  • Prefix for ABAP Class Names (if needed).
  • Package assignment (should be a transportable package, not $TMP if moving to QA/Prod).
  • Transport request for recording the generated objects.
  • The system creates ABAP proxy classes:
    • Inbound Server Proxy → ABAP Class implementing the interface with predefined methods (developer writes business logic here).
    • Outbound Client Proxy → ABAP Class to call external services (system generates methods to call the remote service).
    • Supporting DDIC structures, types, and message interfaces are also generated.
    • Save and Activate the generated proxies

Use the generated proxy class to implement the Business logic in Transaction SE80 or SE24 .

Current Limitations in the SPROXY Navigation Tree :

• Folders are not visible in the SPROXY navigation tree
• Datatype enhancements are not listed.
• Classifications and Matching Service Interface details will be missing in the Proxy Editor of the Service Interface
• ...

Recommended view to be used - Enterprise Services Browser view.

Also please ensure to import the service interfaces and its dependants to the Integration Suite tenant from the PI/PO ESR system that was earlier configured in SM 59 destination to be able to retain the already generated proxies. Try maintaining SWCV to Integration Package mapping i.e. Avoid importing objects from multiple SWCV's to one Integration Packages.. Avoid having objects with same name and namespace in multiple Integration Packages.