Need info on Universal worklist

Hi all,
Need some info on universal worklist -
1. What is Universal worklist?
2. How do we configure it?
If someone has some good documents, please mail them to [email protected]
Kind Regards,
Ashwini.

hi,
The Universal Worklist enables SAP portal users to manage their work by bringing together assignments from different workflow systems, including:
       Workflow
       Alerts
       Knowledge Management (KM) notifications
       Collaboration Tasks
The Universal Worklist is used as the central access point to tasks, alerts, notifications. You can access the UWL to manage and track your tasks
For configuring UWL
http://help.sap.com/saphelp_ep60sp2/helpdata/en/ff/83fd4d5a644336b13ae54528cfef57/content.htm
http://service.sap.com/netweaver -> Media Library -> How-to Guides _> Portal, KM and Collaboration -> All ->Configuring the Universal Worklist.
Regards,
Ganesh N

Similar Messages

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

Launch URL/BSP from attachments link in workitem in Universal Worklist

Background info:
We have a custom business object. Default method on object in SWO1 is a custom display method. This display method returns a URL to a BSP.
When I open my workitem in SBWP and click the attachments link, it properly launches the URL which opens the BSP.
However, when I open same workitem in Universal worklist and click the attachments link, it does not properly open the BSP. It looks like it's trying to open a SAP GUI version of the object but nothing is displayed. When our developer puts a breakpoint in the ABAP code and we click the workitem link in UWL, the URL/BSP opens fine. So, UWL config must be doing something extra (added code? redirect?) that clobbers the URL/BSP launch. Anyone have any ideas/suggestions?
Thanks,
Matt
*Reminder, We are not trying to launch the BSP when you click the workitem link in the UWL list. This is the attachments link inside the workitem itself.

G'Day Matthew,
The reason this works from SBWP and not from UWL is because you have an ABAP session in between. You don't mention the type of attachment, but usually what gets executed is the default method of the object. Thus the UWL has to initiate an ITS/WebGUI session to execute the default object method - this method may contain code to launch a BSP but it still needs to get to the code to start with.
You need to find alternatives, see if Karri's suggestion does what you're after.
Cheers,
Mike

Universal Worklist items open in new window instead of existing frame

After our recent upgrade we noticed that workitems in Universal Worklist open in new window instead of existing frame. Do you know if there is a system or universal setting to make all the workitems open in existing frame? I know we can change the settings for parameters launchInNewWindow and openInNewWindow to "no" in XML files to fix this.   However, my concern is that I would need to do this for each and every task we use. (still doable but wondering if there is simpler solution)
Example:
    <ItemType name="uwl.task.webflow.TS12300097.SAP_R3_CUSTOM_DEV" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
      <ItemTypeCriteria systemId="SAP_R3_CUSTOM_DEV" externalType="TS12300097" connector="WebFlowConnector"/>
      <Actions>
        <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="WebDynproApplication" value="LeaveRequestApprover"/>
            <Property name="WebDynproDeployableObject" value="sap.com/ess~lea"/>
            <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
            <Property name="openInNewWindow" value="yes"/>
            <Property name="display_order_priority" value="5"/>
          </Properties>
          <Descriptions default=""/>
        </Action>
      </Actions>
    </ItemType>

We downloaded uwl.standard.xml from UWL admin. Made a copy and renamed file. Changed all "launchInNewWindow" from "yes" to "no". Uploaded new file in UWL admin. Re-registered systems, cleared cache. Not sure what exact line changed the behavior but the workitems no longer open in new window.
We are still experimenting with file in our sandbox environment.

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

PO Approval Items Workitems are not removed from the Universal Worklist UWL

Hi,
Certain of our purchase orders require approval, they are sent to the relevant approver via workflow to their SAP inbox (SBWP) and universal worklist.
When the user executes the workitem (Approve or Reject) The workitem should be removed from the universal worklist and SBWP when refreshed.
The problem we experiencing is that the Workitems are not removed from the UWL after they have been executed. The SBWP is behaving correctly and the items are removed.
It is not all the workitems that have this problem, only certain ones - but there is no pattern.
Thanks for the help.

Hi,
The user B approved the PR accessing the transaction SBWP or via PR transaction directly?
If via PR transaction directly, then your workflow needs a Wait Event step.
Regards,
Kleber

Universal worklist- search people

Hi,
I need inputs/suggestions regarding UWL people picker enhancements
Currently we are on EP 7.02 SP 7 version, and planning to upgrade to support pack 12.
So we saw a wiki on UWL people picker enhancements on Sp12.
http://wiki.scn.sap.com/wiki/display/BPX/Enhancements+to+the+Universal+Worklist+People+Picker.
It explains about activating UME company properties, currently we don't have.
We have two clients integrated to same Portal and user base is LDAP.
We use user administration in Portal only to assign Portal roles to LDAP groups.
Coming to current config of restricting Users while creating the substitution,
We defined trusted attribute "department" in system admin-->km content management repository-->Manage UME object settings, and assigned Users with a protal role having UME action searchrestircted to allow Users to search the User details from the same department while creating substitution.
Current configuration which I explained above will not work if we upgrade our Portal to SP12?
So, for the UWL people picker enhancement,Company concept needs to be activated and is mandatory? if that is correct,
setting UME company properties will create company groups, how we need to tag the LDAP users to this company groups?
Can we assign tam groups to company groups, so that respective clients can see the User details of the same client while creating substitution rule?
Please provide your thoughts and suggestions.
Many Thanks
Chandra.

Hi Naziem,
Read,
http://help.sap.com/saphelp_nw04/helpdata/en/a6/3aff38d9b149bea885c1a37357a1ba/content.htm
and
http://help.sap.com/saphelp_nw04s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm
regards
Juan
Please reward with points if helpful

Customizing of Universal Worklist (UWL) Preview

Hello,
i have to customize the UWL preview, that is shown in the portal for every work item below the list view.
The customization shall be done only for the current project, so there are only a few worksteps involved that should use the customized preview.
I already read the UWV configuration documentation, but i hav absolutely no clue how i can do the customization if it is possible at all.
What i have to achieve:
- remove Buttons from the workitem preview (e.g. forward)
- remove attributes from the workitem preview (e.g. priority)
- the configuration shall only be done for specific work items because other projects want to see the preview.
Can you please help or point me to some documentation/ guide?

have a look at these weblogs
Customizing Default actions of items in UWL
Customizing Default actions of items in UWL
Launching WebDynpro from Universal Worklist
Launching WebDynpro from Universal Worklist
ALERTS
Integrating Alerts into UWL - it's no problem!
Integrating Alerts into UWL - it's no problem!
Support for secondary methods in UWL!
Support for secondary methods in UWL!
Innovative ways to use alerts
Innovative ways to use alerts
Universal Worklist - when you only need a single tab
Universal Worklist - when you only need a single tab
Swathi
Do offer points:-)

Processing EIC follow up via the Universal Worklist (UWL)

Hi
We are implemented EIC (Employee Interationc Centre) ERP and have an issue whereby the follow up appears in both the agent inbox within EIC and the Universal Worklist. The workflow for follow up is WS61000086. How do we get the follow up to work from the UWL as well as the EIC agent inbox? At the moment if the user clicks on the work item in the UWL a blank window is opened 'Display Object' close window.
Many thanks
Julie

Hi,
You are most likely missing a proper configuration for the task in UWL. The UWL configurations are done in Portal in system admin -> system config -> UWL (->Manage item types). This will require some XML "coding" experience, since you would need to do a proper XML configuration for the task. Now I don't know that what should happen when the user clicks the task in UWL, since I don't know this workflow or this area. Is there some web application existing for this task, are you just supposed to open the SAP GUI for the task? In both cases it might also be possible to do the needed configuration in transaction SWFVISU. Basically you need to enter your task ID there and then configure what is the "visualization" for the task. After the SWFVISU has been done correctly, you need to re-register the workflow system (in system admin -> system config -> UWL), and this would create the XML configuration automatically.
Regards,
Karri

UWL/Universal Worklist/Substitution - Removing the "Rule Activation" column

Hi SDNers,
From the Universal Worklist, it is possible to access the "Manage Substitution Rules" screen, in which one can manager substitutions over its colleagues.
I would like to remove a column in the standard "My Substitution Rules" table : the "Rule Activation" column.
Is there a way to do it ?
Regards

Michael, you can do this in the UWL but only with a 6.40 backend (ex. ECC 5) with a specific patch level (can not remember that patch level).
Before this you need to set these substituion in the R/3 inbox.
This being said it is only for workflow task routing. If I read your message correctly you want a manager to assign his authorizations (roles in R/3 or the portal) to a secretary. This is not supported in any standard SAP (or portal) scenario as far as I am aware.
Cheers,
D.

Standard Portal activity report configuration and Universal worklist config

Hi,
I need help for follwong topics:
Standard Portal activity report configuration and Universal worklist configuration.
Thanks & Regards
Sushama Pandey

Hi
Check this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/904ca240-63bc-2a10-1c98-de81b6a045bf

LeaveRequestApprover : "Page cannot be displayed" in universal worklist

Hi,
I really need some help on the leave request approver application.
When the approver clicks on a request in his universal worklist, the LeaveRequestApprover should be called. In our case, we have a "Page cannot be displayed" error message.
We have upgraded our system form ECC5 to ECC6.
Is there some configuration to do?
Thanks a lot for your help.
Karim

Hello Karim,
Can you check the whether the TASK of that workflow is properly configured in SWFVISU with your application name/component name.
Please check and confirm.
Regards
Nizamudeen SM

Developing Third Party Connectors for the Universal Worklist

Hi,
We need to develop a third party connector for the Universal worklist.
In order to retrieve the workflow items we want to use a web service that will be developed according our needs.
The documentation that I found regarding the UWL states that in terms of connectivity we can use Web based protocols such as HTTP and Web Services, but i couldn't find any example for this, besides the SONIC.
Has someone already developed a third party connector? Examples?
Thanks in advance.
Best regards,
José

Hi,
Have a look at these PDFs...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/405729e9-314f-2a10-eab6-fcebe6fe8cba
http://help.sap.com/javadocs/nwce/current/uw/UWL%20Custom%20Connector%20API.pdf
Regards,
Srinivas.

Java Web DynPro and Universal Worklist Interaction

HI ESS/MSS Gurus,
Good day!
I am a workflow consultant who is working on an ESS/MSS project. I have already completed and tested (successfully) all of the workflows needed in the backend using the PTARQ and PTCOR applications. We are also successful in showing the work items in the universal worklist.
Now the question is, whenever we click on the work item, we encounter an error in the portal. Now, I need to determine the following:
1. How are we going to integrate the ESS/MSS portal with the execution of the work item in the universal worklist?
2. Do we need to develop custom Java web dynpro applications for the approval process of the leaves, or is there a standard offering from the ESS/MSS packages?
Your inputs are very much welcome.
Regards,

Hi Gurus,
Here is what we have done so far:
1. Implemented the details as indicated in note 779075 and changed the parameters defined in SWFVISU
2. Upon re-registering and clearing the cache from the UWL, we tested if the task will call the standard application for leave request approval. It returns the error Internal error. :
Item is null for action acknowledge, and for item type uwl
It seems that the xmls files are not being generated or read successfully. although when we check uwl.webflow.SAP_ECC_HumanResources, there is an updated xml file for the task
Questions are:
1. What checks do we need to execute between the back end, UWL and portal?
2. Whenever changes in SWFVISU are made, what items do we need to check to ensure that the changes are reflected in the UWL? I have read that SWFVISU helps the user do away with the tedious xml creation. How can we verify that the changes are implemented/updated in the xmls generated?
3. Any other items we need to look into?
Regards,

Integrating "Recent Notifications",- from KM intto Universal worklist

Hi There
Has anyone any experience with integrating The action inbx = "Recent notifications" from KM in the portal into the universal worklist so the users will get a complete picture of notifications from R/3 and also from KM in the portal... Is it duable..How, and is there any info on this..
Thank You very Much
Steen C.C. Hammer

Hi Steen,
Which version do you have?
Regards Ralf

Need info on Universal worklist

Similar Messages

Maybe you are looking for