SPRO2Cloud

On-premise IMG/SPRO configuration to Cloud CBC mapping and delta analysis

Content reviewed September 26, 2026

Engine: SPRO2CLOUD
Domain: Migration & Clean Core
Version: 2.2.0
Target releases: S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Accepted formats: CSV, JSON, TEXT, XLSX

Input contract

SPRO / IMG activity export: CSV (comma, semicolon, tab or pipe separated) with an activity (ActivityID / IMG activity / node), activity name, SPRO path or table column; JSON rows {'activity_id', 'activity_name', 'spro_path', 'table_name', 'module', 'country', 'source_release'} (list or {'activities': [...]}); an XLSX workbook (base64) whose worksheets start with such a header row; or a plain list of IMG activity IDs / table names, one per line.

Required input

At least one IMG activity ID, activity name, SPRO / IMG path or configuration table name

XLSX: every worksheet whose first non-empty row is a header naming an activity / table / activity-name / SPRO-path column is assessed; evidence uses worksheet coordinates (line = row, column = column) of '<file>!/<sheet>'. The workbook is read with the bounded XLSX reader (ZIP ratio / size / entry limits, defused XML).
Rows are matched to the catalog by IMG activity ID first, then by configuration table, then by an activity name (or the last SPRO path node) that identifies exactly one catalog entry.
Differences from the legacy behaviour are attached to every mapping verdict (technical_details.legacyDifferences). When the source release (row column or configuration.source_release) identifies a legacy system (ECC, S/4HANA on-premise or private cloud), mapped settings with documented behaviour changes are also reported as SPRO_CLOUD_BEHAVIOR_DIFFERENCE.

Finding codes

Finding codes (7)

SPRO_MAPPING_NOT_AVAILABLEDefault severity: CriticalCategory: Cloud Parity Gap
IMG activity not available in S/4HANA Cloud Public Edition
Remediation: Treat as a cloud parity gap: adopt the standard process, move the requirement to a side-by-side extension on SAP BTP, or reconsider the Private Edition.
SPRO_MAPPING_PROCESS_REDESIGNDefault severity: MajorCategory: Process Modernization
Legacy configuration concept requires process redesign
Remediation: Redesign the process on the cloud successor concept named in the finding (e.g. Output Management instead of NACE); plan it as a migration work package with business sign-off.
SPRO_CLOUD_BEHAVIOR_DIFFERENCEDefault severity: MinorCategory: Cloud Behavior Difference
Mapped cloud setting behaves differently from the legacy IMG activity
Remediation: Review each listed difference with the process owner before re-creating the setting: adapt the configuration workbook, test the changed behaviour in the quality tenant and update the user documentation; settings that relied on the legacy behaviour need a fit-to-standard decision.
SPRO_MAPPING_NEEDS_REVIEWDefault severity: MinorCategory: Uncataloged Configuration
Uncataloged / custom configuration needs manual review
Remediation: The activity is not in the curated SPRO→SSCUI catalog snapshot. Assess it manually; custom Z/Y tables can be rebuilt as Custom Business Objects or ABAP Cloud tables with a maintenance app.
SPRO_MAPPING_PARTIALDefault severity: MinorCategory: Configuration Modernization
IMG activity only partially available in cloud
Remediation: Use the mapped SSCUI for the supported parameters; re-implement the restricted sub-parameters with key-user extensibility or document them as a fit-to-standard deviation.
SPRO_MAPPING_SCOPE_DEPENDENTDefault severity: MinorCategory: Scope Dependency
Cloud setting requires scope item activation
Remediation: Activate the listed scope items in Central Business Configuration before configuring the SSCUI; check licensing for the scope item.
SPRO_MAPPING_EXACTDefault severity: InfoCategory: Configuration Modernization
IMG activity has an exact cloud SSCUI equivalent
Remediation: Re-create the setting in the target tenant via the mapped SSCUI in 'Manage Your Solution' > Configure Your Solution, under the listed scope item; no redesign required.

Input validation codes (5)

SPRO_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 SPRO2Cloud (CSV, JSON, TEXT, XLSX) and re-run the analysis.
SPRO_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 SPRO2Cloud (CSV, JSON, TEXT, XLSX) and re-run the analysis.
SPRO_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 SPRO2Cloud (CSV, JSON, TEXT, XLSX) and re-run the analysis.
SPRO_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 SPRO2Cloud (CSV, JSON, TEXT, XLSX) and re-run the analysis.
SPRO_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 SPRO2Cloud (CSV, JSON, TEXT, XLSX) and re-run the analysis.

Back to the documentation