EHP with ESS/MSS

Hello everyone,
We have a ERP 6.0 (based on NetWeaver 7.0) and a SAP Portal 7.0 with ESS/MSS. We now need to update the ERP to EHP6 or EHP7, my question is regarding SAP Portal, do we need to upgrade the Portal to 7.3x or 7.4? Where can I validate this dependencies?
Best regards,
JAM

Hi JA,
The line means you can use existing SAP Portal and you can update you SPS level to latest version in-order to support the ECC6 with EHP7 rather than upgrading Portal version to NW7.40.
"you can do a SP update in your portal to get a equivalence level and get the newer version of SAP ECC backend supported"
And the equivalence of SP level is as below which you can find for ECC version:-
EhP7 SPS 06 -- EhP6 on Hana SPS08 -- EhP6 SPS13 -- EhP5 SPS13 -- EhP4 SPS16 -- EhP3 SPS15 -- EhP2 SPS16 -- SAP ERP 6.0 SPS26
For Netweaver:-
Installed Release             Target Release
SAP NetWeaver 6.20       SAP NetWeaver 7.3
SPS 70 (or lower)           SPS 05 (or higher)
SPS 71                          SPS 07
SPS 72                          SPS 08
SPS 73                           SPS 09
Installed Release               Target Release
SAP NetWeaver 2004        SAP NetWeaver 7.3
SPS 25 (or lower)             SPS 01 (or higher)
SPS 26                            SPS 02
SPS 27                            SPS 03
SPS 28                            SPS 04
SPS 29                            SPS 07
SPS 30                            SPS 08
SPS 31                            SPS 09
Installed Release               Target Release
SAP NetWeaver 7.0           SAP NetWeaver 7.3
SPS 22 (or lower)              SPS 01 (or higher)
SPS 23                             SPS 02
SPS 24                               SPS 03
SPS 25                             SPS 04
SPS 26                             SPS 07
SPS 27                             SPS 08
SPS 28                             SPS 09
SPS 29                             SPS 10
SPS 30                             SPS 11
SPS 31                             SPS 12
Installed Release               Target Release
SAP EHP 1 NetWeaver 7.0 SAP NetWeaver 7.3
SPS 07 (or lower)             SPS 01 (or higher)
SPS 08                            SPS 02
SPS 09                            SPS 03
SPS 10                            SPS 04
SPS 11                            SPS 07
SPS 12                            SPS 08
SPS 13                            SPS 09
SPS 14                            SPS 10
SPS 15                            SPS 11
SPS 16                            SPS 12
Installed Release Target Release
SAP EHP 2 NetWeaver 7.0 SAP NetWeaver 7.3
SPS 06 (or lower)             SPS 02 (or higher)
SPS 07                            SPS 03
SPS 08                            SPS 03
SPS 09                            SPS 04
SPS 10                            SPS 07
SPS 11                            SPS 07
SPS 12                            SPS 08
SPS 13                            SPS 09
SPS 14                            SPS 10
SPS 15                            SPS 11
SPS 16                            SPS 12
Installed Release              Target Release
SAP NetWeaver 7.1          SAP NetWeaver 7.3
SPS 10 (or lower)             SPS 01 (or higher)
SPS 11                            SPS 02
SPS 12                            SPS 03
SPS 13                            SPS 05
SPS 14                            SPS 07
SPS 15                            SPS 08
SPS 16                            SPS 09
SPS 17                            SPS 10
SPS 18                            SPS 11
Installed Release              Target Release
SAP EHP 1 NetWeaver 7.1 SAP NetWeaver 7.3
SPS 05 (or lower)             SPS 01 (or higher)
SPS 06                            SPS 02
SPS 07                            SPS 03
SPS 08                            SPS 05
SPS 09                            SPS 07
SPS 10                            SPS 08
SPS 11                            SPS 09
SPS 12                            SPS 10
SPS 13                            SPS 11
Installed Release Target Release
SAP NetWeaver 7.2          SAP NetWeaver 7.3
SPS 03 (or lower)             SPS 01 (or higher)
SPS 04                            SPS 02
SPS 05                            SPS 03
SPS 06                            SPS 05
SPS 07                            SPS 07
SPS 08                            SPS 08
SPS 09                            SPS 09
Also Do check the 1532805 - Add-On Compatibility of SAP NetWeaver 7.3 note as well so that you can have a add-ons checks too.
Regards,
Ram

Similar Messages

With EHP-6,ESS/MSS,E-REC can we implement Talent Mgmt & succession Mgt or still NAKISA required

Hi All,
In scope E- Recruitment & System is going to be on EHP-6 with ESS/MSS, i went through Mr.Luke Marsons some ofthreads which talks about if system is at EHP-4 then STVN(Nakisa),Netviewre is required.
Now i am confused my question after all this reading & exploration is , As E-Rec,ESS/MSS,EHP-6 is gonna be in placestill does the client has to go for NAKISA & buy those additional 3rd part lisences Or is this task of Talent Mgmt & Succesion Plan acievable in Standard SAP EHP-6.
Please guide as i in mid of somthing & need ur urgent assistance.
Thanks.

Hi Experts,
Can i get any updates on this issue.

EP7.1 compatibility with ESS/MSS 1.0

Does anyone know if EP7.1 is compatible with ESS/MSS 1.0?
Thanks,
Rose

check
http://sdn.sap.com/irj/portal/contentportfolio
service.sap.com/ess
service.sap.com/mss
reward points if helpful

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

Help with ESS MSS documentation

Dear All,
please help me with the documentation on ESS MSS.
Thanks in advance
Regards
Minal

Hi,
Check this links:
http://help.sap.com/saphelp_erp2005/helpdata/en/f6/263359f8c14ef98384ae7a2becd156/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm
Regards,
NR

EP 7 with ESS/MSS errors

Hi Guys
We are using EP 7 sp13 with ECC 6 (sp13 ) we currently have ESS/MSS sp11 on it.
All the ESS links work except EMPLOYEE SEARCH> CHANGE OWN DATA. it gives me the following error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.xss.hr.cod.model.CodModel' in scope APPLICATION_SCOPE with instanceId 'null'
    at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:102)
    at com.sap.xss.hr.cod.FcCodBusinessLogicComp.callRFCDequeuePernr(FcCodBusinessLogicComp.java:396)
    at com.sap.xss.hr.cod.FcCodBusinessLogicComp.onCleanup(FcCodBusinessLogicComp.java:259)
    at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicComp.onCleanup(InternalFcCodBusinessLogicComp.java:520)
    at com.sap.xss.hr.cod.FcCodBusinessLogicCompInterface.onCleanup(FcCodBusinessLogicCompInterface.java:126)
    ... 57 more
Here are those logs : #sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement#shkaidyc#259##iecnt4006.ho.iec_EPD_12230850#shkaidyc#4f231680db9211dcbf1a001a64353d88#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/UserInterface#Java###An exception occured during application processing which got lost due to an additional exception that occured during session management post-processing phase. See nested exception for details about the original problem. Application=, RID=#2#com.sap.xss.hr.cod.ChangeOwnDataApplication#524da280db9211dcc053001a64353d88#
#1.5 #001A64353D8800700000003000000F480004462CD31C2A02#1203058240790#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#shkaidyc#259##iecnt4006.ho.iec_EPD_12230850#shkaidyc#4f231680db9211dcbf1a001a64353d88#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.#1#sap.com/ess~cod/ChangeOwnDataApplication#
#1.5 #001A64353D88005E0000001F00000F480004462CE8F64BF0#1203058607346#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleExpiration#Guest#0##iecnt4006.ho.iec_EPD_12230850#shkaidyc#4f231680db9211dcbf1a001a64353d88#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.tc.webdynpro.sessionmanagement#Java###Session unknown: Request was sent to unknown session. Either request with wrong session parameters was sent, or session has expired before . Current request parameters=. Is termination request=. Hint: see SAP note 842635 for more details on session expiration. RID=#7##Fri Feb 15 08:10:17 CAT 2008#{sap-wd-norefresh=X, DESTRUCTION_REASON=Destroyed by invalidation of HTTP session}#true###2cda6d20db9311dcbf6b001a64353d88#
#1.5 #001A64353D8800750000001F00000F480004462CED64CEC3#1203058681692#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.i18n.ClientSession.computeLocale#shkaidyc#402####592848c1db9311dca3cb001a64353d88#SAPEngine_Application_Thread[impl:3]_20##0#0#Info#1#com.sap.tc.webdynpro.i18n#Java###Computed locale for session : . Locale usage=. RID=#4#ClientSession(id=(J2EE12230800)ID1122215150DB00456128513810716498End_968000287)#<null>#locale was already computed in the session#592848c0db9311dccbae001a64353d88#
#1.5 #001A64353D880056000003B700000F480004462CEE901955#1203058701301#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement#shkaidyc#402##iecnt4006.ho.iec_EPD_12230850#shkaidyc#592848c1db9311dca3cb001a64353d88#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/UserInterface#Java###An exception occured during application processing which got lost due to an additional exception that occured during session management post-processing phase. See nested exception for details about the original problem. Application=, RID=#2#com.sap.xss.hr.cod.ChangeOwnDataApplication#64ceeb70db9311dc9d1e001a64353d88#
#1.5 #001A64353D880056000003B900000F480004462CEE902134#1203058701301#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#shkaidyc#402##iecnt4006.ho.iec_EPD_12230850#shkaidyc#592848c1db9311dca3cb001a64353d88#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.#1#sap.com/ess~cod/ChangeOwnDataApplication
And the link CAREER AND JOBS only SKILLS PROFILE works, the rest gives the following error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 02:21_15/02/08_0004_12230850
See the details for the exception ID in the log file.
#1.5 #001A64353D88005F0000001C00000BE400044631A5243BC5#1203078944497#/System/Server#sap.com/irj#com.sap.portal.sapapplication#shkaidyc#331##iecnt4006.ho.iec_EPD_12230850#shkaidyc#922658f0dbc111dc9663001a64353d88#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#com.sap.portal.sapapplication#Java###Content pass of Application Integrator failed.
Component Name:       'com.sap.portal.appintegrator.sap.BSP',
Context Name (iView): 'pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_career_job/com.sap.pct.erp.ess.profile_release/com.sap.pct.erp.ess.profile_release',
Top Layer:            'BSP/TopLayer',
Producer ID (FPN):    'null',
System Alias:         'SAP_EREC_TalentManagement',
#1.5 #001A64353D88005F0000001E00000BE400044631A5244180#1203078944497#/System/Server#sap.com/irj#com.sap.portal.portal#shkaidyc#331##iecnt4006.ho.iec_EPD_12230850#shkaidyc#922658f0dbc111dc9663001a64353d88#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#com.sap.portal.portal#Java###Exception ID:02:35_15/02/08_0006_12230850##
#1.5 #001A64353D8800720000002D00000BE400044631A82673C3#1203078994967#/System/Server#sap.com/irj#com.sap.portal.sapapplication#shkaidyc#331##iecnt4006.ho.iec_EPD_12230850#shkaidyc#922658f0dbc111dc9663001a64353d88#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#com.sap.portal.sapapplication#Java###Content pass of Application Integrator failed.
Component Name:       'com.sap.portal.appintegrator.sap.BSP',
Context Name (iView): 'pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_career_job/com.sap.pct.erp.ess.data_overview/com.sap.pct.erp.ess.data_overview',
Top Layer:            'BSP/TopLayer',
Producer ID (FPN):    'null',
System Alias:         'SAP_EREC_TalentManagement',
#1.5 #001A64353D8800720000002F00000BE400044631A82679B3#1203078994967#/System/Server#sap.com/irj#com.sap.portal.portal#shkaidyc#331##iecnt4006.ho.iec_EPD_12230850#shkaidyc#922658f0dbc111dc9663001a64353d88#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#com.sap.portal.portal#Java###Exception ID:02:36_15/02/08_0007_12230850##
If one clicks on MMS it opens fine, but when you go to the tab REPORTS it gives the same error as the CAREER AND JOB ERRORS in ESS.
Edited by: Clyton Shkaidy on Feb 15, 2008 1:58 PM

Hi Clyton,
We are implementing SAP ESS on EP 7.0. This is the first time i been working on ESS project.
Can you let me know the process of EP installation and about ESS Bussiness Packages and
How you connect R/3 and ESS ???
Can you mail me some screen shot of your ESS screen...
Following things are in our scope
Employee Self Service (ESS) will be activated for the following functionalities:
              Address Book
            Whos Who
             Organizational Chart (if available)
              Time Management
           Leave Request
           Time Accounts
           Record Working Time (CATS)
           Clock-in/out corrections
           Time Statement
              Payroll & Payment
            Salary Statement
            Total Compensation Statement
             Form 16
             Declarations against Sec 80C
             Claims / Reimbursements
             Loan Applications (To be decided during Blueprint)
              Personal Information (Browse only)
           Address
           Bank Information
            Personal Data
            Family Data
            Travel Management
           Travel Planning
           Travel Expenses
           Trips and Expenses
           Travel Profile
             Life and Work Events
             My First Days
             Birth / Adoption / Marriage / Divorce
              Performance Management
             Appraisals
              Corporate Information
             Code of Business Conduct
All workflows / Alerts required to support the above functions will be activated/configured.
Please guide me for the same...

Problem with ESS/MSS configuration

Hi All,
I want to start with ESS and MSS development. For the purpose I have downloaded the file BPERP4ESS01_0-10003146.sca and deployed it using SDM.
I am going through the pdf ESS Configuration Document.pdf.
The pdf talks about JCo which need to be created in Web Dynpro Content Administrator.I am unable to find the JCo's .
Please let me know how to proceed.
Thanks
Nikhil

Hi,
Login to http://server:port/index.html
If u want to see the jco, then go to Web Dynpro-->content administrator and click the tab 'create jco'.
But the tab wont be enabled unless u give permission in visual admin for the service 'sld data supplier'. i.e check the .lcr and webdynpro check boxes. Once checked, check if the CIM client test is successful.
Regards,
Vijai

WebSphere Integration with ESS/MSS Error

Hi All,
We are trying to setup a scenario where we embed the SAP Portal within WebSphere portlets. Plan is that we would have WebSphere link to the ESS HomePage. We have setup a URL alias in the web-inf with nested_window=1. The websphere guys are using the the WebSphere clipper to create the portlets but this is giving us javascript errors (e.g. Access Denied, etc). This means when we click on any of the ESS framework links e.g. Personal Data the webdynpro spinner comes up and nothing happens i.e. they screen does not change.
Any thoughts on what might be the issue? Is the Clipper the best tool to use?

Hi Mendonca,
Error is due to mis match of patches.
Check with SAP_HR and EA_HR patches. Try to maintaine the patches to 26 patch. By this u can resolve the issues.
That means Patches from Java side and Backend side need to be maintained at there same levels.
Regards,
kishore.

Time record approval with ESS/MSS

Hello,
I am new to MSS and I am facing some problems. I would like to get the time approval process started.
The projects are set up with cProjects and then transfered to PS. The WBS-items are taken for the time recording. Now I would like to approve this time recordings.
Unfortunately I don't have an idea what has to be configured to use the uwl:
- I think that I need to customize CATS to use the workflow (but which one)
- and then to configure the UWL in order to get the items...
Is this true?
Navigation through the portal and calling "team" in the MSS-menu an uncaught exception occurs saying that I have to configure infotyp 0008 for the employee I am using. Why do I need to set up the infotyp 0008 in order to see my team?
Calling the application for approval direct leads to the MSS overview.
Could somone bring some light in my darknes and tell me what I have to configure so that the project manager / line manager can see the recorded time that needs to be approved?
Thanks in advance, Vanessa

Thanks ...we would implement both then and I assume that the approve Timesheet application would be under "Team" Workset but when I click on it ..I get the error as:
No Views found: Missing customizing:
java.lang.Exception: No Views found: Missing customizing
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
     at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface.java:229)
     at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendarInterface.initialReadData(InternalFcTeamCalendarInterface.java:294)
     at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendarInterface$External.initialReadData(InternalFcTeamCalendarInterface.java:382)
     at com.sap.xss.ser.tecl.vc.VcTeamCalendarInterface.initialReadData(VcTeamCalendarInterface.java:362)
     at com.sap.xss.ser.tecl.vc.wdp.InternalVcTeamCalendarInterface.initialReadData(InternalVcTeamCalendarInterface.java:327)
     at com.sap.xss.ser.tecl.vc.VcTeamCalendarInterface.onBeforeOutput(VcTeamCalendarInterface.java:174)
     at com.sap.xss.ser.tecl.vc.wdp.InternalVcTeamCalendarInterface.onBeforeOutput(InternalVcTeamCalendarInterface.java:263)
     at com.sap.xss.ser.tecl.vc.wdp.InternalVcTeamCalendarInterface$External.onBeforeOutput(InternalVcTeamCalendarInterface.java:436)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
Appreciate your help.

NetWeaver Portal and ERP 6.0: BI, ESS/MSS and full Portal on one machine

Hello,
with ERP 6.0 you need a EP Core Portal for BI Java. An other EP Core Portal for HCM ECC/MSS. The iViews from this portal you integrate in the main portal via federated portal. But in this scenario i need to much portals and have a lot of maintenance costs (administration overhead for evry portal). For a small Customer i will build one Portal for all. It is possible e.g. to use the BI Portal with ESS/MSS and as full portal?
Best regards,
Patrick

Hi,
So you would like one BI installation with both the ABAP and the Java-stack with the full BI-functionallity and additionally the XSS-component and set it up to work against the ECC ABAP-only system ?
I think the scenario would actually work, but:
1) You might get future problems if you want to upgrade your BI-system and not the ECC-system.
Is it possible to run the old XSS-components in the new java-stack ?
2) You might get future problems if you want to upgrade your ECC-system and not the BI-system.
What if the new version of the XSS-component demands certain java-components which the BI-system do not have.
So my recommendation is still to run the java-stack on both systems.
ECC with the XSS-java-components and BI with the Bi-java-components.
This way you do not lock yourself into a corner and each system can be upgrade independent of the other.

Approve link not working in ESS/MSS UWL portal

Hi experts,
we are using portal 7.3 with ess/mss.
in mss when user is approving a leave request, he is not ale to proceed
after few steps as one link "pprove another request" is not working.
this i a standrd portal scren in UWL. please suggest.
Thanks a lot in advance.

Hello,
This should be possible with some UWL configuration. Please check the following forum post: http://forums.sdn.sap.com/thread.jspa?threadID=1677777
Kr,
Julien

Can anybody send me some docs on ESS/MSS and Adobe Forms.

Hi all,
Can anybody please send me some doc/materials/link on how to coonfigure/develop/work with ESS/MSS and Adobe forms.
Its very urgent requirement.
Thanks n Regards
A.M.Rao

For ERP 2005 check out
hi ,
for ess..
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAESS/ESSIAC.pdf
Personnel Admin.http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/0fab358b096510e10000009b38f839/frameset.htm
Training & Event management
http://help.sap.com/saphelp_erp2005vp/helpdata/en/44/2bc9367a23fb68e10000009b38f889/frameset.htm
Personnel Development
http://help.sap.com/saphelp_erp2005vp/helpdata/en/cf/5e9b38f8236e6de10000009b38f842/frameset.htm
ESS - http://help.sap.com/saphelp_erp2005vp/helpdata/en/5b/76a6d7fd3a4e91bfb422405bf3e04d/frameset.htm
MSS - http://help.sap.com/saphelp_erp2005vp/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm
For ERP 2004
ESS - http://help.sap.com/saphelp_erp2004/helpdata/en/5b/76a6d7fd3a4e91bfb422405bf3e04d/frameset.htm
MSS - http://help.sap.com/saphelp_erp2004/helpdata/en/0a/8b3b40b1607a56e10000000a1550b0/frameset.htm
Also if you have S User ID on SAP Service Marketplace, check out https://service.sap.com/mss-staging for MSS.
regards,
venkat.

Multi Level Leave workflow in ESS MSS

Hi Guys,
This is the first time I am working with ESS MSS and I have to implement 2 level workflow for leave, I have gone through lot of threads and concluded that i have to enhance class CL_PT_REQ_WF_ATTRIBS
with new method where I have to change the status back to SENT after first level of approval and create new background task and attach it to custom workflow which is copy of standard.
Now my problem is I have enhanced the class CL_PT_REQ_WF_ATTRIBS with new method change status but when I am creating the task I canu2019t see that method in drop down list of methods.
Any idea why it not showing.
We are on ECC6. EH4
Atul
Edited by: Atul Dhariwal on Mar 8, 2011 4:56 AM

Hi Atul
You are doing wrong way. You need to use BADI to enhance that for that goto SE18 search with PT_GEN* and get the BADI name and goto se19 and create a implementation for that there you in the desiered method you can code. But remember you cannot add you own need method the BADI. What ever SAP is providing that one only you can use to add additional code not addding new method.
Regards
Vijay

Debugging Workflow in ESS/MSS module .

Hi,
I know the stpes to debugging simple workflow and trouble shooting the same, but now
I want to know the debuggibg workflow steps for workflow running with ESS/MSS module Framework,
The scenario is
Its actually Approving Forms in ESS/MSS module, The Employee applying medical leave from his Id, then it will go to first level approver inbox once he approve it goes to second level approver inbox once he approves then it will go to third level approver inbox and he is the final level approvel once he approve the proces will be done.
The problem is, After the second level approver approves the form its updating wrong third level approver so its not comming to third level approver inbox. The workflow is designed under Z class but I dont have update cone in Z class methods.
The updation part is comming under standard ess/mss framework code.
So please tell me the steps how i can debugg or execute worklow in background for all the steps,
like from first step I like pass the container to second steps and goes on.
Help really appreciated.
Thanks & Regards
James.

Hi James
In ESS/MSS leave request the employee will apply the leave from portal and the workflow will triggered based on the spro which workflow template is used. Has you said that updation my custom cone. What is meant by that. Has as has i know we need to update the infotype 2001. This can be done by std FM.
To degbug.
In the put a external break point of the std FM which screen it call. I hope its called the webdypro java screen which nothing but a std FM. You need to find that FM. Then put a external breakpoint. change the user name from goto menu. Once you approve button is clicked in the portal. The debugger will open.
Regards
vijay

Error on ESS/MSS WebDynPros

Hi
We are struggling with ess/mss. Portal is ep6sp9 WAS640. Business packages (ess/mss )have been deployed in the portal and the ess50/mss50/pcui_gp50 components were deployed on WAS.
The SLD SERVER on the portal pc. The WAS is set to upload its sld information to the portal sld.
JCO connections(SAP r/3 HumanResources & SAP r/3 HumanResources Metadata) are on WAS and it tests successfully.
1. Is this the recommended architecture/landscape or should the ess mss pcuigp components be deployed on the portal?
2. Should we upgrade the ess/mss/pcuigp components to 5.1 or 6.0?
3. We get an error on the ess/mss webdynpros :
WDTypeNotFoundException caused by sap.dictionary.
4. When we use the ess/mss/pcuigp 6.0 version, we get a WDRuntimeException caused by 'There is no such method'.
Please help..
Rakhee

Hi Armin
Thannk you for your reply.
Below is the complete stack trace :
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC sap.com/mss~ewa:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/pcui_gp~xssutils:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/pcui_gp~xssfpm:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/mss~finutils:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87289.311
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException:
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
     at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:471)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:362)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:199)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:171)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
     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:346)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:352)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     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:385)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.dictionary.runtime.DdException:
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)
     at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
     at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
     at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
     at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
     at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:78)
     at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:64)
     at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:39)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
     at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
     ... 40 more

EHP with ESS/MSS

Similar Messages

Maybe you are looking for