RFC connectivity
Calling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.
Overview
@sap/cds-rfc Calls ABAP function modules over RFC from a CAP service.
Not covered: It stops at the SAP NW RFC SDK. The official path needs that proprietary native library installed, licensed and built for every platform you deploy to — which is the part the community has been working around.
RFC clients that run without the native library, such as open-rfcopen-rfcAn SDK-free TypeScript and JavaScript client for SAP classic synchronous RFC on Node.js, with no native addon and no runtime dependencies, that works as a drop-in under @sap/cds-rfc through an npm override.independent, cap under @sap/cds-rfc@sap/cds-rfcCalls ABAP function modules over RFC from a CAP service.sap official, cap, and samples that wire RFC calls into a CAP service.
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysA covered CAP application uses RFC connectivity to extract SAP product data into a non-SAP product.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
RFC transport does not itself establish permitted use. When the flow copies SAP product data into a non-SAP product, section 1 and its interoperability exception become relevant to the concrete design.
SAP Developer License Agreement 3.2 CAP →Artifacts
Content
Seen working
Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
Details
Coverage
For your agent
- Ref
capability:rfc-connectivity- JSON
- /capabilities/rfc-connectivity.json
- MCP
- Connecting an agent