Symptom
- HTTP trace shows OData request fails:
{
"error": {
"code": "System error",
"message": "ABAP Runtime error 'System error'",
"@SAP__common.ExceptionCategory": "Framework_Error",
"@SAP__common.ErrorResolution": {
"Analysis": "Use ADT feed reader 'ABAP Runtime Errors' or run transaction 'ST22' on the SAP Gateway hub to check the details of this error from 20250606 approximately at 040431",
"Note": "See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"
}
}
} - However in the system, there is no ST22 dump, there is no error log can be found, and even payload trace is not able to capture the failed OData request.
- From OData framework side, Explicit Response Page is triggered, even though the error does not occur on frametwork layer.
- ICM trace level 2 can trace the request.
"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 NetWeaver
- SAP NetWeaver Application Server for SAP S/4HANA
- ABAP PLATFORM - Application Server ABAP
Product
ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions
Keywords
ABAP Runtime error, System error, Framework_Error, /IWBEP/CL_OD_ICF_HANDLER, ICF_ATTACH_ITS_PLUGIN, ICF, Internet Communication Framework, SICF, Service, Services, ICF service, ICF_GDPR , KBA , BC-MID-ICF , Internet Communication Framework , OPU-GW-COR , Framework , OPU-GW-V4 , Gateway Framework, OData v4 , 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