Meta JCo connection issue - cannot have 2 systems for ESS????

[Former Member]

I have a finance R/3 system and also an HR R/3 System.

I need to be able to use the FI system for the timesheet ESS screens and the HR system for the others. I have used the iView Application parameter as documented;

(sap-wd-arfc-useSys=SAP_R3_HumanResources:FIN&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:FIN)

The JCo destinations have been configured and do work ....

However the problem is that the meta data jco connection that is used first appears to be cached and is then used going forward for every subsequent screen.

Therefore if I leave the menu screens as they are by default my timesheet screen won't work because the meta connection has been opened to the HR system and therefore the meta and data connections now don't match - even though the parameter has been set as above the configuration is ignored.

I get the following error message

Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:

Accessing System DE7 is not possible because RFC Metadata was retrieved

using System DH7. Please assure you have configured the RFC Connections

properly. A Server restart may be necessary!

So if I change the menu to use the finance system then the timesheet screen will work but none of the HR screens will work. (same error with the systems reversed)

Is there any way of getting this to behave properly and make sure that the right Jco connection is used. It is very frustrating because the configuration is correct, I just need to be able to force the applications to use the the Jco destination that has been defined for the iView.

Regards

Marina

[daniel_rothmund]

Hello ,

i have read the hole thread now I have on question wew have 5 HCM systems and on one portal.

Must I copy all the ess and mss Iviews five times ? And set sap.wdarfc.useSys parameter ?

Can plz someone send me a small howto for ess/mss with more than one hcm system ?

Regards

Daniel

[daniel_rothmund]

push

[Former Member]

pop

[Former Member]

Hi,

i am just wondering whether SAP or anyone else has found a solution for the problem described by Marina Walden?

We encounter exactly the same problem. We have two different back-end systems providing Homepage Framework information. In our scenario it is possible that a user gets access to both back-end systems within one session.

We have duplicated the JCO destinations and used parameter sap-wd-arfc-useSys as described in SAP Help. In general the parameter is working. The problem that we have is, that the METADATA information seems to be cached together with the system information with the first HPF overview call.

Now when the user swiches to an HPF Overview iView that is pointing to a different system we get the following error:

"Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Accessing System E04 is not possible because RFC Metadata was retrieved using System E43. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!

"

This is exactly the problem Marina described in her first post.

Best Regards,

Dirk

[Former Member]

Does below link help...

please read the discussion also...

/people/barin.desai3/blog/2009/09/09/self-services--one-ep-multiple-ecc-systems

[Former Member]

Hi Barin,

thanks for the link but it did not really help. My feeling is that everybody is talking about a multiple client landscape. In this case i think our issue would not occur because the JCO MetaData information will be read from the exactly same system - no matter which client is called.

In our case there are really two different physical systems - one HCM system based on ERP2005 EHP4 and one BW system where we have all our HCM BW queries. We are using hompage framework for all end-user related services (ESS, MSS, BW etc.)to have one look and feel.

The problem is that when the user opens a top-level navigation entry in the portal which contains for instance the areagroup page for the ESS the JCO MetaData information is retrieved via JCO destination "SAP_R3_SelfService_Generics_MetaDataHR" from the ERP2005 HCM system. This works so far. But when the user switches to another top-level navigation entry which contains the areagroup page for our BW queries the JCO MetaData information is retrieved via JCO destination "SAP_R3_SelfService_Generics_MetaDataBW" from our BW system. This in the end causes the error because it seems that the ARFC Model of the xssutils development component is caching the information from the first call and cannot refresh it when swichting to another back-end system. if we start with the BW system it works too but if we swicht to the HR we get the error. So in the end the first call always works but once changing to another system the above mentioned error occurs.

Any idea?

Edited by: Dirk Jäckel on May 11, 2010 9:31 AM

[Former Member]

I understand your point

You need to access two different meta data systems for an application that currently accesses one metadata... i.e. homepage...

unfotunately you are using same iview which hits only on jco... hence only chaning application parameters in not going to help....

it is difficult to visualize without system access, however can I suggest you for customizing the homepage code and using another copy of same iview call on top navigation.

To simplify above

create two copies of the homepage iview one has metdata for HCM other has metadta for BIW.

Identify the link when you need to call metadata iview with biw and change the code using NWDI .

This may call for some hardcoding which can be later removed once we can makeit work.

Above is very abstract hence you may need to ask more questions. kindly feel free to respond.

[Former Member]

Hi Barin,

i have seperate page objects in the PCD containing the HPF iViews. This is the only way to pass the parameter "sap-wd-arfc-useSys" in the property "application parameters" of the iView with different values (JCO destinations for HR and JCO destinations for BW).

To explain my situation in more detail:

I have two seperate pages in the PCD containing the iView for the Homepage Framework areagroup WebDynpro - let me call them

areagroup_hr and areagroup_bw. The SAP WD4JAVA application is called "XssMenu" from development component sap.com_{pcui_gp}xssutils.

The application parameters in the iView properties are defined in the following way:

1) Areagroup for HR ESS:

-

---

sap.xss.menuargrp=/UCIHR/ES&sap.xss.menuhdr=SAPDEFAULT&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:HR&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:HR

2) Areagroup for BW:

-

---

sap.xss.menuargrp=/UCIHR/BW&sap.xss.menuhdr=SAPDEFAULT&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:BW&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:BW

In addition to that i have two seperate pages in the PCD containing the iView for the Homepage Framework area WebDynpro - let me call them area_hr and area_bw. The SAP WD4JAVA application is called "XssMenuArea" from development component sap.com_{pcui_gp}xssutils.

The application parameters in the iView properties are defined in the following way:

1) Area for HR ESS - Personnel Data:

-

---

sap.xss.menuarea=/UCIHR/ES_PA&sap.xss.menuargrp=/UCIHR/ES&sap.xss.menuhdr=SAPDEFAULT&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:HR&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:HR

2) Area for BW - Reporting:

-

---

sap.xss.menuarea=/UCIHR/BW_RP&sap.xss.menuargrp=/UCIHR/BW&sap.xss.menuhdr=SAPDEFAULT&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:BW&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:BW

The first call of the areagroup iView will always work no matter whether i call the HR ESS one or the BW one first. When jumping to the other one which queries the other system we get the mentioned error message.

[Former Member]

Hi

I understand that you already have different pages and iviews where respective jcos are mapped...

can you please explain what is the error and what are the sequence of iviews called.

sorry to ask this again but the message has too huge a trail and I want to understand the issue properly before providing further steps.

regards

barin

[Former Member]

Hi,

it doesn't matter in which sequence you call the iViews. You can start with the areagroup_hr for HR ESS. HPF generates the areagroup overview in the correct way. When you call after that the iView areagroup_bw for BW you will receive the error below. You can also do that vice versa and start with the iView areagroup_bw for BW and after that call the iView areagroup_hr for HR ESS. The problem is the switch from one back-end to the other.

The error we get is the following (pay attention to the bold part. A server restart does not help):



com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:206)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:429)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:583)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:291)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:388)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:545)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
at com.sap.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:313)
at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:282)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
at com.sap.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.java:220)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Accessing System E04 is not possible because RFC Metadata was retrieved using System E43. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.verifyClientIsConsistentWithMetadataConnection(AiiModel.java:299)

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.prepareExecute(DynamicRFCModel.java:181)

at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:170)

at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)

... 74 more

Edited by: Dirk Jäckel on May 11, 2010 4:09 PM

[rohitpathak]

Hi Dirk,

Did you get a solution for this issue.

I am also facing the same issue and would like to know how were you able to resolve this issue.

Thanks and Regards,

Rohit

[Former Member]

In the end we had to apply EA-HR enhancement pack 2 SP8 to our Finance system.

All menu configration is done in our finance system so the Generics connection points there.

We needed to create an override for the HR connection, as our timesheets are configured in our finance system.

The expenses connection is configured to point to finance, all other connections are configured to point to HR.

[Former Member]

It worked for us below sceanario......

One Portal server connecting to multiple clients in one R/3 server.

We have created as many JCo's as required and various homepage resources in each of those respective clients.

And then, used the Jco's through application parameters in each of the Java WD iviews as follows to load the respective homepage ESS overview screens.

sap.xss.menuargrp=ZSAPDEFAULTESS&sap.xss.menuhdr=SAPDEFAULT&sap-wd-arfc-useSys=SAP_R3_HumanResources:302&sap-wd-arfc-useSys=SAP_R3_HumanResources_Metadata:302&sap-wd-arfc-useSys=SAP_R3_Financials:302&sap-wd-arfc-useSys=SAP_R3_Financials_MetaData:302&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:302&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:302&sap-wd-arfc-useSys=SAP_R3_Travel:302&sap-wd-arfc-useSys=SAP_R3_Travel_MetaData:302&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenericsFIN:302&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaDataFIN:302

Hope this might be usefull.

[Former Member]

Hi, I have created new iview for Who's Who and put the below in Application Parameters:

sap-wd-arfc-useSys=SAP_R3_HumanResources:UTL&sap-wdarfc-useSys=SAP_R3_HumanResources_MetaData:UTL&sap-wd-arfc-useSys=WD_MODELDATA_DEST:UTL&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:UTL

The Home Page Framework is working fine. but when clicking on the who's who service the below error is there:

The initial exception that caused the request to fail, was: java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) ... 75 more See full exception chain for details. System Environment Client Web Dynpro Client Type HTML Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) Version null DOM version null Client Type msie7 Client Type Profile ie6 ActiveX enabled Cookies enabled Frames enabled Java Applets enabled JavaScript enabled Tables enabled VB Script enabled Server Web Dynpro Runtime Vendor: SAP, build ID: 7.0103.20081111115141.0000 (release=NW701_03_REL, buildtime=2008-12-07:13:19:14[UTC], changelist=51958, host=pwdfm246), build date: Mon Dec 20 02:32:06 CST 2010 J2EE Engine 7.01 PatchLevel 56102. Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation Operating system AIX, version: 6.1, architecture: ppc64 Session & Other Session Locale en_US Time of Failure Wed Feb 09 14:56:21 CST 2011 (Java Time: 1297284981490) Web Dynpro Code Generation Infos sap.com/pb SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tc_wddispwda No information available null sap.com/pb_api SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tc_wdcorecomp No information available null Detailed Error Information Detailed Exception Chain java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.FcWiwBusinessLogicComp.onInit(FcWiwBusinessLogicComp.java:217) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicComp.onInit(InternalFcWiwBusinessLogicComp.java:414) at com.sap.xss.hr.wiw.FcWiwBusinessLogicCompInterface.onInit(FcWiwBusinessLogicCompInterface.java:115) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface.onInit(InternalFcWiwBusinessLogicCompInterface.java:298) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface$External.onInit(InternalFcWiwBusinessLogicCompInterface.java:358) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.selection.VcWiwSelectionComp.onInit(VcWiwSelectionComp.java:212) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionComp.onInit(InternalVcWiwSelectionComp.java:206) at com.sap.xss.hr.wiw.selection.VcWiwSelectionCompInterface.onInit(VcWiwSelectionCompInterface.java:162) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface.onInit(InternalVcWiwSelectionCompInterface.java:144) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface$External.onInit(InternalVcWiwSelectionCompInterface.java:220) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438) at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196) at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289) at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

[siddharthrajora]

Unfortunately the standard rules for web-dynpro iViews do not apply to ESS iviews - there is no system parameter to change.

ESS iviews are not WD iview?? Please check it I can see the

application parameters for my iview!

[Former Member]

I agree - the application parameter exists, and this has been configured to override the standard behavior (see my first post for the syntax used)

The "System" parameter in an iview definition does not however exist, therefore it is not possible for me to simply change the "system" parameter to use a different JCo connection.

Edited by: Marina Walden on Aug 14, 2008 12:05 PM

[Former Member]

Marina,

I was finally able to figure out the solution to the Problem .

SAP has two connection for

SAP_R3_HumanResources_Metadata

SAP_R3_HumanResources_MetaData

Pay attention to the right spelling! I mean the second one is the right one.

JCO 'SAP_R3_HumanResources_MetaData' instead of 'SAP_R3_HumanResources_Metadata'

Create SAP_R3_HumanResources_MetaDataR3Q and remove SAP_R3_HumanResources_MetadataR3Q and SAP_R3_HumanResources_Metadata.

Once the Jcos are created successfully , create URL Iview by providing the application URL for Time Entry and pass both the Parameter to it. It will be now connect to the other system R3Q rather then HRQ.

Let me know, if you still face any problem.

[Former Member]

Let me know, if you clear the hurdle of Metadata connection cashing and if yes , what approach need to be taken.

Thanks

[Former Member]

SJ,

Does the solution you suggest also require adding the Application parameter 'sap-wd-arfc-useSys=app_name:sys_name' to the various IViews of ESS?

[Former Member]

Unfortunately our problem seems to be more complex - we are already using the correct spelling for the connections however the problem still exists.

We have a long standing message with SAP on this issue, if we ever get a resolution I will update this message to let you know.

[Former Member]

Is this resolved?

If I understand you correctly you want CATS app to point to FIN box and remaining apps to different r/3 box. If that is the case then open the cat DC and change the JCO reference only for cat app. (Create new JCOs first for cats to point to FIN)

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3083] [original link is broken] [original link is broken] [original link is broken];

Vishal

[Former Member]

If possible I would prefer to not make modifications to the cats application - we have a policy of not making modifications unless absolutely necessary.

SAP are still looking into the issue, however it has to be said that they are having some difficulty understanding the problem. I will of course update this thread if we have any success.

[Former Member]

Hello together!

We have a similar problem with multiple HR Systems. Generally the parameter sap-wd-arfc-useSys is working. We have the following string into the application parameter of the ESS/MSS iviews.

sap-wd-arfc-useSys=SAP_R3_HumanResources:001&sap-wdarfc-useSys=SAP_R3_HumanResources_MetaData:001

As mentioned in the previous statements we copied the existing JCO's and directed them to the right system. That works.

But:

What is not working is the following:

&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:001&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:001

The ESS Homepagecustomizing will be always provided by the system which is defined via SAP_R3_SelfServiceGenerics and SAP_R3_SelfServiceGenerics_MetaData. This means, that all users must also exist on this system - otherwise you will get a Java-Dump. I checked this also via an RFC-Trace.

Any ideas how to avoid this - as said - the application parameter sap-wd-arfc-useSys for the Homepagecustomizing is not working.

Kind Regards,

Harald

[Former Member]

Hi Harold,

It seems that there is no way around the users existing in both systems.

The way that these connections work is very clunky - hardly an elegant solution.

In the end we have got our Timesheet & expenses applications using connections to our Finance R/3 system. The Timesheet required us to create a connection HumanResourceConnection:FIN as well as having the standard HR connection.

Our generics connection points directly to our finance system - All of our menu configuration is in that system.

I hope that this makes sense?

regards

Marina

[siddharthrajora]

Accessing multiple Backends in WebDynpro:

How it can be done?

1) Define different JCO Destinations

The logical System names have to be defined in the Web Dynpro Content

Administrator.

Different clients or completely different Systems can be accessed

given that the function modules called exist in those systems

The logical System to be used can be passed to the Web Dynpro

Application by using a URL Parameter

The URL Parameter can be easily maintained in the iView Property when

using the portal.

The standard way to handle this is to create copies (via delta-link) of

all the business package iviews and change the 'System' property in the

newly created iviews to point to the correct system Alias. From the

portal point of view this is all that is required in order to point an

view to a different system

Refer these links for further information:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.

docs/library/webas/webdynpro/How%20to%20Use%20the%20Web%20Dynpro%20Conte

nt%20Administrator.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/f4/

651741f163f023e10000000a155106/frameset.htm

Let me know if this helps

[Former Member]

Siddharth

Unfortunately the standard rules for web-dynpro iViews do not apply to ESS iviews - there is no system parameter to change.

This is why the application parameter has to be used to override the standard JCO connection that has been "hard coded" into the application by SAP.

Unfortunately the issue seems to arrive because the overview menu screens are not handling the connections correctly, it seems to hold onto the metadata connection that has been established by the menu screen and continue to use this in further applications.

Has anyone else experienced a problem where by the ESS applications are using the incorrect metadata connection where the configuration has been completed correctly (ie, the application parameter has been set and the JCo destinations have been maintained)

regards

marina

[Former Member]

Has anyone seen this problem before ?

[Former Member]

We are also having the same requirement and experiencing the same problem. Please let me know, if you find the solution to it.

Thanks in advance.