Error when connecting to MDM Repository in SRM MDM UI App in portal

[Former Member]

Hi All,

We have a Nw 7.31 SP5 Portal system connected to SRM and MDM.

We are trying to check SRM MDM UI App. the backend MDM repository is up and running and also the user credentails are working fine in MDM.

The App UI is able to connect to the MDM server without the password and retries the respository list.

Once we give the user details for a repository and click login we get "unable to invoke method" error.

Please find below the details.

Can you please suggest a solution.

I have already redeployed the SRM MDM Catalog, MDM JAVA API and MDM COnnector and restarted system.

Still i am getting the same error.

Best Regards,

Raghavan

Steps to recreate:

1. Login to url:https://<hostname>:<port>/webdynpro/dispatcher/sap.com/tc~mdm~srmcat~uisearch/MDM_SRM_UI_App

2. Input server name of MDM System: v31cs01.sce.com

3. Press Connect

4.Choose the appropriate repository.

5. Provide the user credentials:

6. Press Connect. You will get an error.

java.lang.RuntimeException: java.lang.NullPointerException: while trying to invoke the method com.sap.srm.mdm.configurations.sustainabilityOption.isShowSustainabilityAttribute() of an object loaded from local variable 'sustainableOptionConf'
  at com.sap.mdm.srmcat.uisearch.master.Master.login(Master.java:1386)
  at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMaster.login(InternalMaster.java:1177)
  at com.sap.mdm.srmcat.uisearch.master.LoginView.onActionlogin(LoginView.java:457)
  at com.sap.mdm.srmcat.uisearch.master.wdp.InternalLoginView.wdInvokeEventHandler(InternalLoginView.java:202)
  at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
  at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
  at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
  at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
  at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
  at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
  at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
  at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
  at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
  at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
  at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:367)
  at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:490)
  at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:63)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
  at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
  at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
  at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
  at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
  at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.NullPointerException: while trying to invoke the method com.sap.srm.mdm.configurations.sustainabilityOption.isShowSustainabilityAttribute() of an object loaded from local variable 'sustainableOptionConf'
  at com.sap.mdm.srmcat.uisearch.master.CustomConfiguration.loadConfiguration(CustomConfiguration.java:313)
  at com.sap.mdm.srmcat.uisearch.master.wdp.InternalCustomConfiguration.loadConfiguration(InternalCustomConfiguration.java:412)
  at com.sap.mdm.srmcat.uisearch.master.Master.login(Master.java:1237)
  ... 68 more

[Former Member]

Hi,

We had this problem, and have now resolved it.

The reason was that we had upgraded the system from 7.01 to 7.02, and old content remained in the system. We had repositories on the upgraded MDM server, with the same name as we had had on the old one. Therefore, when accessing these repositories in the UI Config, the system retrieved the EhP01 UI.

What we did, was to

- Delete the relevant repositories from the MDM Server.

- Delete old config content in DB entries from MDM_SRM_CATCONFIG table.

- Unarchive new MDM repository

That should do the trick. At least it did for us.

Also, we had a problem with not having the new activating switches showing. The resolution was the same. This was the answer from a SAP resource:

For whatever reason you first need to erase the old EhP01 switch entries in the J2ee DB, then (re-)deploy the EhP02 package on the J2ee and then the new additional EhP02 switches will show up.

Unfortunately, I believe erasing the old DB entry for EhP01 is not really mentioned anywhere.

After we did this, all four switches was visible, two for SRM_CATALOG_1, and two for SRM_CATALOG_2.

KR,

Thomas

[Former Member]

Hi!

Did you find an answer to your problem? We have the same issue after following the steps detailed in the OSS Note 1753440 - Activating SRM-MDM Catalog Enhancements and importing the configuration.xml file attached to this note.

thanks,

eb

[anja_engelhardt2]

moved to SAP NetWeaver Master Data Management by moderator