20.2 Transport & Content Lifecycle
SAP Datasphere provides a Transport app for moving content between tenants. SAP also supports integration with SAP Cloud Transport Management for landscape-based transport routes. Consult the current SAP Datasphere Help Portal transport documentation for the supported options and prerequisites.
Transport mental model
Source tenant -> package -> transport mechanism -> target tenant -> import -> deploy -> validate
Common mechanisms include:
- Transport app between tenants
- SAP Cloud Transport Management
- CSN or JSON based object exchange for supported objects
- Content Network for SAP and partner content
Important distinction
Transport definitions are not a substitute for environment-specific configuration. Connections are a critical example: imported packages do not simply overwrite target connections.
Package design
Keep packages aligned to a business capability or bounded release:
- source acquisition
- transformation/modeling
- semantic layer
- consumption
- authorization artifacts
- supporting objects
Avoid giant packages that make dependency analysis and rollback difficult.
Enterprise rule
Use a stable promotion path and record:
- package identifier
- source commit or change reference
- approver
- target tenant
- import result
- validation result
- release timestamp
Transport failure triage
- Identify the failed object.
- Determine whether failure is dependency, privilege, configuration or runtime related.
- Check target-space readiness.
- Inspect transport/import logs.
- Correct the source definition where possible.
- Re-export and repeat validation.