@sap/cds-rfc
Calls ABAP function modules over RFC from a CAP service.
Facts
Where it sits
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1from RFC connectivityA 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 →What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Node.js
As a package
- Declared for
- >=9
- Where it runs
- Inside its host
- Distributed through
- npm
Connections
SDK-free TypeScript client for SAP synchronous RFC on Node.js
Calling ABAP function modules from outside the system over RFC
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
Download
Install
npm add @sap/cds-rfcDerived from the package name. No recipe recorded; the README has the configuration.
Learn more
- Introducing open-rfc: Calling SAP RFC from Node.js Without the SDKIntroducing open-rfc: Calling SAP RFC from Node.js Without the SDKopen-rfc is a TypeScript and JavaScript RFC client for Node.js with no runtime dependencies and no SAP NetWeaver RFC SDK, written after SAP archived node-rfc and PyRFC and while the connector below @sap/cds-rfc needs an S-user, an SAP Build Code licence and a private registry. The history of RFC connectivity from Node.js is the first half; the second shows the package on its own, as an npm alias for node-rfc, and through an npm override as the connector below an unchanged @sap/cds-rfc. The 0.2.3 beta stops at direct application-server connections with password authentication and classic Unicode RFC: no message-server load balancing, SNC, tRFC, qRFC, bgRFC or server mode.published 2026-08-10Marian Zeis, blog.zeis.de — Marian Zeis
README
quoted from @sap/cds-rfc@2.2.1, read@sap/cds-rfc
An integration plugin for ABAP RFC Function Modules into the SAP Cloud Application Programming Model (CAP). This applies to general RFC-callable Function Modules and to BAPIs.
The plugin contains
- A converter from an RFC interface description to CDS.
- The runtime integration for CAP Node.js.
The integration for CAP Java is covered in a different Java-specific plugin. Currently this is not yet available.
History
Fixes 2
Others providing
Compare all 3 on the RFC connectivity page →- 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, capSDK-free TypeScript client for SAP synchronous RFC on Node.js
- SAP Connectivity serviceSAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btpProxy from cloud apps to on-premise systems via Cloud Connector
- 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, capSDK-free TypeScript client for SAP synchronous RFC on Node.js
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-cds-rfc- JSON
- /artifacts/sap-cds-rfc.json
- MCP
- Connecting an agent