SAP EP ESS CX_HRPA_INVALID_PARAMETER

Dear Experts,
Iam getting the below error while accessing the SAP EP ESS webdynpro screen.
Category          
ABAP Programming Error
Runtime Errors    
UNCAUGHT_EXCEPTION
Except.           
CX_HRPA_INVALID_PARAMETER
ABAP Program      
CL_HRESS_PER_OVERVIEW=========CP
Application Component  PA-ESS-XX-WDA
What can you do?                                                                             
|
|
Note down which actions and inputs caused the error.                                     
|
|                                                                                             
|
|                                                                                             
|
|
To process the problem further, contact you SAP system                                   
|
|
administrator.                                                                           
|
|                                                                                             
|
|
Using Transaction ST22 for ABAP Dump Analysis, you can look                              
|
|
at and manage termination messages, and you can also                                     
|
|
keep them for a long time.                                                               
|
|Error analysis                                                                               
|
|
An exception occurred that is explained in detail below.                                 
|
|
The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not           
|
|
caught in                                                                               
|
|
procedure "GET_INFTY_SUBTY_DATA" "(METHOD)", nor was it propagated by a RAISING          
|
|
clause.                                                                                 
|
|
Since the caller of the procedure could not have anticipated that the                    
|
|
exception would occur, the current program is terminated.                                
|
|
The reason for the exception is:                                                         
|
|
Invalid parameter EXCEPTION, value                                                       
|
|                                                                                             
|
|
The occurrence of the exception is closely related to the occurrence of                  
|
|
a previous exception "CX_HRPA_INVALID_SUBTYPE", which was raised in the program          
|
|
"CL_HRPA_READ_TIMECONSTRAINT===CP",                                                     
|
|
specifically in line 142 of the (include) program                                        
|
|
"CL_HRPA_READ_TIMECONSTRAINT===CM002".                                                  
|
|
The cause of the exception was:                                                          
|
|                                                                                             
|
|
Subtype  Not Permitted for Infotype 0105 &TCLAS&

Hi Philip
Check this SAP Notes
1030938 - Infotype 0001: Dump CX_HRPA_INVALID_PARAMETER during saving
1147540 - IT0008: Dump CX_HRPA_INVALID_PARAMETER
BR
SS

Similar Messages

  • SAP delivered ESS/MSS services

    Hi Gurus
    What are all the standard SAP delivered ESS/MSS services available for Indian market in ERP 2005.
    Regards,
    Samba.

    Hi,
    I assume, your portal language and also all the tabs and even all the MSS services which are based on Java (par files) are in French and all the WebDynpro services (almost all of the ESS services) are still in English.
    If that is the case, some of the services of ESS only have English and German, basically because you probably are using the US version of the ESS services. For example essusaddr only has English and German. But some of other services (like the MSS services and ess~cat) have all the languages. If you still see English for those service, you can manually change the language in the iView property of your service if you have an iView for them.

  • Step by Step procedue to modify SAP standard ESS screens

    Hi all,
    I am new to Enterprise portal..
    I have a requirement to modify the SAP Standard ESS screens, basically to add some new fields into it. I have the NWDI configured in the system. Can some explain me the step by step procedure to bring the source code into NWDS?
    Regards,
    Bharath Mohan B

    Hi
    Complete Custom  like ESS development
    SDN Day session in Las Vegas: Custom development of Web Dynpro ESS applications using Floor Plan Manager
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/essPersonalInformationUIenhancementwithoutmodification&
    Re: Steps for  ESS MSS  installation,Configuration
    Go to above links step by step
    Or you can search in SDN accrding to ur requiremt.
    Regards
    _SS

  • Sap Netweaver ESS - how does it work, how does it look like?

    Hello,
    I'm a newbie at Sap Netweaver ESS configuration and development and I'm trying to get some information about the most recent versions of ESS. Can anyone send me some print screens and/or usefull information about it?
    Thank you in advance.
    Best regards,
    Ricardo Inácio

    Pls send to me at peckhan at gmail as well, if possible

  • Style sheet of the SAP standard ESS package.

    Hi,
    Our client installed the standard ESS package and after adding a theme to portal the dropdowns , calendar widgets doesn't take the style sheet correctly and therefore the dropdowns , calendar widgets  and other display attributes doesn't appear properly.
    It would be great if any one provide the solution why this is occuring.
    Thanks
    Ritushree Saha

    Hi Ritushree,
    we experienced the same thing a couple of month ago. Some of the ESS/MSS GUI elements were not properly rendered after we applied a new SP (SAP NW 7.0 SPS 9 or SPS 11). As far as I remember SAP promised to fix the probleme in the next SPs.
    As a workaround we configured the affected ESS/MSS iViews in a way that they did not use the Portal Theme. As a result the iViews had a slightly different design but the GUI elements were working again.
    Best regards,
    Martin

  • SAP Standard ESS country structure not showing on the iViews

    Hi All,
    Some of the Fields in the SAP Standard Employee Self Service Country structure not showing on the iViews, if we want to bring those fields to iView level, What would be the solution.
    Please suggest.
    Thanks
    PRadeep

    Hi Pradeep
    If these are mandatory fields or legall required in that country and delivered in V_T588M or V_T588MFPROPS then you need to check with SAP why they are not shown in the ESS scenario
    If these are optional or R3 specific fields it could be they are not delivered in V_T588MFPROPS - try inserting
    an overide in V_T588MFPROPC
    If still you cannot get these fields you may need to add a field to the ESS application using NWDI
    and you may also need to change the model so it recognises the new field - this is effectively changing
    the SAP delivery
    Best regards
    Stuart

  • SAP HR - ESS

    Hi,
    Is there any trial versions for SAP HR system? I want to try some ESS customizations in my local portal. I have already installed the business packages. But the preview of ESS pages fail throwing error - system alias not defined.
    Or, Can I create a dummy system alias and try some sample ESS customization.
    Thanks.

    You might need to check this blog.
    Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
    Also plz check
    Configuring ESS in SAP Enterprise Portal 6.0

  • Is it bug/error from SAP on ESS - Personal Information-Address exit button

    Hello Experts,
    when i click on ESS - Personal information - Address  exit button here when i click on exit button its opening another portal actually it should go back to same portal ESS - Personal information -  Address
    is this error/bug from SAP
    if no what could be
    could anybody help me on this issue.
    Thanks
    Regards
    Vijay

    Hello Eperts,
    Sorry, i want to reopen this thread, to clear one issue.
    i tryed and solved this issue.
    try to configre the workprotect in personalization so it discard changes and open in the same page.
    all my portal user are facing the same problem.
    my question is Do i need to do changes for all user in personaliztion.
    Do we have any global chage at once i do it takes effect for all users.
    Any help on this Please.
    Thanksyou,
    regards
    Vijai

  • SAP Portal ESS SingleSignOn

    Hi!
    We are facing following Problem in our Sap Portal Environment.
    First of all SSO was working as intended. But after a Windows DC Migration with new computernames and new physical hosts we had to reconfigure SSO on our Portal-Servers. After the reconfiguration, SSO seemed to work again for everyone....but then some users started facing following problem (maybe 1 out of 100): That user cant login to SAP ESS via SSO. But when that person moves to another computer SSO is working there. So basically AD-Useraccount seems to be ok. So we thought "ok maybe a local computer problem". So a user with a working SSO tried to login on that "problem-computer" that had SSO problems. But SSO was working there suddenly with that user. So basically its not working only with that one useraccount on that specific computer. That user can login via SSO on every other computer and also other users can login via SSO on that "problem-computer".  We have several users right now that are facing that problem on their own computers.
    Our Windows group says that they cant see any problem in their Active Directory and point with their fingers on the SAP Portal as error source. So my Question: Is there any chance, that this problem really has his roots in the SAP Portal. i mean SSO is working for like 99% of the users. only for like 1% its not working only on their own specific computers. On other computers those 1% can also login via SSO.
    i would be really thankful for every idea!
    regards Alex

    Hi,
    for SSO, the browser has to get a HTTP 401 from the server. The browser should than get the token and send it to the server:
        Authorization: Negotiate YIIQCQYGKwYBBQUCoII long cryptic text P/TCCDBdxfqo=
    If the browser cannot resolve the SPN, or get it wrong, the browser will ignore the 401 or send a short Authorization answer back.
    What you can check besides the HTTP trace with the user::
    - Check if the computer of the user is in the domain and that the DNS is set correctly on that computer
    - Verify the logon process on the server with diagtool (complex but gives you every detail)
    - The users are using the same userID in the LDAP and UME?
    - All are using IE or some are using Firefox? In both the configuration for SSO has to be enables. IE: Windows integrated authentication + check the security zone. In FF: about:config and enter the correct domain.
    br,
    Tobias

  • Content provided by SAP  for ESS in Portal -ISSUE

    Hi All,
        We are using ESS iViews provided by SAP for Family,Leave,Personnel data etc..
          For each iView in top right corner we get <b>Quit</b> and <b>Help</b>. How can we disble them.
    Regards,
    Gangadharayya.

    Hello,
    Are you using ITS.  If so you have to edit the templatelibarybasis.html file situated in the following location:
    c:| program files\sap\its\6.20\ITD\templates\system\dm
    Search for Quit and help and comment the code out.
    Nick

  • SAP HR ESS Issue - Remove Approvar

    Hello All,
    I have a query where in I need to remove the approvar in ESS. For Eg. if an employee applies for leave through ESS, it shud trigger Y and not X. How to go for i in OM?

    Hi,
    Change in HRP1001 for A002 instead of x possition give Y position.
    In system Employee Position reporting to X position.. Change from particular date on wards to Y position.
    Use T. Code:PP02
    Select object type S. Then infotype as 1001, subtype as A002, Planning Status as 1, Give dates and maintain data for Position.

  • CMS import  for SAP ESS component(SP 15) fails with fatal error.

    Hi,
    We are working on EP 7.0 SP 15. We have a requirement for changes to be made to SAP delivered ESS codes. We have set up the NWDI and and from the checkin tabn of CMS, the components SAP-JEE (7.00 SP18 ), SAP_JTECHS(7.00 SP18 ), SAP_PCUI-GP(SP 18), EP_BUILDT (7.00 SP18 )and SAP_BUILDT (7.00 SP18 )have been imported successfully to the development tab. But when we try to import the SAP ESS 600(SP level 15) from Checkin tab to the Development tab, the import fails. The exception chain as checked by clicking Details button in teh Develepoment tab of CMS shows the details as:
    20090610145206 Info   :Starting Step Repository-check at 2009-06-10 14:52:06.0283 +5:00
    20090610145206 Info   :Component:sap.com/SAP_ESS
    20090610145206 Info   :Version  :MAIN_ERP05PAT_C.20090427083436
    20090610145206 Info   :1. propagation request is of type TCSSoftwareComponent
    20090610145206 Info   :Propagatable:d647b419330511de9f130030057116fe exists allready in the repository. No import necessary.
    20090610145232 Fatal  :VcmFailure received
    20090610145232 Fatal  :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Fatal  :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Info   :Step Repository-check ended with result 'fatal error' ,stopping execution at 2009-06-10 14:52:32.0796 +5:00
    The above log is displayed when I click the import -check button on the development tab of CMS. The same error is displayes when the import button is clicked  with only the last sentence changed to:
    Step Repository-check ended with result 'fatal error'
    Can anyone help me on this.... ?
    Thanks,
    Sonali.
    Edited by: Sonali M S on Jun 10, 2009 1:16 PM

    Hi Bala,
    The problem still remails even after making changes in Visual Admin as per the thread Re: Assembly finished with errors
    Also from http://<server>:<port>/nwa we have run the configuration task for "Initial setup of functional unit Development Infrastructure (DI all-in-one)" and there we donot have the option for individual CBS, CMS and DTR installations as told in the thread.
    The other thread import into devlopment failed tells about the SAP note: 988010 iin which it is mentioned that this has been fixed in SP 11 for 7.00 version. We are already on SP 18. So it is assumable that this thing has already been fixed.
    Can there be any other reason for this?
    Thanks,
    Sonali.

  • Error in Deployment of SAP ESS 100 SP16 ess/au/addr

    Hello Gurus
    Greetings !..
    I am trying to Deploy SAP ESS 100 SP16 for Netweaver 2004s using SDM but getting error while i deploy in the phase ess/au/addr.
    Please check for the log below if any one can helpout soon....
    May 22, 2007 10:16:50... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:16:50... Info: Finished successfully: development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'680352'/'0', grouped by
    May 22, 2007 10:16:50... Info: Starting to save the repository
    May 22, 2007 10:16:52... Info: Finished saving the repository
    May 22, 2007 10:17:04... Info: Starting: Update: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0' updates currently deployed development component 'ess/at/pdata'/'sap.com'/'MAIN_ERP05VAL_C'/'766644'/'0'.
    May 22, 2007 10:17:04... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\at\pdata\MAIN_xss04VAL_C\0\680388\sap.com_essatpdata.sda
    May 22, 2007 10:17:04... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:04... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Begin of log messages of the target system:
    07/05/22 22:17:04 - ***********************************************************
    07/05/22 22:17:04 - Start updating EAR file...
    07/05/22 22:17:04 - start-up mode is lazy
    07/05/22 22:17:04 - EAR file updated successfully for 78ms.
    07/05/22 22:17:04 - Start updating...
    07/05/22 22:17:04 - EAR file uploaded to server for 219ms.
    07/05/22 22:17:05 - Successfully updated. Update took 734ms.
    07/05/22 22:17:05 - Deploy Service status:
    07/05/22 22:17:05 - Application : sap.com/essatpdata
    07/05/22 22:17:05 -
    07/05/22 22:17:05 - sap.com/essatpdata - WEBDYNPRO
    07/05/22 22:17:05 - ***********************************************************
    May 22, 2007 10:17:06... Info: End of log messages of the target system.
    May 22, 2007 10:17:06... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Finished successfully: development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0', grouped by
    May 22, 2007 10:17:07... Info: Starting to save the repository
    May 22, 2007 10:17:08... Info: Finished saving the repository
    May 22, 2007 10:17:21... Info: Starting: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0' will be deployed.
    May 22, 2007 10:17:21... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\MAIN_xss04VAL_C\0\681439\sap.com_ess~au.sda
    May 22, 2007 10:17:21... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:21... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Begin of log messages of the target system:
    07/05/22 22:17:21 - ***********************************************************
    07/05/22 22:17:21 - Start updating EAR file...
    07/05/22 22:17:21 - start-up mode is lazy
    07/05/22 22:17:21 - EAR file updated successfully for 188ms.
    07/05/22 22:17:21 - Start deploying ...
    07/05/22 22:17:22 - EAR file uploaded to server for 859ms.
    07/05/22 22:17:24 - Successfully deployed. Deployment took 2547ms.
    07/05/22 22:17:24 - Application : sap.com/ess~au
    07/05/22 22:17:24 -
    07/05/22 22:17:24 - sap.com/ess~au - WEBDYNPRO
    07/05/22 22:17:24 - ***********************************************************
    May 22, 2007 10:17:25... Info: End of log messages of the target system.
    May 22, 2007 10:17:25... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Finished successfully: development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0'
    May 22, 2007 10:17:25... Info: Starting to save the repository
    May 22, 2007 10:17:27... Info: Finished saving the repository
    May 22, 2007 10:17:39... Info: Starting: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' will be deployed.
    May 22, 2007 10:17:39... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\addr\MAIN_xss04VAL_C\0\681471\sap.com_essauaddr.sda
    May 22, 2007 10:17:39... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:39... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Info: Begin of log messages of the target system:
    07/05/22 22:17:39 - ***********************************************************
    07/05/22 22:17:39 - Start updating EAR file...
    07/05/22 22:17:39 - start-up mode is lazy
    07/05/22 22:17:39 - EAR file updated successfully for 94ms.
    07/05/22 22:17:39 - Start deploying ...
    07/05/22 22:17:40 - EAR file uploaded to server for 297ms.
    07/05/22 22:17:40 - ERROR: Not deployed. Deploy Service returned ERROR:
    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?
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
    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)
    Caused by: 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?
    at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
    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)
    ... 10 more
    For detailed information see the log file of the Deploy Service.
    07/05/22 22:17:40 - ***********************************************************
    May 22, 2007 10:17:40... Info: End of log messages of the target system.
    May 22, 2007 10:17:40... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Error: Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'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)
    May 22, 2007 10:17:40... Info: Starting to save the repository
    May 22, 2007 10:17:42... Info: Finished saving the repository
    May 22, 2007 10:17:54... Info: Starting: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0' will be deployed.
    May 22, 2007 10:17:54... Error: Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
    Failed deployment of SDAs:
    development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' : aborted
    Please, look at error logs above for more information!
    Hope for a prompt response.
    Reply awaited urgently....
    Thanks in Advance
    Thanks & Best Regards
    Ashish

    Hello Gerard Christopher
    Yes i got the problem solved, actually SAP ESS 600 & SAP MSS 600 are the component we have to use. As we were on WAS 7.00 and ERP 2005 so
    SAP ESS 600
    SAP MSS 600
    SAP PSS 600
    SAP ASR 600
    SAP PCUI_GP 600
    Try with this you will able to solve.
    Thanks & best Regards
    Ashish

  • Integration of ESS Portal and SAP

    Hi,
    Project Systems report  RPSISKB000 - Capacity Requirements Overview  (t-code CN50N) is a report works correctly when analyzing time that was entered via the R/3 GUI in transaction CAT2 u2013 Time Sheet: Maintain Times.  However, when executing against time entered via Employee Self Service (ESS) Time Sheet Entry,  the u201CActual Worku201D hours are not pulling through to the report. 
    I believe this is because when time is entered via ESS Time Sheet Entry  the fields Capacity ID (KAPID) and Split Number (SPLIT) in table CATSDB are not populated.   These two fields are populated when time is entered via the R/3 GUI in transaction CAT2.
    I need how to populate these two fields when time is entered via ESS. How data flows from ESS Portal to SAP.
    How SAP and ESS Portal integrated for data flow in between.
    Thanks,
    Suresh

    You have to ensure that these fields in The CATS profile are set as input in CAC2 ie fields should be input and not is display
    Please check it
    Implement Note 1385803

  • SAP ESS 600 Web Dynpros Missing After Install

    Hi,
         We are running EP 7.0 SP11 on a linux platform. We deployed the following
    components in the given order-
    SAP PCUI_GP 600
    IS-HER 600
    SAP ASR 600
    SAP PSS 600
    SAP MSS 600
    Each of the above components was at Support Package 08.
    In Content Administraton -> Web Dynpros -> sap.com, we expected to find web dynpros
    that start with "sap.com/ess~" but found none.
    Any ideas what is going on?
    Sincerely,
    Jonathan Yun
    Duke University

    Hello Deb,
    Even though note 761266 is primary for ERP 2004, we were able to extract the necessary information to apply to our ERP 2005 system.  After we deployed SAPESS08_0-20000512.SCA, the missing ess web dynpros show up in the Portal.  Thank you very much for your help.
    However, I do have one additional question.  We noticed that the base ESS Business Package (BPERP5ESS08_0-10003288.sca) downloaded from SDN is only about 3MB and the SAP ESS 600 patch (SAPESS08_0-20000512.SCA) is about 270MB.  Are these two different components of the "ESS"?  This is very different from MSS.
    Thanks again for your time,
    Jonathan

Maybe you are looking for