Sub-set of Universal Worklist as a Item Specific Worklist

Hi
We are developing a bespoke system which will use SAP workflow to populate the UWL with tasks and notifications.  The tasks will refer to a specific item ie a single proposal and a user will receive tasks on more than one proposal.
The user will be able from their overall dashboard to view the UWL, however we are required to also show a task list within each proposal for tasks/notiifcations relating to that proposal only. 
I am sure that this must be possible as in the leave request application the manager sees a workist specific to absence approvals which is a subset of the items in their UWL.
How is this done - is it using the POWL functionality or something else?
Many thanks

Hi Claire,
The leave request list is a custom application and has nothing to do with workflow.
Leave requests are entered into the database, and can either be approved by executing the work item or by launching the leave request application compionent of MSS. Both do the same thing.
You would need to build something custom in the same way.
Regards,
Mike

Similar Messages

  • 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.

  • 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

  • To remove work item from Universal worklist

    Hi,
    Can we remove work item from Universal Worklist by deleting. We don't want to approve or reject them but want to remove from inbox.
    Is there a way for this?
    Regards
    PV

    Hi Parveen,
    check the below note
    check below note
    Note 49545 - Deleting unnecessary work items
    Koti Reddy

  • 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

  • Custom ItemTypes in Universal Worklist

    Hi Comunity,
    I have created two views in the Universal Worklist configuration that work just fine. Now I want to have certain items to only show up in one of those views. Therefore I have set the supported itemtypes parameter to the itemtype I want to show up in this view. Unfortunatelly the item type is none of the standard types. I have added one level of hirarchy by adding staff to the standard uwl.task.webflow item type. I have also tried to add an item type uw.task.webflow.staff into the file but this does not work either, there is no item showing up in my UWL.
    Please have a look at the xml, I have inserted some snippets.
    Any hint is welcome.
    Regards Nicolas
    Edited by: Nicolas Löwe on Oct 8, 2009 11:59 AM

    Hi I found the solution myself.
    I have done the configuration correctly. But the new Item Types do only appear when there are no other items in the cache.
    Cheers Nicolas

  • 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

  • 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

  • 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.     &#9679;      Function group and transaction SWK1 (for back end systems using WP-PI plug-in)
    2.     &#9679;      Function group SWN_UWL_WL (for back end system on release 6.40 and above, without the need of WP-PI plug-in)
    3.     &#9679;      Function group SWRC, SSCV (for all cases)
    4.     &#9679;      Authorization rights for SDTX
    User Mapping:
    1.      Navigate to User Administration ®&#61472;&#61513;identity Managementà User Mapping.
           2.      There are three scenarios:
    &#9675;     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:...&#9679;      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.     &#9679;      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.&#9679;      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.&#9679;      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 →&#61472;System Configuration →&#61472;Universal
    Worklist and Workflow →&#61472;Universal Worklist →&#61472;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.
    &#9675; System alias: SAP_ECC_Financials
    Connection types:
    &#9632; WebFlowConnector
    &#9632; AlertConnector
    &#9675; System alias: SAP_ECC_HumanResources
    Connection type WebFlowConnector
    &#9675; System alias: SAP_SRM
    Connection type WebFlowConnector
    Leave the Web Dynpro Launch System field blank for all system connections.
    With regards
    subrato kundu

  • 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

  • Configuration problem Universal Worklist (UWL)

    Hi,
    I'm trying to do the configure the Universal Worklist using the
    <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fa21a890-0201-0010-708b-d0cfc117e7cd">How to Configure the Universal Worklist.pdf</a>.
    Problem is that I can't find the 'Registration for Item Types of Universal Worklist Webflow' in System Administration -> System Configuration -> Universal Worklist.
    Does anyone know where it went or how I can make it visible again.
    Thanks in Advance,
    Jeschael

    Hi Jeschael,
    I have the similar kind of issue with my UWL.
    Could you please help in Configuring UWL.
    I will be grateful if you can share any docs or any sought of assistance will be appreciated.
    Screenshot for your reference:
    Thanks in advance.
    Srikanth Naidu. Akula

  • HT3349 How do you select a sub-set of cells from the entire document so you can print only those specific cells?

    How do you select a sub-set of cells from the entire document so you can print only those specific cells?

    There is no analog to MS Excels print range.  So the next best thing is to plan your data so that you don't need to use print range.  The next best thing after that is to select the range of cells you want to print, then copy, the switch to the application Preview, and create a new document from the clipboard (select the menu item "File > New from Clibboard") then select all, copy then paste to the destination (maybe an email) .
    You can also paste that portion of the table into another table (or a new table) by pasting values only

  • Error Naviating in Universal Worklist

    Hi All,
    If I click on an item in the universal worklist (i.e. trip approval) I am taken to the aproval screen here I get an option to 'Display Details in SAP GUI'.
    If I select this I am taken to the details screen.  If I then try to select back/cancel to exit SAP GUI I am taken to the ITS log-off page and not back to the universal worklist.  
    Does anyone know how to get the navigation back to the universal worklist to work?
    Many Thanks,
    Paul

    Hi Paul,
    Did you get a solution to ur problem?
    If yes, kindly share it please.
    Awaiting Reply.
    Thanks and Warm Regards,
    Ritu

  • Filtering in universal worklist

    Hi All,
    We are using Universal worklist for workflow approval. When I configure webdynpro application in "SWFVISU" using the workflow task and webdynpro application. I didn't give the system name.
    In portal we have five system landscape, so I i register the Item Types in potal it is registered for all system. During SAP audit, they have asked to use filtering.  Please let me know what is this filtering and how to use this.
    Further when i register a system landscape in universal worklist the is field called "Roles". Please let me know what is the purpose of this field.
    Thanks & Regards,
    H.K.Hayath Basha.

    Mark us answerd

  • 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>
        <!-- configuration node for local system gp portal,
         where SystemAliasfor_local_system_ is the alias of the local system -->
        <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}&amp;app.taskId=${item.activityID}&amp;"/>
                <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>

Maybe you are looking for

  • Multiple text fields in Print Module

    Allow multiple text fields in Print Module with flexible editing.

  • ICal in Lion - I want my monthly calendars on the left side back

    First, I agree with the frustrations I've read around multiple calendars and the fact that you can't easily swich between them anymore for adding new events (Not a smart move, frankly, but hey, Apple can do what they want, at least it seems like they

  • Enum value not displaying in view - correct method to display in column?

    Hello again Experts, Having trouble with certain columns not populating in my custom class. I know I must have entered them incorrectly, hoping someone can shed some light on it. Its a custom work item class, so I borrowed the Work Item Status proper

  • Tx2500 keyboard problem

    Hi guys, After a sudden crash of my tx2500 laptop, I cannot get the laptop turned on. The system doesn't boot at all,eEven cannot get into the bios screen. However, after one day, the system magically back to live. However, this time I got another pr

  • Lion mail for windows

    Howdy, I'm curious if anyone has any advice on how to achieve a Mac OS Lion similar look/functionality in a windows mail application. I want a stand alone application for windows 7but all the email programs I find are really cluttered and in some cas


HashFlare