PackagePackageA library you install and call yourself.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
capire/s4
A pre-built integration package for SAP S/4HANA, holding the imported service definitions a CAP project would otherwise generate for itself.
Facts
Last pushLicenceApache-2.0
Where it sits
Lives in
Provides
Service integrationCAPService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.DestinationsCAPDestinationsReaching 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.
Who is behind it
Capire Docs & SamplesCapire Docs & SamplesMaintains this
In the atlas: maintains 20, wrote 1@capiremaintainerDaniel HutzelContributes to this
In the atlas: contributes to 32, wrote 3@danjoaRené JeglinskyContributes to this
In the atlas: contributes to 20@renejeglinskySteffen WeinstockContributes to this
In the atlas: contributes to 14@stewsk3 contributors
In the atlas: maintains 20, wrote 1@capiremaintainerDaniel HutzelContributes to this
In the atlas: contributes to 32, wrote 3@danjoaRené JeglinskyContributes to this
In the atlas: contributes to 20@renejeglinskySteffen WeinstockContributes to this
In the atlas: contributes to 14@stewsk3 contributors
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1from DestinationsA destination used by a covered CAP application sends SAP product data to a non-SAP product rather than only addressing a remote endpoint.
- § 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.
A destination is configuration, not the deciding boundary. The licence becomes material when the resulting data flow is extraction into a non-SAP product, so the target and purpose need review.
SAP Developer License Agreement 3.2 CAP →What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
As a package
- Where it runs
- Inside its host
- Distributed through
- does not say
Connections
Group by
NodeRelationBasis
Functional
DestinationsDestinationsReaching remote systems without addresses or credentials in the codeSAP and community, unassessed
provides
authored
provides Destinations
Reaching remote systems without addresses or credentials in the code
Service integrationService integrationUsing a remote service as if it were one of your ownSAP and community, narrow by design
provides
stated
provides Service integration
A pre-built integration package for SAP S/4HANA: the imported service definitions a consuming project would otherwise generate itself, registering a service binding endpoint for the business partner service when added as a dependency. A sample, not for production, by its own README.
“This sample showcases how to provide pre-built integration packages for SAP S/4HANA integration.”“Following the plug & play principle of CAP plugins, adding this dependency to your project will automatically register a service binding endpoint for S4BusinessPartnerService.”
Using a remote service as if it were one of your own
Technical
connects to
stated
connects to SAP S/4HANA
The service binding endpoint it registers reaches SAP S/4HANA's S4BusinessPartnerService
“adding this dependency to your project will automatically register a service binding endpoint for S4BusinessPartnerService.”
SAP's ERP suite, run on-premise or as a private cloud edition, with its business data and processes reached over OData, RFC and the ABAP platform. For the things here it is the system a tool reads from or writes to. The public cloud edition is its own entry.
Download
Where it sits in your app
Download
SAP S/4HANASAP's ERP suite, run on-premise or as a private cloud edition, with its business data and processes reached over OData, RFC and the ABAP platform. For the things here it is the system a tool reads from or writes to. The public cloud edition is its own entry.
capire/s4A pre-built integration package for SAP S/4HANA, holding the imported service definitions a CAP project would otherwise generate for itself.sap official, cap
capire/s4 → SAP S/4HANAStated in the document, dataThe service binding endpoint it registers reaches SAP S/4HANA's S4BusinessPartnerService
SAPnot SAP's, or the project's ownstated in the document
README
quoted from capire/s4 under Apache-2.0, readcapire/s4/readme.mdthe maintainer’s wordsOn GitHub
@capire/s4
This sample showcases how to provide pre-built integration packages for SAP S/4HANA integration.
Caution
This is just a sample, not intended for production use. It is meant to demonstrate how to create a CAP plugin and how to use it in your application. It is not optimized for performance or security.
Plug & Play
Following the plug & play principle of CAP plugins, adding this dependency to your project will automatically register a service binding endpoint for S4BusinessPartnerService.
License
Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.
Others providing
Service integrationService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from destinations, which is how the address and the credentials are found, and from replication, which is holding the data locally.SAP and community, narrow by design
- com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, capRemote Services for consuming OData V2 and V4 APIs in CAP Java
- cds-data-federationcds-data-federationA data federation plugin for SAP CAP applications that declares delegation, caching and replication on a consumption view through CDS annotations, instead of hand-written handlers.independent, capData federation for CAP via delegation, caching and replication
- @sap/cds-dk@sap/cds-dkThe command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.sap official, capCommand line client and development toolkit for CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
DestinationsDestinationsReaching 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.SAP and community, unassessed
- SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btpNamed, credentialed addresses of other systems resolved at runtime
- com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, capRemote Services for consuming OData V2 and V4 APIs in CAP Java
- com.sap.cds:cds-integration-cloud-sdkcom.sap.cds:cds-integration-cloud-sdkA CAP Java feature that integrates the SAP Cloud SDK, so features such as remote OData and enterprise messaging resolve a destination or service binding and reach a remote REST-based service.sap official, capSAP Cloud SDK integration for remote REST services in CAP Java
- cdsecdseResolves a destination from a CAP project's own configuration, then makes the outbound call with axios: the url, the method and the body are written at the call site.independent, capDestination resolution and axios calls from CAP configuration
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
- @sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.sap official, capDestination lookup and connectivity proxy for the Cloud SDK
- @sap-cloud-sdk/http-client@sap-cloud-sdk/http-clientThe HTTP client that carries a destination's credentials, so an outbound call inherits the authentication rather than assembling it.sap official, capHTTP client carrying a destination's credentials
- @sap-cloud-sdk/odata-common@sap-cloud-sdk/odata-commonThe shared machinery under the SDK's OData and OpenAPI client generators; a dependency of the generated clients rather than something written against directly.sap official, capShared machinery under the Cloud SDK's OData and OpenAPI clients
- @sap-cloud-sdk/openapi@sap-cloud-sdk/openapiGenerated OpenAPI clients for the Cloud SDK, so a REST API described by a specification is called through typed functions.sap official, capGenerated OpenAPI clients for the Cloud SDK
- @sap-cloud-sdk/resilience@sap-cloud-sdk/resilienceTimeouts, retries and circuit breaking around a remote call, so one slow downstream system does not take the application with it.sap official, capTimeouts, retries and circuit breaking around remote calls
- @sap-cloud-sdk/util@sap-cloud-sdk/utilGeneral utilities shared across the Cloud SDK packages — a dependency, not a thing to reach for on its own.sap official, capGeneral utilities shared across the Cloud SDK packages
- @sapmentors/cds-scp-api@sapmentors/cds-scp-apiA Node module for CAP that calls an external API through a destination instead of a hardcoded endpoint, taking its address, credentials and on-premise tunnel from the SAP Destination and Connectivity services.community org, capNode module for CAP calling external APIs through a destination
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
discovered viaGitHub API · capire
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:capire-s4- JSON
- /artifacts/capire-s4.json
- MCP
- Connecting an agent