Skip to main content

S/4HANA & CDS Modernization

1. Start from the business entity​

For S/4HANA sources, identify the business object and its supported semantic interface before deciding on extraction mechanics.

Examples include finance, procurement, sales, inventory, and master-data scenarios.

2. Prefer semantic acquisition​

SAP Datasphere supports importing entities from SAP S/4HANA Cloud and S/4HANA on-premise with rich metadata through supported integration capabilities.

The architecture decision should consider:

  • source release
  • API/CDS availability
  • delta capability
  • latency
  • source-system impact
  • authorization
  • semantic stability
  • required historical depth

3. CDS is not automatically a migration target​

A CDS view can be:

  • an acquisition interface
  • a semantic contract
  • a source for replication
  • a transient federated source
  • a component of a broader model

Choose based on workload requirements rather than treating CDS as a universal replacement for BW.

4. Validation​

Compare source semantics and target semantics explicitly: keys, associations, filters, units, currencies, time dimensions, and delta behavior.

5. Architect rule​

Use the highest-quality supported semantic contract available at the source, then decide whether the target needs federation, replication, or further transformation.