Video Summary:
The video explains the Selective Data Transfer (SDT) process for migrating relevant documentation and test artifacts from SAP Solution Manager to SAP Cloud ALM during a transition. It covers why to run the SAP Readiness Check first, the SDT workflow across Activate phases (scope, extract, simulate, upload, validate), the artifact types supported, how entity relationships are rebuilt in Cloud ALM, document-handling options, technical prerequisites, and practical recommendations (start with a POC, validate with analytics).
Key Points:
- Purpose and scoping: SDT is a one‑time, selective migration to preserve only relevant Solution Manager documentation and Focus Build test artifacts; start by running the SAP Readiness Check and use the Activate roadmap to define source branches, up‑to‑date content, and the migration scope.
- Extract → simulate → iterate → upload → validate workflow: extract process hierarchy, libraries, process content/diagrams, documents, and test steps; simulate uploads to correct issues, then perform final upload and validate results in Cloud ALM analytics.
- Artifacts and entity relations: supported items include process hierarchies, multiple library types, custom solution processes/diagrams, documents, and Focus Build test cases/steps; unique IDs are used during upload to rebuild relationships (process → activities → executables → documents → test steps).
- Operational constraints and recommendations: SP50 is the minimal prerequisite for SDT reports; SDT is not a synchronization (no continuous updates) and there is no rollback after upload (only delete), so start with small proof‑of‑concept packages, choose document handling (external DMS links or push files to SAP BTP DMS), and thoroughly validate completeness and quality with Cloud ALM analytics.