Upload and bundle behavior
A supportable explanation of what happens after an Agent ZIP reaches S4Ready Web.
Agent and SAP access
Use this when a user asks whether an upload is stuck, cancelled, too large, or safe to rerun.
Understand upload phases
The overlay names the major server-side steps.
- Uploading transfers the ZIP bytes to the backend.
- Creating web datasets creates one dataset per detected migration domain.
- Confirming dataset creation verifies ingestion after a lost response or reconnect.
Handle bundle limits
The standard customer-managed license has no commercial bundle-size cap; host-safety and evaluation controls remain separate.
- LICENSED does not cap bundle size. Plan limit reached applies only to an explicitly capped non-standard profile, not the normal customer-managed license.
- A host-safety guard protects the installation; Web reports Bundle too large to process. The instance operator, not a workspace user, owns its sizing.
- Split extraction by migration object when a bundle is too large to process.
Recover from partial work
Partial ingestion should be visible and explainable.
- A cancelled ingestion keeps datasets committed before the safe checkpoint.
- A run with failed tables can still upload when early review is useful.
- Recognized S/4HANA config tables become stage-scoped reference-data snapshots.
How to use this page
Each guide is a compact operating view. Use it to act, then continue into the related workflow page when you need the next step.
- 1ScanRead the section headings and confirm you are in the right guide for the role or moment.
- 2ActUse the bullets as the checklist for the extraction, review, approval, or handoff task.
- 3ContinueJump to a related guide when the work moves into upload, mapping, governance, or security.
Related guides
Use these when the workflow moves to the next handoff point.