Software collections · Software Collection Dependency Guard
Suggested grouping to resolve cyclic collections
- Default severity
- Minor
- Finding code:
- SC_GROUPING_SUGGESTED
- Engine version:
- 1.1.0
What this finding means
Software Collection Dependency Guard reports this finding with the default severity “Minor”.
About the engine: Export software collection cross-reference & release validator
How to fix it
Apply the suggested grouping: move the listed shared items into a foundation collection imported first (EXTRACT_FOUNDATION), or merge the cyclic collections into one (MERGE) when extraction cannot break the cycle; re-export and re-run the preflight.
How ERP Preflight detects it
The analysis is deterministic: the same exported files and the same knowledge snapshot always produce the same findings. No SAP system connection is required — you upload exports.
- Engine
- Software Collection Dependency Guard
- Accepted formats
- JSON, XML, ZIP
- What to export
Key-User Software Collection export: JSON {'collections': [{collection_id, items: [{item_id, type, status, dependencies}], dependencies}], 'target_system_collections': [...], 'import_order': [collection ids]}, XML <software_collections> (optional <import_order><step collection="…"/></import_order>), or a ZIP (nested up to 2 levels) containing manifest.json / manifest.xml.
- Required input
- At least one software collection
- Evidence
- Each finding points to the artifact path, line and column, the code snippet and the SHA-256 of the uploaded file. Findings without such a pointer are demoted to confidence UNKNOWN.
- Confidence
- The verdict rests on your artifacts only. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN) that shows how strong the evidence is.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- BlockerPrerequisite collection neither exported nor in target
- BlockerCollection or item entry violates the export schema
- CriticalCircular dependency between software collections
- CriticalItem references a field that is not exported or present
- CriticalPlanned import order places a collection before its prerequisite
- MajorUnpublished (draft) item in collection
Terms used on this page
Background reading
- 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.