Transport Manager

Move objects between SAP Datasphere tenants using CSN/JSON transport packages.

25|7|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork --skill transport-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Transport Manager
Source: https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork/tree/main/skills/datasphere-transport-manager
Command: npx skills add https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork --skill transport-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transporting data models and objects between isolated SAP Datasphere tenants is error-prone and time-consuming; this Skill streamlines packaging, dependency resolution, and controlled deployment so teams can move changes from Dev to QA and Prod reliably and audibly. It reduces import failures caused by missing dependencies, inconsistent versions, or unavailable connections and provides validation and rollback guidance to protect production environments.

Core Features & Use Cases

  • Package Creation: Plan and build CSN/JSON transport packages with metadata, changelogs, and semantic versioning.
  • Dependency Analysis: Automated and manual checks that detect transitive dependencies, external connections, parameters, and potential circular references.
  • Export & Import Workflows: End-to-end export (compression, checksum, encryption) and import (conflict resolution, overwrite/rename/skip options) with post-import verification.
  • SAP Content Network Integration: Discover and import Content Network packages with guidance for customization and connection mapping.
  • Conflict & Connection Handling: Interactive strategies for existing object updates, missing dependencies, and absent connections, plus rollback and backup recommendations.
  • Use Case: Migrate a Customer Analytics suite from Development to QA, validate dependencies and connections, then deploy the approved package to Production with version tracking.

Quick Start

Use the Transport Manager to create an export package from your Dev space, verify dependencies and connections, and import the package into the QA tenant with chosen conflict resolutions.

Frequently Asked Questions about Transport Manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transport objects between SAP Datasphere tenants safely?

Transporting objects between SAP Datasphere tenants is done using CSN/JSON transport packages with dependency detection, checksum validation, and conflict resolution options to ensure safe automated or guided migrations.

What is the best way to resolve missing dependencies when importing a Datasphere package?

Resolving missing dependencies during Datasphere package import involves running automated dependency analysis to detect transitive dependencies and external connections, then applying interactive conflict resolution strategies like overwrite, rename, or skip.

Why does my SAP Datasphere migration fail due to unavailable connections?

SAP Datasphere migrations fail due to unavailable connections when target tenants lack required external connection mappings; performing connection availability checks before deployment prevents these import failures.

Can I use transport packages to deploy a Dev to QA and Prod workflow in SAP Datasphere?

Yes, you can use transport packages to deploy multi-tenant Dev to QA and Prod workflows in SAP Datasphere by applying semantic versioning, encryption validation, and post-import verification for controlled deployments.

Does the SAP Content Network support package import and customization mapping?

SAP Content Network integration supports discovering and importing Content Network packages into Datasphere, providing guidance for customizing objects and mapping required external connections during the import process.

What are the limitations when handling circular references during Datasphere transport?

Handling circular references during Datasphere transport requires automated dependency analysis to detect potential loops, though complex circular dependencies may need manual resolution before building the CSN/JSON export package.