メニュー
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.
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.
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.
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-console |
| description | 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. |
Pre-built SAPUI5 app shipped at cds-data-pipeline/app/pipeline-console/. Reads/writes management OData at /pipeline/.
| Column | Purpose |
|---|---|
| Data Pipelines (begin) | Searchable list with status, last run, errors |
| Detail (mid) | Network graph, Overview / Runs / Health / Statistics tabs, pipeline actions |
| Data inspector (end) | Source/target preview via inspectData, column picker, advanced filters |
Adaptive polling: 30 s idle, 3 s while any pipeline is running.
Add to package.json:
{
"cds": {
"requires": {
"data-pipeline": {
"impl": "cds-data-pipeline",
"management": {
"reuse": {
"api": true,
"console": true
}
}
}
}
}
}
cds deploy
cds watch
Open http://localhost:4004/pipeline-console/index.html.
Sources live in packages/cds-data-pipeline/app/pipeline-console-src/. Rebuild with:
cd packages/cds-data-pipeline && npm run build:pipeline-console
The app uses SAPUI5 (not OpenUI5) for sap.suite.ui.commons.networkgraph.
cds add pipeline-console
Do not combine cds add pipeline-console with management.reuse.console.
cds-data-pipeline installedmanagement.reuse.api or using from 'cds-data-pipeline/index.cds'❌ Wrong — management.reuse.console + cds add pipeline-console (duplicate UI route).
✅ Correct — pick reuse or own, not both.
❌ Wrong — expecting the console without exposing the management OData service.
✅ Correct — set management.reuse.api: true or import index.cds.
❌ Wrong — exposing inspectData without securing underlying entity read access.
✅ Correct — apply the same authorization to /pipeline and source/target services as for production data reads.