SAP Knowledge Base Article - Preview

3197578 - OData call fails in SAP PI due to caching of old metadata

Symptom

  • In SAP Process Integration (PI) or Process Orchestration (PO) you have interfaces using the OData Adapter. 
  • Perhaps you have added new fields to the OData xsd or EDMX file you are using or made some specific changes. 
  • PI caches the OData metadata for the OData service and any changes to the metadata are not automatically refreshed on PI side. 
  • Errors can occur during the message processing, such as:
    Parsing response from ODATA call with cached older metadata on PI gives error such as: org.apache.olingo.odata2.api.ep.EntityProviderException: Illegal argument for method call with message <Changed metadata field>.
    ODATA_CALLING_ERROR:OData call failed com.sap.aii.adapter.lib.exception.ODataProcessingException: The XML is malformed 
  • How to Force refresh OData metadata on SAP PI side?


Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration

Product

SAP NetWeaver 7.5 ; SAP Process Integration all versions

Keywords

odata, pi, edmx, refresh, cache, metadata, structure,  , KBA , BC-XI-CON-ODT , ODATA Adapter , 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.