ESS/MSS : SP Stack mismatch issue

Hi all,
I need help on finding out exact SP level of ESS/MSS for our landscape. This EHP stack is really confusing me to nail down exact business package requirement.
Below are the deatils about ERP6.0 System:
Component     Release     SP-Level
SAP_ABA     701              7
SAP_BASIS     701              7
SAP_APPL     600             18
SAP_HR          604             26
EA-HR          604             26
And basis team has uploaded below versioned ESS/MSS BP:
SAP EP NW7.0 EHP1 SP3
BP_ERP5ESS     1.41 SP7
BP_ERP5MSS     1.41 SP7
SAP_ESS          603 SP7
SAP_MSS     600 SP7
SAPPCUI_GP     603 SP7
I have already visited the wiki page available at https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES. But still not able to make out needed version. With above installation, we are facing error of model incompatibility in Code of conduct application. I am sure its because of SP stack mismatch.
I would appreciate, if you could help me by suggesting BP version for above mentioned ERP system.
Regards,
Amol

Hi Harika,
I guess they have installed ERP stack 18, as I could see vesrion for SAP_APPL 600 is "18". Also they have installed SAP_ESS 603 SP7 , SAP_MSS 600 SP7, SAPPCUI_GP 603 SP7 . And not SP6 as you mentioned for ESS,PCUI_GP components.
As per SAP Note 1297231 - SAP ERP Enhan. Pk. 4 SP Stacks - Release & Information Note, SP Equivalence Levels are
EhP4 SPS08 === EhP3 SPS07 === EhP2 SPS08 === SAP ERP 6.0 SPS18.
So I believe SP7 of ESS, PCUI_GP XSS components should work.
But in the same note it is mentioned that, we need to apply SAP NetWeaver 7.01 SP Stack 07 (07/2010) for customers who have their non- ABAP NetWeaver instances on SAP NW 7.01.
We are currently on SAP NetWeaver 7.01 SP Stack 03.
The error I am getting in Code of Conduct application under ESS-> Corporate Information is :
java.lang.ClassCastException: com.sap.pcui_gp.isr.isrprocessevent.model.Bapiret1 incompatible with com.sap.pcui_gp.isr.isrprocessevent.model.Bapiret2.
Will SAP NW SP stack make difference to throw above kind of error.
Regards,
Amol.

Similar Messages

ESS/MSS EHP5 role customization issue

Hi,
We have implemented EHP5 roles on Enterprise Portal 7.0, other version details are: EHP6 and SP9.
Following issues are coming:
1. Our portal is having customized theme. However, the lpd_cust ESS/MSS roles created when rendered Portal is taking Standard blue theme, how can we get our custom theme when lpd_cust roles are launched on Portal.
2. The link text is getting vertically splitted in service map area. Eg. If we have "User Manual" as link text of a application created under lpd_cust folder ESS->User Manual, the text is getting splitted. How can we adjust size of this text?
Please check attachment for both issues.
Looking forward for help.
Regards,
Ashvini.

Hello Luke,
Yes, I mean talent management. The appraisal forms are in the flexible template in SAP Portal.
Thanks in advance for your help
Best regards
Joao

Dropdown buttons not working in Portal (UWL, ESS & MSS)

Hi,
I am having this problem in the portal. When a user clicks on any dropdown button in Webdynpro applications such as UWL, ESS & MSS in the portal, an error message 'Error: Access is Denied' appears in the left bottom corner of Internet Explorer 6.0, with a yellow triangle sign. The dropdown buttons then appears disabled and nothing happens when they are selected. I will appreciate if you can provide suggestions as to why this is happening and how to solve it.
Thanks
John

Hi John
Please ensure you have the latest patch for your JTECHS and JTECHF SP level
If this does not resolve the issue please ensure you have the correct Netweaver stack (including JTECHS and JTECHF) for you ESS/MSS SP levels - see the following wiki for help identifying which Netweaver SP levels are recommended for each ESS/MSS SP level
https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/marcio+leoni
--->HOW TO GET RID OF SP STACK MISMATCH ISSUES
If the issue continues please ensure you browser client and version is suitable for this version of ESS/MSS
via the PAM www.service.sap.com/swdc
Best wishes
Stuart

Impact of ESS/MSS Business Packages

We are implementing the SAP Portal and therefore will be downloading and installing the ESS/MSS Business Packages. I would appreciate if anyone could tell me if there is any impact on any SAP HR existing functionalities as a result of this. Do we need to be aware of any issues that you may have encountered in your implementation.
Thanks
Pascal

Hi Pascal
I don't think any problem with existing functionality. but you need to make sure you download and install the correct version and SP stack.
Refer to [HOW TO GET RID OF SP STACK MISMATCH ISSUES |http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES]
Hope it will helps
Best Regards
Arun Jaiswal

ESS/MSS config

Dear Experts,
Can anyone send me ESS/MSS config and support issues pdf ?
Regards
RS

Hi,
Check the below links
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3467
https://www.sdn.sap.com/irj/sdn/developerareas/contentportfolio
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAESS/ESSIAC.pdf
http://www.passhe.edu/content/?/administration/HR/SystemHR/HRS/ESS
Also some more
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1841
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
Hope they are more than enough
Raghu

Issue while accessing two web-dynpro application, ESS/MSS and Payroll

Hi All,
We are facing one Critical Server Issue in our systems. Following is the scenerio:-
Our Portal system was having one Application known as German Payroll application. Before last two week one more application of ESS/MSS i.e. Time Management has been deployed to our system.
Now the user has two application with two different roles in the portal.
When user try to navigate from Time Management Application to German Payroll application or German Payroll Application to Time Management Application then they are facing Critical Server Error issue.
But once the user try to refresh using CTRL+F5 then the problem got resolved.
========================================================================
German Payroll applications back end server details:P95.
Time Management Application back end server details: P23
Steps to reproduce the issue:
1-login to portalgot to Employee self service tab-wait for 3-5mins
& than navigate to german payroll applications----& faced crtical
server errors:
Log from deafult trace:-
=======================================================
1.#0021280FECEE0028000000A400005A4B0004A2FA644F345C#1305096215265#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdyn
pro.progmodel.generation.DelegatingComponent#km048893#2758##n/a##fa2a61757b9911e08e660021280fecee#SAPEngine_Application_Thread[impl:3]
_9##0#0#Fatal#1#/Applications/Xss#
Java###null
[EXCEPTION]
#1#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:205)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit
(InternalModelHandler.java:428)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber
(FcXssMenu.java:570)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit
(FcXssMenu.java:292)
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)
System 'P95' is not possible because RFC Metadata was retrieved using
System 'P23'. Please assure you have configured the RFC Connections
properly. A Server restart may
be necessary!#
==============================================================
here is the catch....When user is trying to navigate from ESS tab(using
custom jcos for Backend system P23) to German payroll(backend system
P95) after 3 mins ---getting crtical error...Still its using the
data/metadat jcos connection information of ESS applications from
cache...that you can see in default trace.
PS: Standards Jcos are configured for P23 systems:
====================================================
SAP_R3_HumanResources----created with P23
SAP_R3_HumanResources_MetaData----been created with P23
SAP_R3_SelfServiceGenerics----been created with P23
SAP_R3_SelfServiceGenerics_MetaData----been created with P23
=====================================================
P95----Germman payroll
P23---ESS/MSS
Name of Cutsomn Jcos created for bakcend P95 i.e. german payroll
A-P95
=======================================================
SAP_R3_HumanResources:D95
SAP_R3_HumanResources_MetaData:D95
SAP_R3_SelfServiceGenerics:D95
SAP_R3_SelfServiceGenerics_MetaData:D95 configured with sap-wd-arfc-
useSys.
Name of cutom jcos created for backend ESS/MSS P23
B-P23
=========================================================
SAP_R3_HumanResources_MetaData:X23
SAP_R3_HumanResources:X23
SAP_R3_SelfServiceGenerics:X23
SAP_R3_SelfServiceGenerics_MetaData:X23 configured with sap-wd-arfc-
useSys.
========================================================
Jcos parameter of P23 backend:
JCo Pool Configuration
Maximum Pool Size: 50
Maximum Connections: 100
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
Jcos parameter of P95 backend:
JCo Pool Configuration :
Maximum Pool Size: 5
Maximum Connections: 10
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
===================================================================
After more analyzing the situation we found that one web dynrpo component i.e. pcui_gp~xssutils is common to both the application and it is configured to standard JCO i.e.
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
My thinking is that this component is giving us the problem.
Please provide your comments and solution to rectify this issue.
Also, let me know in case you need more information.
Thanks in Advance
Kuldeep Verma

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

ESS/MSS Leave Request Issue

Hello All Experts
We have implemented ESS/MSS. Everything is working fine except the Leave Request approval. The approval request comes to the approver's inbox.When we try to open the approval request, the webdynpro application is getting but there is no data in the same. I mean the webdynpro application which is launched is blank.
Could anyone please try to help me how to make this webdynpro application up and running ?
We are using EP 7.0 with ECC 5.0
TIA,
Vivek

Hi Chuckie/Ton Groot,
As mentioned in post by Ton Groot,
I navigated to System Administration --> System Configuration --> Detailed Navigation --> Universal Worklist Workflow à Universal Worklist - Administration
I get a list of
Universal Worklist Systems
System Alias       Connector Type                       Action            Activate
AdHocSystem |   AdHocWorkflowConnector |                        | Deactivate
SAP_ITS_XSS |   WebFlowConnector           |   Re-Register    | Deactivate
ActionInbox     |   ActionInboxConnector        |                        | Deactivate
When I click on Re-Register button under Action, I get the following message
Item type registration was successful for the following systems:
- SAP_ITS_XSS (WebFlowConnector)
I have also cleared the cache by navigating to Cache Administration Page
Still the issue remains.
TIA,
Vivek

Is it possible to run BP ESS/ MSS 60.x on J2EE stack 7.0 (EP 7)?

Hi there,
is it possible to run BP ESS & MSS version 60.x on a J2EE server stack 7.0 (EP7.0) ?
In the contentportfolio area of SDN ([https://www.sdn.sap.com/irj/sdn/contentportfolio]) it is stated, that BP MSS 60.1.2 runs on
---> iView Runtime Technology:
Java / WebDynpro (WAS 6.40 and higher)
(Link: [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/70649942-a46d-2910-be9b-88db98b484f5 [original link is broken]])
Same for BP ESS 60.2.
([https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/d0dfa6ad-9b6d-2910-3d9a-f278ecc80c60 [original link is broken]])
What does "and higher" mean? Do you see any problems ?
I have studied a lot of notes already, but couldn't find a clear statement on this.
Many thanks and kind regards,
Jenny

From what I have "heard", it is possible. I say that because right now, I am on ECC6/EP7 at my current client. But my previous client was on ECC5/EP6 but are now moving to EP7...and have not had problems yet. I would suggest giving it a go in a sandbox system and checking it out...same as you would do for any upgrade. The fallback is that you can upgrade your portal to EP7 but then run a separate server for your XSS apps from ECC5 (that's kinda the point of the WAS anyways....you can run your apps on separate servers than your "main" server). Your JCO connections would point to the "middle" server and those apps would then "talk" back to your ECC5 box. Anyways, I "think" just having them on the EP7 box would work.

Issue with ESS/MSS Business package 1.41

Hi All
I had an issue with ESS/MSS recently we deployed Business package 1.41 it contains HCM Forms and Process also,
and we assigned the standard Manager-self-service role & Employee-self-service-role to test user but when the user is trying to access the standard application he is getting Portal runtime error.
 Is there any configuration is need from HRFunctional side and Basis side
if any body have an idea please let me know ASAP.
For every MSS standard applications like :work overview ,Recruiting,Team,Talent Management,Budjet,Projects,Planning ,Organization, leave
I am getting like below error.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:17_13/04/11_0031_116801250
Refer to the log file for details about this exception.
Thanks
Renu.

Hi All
 Here I am giving logs detail I got two logs so giving both logs , can anybody help on this issue , if any configuration need please suggest.
Full Message Text
03:19_13/04/11_0045_116801250
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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)
Next One
Full Message Text
Exception ID:03:19_13/04/11_0045_116801250
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.14.bp_folder/com.sap.pct.erp.mss.14.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.workoverview/com.sap.pct.erp.common.key_figure_monitor
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : P00000531
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more

IMP: Read this WIKI and search for ESS MSS issues before posting any thread

Here is the link to the new WIKI topic area ESS MSS
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HCM+ESS
and
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HCM+MSS
Feel free to add FAQs, Guidelines, Links and everything of interest for Human Capital Management into this WIKI. With your help this will become a valuable resource for the HCM community for ESS MSS
I would appreciate if you search in the WIKI and earlier threads, before posting a new thread
For Beginners, Please refer the ESS/MSS customisation Guide here
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c4dc?QuickLink=index&overridelayout=true
Edited by: Siddharth Rajora on Dec 19, 2011 8:35 PM
Edited by: Siddharth Rajora on Dec 19, 2011 8:36 PM

teshlachris,
iTunes, like other applications, will sometimes have issues trying to install from a different admin user than the one used to first install it.
Did your son install iTunes with a different account? If so, your previous post did not include the fact your son had previously installed iTunes, or I would have suggested trying the install while logged in under his account.
Hope this helps,
Nathan C.

ESS/MSS assert violation dump

Hi everyone,
When i try to access the personel data in the general information tab in ESS/MSS portal.
I am facing the below dump.I have searched in all sites but am not clear about this dump.please help me out.
Team...and then General Information
Unexpected exception when calling RFC from Profile-Application 'General Data'
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE.
Thanks,
Shalini
Edited by: salini bhimireddy on Jan 5, 2011 11:24 AM

the issue is either due to mismatch of use cases with time contraints in table below
1) The time constraints in T591A have been modified and the
   use case and time constraint combination is not consistent
   The recommended use case and time constraint combinations are
   TC1 can use A1,A4,B1,B4
   TC2 can use A1,A2,A3,A4,A5,B1,B2,B4,B5
   TC3 can use A6,B3
   It is also not recommend to modify time constraints as not
   only may it make the use case combination inconsistent but it
   may cause data inconsistencies

Need help on ESS/MSS BP's impact due to Upgrade from ECC 5 to ECC 6 EHP5

Hi,
We are upgrading from ECC 5.0 to ECC 6.0 EHP5 and EP 6.0 SP23 to EP 7.0 EHP2 {7.02}.
Right now the ESS/MSS BP's used in the Existing system (ECC 5.0 and EP 6.0) are given below.
sap.com BP_ERP4ESS 60.2 SP0 (1000.60.2.0.0.20050419020715)
sap.com BP_ERP4MSS 60.1 SP1 (1000.60.1.1.0.20080618080447)
i.e.
sap.com SAP_ESS 100 SP16 (1000.100.0.16.0.20090316001300)
sap.com SAP_MSS 100 SP20 (1000.100.0.20.0.20081013052238)
sap.com SAPPCUI_GP 100 SP20 (1000.100.0.20.0.20081013052239)
We want to run the same BP's in the New environment (ECC 6.0 EHP5 and EP 7.0 EHP2 {7.02}).
If anyone has idea on this, Please let me know is it possible or any modifications to be done ?
Please send me some documentation to get clear idea.
Thanks & Regards,
Ashok M.
Edited by: Ashok Kumar Munugoti on Oct 20, 2011 8:22 AM

Well i would recommend to use lates BP cause lot has changed from ECC 500 to ECC 600
and they wont be supported and you ll definately get support mismatch here
read here for compatibilty issues
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES

Help about ESS/MSS - Deploy error and landscape question

Hi.
I read a lot of post about this topic, but I continue something confuse about them.
I want to configure ESS and MSS.
My landscape is:
- J2EE 7.0 with Portal 7.0 (2004s) in a server A.
- ECC 5.0 ( with HR component SP05) in a server B.
Server B, has only stack Abap.
Server A is the latest version of Netweaver today. (stack j2ee and stack abap, BI, XI, Portal, etc)
I download and deploy in server A (J2EE 7.0), this components:
- BP ESS for erp2004
- BP MSS for erp2004
When I deploy the ESS BP, the deployment break raising this kind of error with the most of components, for example:

===========================================================================
Deployment started Tue Apr 10 12:01:57 ART 2007
===========================================================================
Starting Deployment of ess/au/addr
Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr.. Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of ess/au/addr finished with Error (Duration 5187 ms)
Starting Deployment of SAP_ESS
Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0' : aborted
Please, look at error logs above for more information!
Deployment of SAP_ESS finished with Error (Duration 4781 ms)

Obviously, for this reason the most of iviews raise errors. A few of these works ok.
I assign role, and others configuration steps, this part I thinks that is OK
I configured the Jco, the role in Portal, the profile in ERP for ESS, etc.
My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
Is necesary install J2ee stack in my server B ? or not?
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Why when I deploy have this problem and the most of components cant deploy it?
For my landscape, which is the recommended setup ?
thanks in advance.!
Leandro.

My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
You can use Portal 7.0 against ECC 5.0
Is necesary install J2ee stack in my server B ? or not?
You don't need to install J2EE stack on ECC system
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Deploy XSS on Portal server not on ECC.
Why when I deploy have this problem and the most of components cant deploy it?
There won't be any issue. Go for ERP 2005
For my landscape, which is the recommended setup ?
As per the landscape mentioned by you, I will suggest go for ERP 2005 & XSS 600.
If you have further queries, mail me at [email protected]

Error Deploying ESS/MSS ERP2005 WebDynpro Components for SP7

Hi,
I have been in process of trying to Patch up the J2EE stack in an attempt to turn on SAP Delivered Solution for ESS/MSS.
We are on EP7 with ECC6 Backend.
What I have done so far::
1. Updated J2EE with Netweaver SP stack 11.
2. Imported the business package for ESS/MSS into EP. I can confirm that the content is now available on PCD.
3. Then i tried to upload the WebDynpro Components for ESS/MSS. Files are PCUI_GP, ESS and MSS. they all have a named reference to 600 SP7. These are the ones available to download for self-services from mySAPERP components on service market place.
This step is now falling over. Deployment of these components fail when its trying to deploy the application component. I must add that once we loaded the Business packages for ESS/MSS (step 2), i then checked the delivered content and created a delta link to the AU/Address iView into my own content folder. I am not sure if this has anything to do with the Failure of deployment but this is the only thing that i did in between steps 2 and step 3.
I didn't think that it would have caused any issue as this was an iview while the component its trying to deploy is a webdynpro application, but i am not sure now.
Please see the trace below.
Message : Failed to deploy application 'sap.com/essauaddr' for deployment state listener 'com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook'.
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\.\temp\webdynpro\public\sap.com\essauaddr\webdynpro\Applications\com.sap.xss.hr.per.au.address.Per_Address_AU\Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Severity : Error
Category : /System/UserInterface
Location : com.sap.engine.services.webdynpro.WebDynproContainer
Application :
Thread : SAPEngine_Application_Thread[impl:3]_8
Datasource : 1173687328333:C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 001321C841EF0056000000030000110800042B7618DD7104
Source Name : com.sap.engine.services.webdynpro.WebDynproContainer
Argument Objs : sap.com/essauaddr,com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook,com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\.\temp\webdynpro\public\sap.com\essauaddr\webdynpro\Applications\com.sap.xss.hr.per.au.address.Per_Address_AU\Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Arguments : sap.com/essauaddr,com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook,com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\.\temp\webdynpro\public\sap.com\essauaddr\webdynpro\Applications\com.sap.xss.hr.per.au.address.Per_Address_AU\Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Dsr Component :
Dsr Transaction : 0b312900d06f11db9da1001321c841ef
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/UserInterface
Resource Bundlename :
Session : 4
Source : com.sap.engine.services.webdynpro.WebDynproContainer
ThreadObject : SAPEngine_Application_Thread[impl:3]_8
Transaction :
User : J2EE_ADMIN
Any thoughts and ideas would be greatly appreciated.

Hi Friends,
I got the same problem but not on ESS/MSS component. But the exception was exactly the same. The solution what i found is
1. Find the exception in the Default trace. By searching for DC Name.
2. Here you should find the one in which its mentioned below error
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file '/usr/sap/EPD/JC35/j2ee/cluster/server0/./temp/webdynpro/public/burton.com/portal~passwordchange/webdynpro/Components/com.burton.webshop.b2b.myprofile.EditPassword/EditPassword.xml' into the database. Reason: Development Object 'local/wdMyProfile' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
3. Now go to the visual administrator -> deploy -> webdynpro and undeploy the local webdynpro with which the current DC is conflicting. (You should decide whehter you can undeploy or not)
4. Now try activate the activity or Deploy the DC you shouldnt get the problem.
Actually i got this problem when i created a WebDynpro DC by importing the local webdynpro project. So, when i try to activate the activity of DC created then its not getting deployed. When i check the logs, i had same exceptions as you ppl got. So after going thru default trace then i figured out that the local webdynpro is the reason for this conflicting. Then i undeployed that webynpro.
Hope this may be useful for you and others...
Thanks,
Raags

Customised Error Message for ESS-MSS Applications

Hello All,
Currently, if there are any errors in the ESS/MSS transactions, we get the 503 error with lot of irrelevant data to the users. We have a basic html page which says, "There is a issue-Please contact XXXX".
Is there a way to replace the standard error message with this html page ?
PS: I am not talkign about the "Dispatcher Running" or "Application Stopped" messages, Please do not point me again to SAP Help website which doesn't answer my query. THIS IS ABOUT REPLACING THE STANDARD ERROR MESSAGES FOR ESS/MSS APPLICATIONS.
Any help is much appreciated.
We are on EP 7.01 SP3 (ESS 1.41)
-Raj

Hi Raj
Let me clarify the difference between ESS and MSS errors and JAVA stack errors
A "503 Service not available" is not an ESS or MSS error - this is the thrown by the stack (possibly while navigating
in ESS or MSS)
The only information I have available in the case of java stack errors is to follow
http://help.sap.com/saphelp_nw70/helpdata/en/9a/e74d426332bd30e10000000a155106/frameset.htm
Whcih indicates how to customize stack errors like 404 or 500
Lastly you can also decide to hide the stack trace as per KBA 1596212
To modify an ESS or MSS message this may require modification to front and back-end HCM application - usually
ESS gets error information based on back-end errors example "fill in all required fields"
Hope this helps

ESS/MSS : SP Stack mismatch issue

Similar Messages

Maybe you are looking for