ESS Travel Exception after Portal Patching

Hello Everyone,
We have recently upgraded the portal from SP14 to SP17. So, this resulted in Various Software components like ESS are patched as well. But, in our old ESS track we have done lot of customisation to the Travel iViews. So, when we have patched ESS, it is really annoying that we have to make all the customisation manually again in the new ESS track. We have followed the "NWDI Cookbook for XSS/ESS" after patching as well. But, it is of no use.
Now, we have done all the customisation manually again to the new track and the strangest thing is we are getting a completely irrelevant Exception as given below. We have not even touched that DC and it is throwing an exception. We are very surpised with all these complexeties. Can anyone help me in resolving these two questions? I am completely fed up searching on SDN to resolve these 2 issues and have given up now.
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: MappedAttributeInfo(FcTreReceipts.Customizing.E_Jurcodes_External): mapped attribute E_Jurcodes_External not found
     at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.initNodeMapping(MappedAttributeInfo.java:377)
     at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.init(MappedAttributeInfo.java:281)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initMappedAttributes(NodeInfo.java:699)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAfterCompletedMapping(NodeInfo.java:705)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:87)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:69)
     at com.sap.tc.webdynpro.progmodel.context.Node.getDataNode(Node.java:1684)
     at com.sap.tc.webdynpro.progmodel.context.Node.isValid(Node.java:368)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:344)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:333)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:615)
     at com.sap.tc.webdynpro.progmodel.context.Node.getCurrentElementInternal(Node.java:868)
     at com.sap.tc.webdynpro.progmodel.context.Node.getCurrentElement(Node.java:875)
     at com.sap.xss.tra.tre.fc.receipts.wdp.IPublicFcTreReceipts$IContextNode.currentCustomizingElement(IPublicFcTreReceipts.java:2274)
     at com.sap.xss.tra.tre.fc.receipts.FcTreReceipts.onEventCustomizingChanged(FcTreReceipts.java:1406)
     at com.sap.xss.tra.tre.fc.receipts.FcTreReceipts.onInit(FcTreReceipts.java:475)
     at com.sap.xss.tra.tre.fc.receipts.wdp.InternalFcTreReceipts.onInit(InternalFcTreReceipts.java:3322)
     at com.sap.xss.tra.tre.fc.receipts.FcTreReceiptsInterface.onInit(FcTreReceiptsInterface.java:161)
     at com.sap.xss.tra.tre.fc.receipts.wdp.InternalFcTreReceiptsInterface.onInit(InternalFcTreReceiptsInterface.java:299)
     at com.sap.xss.tra.tre.fc.receipts.wdp.InternalFcTreReceiptsInterface$External.onInit(InternalFcTreReceiptsInterface.java:427)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.xss.tra.tre.vc.receipts.VcTreReceipts.onInit(VcTreReceipts.java:255)
     at com.sap.xss.tra.tre.vc.receipts.wdp.InternalVcTreReceipts.onInit(InternalVcTreReceipts.java:412)
     at com.sap.xss.tra.tre.vc.receipts.VcTreReceiptsInterface.onInit(VcTreReceiptsInterface.java:122)
     at com.sap.xss.tra.tre.vc.receipts.wdp.InternalVcTreReceiptsInterface.onInit(InternalVcTreReceiptsInterface.java:124)
     at com.sap.xss.tra.tre.vc.receipts.wdp.InternalVcTreReceiptsInterface$External.onInit(InternalVcTreReceiptsInterface.java:200)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseEvent(FPMComponent.java:938)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseEvent(FPMComponent.java:1101)
     at com.sap.xss.tra.tre.vc.generaldata.VcTreGeneralData.raiseFPMEvent(VcTreGeneralData.java:463)
     at com.sap.xss.tra.tre.vc.generaldata.wdp.InternalVcTreGeneralData.raiseFPMEvent(InternalVcTreGeneralData.java:589)
     at com.sap.xss.tra.tre.vc.generaldata.GeneralDataView.onActionNextStep(GeneralDataView.java:673)
     at com.sap.xss.tra.tre.vc.generaldata.wdp.InternalGeneralDataView.wdInvokeEventHandler(InternalGeneralDataView.java:674)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java: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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
I would be very thankful if someone could help me in resolving this issue. I would appreciate your help.
Regards,
Gopal.

Hello Gopal
It seems and clear that context mapping is broken.
1.Do the reimport of all the models/ services for the concerned DC.
2.Open contexts one by one, find X(red marks) mark for which the mapping is broken.
It happen that structure field not found, or data type mismatch or some new added field or deleted field etc
Do these check let us know
Best Regards
Satish Kumar

Similar Messages

  • Java Exception after applying Patch 10.1.0.3

    After applying the 10.1.0.3 patch to an XP system, I am getting the following error:
    sys@MYDB>exec dbms_java.grant_permission( 'SCOTT', 'SYS:java.io.FilePermission','C:\tmp\*','read,write,delete');
    BEGIN dbms_java.grant_permission( 'SCOTT', 'SYS:java.io.FilePermission','C:\tmp\*','read,write,delete'); END;
    ERROR at line 1:
    ORA-29532: Java call terminated by uncaught Java exception: java.lang.Error: Updater error on insert
    ORA-06512: at "SYS.DBMS_JAVA", line 313
    ORA-06512: at line 1
    Anyone got any ideas

    I forgot to mention that I did flush the JAR cache to make sure the new JAR's would be downloaded.
    Gerrit

  • Portal Runtime error after applying patch 12 to portal

    hi experts,
    i m getting following error
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.portal.webdynpro_ws/com.sap.portal.content_administrator/com.sap.portal.wd_content_administrator
    Component Name : com.sap.portal.appintegrator.sap.WebDynpro
    Exception in SAP Application Integrator occured: ApplicationIntegratorException.
    Exception id: 09:30_22/01/08_0005_16892850
    See the details for the exception ID in the log file
    after applying patch 12 in portal
    i m getting this error in guided procedures,Universal worklist ,webdynpro workset undfer content administration
    Please suggest me the solution
    regards,
    vani

    Hi Vani,
    Just go to the System Configuration and UME configuration.
    Now go to user mapping tab, and remove the entry for a reference system. Then check for the issue if persists, restart system.
    Hope this helps!
    regards
    Atul Shrivastava

  • WD Exception when pointing ESS Travel & Expense to multiple backend systems

    Hi All,
    I have a query regarding ESS Travel Management pointing to multiple backend systems.
    ESS MSS is installed on a single portal(Portal1).
    ESS MSS is currently pointing to Backend System1. The requirement is that ESS Travel from Portal1 should point to various multiple Backend Systems therefore making ESS Travel region-specific.
    Is this possible? and if so what are the pros and cons?
    This is what I have attempted:
    1. Followed the documentation from "Multiple Back End Support for the Adaptive RFC Model" [http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/frameset.htm]
    Therefore, I created 2 JCOs namely: SAP_R3_Travel_R1 and SAP_R3_Travel_MetaData_R1 pointing to Backend Sytem 2. SSO and JCO tests successfully.
    2. On the iview properties for ESS Travel & Expenses, I added the following to the Application Parameters: sap-wd-arfc-useSys=SAP_R3_Travel:_R1&sap-wd-arfc-useSys=SAP_R3_Travel_MetaData:_R1
    3. I additionally created a system in the Portal under  System Configuration pointing to Backend System2 and adding the SAP_R3_Travel_R1 as the default System Alias. Do I need to add SAP_ITS_XSS and SAP_WebDynpro_XSS system alias, if so how since it is seeing as redundant because it is added in the system I created for Backend System1.
    4. I then tested one of the ESS Travel & Expenses iviews. I have the following error:
    Accessing System XYZ is not possible because RFC Metadata was retrieved using System ABC. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!
    Your help is appreciated.
    Thanks.
    RD

    Hi,
    Can you please share the solution you got for this problem as we are also facing the same kind of problem.
    thanks
    Gaurav

  • Issue with updation of PAN details in ESS after applying patch

    Hi ,
    We have applied a new patch recently,
    as follows:
    SAP_HR - To patch - 49
    EA_HR - To Patch - 49
    When users are trying to update PAN details it says throwing error " fill in the required fields,"
    i tried to apply relevent note :1243216 , but iam not able to apply it as system says it cannot be implemeted.
    Can any body come accross this issue please give me solution as this issue has become critical.
    Thanks in advance .
    Regards,
    Evani

    Duplicate post.
    After applying patch , error found on bottom of signon screen
    After applying patch , error found on bottom of signon screen

  • ESS Travel Plan : Add Additional Destination ( Portal )

    Dear Experts ,
    I have the following issues :
      1-  I want to add additional destination in travel plan when i create a new travel plan through Portal , i have checked additional destination flag in travel schema but , this flag activate the additional destination only in travel request not in travel plan ????
    is there any way to activate additional destination in travel plan ( in portal ) ?? 
    2- How to change field label in travel plan in portal ??

    Use Personalization (Ctrl + Right Clic).
    Check the SAP Note 1234273 - WebDynpro iview personalization not reflected for all users.
    /message/6159308#6159308 [original link is broken]
    Regards

  • Adobe form not working after MSS Patch Upgrade

    Hi,
    We have implemented ESS/MSS and in one of the MSS scenario to create a new personnel chnage request we have an Adobe interactive form (WD) which actually validates the users Social Security number by calling an RFC in the ECC 6.0 and updates the form's filed on the front end. There was an issue of "Expired SSO Ticket" and to resolve this SAP recommended to apply SAP_JTECHS (SAPJTECHS13P_14-10003467) and SAP_JTECHF (SAPJTECHF13P_15-10003468) patches to fix the problem. But after applying these patches Adobe form for PCR has stopped working and it just gets hanged, form appears on the front end and when user enters the values and hit enter to validate, it doesnt communicate with the Backend ECC system only the SAP status picture keeps rotating, i turned the trace ON and checked it, its not at all communicating with the ECC system. Where as in other systems where we have not appplied the pacthes, those are working fine. One of the error i noticed in the server log is as below:
    jco.client.mysapsso2=AjExMDAgAA5wb3J0YWw6QkNPTFNUT4gAE2Jhc2ljYXV0aGVudGljYXRpb24BAAdCQ09MU1RPAgADMDAwAwADU1BEBAAMMjAwODExMDMxNjU3BQAEAAAAEAoAB0JDT0xTVE//AQUwggEBBgkqhkiG9w0BBwKggfMwgfACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0DCBzQIBATAiMB0xDDAKBgNVBAMTA1NQRDENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDgxMTAzMTY1NzQwWjAjBgkqhkiG9w0BCQQxFgQUfD7V7TS!58cgzIFyucxCSL4ltuswCQYHKoZIzjgEAwQvMC0CFA4Q0!Rr2xYFPwFwXz8WeFF1UALlAhUAmHiTdHw!3s4Q!Jc9gDyY4QSvxa4=, user=, mshost=sapdv2.company.com, r3name=DV2, jco.client.type=B, jco.client.trace=0, group=SRS, codepage=1100}
    Client not connected#
    #1.5 #76C1EDD07B440026000000000007501600045ACC2EF6809D#1225732914577#/Applications/BusinessLogic#sap.com/home~zb2bzsrs#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#BCOLSTO#1480##hadspd1.bnet_SPD_306896250#BCOLSTO#daca9e30a9cb11dd99c976c1edd07b44#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface.#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
    Properties: {passwd=?, lang=en, client=150,
    Can someone please suggest what could be the possible reason for such a problem with Adobe form and whats the way out to resolve this. Appreciate a quick help in this regard.
    Thanks in  advance,
    Sarabjeet.

    Hi,
    We had the same issue after the Patch update to SP17 in both Backend as well in Portal, to resolve my colleagues had a look at the standard forms which were working and found that because of the patch update the script used in the custom forms was changed and not the standard and
    on event trigger which was processed in the container they replace the script to the standard one. and it started working.
    But this is not the solution we are looking at solution on having the same version of script as in the standard even after the patch update.
    So to your point to resolve compare the scripts in both standard and customized forms and do the same.
    And also have a look at the SAP Note: 1109392
    .... this is a temporary solution.....
    Hope this helps.
    Cheers-
    Pramod

  • Error in ESS - Travel Expenses & Travel Plan -- Urgent

    Hai,
    We are implementing ESS using WebDynpro in this we are able to create a Travel Request but in Travel Expenses giving the Error as follwos and we are not getting country in Travel Plan after creating a travel Request ..
    The initial exception that caused the request to fail, was:
    <b>   com.sap.tc.webdynpro.services.sal.deployment.api.WDAliasResolvingException: Cannot resolve alias 'host..' since the configuration file is not found.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.resolveAlias(DeployableObject.java:391)
        at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObjectPart.resolveAlias(WDDeployableObjectPart.java:105)
        at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.computeWebResourceURL(AbstractURLGenerator.java:948)
        at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.getWebResourceURLInternal(AbstractURLGenerator.java:211)
        at com.sap.tc.webdynpro.services.sal.url.core.URLGeneratorInternal.getWebResourceURLInternal(URLGeneratorInternal.java:284)
        ... 95 more</b>
    <b>Caused by: com.sap.tc.webdynpro.services.sal.url.api.WDURLException: The URL couldnt be generated because the alias resolving failed.
         at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.computeWebResourceURL(AbstractURLGenerator.java:951)
         at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.getWebResourceURLInternal(AbstractURLGenerator.java:211)
         at com.sap.tc.webdynpro.services.sal.url.core.URLGeneratorInternal.getWebResourceURLInternal(URLGeneratorInternal.java:284)
         at com.sap.tc.webdynpro.progmodel.view.ViewElement.resolvedWebResourceURL(ViewElement.java:406)
         ... 94 more
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.api.WDAliasResolvingException: Cannot resolve alias 'host..' since the configuration file is not found.
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.resolveAlias(DeployableObject.java:391)
         at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObjectPart.resolveAlias(WDDeployableObjectPart.java:105)
         at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.computeWebResourceURL(AbstractURLGenerator.java:948)
         ... 97 more</b>
    Thanx in Advance
    Sreedhar G

    Hi,
    I am getting the same error (com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User UGARG does not exist in this period). This user is already there in ECC as an employee and its validity is same in pa30 and su01. How did you resolve this issue?
    I am using EP 7.0 SP12, ECC 6.0 SP 12, PCUI/ESS SP 10
    I have installed the following business packages on portal server:
    Business Package for Employee Self-Service (mySAP ERP) - BPERP5ESS11_0-10003288.SCA
    SAP PCUI_GP 600 - SAPPCUIGP10P_1-20001215.SCA
    SAP ESS 600 - SAPESS10P_10-20000512.SCA
    What is the difference between SAPESS10P_10...sca and BPERP5ESS11_0...sca? Do I need to install both on portal server?
    Thanks,
    Umesh Garg

  • ESS Travel - request transportation / accommodation

    Help
    I'm using business package ess of the portal.
    I thought he represented the transaction trip with all its features.
    However I am not finding place to come with information, transportation and accommodations in the functionality of creation of requests for travel.
    I need this functionality in my project.
    Do you have any suggestion.
    Does bp ESS does not have this functionality (request transportation / accommodation)?
    thank you.

    it's does effect your current Portal ESS.
    Only you are upgrading the Backend system to Eh P2 which means for travel you will get additional software component FIN_TRAVL_1 which needs to be activated after upgrading the ECC.
    You can read the  below SAP PROVIDED Notes
    SAP NOTES
    FIN_TRAVEL_1: Business Function Travel Management (New)
    Use
    As of SAP ECC 6.0, Enterprise Extension Travel Management Extension, enhancement package 2 (EA-TRV 602), you can use the business function Travel Management. This business function encompasses the new and extended functions of the Travel Management (FI-TV) component described below.
    New User Interface in SAP Enterprise Portal
    The extended travel management applications in Employee Self-Service (ESS) of SAP Enterprise Portal are based on Web Dynpro ABAP technology. If you activate this business function, SAP Enterprise Portal no longer launches the Web Dynpro Java applications, but rather the new Web Dynpro ABAP applications. Users require new authorization profiles, which are defined in the new standard roles. The following Web Dynpro ABAP applications are available in ESS:
    My Trips and Expenses
    The Personal Object Worklist (POWL) for travelers lists the travel requests, travel plans, and expense reports (travel expenses) for each individual traveler. Travelers run applications from within the POWL; for example, to create a new travel plan using the data from a travel request, or to change the expense report. Travelers also can launch the applications for creating travel requests, travel plans, and expense reports, directly in ESS.
    My Employees
    The POWL for travel assistants lists the travel requests, travel plans, and expense reports for all employees assigned to the assistant. Travel assistants can perform tasks such as creating and changing travel plans for employees, and copying travel plans from other employees.
    Create Travel Request
    Create Travel Plan
    Create Expense Report (Create Travel Expense Report)
    My Travel Profile
    Route Planning
    Unlock Personnel Number
    If certain conditions are given, you can implement the new Web Dynpro ABAP application for the following standard role in Manager Self-Service (MSS):
    Approving Manager
    To implement this new application in SAP Enterprise Portal, you need to provide an iView.
    This application enables you to perform the approval process without SAP Business Workflow and Organizational Management. For more information, see the section that follows.
    New User Interface: SAP NetWeaver Business Client (NWBC)
    Users can run the following role-based Web Dynpro ABAP applications in the NWBC, independent of the new standard roles assigned to those users:
    Traveler
    The POWL and applications are the same as the My Trips and Expenses application in SAP Enterprise Portal. The POWL also provides access to the applications My Travel Profile, Route Planning, and Unlock Personnel Number.
    Travel Assistant
    The POWL and applications are the same as the My Employees application in SAP Enterprise Portal. The POWL also provides access to the applications My Travel Profile (for all employees), Route Planning, and Unlock Personnel Number (for all employees).
    Approving Manager
    The POWL for approving managers lists the travel data requiring approval for all employees assigned to the manager. Approving managers can approve or reject expenses, and send explanatory comments to the employees via e-mail.
    The POWL enables approving managers to define substitutes for limited periods of time, and to act as a substitute for other approving managers.
    Travel Policy Administrator
    Users with this role can execute the following Customizing applications for managing travel policy:
    Change Predefined Addresses
    Define Maximum Rates and Default Values for Expense Types
    Define Maximum Amounts for Hotel Nights
    Define Hotel Catalog
    Define Customer Programs
    Define Agreements Between Travel Service Providers on Customer Programs
    Integration of Travel Requests and Travel Planning
    The areas of travel requests, travel planning and expense reports are fully integrated in the new Web Dynpro ABAP user interface. Users can copy the following travel data:
    When creating travel plans, users can copy data from their travel requests. When users create a new travel plan, the system displays a list of open travel requests, from which users can copy data to the new travel plan.
    When creating expense reports, users can copy data from their travel requests or travel plans. When users create a new expense report, the system displays a list of open travel requests and travel plans, from which users can copy data to the new expense report.
    The POWL of each user shows the status of the user's trips and provides users with easy access to the subsequent actions that are possible (for example, once a travel request is approved, the user can choose Create Travel Plan).
    Integration of Travel Services and Travel Preferences in Travel Requests
    In travel requests, you can specify which travel services are required for the following modes of travel (but you cannot reserve or book them here):
    Flight
    Hotel
    Car rental
    Rail
    Other travel services
    For more information, see the section that follows.
    The system displays the preferences of a traveler based on his or her travel profile. At a later date, you can transfer the data a travel request to a travel plan, and book your trip. Alternatively, you can transmit the travel request to a travel agency, which then books the trip for you.
    Other Travel Services
    In travel requests, you can now specify (but not reserve or book) other travel services. Other travel services include the following:
    Ferry
    Helicopter
    Airport shuttle
    In Customizing you determine which other travel services are displayed and which entries can be made by users. See Other Travel Services.
    Copying of Travel Requests
    Users can copy travel requests. Travel assistants can copy travel requests of one traveler for another traveler, and edit the new request. (Both travelers need to be on the employee list of the travel assistant.)
    Saving of Drafts of User Entries
    The Save Draft function allows users to temporarily save your entries in the applications (except in travel travel planning). The system saves the incomplete entries with the status Open.
    Expense Types per Schema
    To each schema, you can assign those expense types that need to be available in the respective schema. If you do not specify any expense types for a schema, then all expense types stored in the system apply to that schema. You can use this function to create a schema for miscellaneous receipts, which enables employees to enter receipts that are not directly related to a specific trip. These might be expenses for phone costs, office supplies, or promotional gifts on behalf of consultants or sales staff. See Restrict Travel Expense Types for Trip Schemas.
    This function is also available in SAP GUI.
    Advanced Passenger Information
    In travel plans, you can enter additional passenger data for Advanced Passenger Information System (APIS). When a flight is booked, this data is transmitted to the airlines via a Global Distribution System (GDS). In Customizing, for each country key you can determine whether travelersare required to enter APIS data, and which data items are required. See Define Data for Advanced Passenger Information System.
    This function is available only in the new Web Dynpro ABAP user interface.
    Sarbanes-Oxley Compliance
    The following functions have been extended to ensure audit ability of statutory rules, such as those prescribed by the Sarbanes-Oxley Act:
    Credit Card Receipts in Expense Reports
    You can define in Customizing that users cannot delete credit card receipts. See the field documentation under Set Up Feature TRVPA for Travel Expenses Parameters.
    In expense reports, you can itemize your private expenses as separate receipts and allocate them to private expense types (for example, use of mini-bar). This documents the personal portion of expenses in the system.
    Additional Receipt Information in Expense Reports
    When entering expenses, you can specify internal and external participants of an entertainment event in the form of a table under additional receipt information. You can evaluate this information in reporting. In Customizing, for each trip provision variant and expense type, you can determine whether users are required to enter such participants. See Field Control for Additional Receipt Information.
    These enhancements are also available in SAP GUI.
    Use of Scanned Receipts and Adding of Attachments
    If you use optical archives for Travel Management, in expense reports you can display receipts that are scanned into the system. When scanned receipts are allocated to an expense report, the system shows them in the POWLs for travelers, travel assistants, and approving managers.
    Travelers can add attachments to their expense reports (for example, the agenda of a convention). This can be done when creating an expense report or in the POWL. Attachments are linked to the trip number and can be viewed by travel assistants and approving managers.
    Enhancements in Flight Reservations
    Flight reservations have the following new functions:
    You can determine whether the Amadeus reservation system should apply Value Pricer or Master Pricer in fare-driven flight availability queries. You do this with the MASTERPRICER attribute in table TA20SWITCH. See Define Enterprise-Wide Control Parameters.
    The system sorts best-price query results by price, but groups different flight combinations that have the same price. Within these groupings, you can select any combination of outbound and return flights.
    If you have set up a direct connection to a flight reservation system such as TRAVELfusion (in addition to GDS), the system shows the available flights for both reservation systems in the fare-driven flight availability list.
    Enhancements in Bookings at Deutsche Bahn (German Railway)
    Train reservations using NVS (Amadeus) have the following new functions:
    You can book tickets for multiple passengers. You can specify whether each individual passenger has a BahnCard. For international trips, you can enter the age of each passenger, for example, to receive a discount for people under the age of 26.
    You can book tickets, reserve seats, or both.
    When booking a trip, you can request a Bahn-Tix. Then, prior to departure you can pick up the train ticket at any DB ticket machine for intercity rail traffic. At the ticket machine you can identify yourself with your BahnCard, credit card, Eurocheque card, or the order number shown in the booking data.
    Enhancements for Hotel Reservations
    You can sort hotels according to different criteria such as price, star rating, or distance from the address.
    Generic XI Interface to Rail Portals
    As an alternative to using a global distribution system (GDS) to include rail connections in Travel Planning, you can instead use rail portals for this purpose. Using SAP NetWeaver Exchange Infrastructure (XI), Travel Planning provides a generic interface for connections to rail portals. One such connection is the Deutsche Bahn Corporate Portal (also referred to as Bahn Internet Booking Engine = BIBE).
    Generic XI Interface to Flight Reservation Systems
    As an alternative to using a global distribution system (GDS) to include flights in Travel Planning, you can instead use flight reservation systems for this purpose. Using SAP NetWeaver Exchange Infrastructure (XI), Travel Planning provides a generic interface for connections to flight reservation systems. This enables you to book flights with low-cost carriers (LCC) and Web fare deals on the Internet. Travel Planning displays the offers of flight reservation systems as part of the fare-driven flight availability list, together with offers from a GDS.
    Enterprise Services
    Report programs and BAdIs (Business Add-ins) are available for the new Enterprise Services for the following process components:
    Expense and Reimbursement Management
    Travel Management
    Business Data Management
    Personnel Administration
    For more information, see HCM_SRV_CI_1: HCM, Enterprise Services 01 (New).
    Effects on Existing Data
    You can continue using existing travel data without restrictions.
    Effects on Customizing
    The following IMG activities are new:
    If you want to implement the other travel services in the Travel Request component, perform the IMG activities under Travel Request.
    To adjust the processes for the integration of rail portals, use the Business Add-in (BAdI) Adjust Processes for Integration of Rail Portals.
    To configure APIS, perform the IMG activities Define Data for Advanced Passenger Information System and BAdI: Adjust Creation of APIS Elements.
    To assign expense types to schemas, perform IMG activity Restrict Travel Expense Types for Trip Schemas.
    The following IMG activities have been extended:
    To define that users may not delete credit card receipts, perform IMG activity Set Up Feature TRVPA for Travel Expenses Parameters.
    To extend the additional receipt information with the participants in entertainment, perform IMG activity Field Control for Additional Receipt Information.
    To use Master Pricer, perform IMG activity Define Enterprise-Wide Control Parameters.
    See also
    For more information, see the SAP Library under Business Function Sets and Busines
    Regards
    Vijay

  • Portal patch issue - EP 6.0 SP2 Patch 41

    Hello Everyone,
    We are upgrading Portal Patch to 41 to enable compatiblity with
    Internet Explorer 7.0 . This is a high importance issue and need
    assistance as soon as possible. Here are the details .
    Existing Environment
    Portal Version: SAP EP 6.2.27.0
    SAP J2EE engine: Version 6.20 patch level 27 (87548.20 on Portal)
    SAP Basic Java Libs version 20
    JDK version - 1.3.1.18
    Internet Eplorer 6.0
    Upgrade Plan order of upgrade)
    SAP J2EE engine: Version 6.20 patch level 41
    Portal Version: SAP EP 6.2.41.0 - Patch 41
    Internet Explorer 7.0
    Summary of Installation:
    1.Installed patch level 41 for J2EE engine 6.20 - Successful
    2.Installed patch 41 on SAP EP 6.O SP2 - Successful
    3.Logging to Portal -Failed
    Error Descripton :
    After i restart my SAP J2EE engine(with 'go' files, since there is no
    startup framework) ; When i try to login to the portal ,the server
    shuts down automatically and i get the
    following error in browser "Service Unavailable 503! "
    SAP Notes Followed:
    1.Note 990763, 1012683 – Internet Explorer 7.0 compatiblity
    2.Central Note for Portal Patch 41: 1009776, 806271
    3.License key issue -Note 777681, 853649
    4.Upgrade J2EE engine – note 616501, 529088
    Steps for the Reconstruction 
    After i restart my SAP J2EE engine(with 'go' files, since there is no
    startup framework) ; When i try to login to the portal ,the server
    shuts down automatically and i get the
    following error in browser "Service Unavailable 503! "
    Can anyone help with this issue ?

    Hi Brad.
    I could activate the SAP * user and then was able to access the portal, as i told , Using CPPO tool somehow changed the database values and we lost content since there was no backup for that day.
    Thanks for your tips .
    Coming to portal patch 41 issue, here are the log files i got(since there are no trace files like those in NW'04)..
    ERROR.LOG
    Portal initialization in progress ...
    Loading core applications:
      Loading application: com.sap.portal.license.runtime
      Loading application: com.sap.portal.pcd.aclservice
      Loading application: com.sap.portal.pcd.basicrolefactory
      Loading application: com.sap.portal.pcd.basictransport
      Loading application: com.sap.portal.pcd.configservice
      Loading application: com.sap.portal.pcd.glservice
      Loading application: com.sap.portal.pcd.lockservice
      Loading application: com.sap.portal.pcd.plconnectionservice
      Loading application: com.sap.portal.pcd.softcacheservice
      Loading application: com.sap.portal.pcd.textrepository
      Loading application: com.sap.portal.pcd.traceservice
      Loading application: com.sap.portal.pcd.umwrapperservice
      Loading application: com.sap.portal.pcm.admin.apiservice
      Loading application: com.sap.portal.runtime.config
      Loading application: com.sap.portal.runtime.system.authentication
      Loading application: com.sap.portal.runtime.system.clusterinformation
      Loading application: com.sap.portal.runtime.system.inqmy
      Loading application: com.sap.portal.runtime.system.notification
      Loading application: com.sap.portal.runtime.system.permission
      Loading application: com.sap.portal.runtime.system.repository
      Loading application: com.sap.portal.umeregistration
      Loading application: com.sap.portal.usermanagement
    Loading services:
      Loading service: com.sap.portal.license.runtime|license
    May 2, 2007 11:15:49 AM # System_Thread_97     Fatal           [Portal.init] Application Broker - initialization failed.
    com.sapportals.portal.prt.runtime.PortalException: [Portal Application Broker] applications start failed
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1452)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.runtime.PortalException: [PortalServiceItem.startServices] initialisation failed:com.sap.portal.license.runtime|license
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:883)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sapportals.portal.prt.service.license.LicenseService of Portal Service com.sap.portal.license.runtime|license because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:689)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.service.ServiceException: Service not found: com.sap.portal.usermanagement.usermanagement
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:171)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sapportals.portal.prt.service.usermanagement.UserManagementService of Portal Service com.sap.portal.usermanagement|usermanagement because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:689)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:371)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.service.ServiceException: Service not found: com.sap.portal.runtime.system.repository.application_repository
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:171)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.getInstance(ApplicationRepositoryService.java:147)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.getRootURLContext(ParURLContext.java:49)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.lookup(ParURLContext.java:187)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.registry.PortalRegistry.getCentralConfigurationContext(PortalRegistry.java:145)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.getPCDContext(UserManagementService.java:603)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.readPCD(UserManagementService.java:1059)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:251)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService of Portal Service com.sap.portal.runtime.system.repository|application_repository because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:689)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.getInstance(ApplicationRepositoryService.java:147)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.getRootURLContext(ParURLContext.java:49)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.lookup(ParURLContext.java:187)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.registry.PortalRegistry.getCentralConfigurationContext(PortalRegistry.java:145)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.getPCDContext(UserManagementService.java:603)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.readPCD(UserManagementService.java:1059)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:251)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.service.ServiceException: Unable to create initial Application Repository structure
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.init(ApplicationRepositoryService.java:137)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.getInstance(ApplicationRepositoryService.java:147)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.getRootURLContext(ParURLContext.java:49)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.lookup(ParURLContext.java:187)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.registry.PortalRegistry.getCentralConfigurationContext(PortalRegistry.java:145)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.getPCDContext(UserManagementService.java:603)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.readPCD(UserManagementService.java:1059)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:251)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.service.ServiceException: Service not found: com.sap.portal.pcd.glservice.generic_layer
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:171)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.init(ApplicationRepositoryService.java:121)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.getInstance(ApplicationRepositoryService.java:147)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.getRootURLContext(ParURLContext.java:49)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.lookup(ParURLContext.java:187)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.registry.PortalRegistry.getCentralConfigurationContext(PortalRegistry.java:145)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.getPCDContext(UserManagementService.java:603)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.readPCD(UserManagementService.java:1059)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:251)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sapportals.portal.pcd.gl.PcdGlService of Portal Service com.sap.portal.pcd.glservice|generic_layer because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:689)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.init(ApplicationRepositoryService.java:121)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.getInstance(ApplicationRepositoryService.java:147)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.getRootURLContext(ParURLContext.java:49)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.lookup(ParURLContext.java:187)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.registry.PortalRegistry.getCentralConfigurationContext(PortalRegistry.java:145)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.getPCDContext(UserManagementService.java:603)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.readPCD(UserManagementService.java:1059)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:251)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.lang.NoSuchMethodError
         at com.sapportals.portal.pcd.gl.util.JarmAccess.startJarmComponent(JarmAccess.java:38)
         at com.sapportals.portal.pcd.pl.PlContext.lookup(PlContext.java:163)
         at com.sapportals.portal.pcd.pl.PlContext.lookup(PlContext.java:204)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.readXfsObjectFromPersistence(XfsContext.java:531)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChildAtomicName(XfsContext.java:434)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.lookupAtomicName(XfsContext.java:245)
         at com.sapportals.portal.pcd.gl.xfs.BasicContext.lookup(BasicContext.java:858)
         at com.sapportals.portal.pcd.gl.PcdPersContext.lookup(PcdPersContext.java:445)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:389)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1106)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1193)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1155)
         at com.sapportals.portal.pcd.gl.PcdGlSchemaContext.lookup(PcdGlSchemaContext.java:89)
         at com.sapportals.portal.pcd.gl.PcdSchemaManager.init(PcdSchemaManager.java:75)
         at com.sapportals.portal.pcd.gl.admin.Pcd.setupSchema(Pcd.java:394)
         at com.sapportals.portal.pcd.gl.admin.Pcd.init(Pcd.java:154)
         at com.sapportals.portal.pcd.gl.PcdGlService.init(PcdGlService.java:192)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.init(ApplicationRepositoryService.java:121)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.getInstance(ApplicationRepositoryService.java:147)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.getRootURLContext(ParURLContext.java:49)
         at com.sapportals.portal.application.applicationrepository.ParURLContext.lookup(ParURLContext.java:187)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.registry.PortalRegistry.getCentralConfigurationContext(PortalRegistry.java:145)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.getPCDContext(UserManagementService.java:603)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.readPCD(UserManagementService.java:1059)
         at com.sapportals.portal.prt.service.usermanagement.UserManagementService.init(UserManagementService.java:251)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:464)
         at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:163)
         at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:132)
         at com.sapportals.portal.prt.service.license.LicenseService.init(LicenseService.java:94)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1381)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    java.security.PrivilegedActionException: com.sapportals.portal.prt.core.PortalCoreInitializerException: Main initialization of plugin failed
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:134)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.lang.IllegalStateException: [Portal.init] Application Broker - initialization failed.
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:351)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    WARNING: Dispatcher could not be set up:
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    OUTPUT.LOG
    [OS: Windows XP] [VM vendor: Sun Microsystems Inc.] [VM version: 1.3.1_15-b01] [VM type: Java HotSpot(TM) Client VM]
    SAP J2EE Engine Version 6.20 PatchLevel 107279.20 is starting...
    Loading: LogManager ...
    Loading: SystemThreadManager ...
    Loading: ThreadManager ...
    Loading: TimeoutManager ...
    Loading: MemoryManager ...
    Loading: PoolManager ...
    Loading: PolicyManager ...
    Loading: IpVerificationManager ...
    Loading: ClusterManager ...
    Loading: ClassLoaderManager ...
    Loading: SwapManager ...
    Loading: LockManager ...
    Loading: FileManager ...
    Loading: R3StartupManager ...
    Loading: ServiceManager ...
    Loading core services:
      Starting core service p4 ... done. (609 ms)
      Starting core service monitor ... done. (985 ms)
      Starting core service log ... done. (891 ms)
      Starting core service dbms ... done. (1500 ms)
      Starting core service security ... done. (5344 ms)
      Starting core service naming ... done. (5156 ms)
      Starting core service file ... done. (5609 ms)
      Starting core service admin ... done. (6140 ms)
      Starting core service deploy ... done. (6578 ms)
    Core services loaded successfully.
    Loading additional services:
      Starting service runtimeinfo ... done. (0 ms)
      Starting service jms ... done. (8156 ms)
      Starting service appclient ... done. (7843 ms)
      Starting service telnet ... done. (7969 ms)
      Starting service shell ... done. (328 ms)
      Starting service ts ... done. (8656 ms)
      Starting service javamail ... done. (8625 ms)
      Starting service logviewer ... done. (8687 ms)
      Starting service eisconnector ... done. (8406 ms)
      Starting service http ... done. (1625 ms)
      Starting service PRTBridge ... done. (1750 ms)
      Starting service dbpool ... done. (10234 ms)
      Starting service rfcengine ... done. (10328 ms)
      Starting service ejb ... done. (18312 ms)
    Unknown version format. Default will be set.
    Unknown version format. Default will be set.
    Unknown version format. Default will be set.
    [com.sapportals.portal.prt.dispatcher.Dispatcher@7d6f07, 5/2/07 11:15:49 AM PDT, System_Thread_97] Exiting main initialization procedure because of exception:
      Starting service servlet_jsp ... done. (27718 ms)
    Additional services loaded successfully.
    SAP J2EE Engine Version 6.20 PatchLevel 107279.20 is running!
    PatchLevel 107279.20 December 07, 2006 09:44 GMT
      Checking for synchronization with cluster elements ...
      Synchronization of all applications completed! 
    >
    Login :Element 239753331 joined.    Wed May 02 11:15:53 PDT 2007
    Shutting down the J2EE Engine [Wed May 02 11:16:00 PDT 2007]
    Stopping additional services.
      Stopping: service jms ... done.
      Stopping: service eisconnector ... done.
    Shutting down service LogViewer
      Stopping: service logviewer ... done.
      Stopping: service javamail ... done.
      Stopping: service telnet ... done.
      Stopping: service appclient ... done.
      Stopping: service PRTBridge ... done.
      Stopping: service runtimeinfo ... done.
      Stopping: service shell ... done.
      Stopping: service rfcengine ... done.
      Stopping: service ejb ... done.
      Stopping: service dbpool ... done.
      Stopping: service ts ... done.
    ........Enterprise Portal is shutting down ........
    ...................Successful....................
      Stopping: service servlet_jsp ... done.
      Stopping: service http ... done.
    Additional services stopped successfully.
    Stopping core services.
      Stopping: service deploy ... done.
      Stopping: service monitor ... done.
      Stopping: service naming ... done.
      Stopping: service admin ... done.
      Stopping: service security ... done.
      Stopping: service file ... done.
      Stopping: service dbms ... done.
      Stopping: service log ... done.
      Stopping: service p4 ... done.
    Core services stopped successfully.
    Until i open the browser, portal is running , but as soon as i open browser , the message i get is "Enterprise Portal is shutting down " ; Could anyone please explain why the dispatcher is shutting down as soon as i open a browser??

  • EP6SP2 Portal patch 4prob: java developement - documentation not running

    hi,
    Before applying EP6SP2 portal patch 4 everything was working fine ... but after applying portal patch 4 <b>java developement -> Documentation and examples tabs</b>are not working ... It is giving <b>Portal runtime error ....... page could not create the iview.</b>
    has neone got this error before?
    rgds,
    Nilz

    Hi vibhu,
    this is the detailed error i am getting .....
    <i>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/developercontent/portaldevelopmentkit/Roles/com.sap.pdk.JavaDeveloper/com.sap.portal.pdk.Documentation/com.sap.portal.pdk.GettingStarted/com.sap.portal.pdk.GettingStarted
    Component Name : null
    Page could not create the iView.
    See the details for the exception ID in the log file
    </i>
    rgds,
    Nilz

  • Add Flight is not Functioning in ESS Travel and expenses

    Hi All,
        I had one issue in Travel and Expenses when I am creating Movement Order
        In ESS ->Travel and Expenses -> Movement Order ->
        After Completion Of giving the  -->General Data(Start date ,End date , address etc...)
        I am clicking  on ->Mode Of Conveyance
       Under Travel Services --> we had the tabs(Add Flight ,Add Taxi , Add Rail)  Add Taxi , Add Rail working fine
      When I am click on -->Add Flight (it is not functioning not throwing any error also)
    At the IE bottom of the line left side , it is showing  * javascript:void(0);*
            please share your ideas ....
    Regards,
    Sony.

    Yes Sidharth it is not working for evry user
    Before it's worked fine ,we didn't do any changes also ,just we done Personalization form Portal side
    Again I removed  all the changes what ever I done , even though it is not working.
    and it is not throwing any error also.
    Regards,
    Sony.

  • Error with the standard ESS, Travel & Expenses

    Hi All,
    We have deployed a ESS package in the portal. And we are able to view some services.
    We are getting the following error, with the Travel and Expense(All My Trips). Actually all the services under Travel and Expenses are giving some kind of errors. But i want to check the My Trips and Expenses one. It is giving the following error.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PTRM_WEB_CCNUM_MASKING'! Please verify, that your model is consistent with the ABAP backend: 'RDX'.
    Our HR SP is 34 and EPortal 7(NW 7) and ECC6 is SP 14.
    Can anybody suggest us in correcting this error.
    Thanks & Regards,
    Ravi

    Hi Ravi,
    The problem may be due to versions mismatch or you may need to apply SAP notes,
    check these
    Regarding Leave & Team calender
    /thread/824753 [original link is broken]
    Regards,
    Siva

  • ESS Travel Manager iview

    Dear All,
    The ESS Travel Manager iView (ITS based) is not getting diaplayed properly. Only a grey area is displayed in the content area. This is happening with some users only others are able to access the same but it takes time for them.
    Any idea why this is happening
    Regards,
    Samir
    Edited by: Samir on Jan 21, 2009 5:51 PM

    If it's only occuring for a subset of users then it could well be browser settings.
    If you're using a proxy server, then check there's a proxy expection stated for the domain of the ITS server.
    Set-up a proxy exception for the portal (if proxy is used):
    - In Internet Explorer, choose Tools -> Internet Options
    - Choose the Connections tab -> LAN Settings
    - In the Proxy server section, make sure u2018Bypass proxy server for local addressesu2019 is ticked and choose u2018Advancedu2026u2019
    - Enter the site within the u2018Exceptionsu2019 section
    - Click OK on remaining screens

  • Best Practice for Portal Patches and effort estimation

    Hi ,
    One of our client is applying the following patches
    1. ECC 6.0 SP15(currently SP14)
    2. ESS MSS SP15(currently SP14 with some level of functional customization )
    3. EP 7 SP18(currently SP14)
    We would like to kwow the best practice for applying portal patches and the effort estimation for redoing the portal devt on the new patch.
    o   What is the overall level of effort with applying Portal patches?
    o   How are all the changes to SAP objects handle?  Do they have to be
         manually re-entered?
    o  What is the impact of having a single NWDI instance across the
        Portal Landscape during the Patch process?
    Regards,
    Revathi Raju.

    Hi Revathi,
    o What is the overall level of effort with applying Portal patches?
    overall effort to apply the patch is apprx 1/2-1 days for NW7 system. This is exclude the patch files download because it's based on your download speed.
    o How are all the changes to SAP objects handle? Do they have to be
    manually re-entered?
    Depending on your customization. Normally it wont effect if you created the customzation application apart from SAP standard application
    o What is the impact of having a single NWDI instance across the
    Portal Landscape during the Patch process?
    Any change that related to NWDI, you might be need to re-deployed from NWDI itself.
    Thanks
    Regards,
    AZLY

Maybe you are looking for