onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

cap-rfc

A CAP Node.js action that calls BAPI_EPM_BP_CREATE over RFC, with the function module's own signature imported as CDS and a destination standing in for the system once deployed.

cds.requires declares abaptrialRFC as kind: rfc against the model imported into srv/external, with credentials.destination: 'abaptrialRFC' under [production], and the handler calls rfc.BAPI_EPM_BP_CREATE({HEADERDATA: req.data.header}) and returns what comes back untouched. The service exposes one action, createBP, whose parameter is typed from the imported DDIC structure BAPI_EPM_BP_HEADER and whose return type is the function module's own result type, so the ABAP signature is the contract rather than a hand-written shape. @sap/cds-rfc supplies that connection kind, and @sap-rfc/node-rfc-library sits in devDependencies, which is where the native library enters. The MTA binds xsuaa, connectivity and destination on the lite plan and nothing else; the README is the CAP scaffold's own, and the project and its deployed application are named cap-rfc2 rather than after the repository.

GitHub0 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
RFC connectivityCAPRFC connectivitycapabilityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.DestinationsCAPDestinationscapabilityReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
@sap/cds-rfc@sap/cds-rfcartifactThe connection the service opens is declared with kind: rfc, the kind this plugin adds, and the project depends on it directly.SAP Destination serviceSAP Destination serviceartifactThe production profile reaches the ABAP system through a destination of the same name, and the MTA binds a destination instance to the service module.SAP Connectivity serviceSAP Connectivity serviceartifactThe MTA binds a connectivity instance to the service module, which is what reaches an on-premise system through the Cloud Connector.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Form
does not say

Connections5

Download
cap-rfc connectionscap-rfcPROVIDES→ demonstrates2demonstrates authoredDestinationsdemonstrates authoredRFC connectivityNEEDS→ needs3needs declared The connection the service opens is declared with `kind: rfc`, the kind this plugin adds, and the project depends on it directly. miyasuta/cap-rfc — package.json, cds.requires: https://raw.githubusercontent.com/miyasuta/cap-rfc/main/package.json miyasuta/cap-rfc — package.json, dependencies: https://raw.githubusercontent.com/miyasuta/cap-rfc/main/package.json@sap/cds-rfcneeds declared The MTA binds a connectivity instance to the service module, which is what reaches an on-premise system through the Cloud Connector. miyasuta/cap-rfc — mta.yaml, resources: https://raw.githubusercontent.com/miyasuta/cap-rfc/main/mta.yamlSAP Connectivity serviceneeds declared The production profile reaches the ABAP system through a destination of the same name, and the MTA binds a destination instance to the service module. miyasuta/cap-rfc — package.json: https://raw.githubusercontent.com/miyasuta/cap-rfc/main/package.jsonSAP Destination service

README

quoted from miyasuta/cap-rfc, read
miyasuta/cap-rfc/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-rfctree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
runtimesnode
deploymentCloud Foundry
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-rfc
JSON
/artifacts/miyasuta-cap-rfc.json
MCP
Connecting an agent