CapabilityIntegration & MessagingJava, read from its artifacts

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 Java applicability. View All CAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for Java.

A Java coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

No community artifact is confirmed here for Java.

A Java coverage assessment has not been written. View all flavors

Licence1

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 →

Artifacts1

1 of 1 artifacts
ArtifactSignals
Services1
SAP Connectivity serviceProxy from cloud apps to on-premise systems via Cloud Connector
Signals
none

Details

Coverage
stateunmapped, CAP, Java, derived
also inBTP/BAIP, ABAP
For your agent
Ref
capability:rfc-connectivity
JSON
/capabilities/rfc-connectivity.json
MCP
Connecting an agent