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.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
Overview
Imports the API of RFC-enabled function modules and BAPIs from an ABAP system as CDS and calls them from CAP Node.js; the low-level RFC library comes from a customer-only registry, and CAP Java is not covered.
A Node.js coverage assessment has not been written. View all flavors
A Node.js coverage assessment has not been written. View all flavors
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