Skip to content
ERP Preflight

Software Collection Dependency Guard

Export software collection item cross-reference and release validator

Content reviewed September 26, 2026

Engine
SOFTWARE_COLLECTION_DEPENDENCY_GUARD
Domain
Release & Transport
Version
1.1.0
Target releases
S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Accepted formats
JSON, XML, ZIP

Input contract

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

Finding codes

Finding codes (7)

  • SC_MISSING_PREREQUISITEDefault severity: BlockerCategory: RELEASE_TRANSPORT

    Prerequisite collection neither exported nor in target

    Remediation: Add the prerequisite collection to the export, or import it into the target tenant first ('Import Collection'), then re-run the preflight.

  • SC_SCHEMA_VALIDATION_FAILEDDefault severity: BlockerCategory: RELEASE_TRANSPORT

    Collection or item entry violates the export schema

    Remediation: Re-export the software collection from 'Export Software Collection'; the named collection/item entry is missing mandatory attributes (id, type, status) and was excluded from the dependency analysis.

  • SC_CIRCULAR_DEPENDENCYDefault severity: CriticalCategory: RELEASE_TRANSPORT

    Circular dependency between software collections

    Remediation: Merge the interdependent items into one collection or move the shared prerequisite objects into a foundation collection imported first; circular collections cannot be imported in any order.

  • SC_DANGLING_FIELD_REFERENCEDefault severity: CriticalCategory: RELEASE_TRANSPORT

    Item references a field that is not exported or present

    Remediation: Add the referenced custom field to an exported collection or confirm it exists in the target tenant; otherwise the import fails activation.

  • SC_WRONG_IMPORT_ORDERDefault severity: CriticalCategory: RELEASE_TRANSPORT

    Planned import order places a collection before its prerequisite

    Remediation: Re-order the planned import so every prerequisite collection is imported first (see the recommended sequence / import waves in the analysis result); importing a dependent collection first fails activation of its items in the target tenant.

  • SC_DRAFT_ITEM_INCLUDEDDefault severity: MajorCategory: RELEASE_TRANSPORT

    Unpublished (draft) item in collection

    Remediation: Publish the item in its key-user app (Custom Fields / Custom Logic / Custom CDS Views) before export; draft items are not transported.

  • SC_GROUPING_SUGGESTEDDefault severity: MinorCategory: RELEASE_TRANSPORT

    Suggested grouping to resolve cyclic collections

    Remediation: 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.

Input validation codes (5)

  • SC_ARCHIVE_REJECTEDDefault severity: MajorCategory: INPUT_VALIDATION

    Archive rejected by ingestion safety limits

    Remediation: The archive exceeded the 100:1 expansion ratio, 500 MB total size, entry-count or 2-level nesting limit, or contained path traversal / encrypted members. Upload a flat, unencrypted archive of the export files. No verdict was produced. Re-export the artifact in one of the formats accepted by Software Collection Dependency Guard (JSON, XML, ZIP) and re-run the analysis.

  • SC_INVALID_INPUTDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact does not match the engine input contract

    Remediation: Provide the artifact type documented for this engine; unrelated or structurally invalid documents are rejected. No verdict was produced. Re-export the artifact in one of the formats accepted by Software Collection Dependency Guard (JSON, XML, ZIP) and re-run the analysis.

  • SC_PARSE_ERRORDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact could not be parsed

    Remediation: Fix the syntax error at the reported line/column (or re-export the file unmodified from SAP). No verdict was produced. Re-export the artifact in one of the formats accepted by Software Collection Dependency Guard (JSON, XML, ZIP) and re-run the analysis.

  • SC_PAYLOAD_TOO_LARGEDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact exceeds the size limit

    Remediation: Split the export (e.g. per package, company code or date range) so each upload stays under the service payload limit. No verdict was produced. Re-export the artifact in one of the formats accepted by Software Collection Dependency Guard (JSON, XML, ZIP) and re-run the analysis.

  • SC_INSUFFICIENT_INPUTDefault severity: InfoCategory: INPUT_VALIDATION

    Required input missing

    Remediation: Supply every input the engine's contract marks as required (see the engine catalog entry). No verdict was produced. Re-export the artifact in one of the formats accepted by Software Collection Dependency Guard (JSON, XML, ZIP) and re-run the analysis.

Back to the documentation
Software Collection Dependency Guard — ERP Preflight Docs