メニュー
Installs cds-data-materialization and cds-data-pipeline in a SAP CAP project. Use when adding the materialization plugin, checking peer dependencies, or ensuring tracker schema is present.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | materialization-setup |
| description | Installs cds-data-materialization and cds-data-pipeline in a SAP CAP project. Use when adding the materialization plugin, checking peer dependencies, or ensuring tracker schema is present. |
npm add cds-data-materialization cds-data-pipeline
Both packages are required. Materialization composes query-shape pipelines on the engine.
From cds-data-pipeline:
using from 'cds-data-pipeline/db';
using from 'cds-data-pipeline/srv/DataPipelineManagementService';
Materialization binds @materialize.snapshot entities to addPipeline at boot — tracker tables must exist.
Auto-loads via cds-plugin.js. No manual server.js registration for annotation-driven snapshots.
| Package | Role |
|---|---|
cds-data-federation | Remote delegate / replicate |
cds-data-materialization | Local aggregate snapshots |
cds-data-pipeline | Shared engine |
Install federation and materialization side by side when you need remote sync and local rollups.
❌ Wrong — cds-data-materialization without cds-data-pipeline.
✅ Correct — always install both.
❌ Wrong — expecting materialization to read remote OData aggregates directly.
✅ Correct — replicate remote data locally first, then snapshot with source.service: 'db'.
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.