Software collection
Software collection (key-user extensibility)
The transport unit of key-user extensibility in SAP S/4HANA Cloud: extension items are exported together and imported into the next system.
Key-user extension items — custom fields, custom logic, custom CDS views — are assigned to a software collection, exported and imported in the target system. Only published items are transported; drafts stay behind.
A collection must contain everything its items depend on, or those dependencies must already exist in the target; otherwise the import fails activation. Collections that depend on each other in a circle cannot be imported in any order.
In ERP Preflight
Software Collection Dependency Guard checks an exported collection for missing prerequisites, circular dependencies, dangling field references and draft items before you import it.
Problems that involve Software collection
- CriticalType / length change breaks consumers
- MajorModification impacts downstream consumers
- MajorCustom dependency not transported with the object
- BlockerCollection or item entry violates the export schema
- CriticalCircular dependency between software collections
- BlockerCyclic extension dependency
- CriticalDeletion blocked by active consumers
- MajorHigh change blast radius
Related terms
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
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.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.