We’re automating sustainability data model deployments using CTS+ in our SAP PLM 2020 environment, but transports fail consistently with dependency errors. Our DevOps pipeline deploys custom sustainability tables and ABAP objects, but the CTS+ transport management shows missing object references during import.
Error snippet from transport log:
Transport TPK900123 import failed
Missing dependency: TABL ZSUST_CARBON_DATA
Dependent object: FUGR ZSUST_CALC_ENGINE
Status: Import terminated
We’ve tried analyzing ABAP object dependencies manually, but our automated pipeline doesn’t capture cross-references properly. The sustainability module requires specific table sequences for carbon footprint calculations. How do others handle automated dependency resolution in CTS+ for complex data models?
For sustainability data models specifically, there’s a critical configuration step many miss. Check table TDEVC for package dependencies - sustainability objects often span multiple packages with implicit dependencies that CTS+ doesn’t detect automatically. Your automation needs to scan these package relationships before transport creation.
I’ve seen this exact scenario with sustainability models. The problem is that CTS+ transport management processes objects in alphabetical order by default, not by dependency hierarchy. Your ZSUST_CALC_ENGINE function group is being imported before ZSUST_CARBON_DATA table exists. You need to split transports by object type - tables first, then function groups, then programs. Also run ABAP object dependency analysis using SE80 before creating transports to map the complete dependency tree. For automated DevOps pipeline integration, you’ll want to script transport creation with explicit sequencing.
Classic dependency chain issue. CTS+ doesn’t auto-resolve complex ABAP dependencies in automated pipelines. You need explicit sequencing in your transport strategy. Check if your function group references tables that haven’t been created yet in the target system.
Absolutely maintain automation, just smarter sequencing. Create transport chains - TR01 for tables/structures, TR02 for function modules, TR03 for programs/interfaces. Your pipeline should generate these programmatically based on object type scanning. Use transaction SE03 to analyze object dependencies before transport creation. The key is building dependency awareness into your automation scripts.
Another angle - use the CTS+ API for programmatic transport management. You can query object dependencies via RFC calls and build dynamic import sequences. We implemented this for our sustainability rollout and it handles complex dependency trees automatically. The API returns dependency graphs that your pipeline can parse to determine optimal import order.