Skip to Content
avatar image
Former Member

Error in UWL for MSS in Portal 7.4

HI

We are on Portal 7.4 and ECC EHP7, basic setting for UWL config under System Admin in Portal has been done, apart from that no other changes been made in SWFVISU and to the properties of PCD objects in Portal.

Working : Leave request respective to the Manager are appearing under UWL

Not Working : Clicking on any ling from UWL taking us to the same screen for leave requests.

SAP_ALL authorization has been provided to the user.

From HTTP TRACE I have found that WI_ID has been passing and it;s different for each link.

ex : /irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fevery_user!2fgeneral!2fdefaultAjaxframeworkContent!2fcom.sap.portal.standalonecontentarea?NavigationTarget=OBN%3A%2F%2FBOTechnicalName%3Demployee%2FOperation%3Dapproveleaverequest%2FBOSystemAlias%3DSAP_ERP_HumanResources&DynamicParameter=Operation%3Dapproveleaverequest%26BOTechnicalName%3Demployee%26wi_id%3D000000385118%26BOSystemAlias%3DSAP_ERP_HumanResources&PrevNavTarget=navurl%3A%2F%2F0e1456b4e0492c0d4a8d1286382b9d86&sap-obn-url=OBN%3A%2F%2FBOTechnicalName%3Demployee%2FOperation%3Dapproveleaverequest%2FBOSystemAlias%3DSAP_ERP_HumanResources&NavMode=1&CurrentWindowId=WID1420964796369

Any help ?

Thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jan 11, 2015 at 11:17 AM

    "Steps to clear the UWL cache:

    Please go to ""System Administration"" -> ""System Configuration"" ->-> Universal Worklist & Workflow-> Universal Worklist - Administration-> Click on cache administration page

    -> Click ""Clear Cache"" button."               

    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f4843e-314f-2a10-2a88-8c4afa20dda6?overridelayout=t…

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      HI

      Cache has been cleared many times,

      clicking on leave request tasks generating url with above format but with different WI_ID.

      But all links shows same request details which is the latest one from the list.

      Thanks

  • Jan 11, 2015 at 06:05 PM

    Hi Mohan

    I hope you are well and many thanks for using the SAP Discussion Forums 😊.

    In relation to the scenario that you have described you mentioned the following:

    • You are on Portal 7.4 and ECC EHP7, basic setting for UWL config under System Admin in Portal has been done, apart from that no other changes been made in SWFVISU and to the properties of PCD objects in Portal.

    • Working: Leave request respective to the Manager are appearing under UWL

    • Not Working: Clicking on any link from UWL taking us to the same screen for leave requests.

    Now based upon the extract you provided from the HTTP Watch Trace have you captured a default trace error log file yourself to ensure there are no accompanied underlying error exceptions?

    What is interesting here is that you mentioned no other changes apart from the upgrade have been performed.  So what we should have here is a decision task that then launches either a Web Dynpro ABAP or a SAPGUI or in turn raises an event.

    Kindly capture a trace and let me know if there are any underlying exceptions appearing.

    Kindly update me as per your findings.

    Kind Regards

    Troy Cronin - Enterprise Portal Support Engineer

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Troy Cronin

      HI

      Here is the log ..

      Problem occured while executing getItemsProxy for system: SAP_ECC_HumanResources
      [EXCEPTION]
      java.lang.Exception: Problem occured while creating JCO client for destination: SAP_ECC_HumanResources
      at com.sap.netweaver.bc.uwl.utils.r3.R3SystemInfo.createJCoDestination(R3SystemInfo.java:84)
      at com.sap.netweaver.bc.uwl.core.connect.abap.functions.UwlGetItemsProxy.execute(UwlGetItemsProxy.java:67)
      at com.sap.netweaver.bc.uwl.core.connect.abap.OptimizedRetriever.getItems(OptimizedRetriever.java:95)
      at com.sap.netweaver.bc.uwl.core.connect.webflow.WebflowConnector.getItems(WebflowConnector.java:2420)
      at com.sap.netweaver.bc.uwl.core.pull.PullChannel.getItems(PullChannel.java:57)
      at com.sap.netweaver.bc.uwl.core.pull.PullThread$1.run(PullThread.java:98)
      at com.sap.netweaver.bc.uwl.core.pull.PullThread$1.run(PullThread.java:76)
      at java.security.AccessController.doPrivileged(Native Method)
      at javax.security.auth.Subject.doAs(Subject.java:335)
      at com.sap.netweaver.bc.uwl.core.pull.PullThread.run(PullThread.java:76)
      at com.sap.netweaver.bc.uwl.core.ThreadManager$PoolWorker.run(ThreadManager.java:209)

  • avatar image
    Former Member
    Jan 15, 2015 at 02:21 PM

    Hi

    Facing these errors .. while accessing UWL...

    "SAP_ECC_HumanResources$WebFlowConnector" destination was created and required config was done under UWL.

    1) com.sap.engine.services.security.authentication.loginmodule.ticket [System [36]] Error: Error while creating assertion ticket on demand. Current principal is null.

    2) com.sap.security.core.server.destinations.service.AssertionTicketRetriever [System [36]] Error: Assertion ticket could not be retrieved. Error was null

    3) com.sap.security.core.server.destinations.service.AssertionTicketRetriever [System [36]] Error: Assertion ticket could not be retrieved

    Any help ???

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Mohan

      Many thanks for the response and update.

      In relation to your analysis findings you outlined the following exceptions being encountered:

      • java.lang.Exception: Problem occured while creating JCO client for destination: SAP_ECC_HumanResources

      In relation to the above kindly review and reference the following:

      Regarding this issue and the scenario that you are encountering your points of analysis regarding SAP Note 1133821 was correct as the UWL Destination Service Configuration is important to review.

      The RFC destinations have to be maitained so that the UWL can make functional calls to the backend applications. I believe on your system somehow the calls to the backend fail and thus you may need to check the configuration of the RFC destination as per the note.

      Check that after applying Note 1133821 the destination names and the UWL connector names exactly match, even considering case-sensitiveness. If your portal system alias (=UWL connector name) is for example XYZCLNT100, then the rfc destination name should be exactly XYZCLNT100$WebFlowConnector. Please correct the rfc destination accordingly.

      After you have checked/prepared the RFC destination for the future use please delete that connector in the UWL config UI (Portal->System Administration->System Configuration->Universal Worklist) with which you would like to use this RFC destination.

      After that

      - restart the portal cluster

      - recreate and reregister connector

      Now retest.  Are you still seeing the issue?

      Kindly update me as per your findings.

      Kind Regards

      Troy Cronin - Enterprise Portal Support Engineer