Universal Worklist Iview

Hi Guys,
I have BI 7.0 Portal on Web AS 7.0 SP4, I getting error "Unable to perform the request. Try again and if the problem persists, inform your system administrator", when I try to check the "Universal Worklist" under "com.sap.ip.bi.business_explorer_showcase".
When Trace the iview location and iview from it's location it show me the results, but under above given role it does not work. Can any one tell me what could be reason I have even assigned the user to Iview permission as well with full control.
Thanks
Regards
Yasir Noman

Hi Santosh,
Have you installed CM onto the portal? UWL is installed with the CM components. If you would like to use UWL without then take a look at sap note 702255.
UWL should be in PCD in
pcd:portal_content/com.sap.pct/every_user/general/iViews/com.sap.netweaver.bc.uwl.iviews/com.sap.netweaver.bc.uwl.uwl_iview
Cheers

Similar Messages

Universal worklist iview didn't not display items of CRM workplace inbox

Hello experts,
I had configurated the UWL as follow steps:
1.Define our SAP system :
   CMDCLNT100
2. Create a system alias to uniquely identify the system:
    SAP_CRM
3. Define exact settings for technical connections:
    Has been difined.
4. Define how users are mapped:(not difined, we used sso with ticket, and the
    user name of all SAP system is same )
5.Test system connections:
   HTTP/HTTPS failed.But the SSO is working fine .
6. Add the new system to UWL configuration
    succssful.
7.Register work item types
   successful.
8.Connection status :
successful.
At the same time , the sso user XC03,XC04 both had the roles SAP_BC_UWL_SERVICE,SAP_BC_UWL_END_USER,SAP_BC_UWL_ADMIN_USER in CRM.
But there is no items in "task" tab of Universal Worklist iview of Portal user XC03, there are more than 10 items of CRM user XC03 in workplace inbox in CRM.
On EP7 SP6, CRM 5.0 .
Urgent!
What is the nature reason and solution ?
BR,
Jianguo Chen

Hi Karri,
could you please give me a link towards the Universal Worklist forum? I could not find it.
By EDIT I mean the editItem action. (http://help.sap.com/saphelp_nw73/helpdata/en/4a/f09ebd4a5a6d62e10000000a42189c/frameset.htm)
I tried to only configure the iView by the excludeActions property but I had the same problem, that the 1st iView acted according to the configuration, but the 2nd not.
In the Detail View, the editItem action can be found in the section "You can also" -> "Edit Task". When I click it, a popup appears where I can edit the task.
Regards,
Milena

Universal Worklist iView not visible///

Hi All,
We have installed EP & I have done the required configuration from SAP HCM module side & everything is working on fine except that I'm not able to see the My Organizer iView (Universal Worklist iView) in the ESS. I can see the other iViews like Employee Search, Working Time, Travel & Expenses etc. My workflows are also working properly just that the iView is not appearing on ESS. Please suggest what configuration is missing & how to do this config.
System Details:
EP version: 7.0
BP ESS/MSS: 11
EHR & SAP HCM package level: 24
Regards,
VJ

have you assigned the standard roles ie for portal and ess role
check in UWL administration
Does the same issue occur when you go to Content Administration and
preview the iview with the following PCD address (Standard UWL iview
provided by SAP)?
Portal Content/Content Provided by SAP/End User Content/Standard
Portal Users/iViews/com.sap.netweaver.bc.uwl.iviews/Universal
Worklist
check the roles and permission assigned to this user again
Please see the UWL Wiki @
http://wiki.sdn.sap.com/wiki/display/BPX/UWL%20FAQ *

Force universal worklist refresh when iView is opened

Hi Experts,
users are complaining because when they open the universal worklist iview, it still shows old work items, and sometimes they click on them by mistake raising some error message.
Although I tried cleaning the cache, setting the cache validity to 1 minute we are not getting the expected results.
What I would like to achieve is that when a user opens the uwl iview it remains "blocked"(not allowing the user to click on any task) until it is completely refreshed and al the work items are valid.
any suggestions?
We are using EP7.0 SP17.
Best regards,
Marco Ustarroz.

Hi Rakesh.
Go to System Administration --> System Configuration --> Universal Worklist & Workflow --> Universal Worklist - Administration
1) Select you System Alias and click in Re-Register.
2) Click in link Cache Administration Page, Select your system and click in Clear Cache.
Good Luck
Eduardo

Can the universal worklist refresh automatically?

When I open our universal worklist iview (EP 6), I need to click on refresh to get the most recent task list. Is there a way to force a refresh every time the UWL iview is opened?
Thank you.
Jeff

Hi all,
We faced simular problems. The UWL iview does not auto refresh at startup, only if you press the refresh button itself. Our problem was of course if someone approved an item an returned from the BXP to the iview he still saw the old item. The workaround is nifty an we got some SDN help as well. Thanks again Thorsten Bingmann! The clue is to make a hidden iview on the UWL iviews page. When you start the page or return to this page the hidden iview triggers the refresh button event. One remarkt though. In our BSP for approval we had to build in a 2 second delay at the end. If you approve an item it takes a second so if you return to the UWL page to fast the refresh comes to early.
I can provide the code for the iview if needed.
Deploy as par to portal an create an iview based on this par.
Enable EPCF Level to 1. Hide tray, heading and all other visible iview controls. Place UWL iview on top of page and hidden-refresh-iview to bottom of page to avoid ugly additional space on top of page. You will see solution working if after <waitduration-param> seconds mouse-cursor show working symbol and UWL will be refreshed.
Hope this helps

Initial view of Universal Worklist has no tasks.

Hi Gurus
We have a universal worklist with one tab only (Tasks)
When a user logs on and goes to Universal Worklist iView, there is no tasks displayed,
Once he clicks on the tab (Tasks) all the messages start to appear.
Please suggest some settings that would enable Universal Worklist to populate all the tasks when user goes on to Universal Worklist first time.
Thanks a lot
Sriram

Thanks for replying Sandeep
We are on Netweaver 2004 s SP17
to give you some more background on this, we have changed and uploaded a new configuration file to shows Tasks tab only on UWL,
I am not sure this issue was existing before we updated because there was Alerts tab which had not data and everytime, we had to click on the tasks tab.
Our new configuration is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'>
<UWLConfiguration version="1.0">
<NavigationNode name="Main_FSS" view="" referenceGroup="" visible="yes" keepItemCountUpdated="yes">
      <NavigationNode name="CombinedTask" view="DefaultView" referenceGroup="" visible="yes" keepItemCountUpdated="no" referenceBundle="tasks">
        <NavigationNode name="task2" view="DefaultView" referenceGroup="UWL_ADD_DYNAMIC_VIEWS" visible="yes" keepItemCountUpdated="no" referenceBundle="new_and_inprogress_tasks">
          <NavigationNode name="PersonalViewPlaceHolderTask2" view="" referenceGroup="UWL_PERSONAL" visible="yes" keepItemCountUpdated="no"/>
        </NavigationNode>
        <NavigationNode name="forwarded2" view="WorkItemsForwardedView" referenceGroup="UWL_ADD_DYNAMIC_VIEWS" visible="yes" keepItemCountUpdated="no" referenceBundle="tasks_forwarded">
          <NavigationNode name="PersonalViewPlaceHolderforwarded2" view="" referenceGroup="UWL_PERSONAL" visible="yes" keepItemCountUpdated="no"/>
        </NavigationNode>
        <NavigationNode name="futureTask" view="FutureTaskView" referenceGroup="UWL_ADD_DYNAMIC_VIEWS" visible="yes" keepItemCountUpdated="no" referenceBundle="tasks_for_resubmission">
          <NavigationNode name="PersonalViewPlaceHolderfuture" view="" referenceGroup="UWL_PERSONAL" visible="yes" keepItemCountUpdated="no"/>
        </NavigationNode>
        <NavigationNode name="completed2" view="WorkItemsCompletedView" referenceGroup="UWL_ADD_DYNAMIC_VIEWS" visible="yes" keepItemCountUpdated="no" referenceBundle="completed_tasks">
          <NavigationNode name="PersonalViewPlaceHolderCompleted2" view="" referenceGroup="UWL_PERSONAL" visible="yes" keepItemCountUpdated="no"/>
        </NavigationNode>
      </NavigationNode>
    </NavigationNode>
</UWLConfiguration>

Universal Worklist customization

Hi SAP Guru's
How to disable or delete links on the universal Worklist iview , We are getting links like
Display Details in SAPGUI
Manage Attachments
Create Ad-Hoc Request
View History
Document Database W:DD7E40D33956783462384182786784EB4
I want to disable/delete some links, Please help , how it can be done
Thanks & Regards
Vinay Patel

Hi,
In Universal Worklist iView, Specify the value for the proeprty "List of UWL Actions to Exclude" as manageAttachments,uwlTaskWizard,launchSAPDetails.
To determine the action name you want remove , Refer this
[UWL FAQ|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bpx/uwl+faq] .
With Regards,
Laksh.

Universal worklist administration iview error

Friends,
I have installed EP 7.0 SP13 and when i click Universal worklist administration iview in system administration i am getting Portal runtime error. Could anyone help me on this . what might be the reason for that error.
Regards,
Arun

Harish,
Please post the error here.
Chintan

Runtime error in Universal Worklist in portal

Hi!
An error occurs when I open the page Universal Worklist -
Administration under System Administration > System Configuration >
Universal Worklist & Workflow. The error message is:
Portal runtime error.
An exception occurred while processing your request. Send the exception
ID to your portal administrator.
Exception ID: 09:44_02/10/08_0004_221082950
Refer to the log file for details about this exception.
This error is also displayed when opening the page Portal Eventing,
Portal Navigation under System Administration > Support > Web Dynpro
Test Tools > Application Integrator Tests.
The portal UME is configured with ADS as data source and we are using
the dataSourceConfiguration_ads_readonly_db_with_krb5.xml configuration
file. Single Sign-On using SAP logon tickets with user mapping to
reference system is also implemented.
Users have different users IDs in the SAP System than in the portal,
and scenario 2 from SAP Help "Single Sign-On to SAP Systems"
(http://help.sap.com/saphelp_nw04/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm) is implemented
"Scenario 2: Single Sign-On using SAP logon tickets with user mapping."
The problem occurred after changing the UME with ADS and implemented
Single Sign-on.
Error messages from log:
Date : 10/03/2008
Time : 10:08:56:057
Message : Content pass of Application Integrator failed.
Component Name:       com.sap.portal.appintegrator.sap.WebDynpro,
Context Name (iView): pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch,
Top Layer:            WebDynpro/TopLayer,
Producer ID (FPN):    null,
System Alias:         SAP_LocalSystem,
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(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)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Severity : Error
Category : /System/Server
Location : com.sap.portal.sapapplication
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007830000B6B800045854D84A3E79
Source Name : com.sap.portal.sapapplication
Argument Objs : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(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)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Arguments : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(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)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 32121
Source : com.sap.portal.sapapplication
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder
Date : 10/03/2008
Time : 10:08:56:026
Message : Cannot provide backend user ID and password for user "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder") for system "SAP_ECC_REFERENCE" because these credentials could not be found in the user mapping data.
Severity : Info
Category :
Location : com.sap.security.core.umap.imp.UserMappingDataImp.enrich(Properties)
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007820000B6B800045854D849CB92
Source Name : com.sap.security.core.umap.imp.UserMappingDataImp
Argument Objs : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Arguments : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 32121
Source : com.sap.security.core.umap.imp.UserMappingDataImp
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder

Hi,
Check the logon type for systems SAP_LocalSystem and SAP_ECC_REFERENCE which must be set to SAPLOGONTICKET not UIDPWD.
It basically fails since the password doesn't exist for the mapping, as it is only dependent on trust.
There was a change in a recent SP which added an extra check in this area.
Dagfinn

Universal Worklist menu does not appear

Hi All
I still have same problem. We are on SP14, EP6. My id is in admistrave group
It looks strange, There is no Universal Worklist & Workflow menu under detail navigation bar.
I don't see Universal worklist & workflow menu under the the following ..System Administration -> System Configuration
I can see the following in System admin-->System config ..system landscape, System landscape overview, keystore admin, UM config, service config, KNowlegement management(content management, collaboration, index admin)....strange ...Universal worklist & workflow menu missing.
As suggested above, i also refreshed the UWL service via System Administration -> Support -> Portal Runtime.
Click on Application Console under "Portal Anywhere" Admin Tools. Select com.sap.netweaver.bc.uwl and click on show. Refresh and restart the services.
It looks like Knolwdge management component is installed as i see the the memnu for knowlege management. Under
System Administration -> System Configuration ...There is Knowledge Management side menu where i can see Universal worklist ( THere are CM, Collaboration,Index admin, Portal app, WF also listed)
But still Universal Worklist & Workflow menu does not appear.
Any suggestions. Thanks again.

HI,
Add eu_role to the user. The home workset will be added to the user. Under home->work you will find the UWL iview.
or
You can find the UWL iview in Portal content -> content provided by SAP-> End user content -> Standard portal users -> iviews -> com.sap.coll.iviews

Notifications in Universal worklist

Hi all,
In the Universal worklist we would like to display the notifications whenever a document is updated or modified in Knowledge management. I have gone through the SDN links and help documentation but still I am not clear.Please guide me step-by-step how we will get the notifications automatically into the Universal worklist.
According the few links I understood that we can get the notifications through"ActionInboxConnector" and "KM Recent Notifications iView"......
Please provide me your valuable help..
Thanks in advance
Regards,
Sundar

Use this document to configure UWL
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3461636-0301-0010-3787-978f5ac8bd45
notifications tab will automatically comes in UWL
check this link
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/ad743c74fa6449e10000000a11402f/frameset.htm
in EP 7 KM notifications are integrated in the Universal Worklist (UWL).
You can now find the notifications in the UWL (in the standard configuration, at Start page => Activities => Overview).
Regards
Krishna.

Cannot open GP process task in universal worklist.

Hi all,
    I cannot open GP process task in universal worklist.It says:"Could not retrieve process instance: contact your system administrator".But i can open the task in Runtime task.
i configure the universal worklist by following this link:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/ef06a7860c7061e10000000a1553f6/frameset.htm
I also create a simple GuidedProceduresConnector and doesn't change the xml file,but it doesn't work,either.
our portal is SP11.
Can anyone help me?
Thank you~!
Best regards
delma

Hello Delma,
Check out SAP note 1104652.    It discusses some changes for the uwl configuration file.   I just did this on a local installation of CE and used the following XML for my GP actions. I just uploaded a paper on this - it should be on SDN within a couple of days and I can get you the link.
The trick is that the name of your GP alias in UWL administration must be included in the XML. The note explains this and there is an example to download. Also, in my example the iView for the portal content to start the GP had to be changed - but that could be due to my local installation.
Check out this note and this XML and let me know if it helps.
Best regards
Ginger
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'
>
<UWLConfiguration version="2.0">
<ItemTypes>
    
    <ItemType name="uwl.task.gp.GPSystem" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
      <Actions>
        <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no"
launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.folders.pages/com.sap.caf.eu.gp.pages.procinstance2"/>
            <Property name="DynamicParameter" value="app.processId=${item.processID}&app.taskId=${item.activityID}&"/>
            <Property name="System" value="SAP_LocalSystem"/>
          </Properties>
        </Action>
      </Actions>
    </ItemType>
</ItemTypes>
<Views>
    <View name="uwlTaskGPView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.gp.GPSystem" columnOrder="subject, process, creatorId, createdDate, dueDate, status" sortby="dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="no" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="new" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom">
      <Descriptions default="Guided Procedures">
        <ShortDescriptions>
          <Description Language="de" Description="Guided Procedures"/>
          <Description Language="en" Description="Guided Procedures"/>
        </ShortDescriptions>
      </Descriptions>
      <DisplayAttributes>
        <DisplayAttribute name="phase" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
          <Descriptions default="Phase">
            <ShortDescriptions>
              <Description Language="de" Description="Phase"/>
              <Description Language="en" Description="Phase"/>
            </ShortDescriptions>
          </Descriptions>
        </DisplayAttribute>
        <DisplayAttribute name="process" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
          <Descriptions default="Process">
            <ShortDescriptions>
              <Description Language="de" Description="Process"/>
              <Description Language="en" Description="Process"/>
            </ShortDescriptions>
          </Descriptions>
        </DisplayAttribute>
      </DisplayAttributes>
    </View>
</Views>
</UWLConfiguration>

SAP Press book on Universal Worklist

Hi all,
I have just started writing a book for SAP Press on the Universal Worklist, to pass along some of what I have learned when working with the portal these past 5 years or so (anyone else remember EP 4.5?)
I've put up a blog entry at
<a href="http://www.fortybeans.com/">http://www.fortybeans.com/</a> and if you click the <a href="http://fortybeans.wishconsultants.co.uk/item/2007/2/6/universal-worklist-book-for-sap-press">Read more</a> link you can see the proposed chapters and sections I will be writing.
I'd really appreciate any feedback any of you can give me - I want to make this the best possible book of its kind, and the only way to do that is to find out what people want from the book and then to give it to them. Maybe this could be the first book from SAP Press with "Powered by SDN" on the cover?
Let me know what you think,
Darren

First off....EP4.5?....yep...when it was a Top Tier product. I was working on Workplace 3.0 (bootcamp) at the time....one week later, SAP and Top Tier announce the joint formation of the company "SAP Enterprise Portals" with their flagship product EP 5.0. Ahhh those were the days. I really want to meet the person who came up with calling it "portal-S" because I spent countless time explaining why the product was "Enterprise Portal" and not "Enterprise Portals". That was only compounded once SAP bought Top Tier outright, brought EP5.0 back into SAP proper and folded the "SAP Enterprise Portals" company. Ugg....anyways...
The book sounds great. I too have fought in the trenches and wrestled with the UWL. It is great when it is used strictly as intended and with the limitations it might have. Past that....let the fun begin!
I read your rough outline. Some chapters/content I would really like to see....
- some basic coverage on Workflow (what it is, how it works, etc).
- some explaination of "webflow", how it got started and where it is today
- how workflow correlates to what the user sees in the UWL
- limitations of the UWL based on support package level ( this is a big one!!! trying to use attachments now...nope...can't until the next SP level unless we backport our own custom webdynpro...that's not fun to find out 2 months in! haha)
- really good examples of customizing items to launch one way in the portal versus another way within the backend inbox (ie. uwl xml config vs. config in the backend) and show ways to launch various SAP apps (dialog in SAP GUI, ITS service, webdynpro, etc). from UWL items.
- same as above but show how to launch NON-SAP apps (we have a situation now where we have a UWL item that launches a Flex application and passes an order number to it)
- similar to the above two, what's possible to pass across from the UWL to whatever through the portal (like UWL to an iView and on to the underlying application)...figuring out how "DynamicParameters" works is new to lots of people who might not have web dev background and/or understand the construction/structure of a URL query string
- some information along the lines of "UWL launched an item/action out to some app, but how does the workflow status get updated to that fact?" ie. what makes the round trip complete?
- a really good BIG, real world example showing multi-system (CRM-to-ECC-to-APO-to-SRM-to- etc) workflow and how the UWL makes it all much easier and fluid (in theory...haha)
That's just a few off the top of my head that seem to always be sooo much fun with the UWL.
Good luck on the book! Looking forward to it already!

Universal WorkList (UWL)

Hello all,
Wanted to verify a quick thing from you regarding the sub-views within the Tasks category in UWL. From my knowledge, if we want to have any particular sub-categories (sub-views) such as "Vacation Approvals", we have to code and define this category in XML and specify the Task IDs which go under this category. Please let me know if I am wrong.
Now, we have a situation where there is a completey new workflow created which involves a new Task ID. Say for example, "Training Approval". Since this Task ID is not defined yet in XML, where does the task item go? For this sub-category do we have to code the XML again, or is this sub-category created automatically in the UWL for the end-user.
Currently in the MDT and Business Workplace, sub-categories are created automatically and do not require any maintenance effort in terms of determining which tasks id go under which sub-category. Is it the same in UWL?
Really appreciate your assistance. Thanks!
Aniruddh

hi
The Universal Worklist allows the administrators to override the standard task mappings to force a certain ITS template to be called for certain workflow tasks
all your xml files location
>Server>\SAPPRT\ROOT\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\portalapps\com.sapportals.pct.emp.universalworklist\
e.g
<?xml version="1.0" encoding="utf-8"?>
<mappings>
<mapping logsys="" task="" template="" iview="" javaiview="" url=""/>
<mapping logsys="" task="" template="" iview="" javaiview="" url=""/>
<mapping logsys="" task="" template="" iview="" javaiview="" url=""/>
</mappings>
also refers the links below
http://help.sap.com/saphelp_nw04/helpdata/en/39/a1bb5c4c0d4ab4a417e87ef35f1efa/frameset.htm
Hope this helps u
don,t forget to give points
With regards
subrato kundu

Universal Worklist Configuration

Hey guys
Please can someone tell me where I can find a universal wordlist config guide for EP7.0?
Many thanks in advance
Jo-lize

Hi
This are the steps need to be followed.please do give full points
The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the Enterprise Portal. It collects tasks and notifications from multiple provider systems SAP Business Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.
Administration and configuration for the Universal Worklist (UWL) is described.
General Prerequisites
1.     As an administrator, you have full administration rights for the Portal and the required business workflow rights in back end system (reference roles such as SAP_BC_BMT_WFM_UWL_ADMIN and SAP_BC_UWL_ADMIN_USER). Refer to SAP note 941589.
Summary
Symptom
UWL administrative and/or end users are not allowed to perform or look up business workflow functions or data in the backend system.
Reason and Prerequisites
Corresponding adminsitrative and end users in the backend systems are created from scratch and have zero initial authorization.
These roles are provided as an option to enable UWL administrative and end user authorization to readily utitlize the APIs of the SAP Business Workflow and relevant basis components remotely.
(Note: Usually these roles are not needed as backend user is already assigned with roles that have sufficient authorization.)
Also refer to BWF note 938717 for the corresponding roles required by business workflow.
SAP_BC_UWL_ADMIN_USER
For UWL administrative user who mainly deals with business workflow system registration.
SAP_BC_UWL_END_USER
For UWL end user to carry out all business workflow actions currently supported in UWL.
Solution
The roles can only be imported with a support package
Header Data
Release Status:     Released for Customer
Released on:     25.04.2006 04:57:52
Priority:     Recommendations/additional info
Category:     Advance development
Primary Component:     EP-BC-UWL Universal Worklist
Releases
SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700
Highest Implemented Support Package
SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     640     SAPKB64019SAP_BASIS     700     SAPKB70008SAP_BASIS
Summary
Symptom
This note delivers two roles (PFCG) with the authorizations required to display and edit Business Workflow work items in the universal worklist.
SAP_BC_BMT_WFM_UWL_ADMIN
This role has the workflow authorizations required to perform the configuration for the Business Workflow connection in the universal worklist. These are authorizations for Business Workflow interfaces on the back-end system. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
SAP_BC_BMT_WFM_UWL_END_USER
This role has all workflow authorizations required by end users to be able to edit Business Workflow work items with the universal worklist. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
You can either use the two roles directly or as templates for your own roles.
Note 941589 contains more information about roles with authorizations for the universal worklist.
Other terms
Universal worklist
Solution
The roles can only be imported with the relevant Support Package.
Header Data
Release Status:     Released for Customer
Released on:     20.04.2006 07:43:26
Priority:     Recommendations/additional info
Category:     Advance development
Primary Component:     BC-BMT-WFM Business Workflow
Secondary Components:     EP-BC-UWL Universal Worklist
Releases
SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700
Highest Implemented Support Package
SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     700     SAPKB70008
Related Notes
941589 - UWL: administrative and end user roles
Attributes
1.     Make sure that each user is known to all connected SAP systems as per role requirement (make sure that there is one-to-one mapping between the portal user and the backend user)
If an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well. User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
2.      Each connected SAP system for back end system (below release 7.0, WP-PI plug-in 6.0) has the connection to its respective SAP Internet Transaction Server (ITS)
Authorizations needed for working with Business Workflow
Normally, when the corresponding back end system user already has the correct authorization to work on the Business Workflow directly, no additional setup is required when working in UWL. However, manual configuration to assign RFC access authorization to the following function groups may be needed (Note: this is not common):
1.     ●      Function group and transaction SWK1 (for back end systems using WP-PI plug-in)
2.     ●      Function group SWN_UWL_WL (for back end system on release 6.40 and above, without the need of WP-PI plug-in)
3.     ●      Function group SWRC, SSCV (for all cases)
4.     ●      Authorization rights for SDTX
User Mapping:
1.      Navigate to User Administration ®identity Managementà User Mapping.
       2.      There are three scenarios:
○     Portal user ID is different than the back end SAP user ID and back end SAP user IDs are different in all back end SAP systems connected to the portal (UIDPW)
1.      Maintain the user mapping for each portal user corresponding to all the respective back end systems
2.      Portal user ID is different than the back end SAP user ID and backend SAP user ids are the same in all back end SAP systems connected to the portal (logon ticket)
Maintain the user mapping for each portal user to the reference system
3.     Portal user ID is the same as the back end SAP user and back end SAP user IDs are the same in all back end SAP systems connected to the portal (logon ticket)
1.       No user mapping is necessary
User Permissions
According to the prerequisites, if an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well.
User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
     Procedure
       1.      Navigate to System Administration ® System Configuration ® Portal Content. Open the folder where the existing systems were created.
       2.      From the available system list, click with the secondary mouse button on the system name and choose Open ® Permissions.
       3.      Assign permissions. Make sure that under the Administrator column you assign Read permissions for the assigned role (for example for role eu_role). Also mark the check box End User.
       4.      Choose Save.
     Registering the Provider Systems
Each UWL iView can retrieve work items from multiple Business Workflow back end systems. Register each back-end connection to be used with the following procedure:
On the port...
       1.      On the portal, choose System Administration ® System Configuration ® Universal Worklist and Workflow ® Universal Worklist Administration.
The Universal Worklist Systems list appears. Here you can define connectors and systems as item providers for the Universal Worklist.
       2.      To add a new entry, choose New. To edit existing information, select (highlight) the row and choose Edit.
       3.      To save the current system registration, choose Ok.
       4.      Multiple system connections are defined by repeating the above steps 1 to 3.
Table describing the parameters
Parameter     Description and Use
Connector     This is the identifier with which the connector is registered. It indicates the type of items retrieved through the connection. For example: WebFlowConnector.For connector types WebFlowConnector or Alert Connector item types have to be registered with the UWL service after defining a new system connection.
Configuration Groups     Leave this blank, when working with the default UWL iView. You can add a number of configuration groups separated by commas but only one configuration group per iView. first installed, one UWL iView is defined. The System Configuration Group property for that iView is empty (blank). This means that no System Configuration Group is named, but in effect there is only a single group. The default behavior for the blank setting is this: when any user logs onto the UWL iView, UWL tries to log that user onto all registered back end systems. There is a limitation with the blank setting. When a large number of systems are accessed during log on, the overall portal load is increased. Also, the user receives error messages from those back end systems that have no user account for the particular UWL user. For large system landscapes do the following:...       1.      Partition back end systems into groups. This is accomplished by creating additional UWL iView instances, each of which refers to a specific group of backend systems. The group is defined, using the System Configuration Group iView property.       2.      Then use the value of the System Configuration Group property when registering back end systems by placing it in parameter Configuration Group, when you register the SAP system.
System alias     The name of the alias for the back end system, as defined in the system landscape. The length cannot exceed 25 characters.If Web Dynpro applications are configured on a SAP NetWeaver Application Server which is different from the SAP NetWeaver Application Server of the system alias, then specify that system alias as a Web Dynpro system
Web Dynpro Launch System     Enter the Web Dynpro system name if the SAP NetWeaver Application Server for the system is not the same as that running the Web Dynpro.Leave empty otherwise
User Roles     Restricts who can get work items via the user role. For example, you can assign a portal role here, such as buyer. Only users with the role buyer will see items from the provider system in UWL.You can have multiple user roles separated by semi-colon. By specifying user roles for the portal users, it can be restricted as to who gets the work items in UWL. For example, you can assign a portal role to a user, such as buyer. Only users with the role buyer will see items from a system, for example, B7QCLNT000 in UWL.
Pull Channel Delta Refresh Period (in Seconds)     Delta Pull mechanism of UWL enables new items to be fetched from the back end SAP systems every minute by default every 60 seconds, and every 30 seconds for alerts. However, this can be configured. The user does not need to use the refresh function to update the inbox. Once items are retrieved, timestamps are updated for the users whose items are successfully retrieved. These retrieved items are updated in the UWL cache. Setup necessary from Business Workflow to enable Delta Pull MechanismSome configuration settings are required if you use the UWL and the Extended Notifications for SAP Business Workflow. Define the following two batch jobs:...●      Background job (for example UWL_DELTA_PULL_1), consisting of a single step of ABAP report RSWNUWLSEL in FULL mode, using a report variant.Run the job once a day.1.     ●      A background job (for example UWL_DELTA_PULL_2), consisting of a single step of ABAP report RSWNUWLSEL in DELTA mode (default mode is delta, so report variant is optional).Run the job every one to three minutes (depending on the performance of the back end SAP system).Setup necessary from UWL to enable Delta Pull Mechanism The UWL service user in portal, with user id uwl_service, has to be granted access to the corresponding back end systems. This is a predefined service user provided by UWL. When the back end system is configured in the UWL administration page, an automated process is triggered to create a corresponding UWL service user in the back end system.Check role assignments and profiles status of this automated generated UWL service user and perform user comparison if necessary.●      If SAPLogon ticket is used (without using user mapping), you first create the system entry. A message about uwl_service user appears. Then in the back-end system give the uwl_service user an initial password. Now edit the system entry.●      If user mapping is used, you can first configure the back end system in the UWL administration page. Then access the respective back end system to initialize the password for the user uwl_service. Then, do user mapping in the portal as usual for service user uwl_service.In case uwl_service fails to be created in the back end and does not exist, you can manually create a back end user with the id uwl_service and assign the role SAP_BC_UWL_SERVICE and the rights as other end users.ORMap uwl_service to an existing back end user. Make sure that there is no multiple user mapping (there must not be two portal users mapped to the same back end user). This back end user must have the role SAP_BC_UWL_SERVICE.
Snapshot Refresh Period (in minutes)     All items at the current time are fetched from the backend (for example from the SAP Business Workflow). The cache is synchronized thereafter. New / modified / deleted / updated items are fetched every session (every log on) if you leave the field value empty or enter a negative number.To specify a particular time frame for which the refresh occurs, enter the number of minutes
The above registration procedure is usually sufficient to use a UWL iView. Item type retrieval and registration requires a connection to the systems and may take a couple of minutes.
For each system, they are generated as the configuration named uwl.webflow..
In Manager Self-Service (MSS), the Universal Worklist groups together in Workset: Work
Overview the various workflow tasks and alerts that are relevant for a manager.
The standard MSS delivery includes the configuration file com.sap.pct.erp.mss.001.xml for the universal worklist.
1. In the portal, choose System Administration →System Configuration →Universal
Worklist and Workflow →Universal Worklist →UWL Systems Configuration.
2. Create the following system connections:
If you have already registered a suitable connector to the system connected to
the system alias, the existing connector is sufficient and you do not have to
register an additional one.
○ System alias: SAP_ECC_Financials
Connection types:
■ WebFlowConnector
■ AlertConnector
○ System alias: SAP_ECC_HumanResources
Connection type WebFlowConnector
○ System alias: SAP_SRM
Connection type WebFlowConnector
Leave the Web Dynpro Launch System field blank for all system connections.
With regards
subrato kundu

Universal Worklist Iview

Similar Messages

Maybe you are looking for