Symptom
Initial sync is failing with HTTP code 500 and Runtime error "SAPSQL_IN_ITAB_ILLEGAL_SIGN".
- Mobile client sync error example:
Retrieve feed "https://[...].hana.ondemand.com/DEST_SAM2410_PPROP/$batch" failed because the OData server returned HTTP code, 500, with message: <?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>SAPSQL_IN_ITAB_ILLEGAL_SIGN</code><message>Runtime Error: 'SAPSQL_IN_ITAB_ILLEGAL_SIGN'. The OData request processing has been abnormally terminated. If you use SAP S/4HANA Cloud, please create an incident. Otherwise, if "Runtime Error" is not initial, launch ADT feed "Runtime Errors" or transaction ST22 / SM21 [...]</message>
- Backend DUMP Runtime error example:
Category ABAP programming error
Runtime Errors SAPSQL_IN_ITAB_ILLEGAL_SIGN
ABAP: Program /MERP/CL_PM_ORDER_TYPE_OD=====CP
Application Component MOB-APP-MAO-ERP
Short Text
Invalid value in SIGN field of value table for IN itab operator.
What happened?
Error in the ABAP application program.
The current ABAP program "/MERP/CL_PM_ORDER_TYPE_OD=====CP" had to be terminated because it found a statement that could not be executed.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
SAP Service and Asset Manager any version
Product
Keywords
HTTP 500, Operator, SAPSQL_IN_ITAB_ILLEGAL_SIGN, /MERP/CL_PM_ORDER_TYPE_OD=====CP, /MERP/CL_PM_ORDER_TYPE_OD=====CM004, GET_DATA_FOR_READ_REQUEST , KBA , MOB-APP-MAO-ERP , S4MERP/SMERP-Mobile Add-On integration to S4/ERP , MOB-APP-MAO , Mobile Application Integration Framework , MOB-APP-SAM , SAP Service and Asset Manager , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview