菜单
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.
用 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.
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.
Creates @federation.delegate consumption views on remote OData entities in SAP CAP. Use when proxying remote data, adding field renames, association renames, read-only defaults, CUD opt-in, or delegate caching.
| name | pipeline-setup |
| description | 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. |
npm add cds-data-pipeline
Peer: @sap/cds >= 9 · Node >= 22
const pipelines = await cds.connect.to('data-pipeline');
await pipelines.addPipeline({ name, source, target, ... });
Option A — reuse from plugin (recommended for local dev):
{
"cds": {
"requires": {
"data-pipeline": {
"impl": "cds-data-pipeline",
"management": { "reuse": { "api": true } }
}
}
}
}
Option B — manual CDS imports:
Tracker schema:
using from 'cds-data-pipeline/db';
Management OData (single import):
using from 'cds-data-pipeline/index.cds';
Served at /pipeline/. Add your own auth — the plugin ships no @requires annotations.
Prune old PipelineRuns rows on a schedule:
"data-pipeline": {
"impl": "cds-data-pipeline",
"housekeeping": {
"retentionDays": 90,
"maxRuns": 1000,
"schedule": "0 3 * * *"
}
}
Per-pipeline override: addPipeline({ ..., retention: { maxRuns: 200 } }). See Run housekeeping.
After boot, /pipeline/Pipelines should list registered pipelines. Log lines from cds-data-pipeline confirm plugin activation.
❌ Wrong — forgetting tracker schema when not using management.reuse.api → tables missing.
✅ Correct — use reuse API or import db / index.cds.