Symptom
- Import job fails with the message "Data mapping ended unexpectedly."
- Newly created import jobs hang and cannot proceed from query selection/mapping; the screen does not advance.
- Newly created import model with same steps works fine.
Environment
- SAP Analytics Cloud 2026.15.6
Reproducing the Issue
- Open the target import model and start the existing import job.
- Observe that the job terminates with "Data mapping ended unexpectedly."
- Create a new import job using the same OData connection.
- Select the source/query and proceed; the workflow hangs and does not move to the mapping step.
Cause
The issue is currently under investigation of development team.
Resolution
The issue is currently under investigation of development team.
See Also
- Refer to: How to collect a HTTP archive (HAR) file and Console Log file in SAP Analytics Cloud
- Refer to: [Best Practice] How to capture the OData query when using import data connection
- Refer to: Unable to run a specific import job of a model in SAP Analytics Cloud (SAC)
- Refer to: Unexpected termination of data load for data models in SAP Analytics Cloud
Keywords
sac, import data, data mapping ended unexpectedly, odata, oauth, authentication_error, error_invalid_auth_request, 502 bad gateway, gather stage, datasphere, odata connection validation, mapping hangs, import job failure, data acquisition, sac upgrade , KBA , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem
Product
SAP Analytics Cloud all versions
SAP Knowledge Base Article - Public