Symptom
- After a successful SAP Note implementation that has made changes to an OData service that belongs to an application, the application shows the following error:
- Resource not found for the segment 'XXXXXXX'" at startup.
- Response from external server has status code of 404.
OR
- After changes that modify custom Z_OData services, the $metadata request of the service does not give back the correct response.
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 Gateway
- SAP NetWeaver
Product
Keywords
$metadata, segment, resource not found, Resource not found for the segment, SAP Gateway, SAP OData Gateway, Odata metadata, Odata service, reload metadata, metadata cache, Gateway, 404, SEGW, error message is generated, because the segment cannot be found, error code: 404, /IWBEP/REG_SERVICE, /IWFND/MAINT_SERVICE, , KBA , response from external server has status , status code of 404 , opu-gw-cor framework , opu-gw-cor framework , OPU-BSE-SDE , SAP Data Enablement , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , OPU-GW-COR , Framework , LOD-ANA-PL-PLI , Planning Integration (BPC import/export/writeback) , 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.