メニュー
Installs and verifies cds-data-federation in a SAP CAP project. Use when adding the federation plugin, checking peer dependencies, confirming plugin boot, or troubleshooting missing cds-data-pipeline for replicate.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Creates @federation.replicate consumption views for scheduled remote-to-local sync in SAP CAP. Use when copying remote OData or REST data locally, configuring schedule, delta sync, or the replicated aspect.
Registers cds-data-pipeline jobs via addPipeline with correct source and target shapes. Use when creating replicate, materialize, or move-to-service pipelines, configuring delta sync, schedules, or REST/OData sources.
Enables the cds-data-pipeline Pipeline Console UI for the /pipeline management API. Use when adding pipeline monitoring, running pipelines manually, viewing run history, inspecting source/target data, or scaffolding with cds add pipeline-console.
Registers cds-data-pipeline event hooks on DataPipelineService. Use when customizing PIPELINE.READ, PIPELINE.MAP, PIPELINE.WRITE, filtering records, or extending pipeline behavior without forking the engine.
Installs and configures cds-data-pipeline in a SAP CAP project. Use when adding the pipeline plugin, importing tracker schema, exposing the management OData service, or connecting to the pipeline engine.
Handles cross-service $expand and navigation in cds-data-federation. Use when expanding local to remote, remote to local, cross-provider mashups, navigation filters, or association renames across federated entities.
| name | federation-setup |
| description | Installs and verifies cds-data-federation in a SAP CAP project. Use when adding the federation plugin, checking peer dependencies, confirming plugin boot, or troubleshooting missing cds-data-pipeline for replicate. |
# Delegate-only:
npm add cds-data-federation
# Replicate or entity cache:
npm add cds-data-federation cds-data-pipeline
| Package | When required |
|---|---|
@sap/cds >= 8 | Always |
@sap-cloud-sdk/http-client, @sap-cloud-sdk/resilience | OData remotes (usually already present with CAP OData) |
cds-data-pipeline | @federation.replicate, cache.strategy: 'entity' |
cds-caching >= 1 | cache.strategy: 'response' (default) |
@cap-js/sqlite >= 2 | Optional — secondary SQLite for entity cache |
Start the app and confirm:
[cds-data-federation] discovered N @federation.* entities
If N is 0, check that entities have @federation.delegate or @federation.replicate and a projection on remote.X clause.
Configure the remote in cds.requires per CAP Reuse & Compose — Service Integration.
❌ Wrong — @federation.replicate without cds-data-pipeline in package.json.
✅ Correct — npm add cds-data-pipeline before annotating replicate entities.
❌ Wrong — expecting the plugin to wire REST delegate reads.
✅ Correct — REST sources use @federation.replicate with explicit rest config.