Release & transport
SAP software collection import problems
Software Collection Dependency Guard checks an exported key-user software collection for items whose dependencies are neither exported nor present in the target.
Detected by:Software Collection Dependency Guard
Documented problems
- BlockerPrerequisite collection neither exported nor in target
SC_MISSING_PREREQUISITE
- BlockerCollection or item entry violates the export schema
SC_SCHEMA_VALIDATION_FAILED
- CriticalCircular dependency between software collections
SC_CIRCULAR_DEPENDENCY
- CriticalItem references a field that is not exported or present
SC_DANGLING_FIELD_REFERENCE
- CriticalPlanned import order places a collection before its prerequisite
SC_WRONG_IMPORT_ORDER
- MajorUnpublished (draft) item in collection
SC_DRAFT_ITEM_INCLUDED
- MinorSuggested grouping to resolve cyclic collections
SC_GROUPING_SUGGESTED
Terms used in this area
Background articles
- Transport dependencies: why imports fail or break production in the wrong orderHow dependencies between transport requests arise, what happens when a transport is imported without its predecessors, and how to check sequencing before an import.
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.