SAP Error Codes and Troubleshooting
This section explains error status codes and how to fix them.
Error Code | Error Message | Action |
---|---|---|
1001 | Request job action is not supported. | Execution flow is incorrect. Check current job state and call only the allowed functions. |
1002 | Current user reached limit of maximum number of active jobs. | Delete or run active jobs to allow creation of a new job. |
1003 | Request not allowed on the selected job. Preconditions failed. | Incorrect requested action. Please check job state and adjust request. |
1004 | The following target fields are incorrect or do not exist on the model. | Incorrect request body not aligned with metadata. |
1005 | Unable to infer import type. | API is not able to infer import type. Specify it in the URL. |
1006 | Request body is incorrect or missing. | Bad request. Review and adjust request body. |
1007 | Current modelID reached limit or maximum number of active jobs. | Delete or run active jobs to allow creation of a new job. For more information, see SAP Note 3491183 ![]() |
1008 | Unable to serialize mapping hash map. | Bad request. Review and adjust request body. |
1009 | A source or target column in the mapping is empty. | Bad request. Review and adjust request body. |
1010 | Request already in progress. | Wait for the execution of the selected job. |
1011 | Temporary storage does not contain valid records. | No valid rows have been pushed. For more information, see SAP Note 3436537 ![]() |
1012 | User is not allowed to interact with selected job. | Missing authorization. |
1033 | Every row in temporary storage is invalid. | Please use /invalidRows on the import job to see the reason. For more information, see SAP Note 3451247 ![]() |
1101 | Request not allowed on the system. | Feature not active on the tenant. Wait SAC deployment or create incident. |
1200 | The supplied content type is not supported by the Data Import Service. | Bad request. Review and adjust request. |
1201 | The request body sent is too large to be processed by the Data Import Service. | Reduce request body. |
1202 | Request body data incorrect or missing. | Bad request. Review and adjust request body. |
1203 | Request body mapping is incorrect. | Bad request. Review and adjust request body. |
1205 | Failed to insert data to temporary data store. | Create an incident. |
1301 | Invalid import type. | Bad request. Review and adjust request. |
1302 | Unable to create temporary data store. | Create an incident. |
1401 | Faild to validate table. | Create an incident. |
1402 | Failed to create table. | Create an incident. |
1603 | Job ID not found. | Review JobID getting list of jobs to make sure that is valid. |
1604 | Job cannot be retrieved. | Create an incident. |
1605 | Job cannot be persisted. | Create an incident. |
1606 | Jobs table migration failed. | Create an incident. |
1607 | Jobs cannot be retrieved. | Create an incident. |
1608 | Job cannot be deleted. | Create an incident. |
1701 | Model cannot be retrieved. | Make sure that you have access to the model before accessing it. If you have it, create an incident. |
1702 | Models cannot be retrieved. | Create an incident. |
1703 | Model metadata cannot be retrieved. | Make sure that you have access to the model before accessing it. If you have it, create an incident. |
1704 | Model does not exist. | Adjust requested modelID. |
1705 | Failed to execute select count table SQL. | Create an incident. |
1706 | Invalid URL parameter. | Adjust request. |
1802 | The model is restricted for import. | Check whether the access and privacy settings on the model that allows for import using the Data Import API is enabled. |
No comments:
Post a Comment