SAP MDM Integration with Enterprise Portal: Field with Code ‘XXX’ does not exist in the table ‘TTT’

[Former Member]

I am currently associated with SAPM-Portal maintenance and support project. SAP MDM version is 5.5, SAP Portal is 7.0 and SAP PI. We have only one master table and number of look up with linking provided by qualified look up tables.

During change requests handling; we came across a scenario; thought of sharing it across the larger community. This has to do with MDM repository schema cache in SAP Portal.

Scenario in summary is as following.

Let us say there is table X; added field F1, deleted as there was requirement reversal and at later point of time though the field is added in MDM; but was not available in portal.

Detailed description of the scenario is explained below.

This is an error faced in Enterprise Portal where an application is connected to SAP MDM and a field from one of the MDM tables is not available or accessible in Portal. The error message provides detail of the field and which table it is trying to access it from. It can occur in multiple scenarios where the field in the table maybe deleted but still be accessed in Portal code or the field dropped and recreated or simply due to the fact that the field may not be available in Portal due to some cache issue.

The first thing we tried is restarting our MDM server which did not resolve this issue. In addition, we then reloaded our repository with updated indices. We tried the option to Verify and Repair the repository as well. We also exported the repository schema to check for any breaks but could not find anything. Finally after much digging around, we tried an option that usually works: we restarted Portal. And our issue was finally resolved!

An explanation for this is: after any Console level changes are done in the MDM which are used in Portal, it is a mandatory process is to restart the Web Application Server. The MDM Repository schema is cached on the portal server so that it will be fast to load the standard iViews versus loading schema every time which consumes more time to load iViews. So, whenever changes are made to the MDM Repository the portal server should be restarted to clear the cache and get the new schema. Similarly in the case of the standard MDM iviews, though it may not throw the same error, for the change to be reflected a restart is necessary.