Hiding buttons on Universal Worklist

We currently migrated to EP6 SP2 and are now in the process of testing  the UWL used with this EP version.  We have discovered a number of differences between the versions used for EP6 and EP5.  Some of the new
functions need to be removed as we do not plan to roll them out for    
some time.                                                                               
We would like to make the following changes:                           
1.  Hide some tabs (e.g., Notifications)                               
2.  Hide some buttons (e.g., New Ad Hoc Request)                       
3.  Hide some columns (e.g., Due Date)                                 
4.  Hide the Personalize View link                                                                               
I looked at the iView properties on the portal                    (com.sap.netweaver.bc.uwl.uwl_iview) and was unable to find a way to   
make these modifications.If anyone knows how to do this, please let us know how to do it.,
Thanks!
VNU Basis Team

Hi,
you know this? https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to configure the universal worklist.pdf
Especially chapter 4, but look around...
Hope it helps
Detlev

Similar Messages

  • Workitem in universal worklist not refreshed after processing the workitem

    Hi,
    We are using EP 7.0, we are having a problem in refreshing workitem in universal worklist.  When a workitem in universal worklist is clicked a ABAP webdynpro application is opened in new window, this window has approve and reject button. Clicking on the approve or reject button completes the business process and workitem should be removed from the UWL. But in our case the workitem is still shown in the UWL and the user can again click on the same workitem and open.
    Has anyone has encountered this problem? Could someone let me know how to resolve this issue.
    Thanks & Regards,
    H.K.Hayath Basha.

    Hi,
    Just check the status of the workitem whether its approved or rejected  before opening the application. If its already approved
    or rejected dont open the application.We also faced the similar problem and avoid opening the work item instead of refreshing
    uwl.
    Because by configuration it is possible to reduce till one minute and frequent refresh of uwl will result in poor performance.
    You can give a try with writing code to refresh uwl once the workitem got approved or rejected.
    http://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/admin/IUWLAdmin.html
    Try using clear cache.
    Best Wishes
    Idhaya R

  • 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:-)

  • Substitution in universal worklist

    Hi,
    We have an issue in substitution in universal worklist.The problem is
    that we will able to create substitution rule in UWL after which when
    we refresh the button it is disappeared from the screen. I have
    enclosed the screen shot for your reference
    Please Suggest
    Regards,
    Prasath

    HI,
    HRUS_D2 has not maintained anything . what should i do
    Regards,
    Prasath

  • 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

  • Problem in Universal worklist configuration

    Hi,
    I wnt to register sap system.
    i have
    Navigated to System Administration  System Configuration  Universal Worklist and Workflow  Universal Worklist - Administration.
    Click new button and provided the following details:
    System alias : sapr3
    Connector type: webflow connector
    then i save and clicked on Register button. Then i get the following error message :
    Status
    Errors:
    System SAPR3: Tue Apr 21 17:05:04 GMT+05:30 2009
    (Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Tue Apr 21 17:05:04 GMT+05:30 2009
    (Connector) :com.sap.mw.jco.JCO$Exception:User RAJU has no RFC authorization for function group SWN_UWL_URL_GEN.
    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.<system_alias>' or 'uwl.alert.<system_alias>'.
    After configuration changes in the backend system, you must re-register the system.
    can i know what is the pbm.
    Raju

    Hi,
    i have used j2ee_admin login to register.
    it has registered successfully.
    But when i login with my user id, it is giving me following error.
    Exception type:com.sap.netweaver.bc.uwl.connect.ConnectorException Message:Tue Apr 21 17:39:39 GMT+05:30 2009
    (Connector) :com.sap.mw.jco.JCO$Exception:User RAJU has no RFC authorization for function group SWN_UWL_WL.
    can i know what is the prob.
    Regards,
    Raju

  • Universal Worklist Error

    I am receiving the following error when I try to forward a task through the Universal Worklist:
    This item is no longer valid. Select another item or refresh the item list view.
      Error Detail: Tue Aug 16 15:02:50 EDT 2005 (Item) Item is missing from the UWL persistent cache   
    I select the "Forward" button and then select a user from the dropdown list.  When I select "Submit" I receive this error.
    Does anyone have any experience working with the Universal Worklist and have encountered this issue?
    Please advise.
    Thanks.
    Jason

    we have a similar problem to this one. We have a user who is receiving the error message "Item is missing from UWL persistent cache". It seems that the old messages are displayed in the inbox initially until a refresh is automatically performed a few seconds later and it is not until this point that the current messages are displayed.
    Any ideas ? Thanks.

  • Can the universal worklist refresh automatically?

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

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

  • Customising Universal Worklist

    Hello All,
    I am attempting to customize the Universal Worklist for MSS.  There are various buttons such as 'Launch Web Dynpro' , 'Resubmit', 'Forward' and 'Assign to me' that appears for the manager when authorizing a leave request.
    Any Ideas on how I remove these buttons?
    Many Thanks,
    Nick

    hi,
    If you want to customise the UWL then, first you have to make a copy of the UWL iviews from Content Administration >Portal Content > Content Provided by SAP >End User Content >
    Standard Portal Users >iViews > Universal Worklist.
    From there you have select the iviews, copy it to your own folder , say 'Custom'. Apply the changes over there. Now Create an workset, set the entry points of the ivews and workset to true. Now create a role. Assign the workset to the role. Add the role to the user. Hence you can personalise your universal worklist.The below given link will explain all in detail:
    [http://help.sap.com/saphelp_nw70/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
    However to customise, you have to make the changes in the folder Content Provided by SAP itself, and then apply it. However this is not desired, since all the users added to the Enduser and Standard user role will be affected. For further information look into the file:
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/904ca240-63bc-2a10-1c98-de81b6a045bf]

  • 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

  • Universal Worklist menu does not appear

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

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

  • 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

  • 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

  • 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

Maybe you are looking for

  • Query to select values that match multiple ranges

    Hi, Oracle 10g. I have a table POINTS(ID INTEGER, CLASS VARCHAR2(15), CUMUL NUMBER(2,1), ...). In my application (APEX application), I show a list of point classes, order by cumul. SELECT CLASS FROM POINTS ORDER BY CUMUL;Then user can choose some ran

  • Remove Printer Name from Crystal Report

    How can i remove the printer name from the Crystal Report so that the PrinterName property of the CRAXDRT.Report object in the RDC SDK is blank WITHOUT having the "No Printer" Option checkbox checked? Here's the scenerio.  When I first create a Repor

  • Can I share music between Mac and iPhone using bluetooth

    While I use Home Sharing to allow my phone and my wife's to access an iTunes library housed on my Macbook Pro, when we travel by air obviously we do not have Wi Fi available. I know I can buy a "Y" cable to connect two sets of earphones to my Mac so

  • CHARSET for Korean language to open Korean .wft files in workflow.

    Hi, I want to open Korean .wft files in oracle workflow builder. For that, I had given 'KOREAN_KOREA.KO16KSC5601' (and also 'KO16KSCCS' as charset) as the NLS_LANG value in the window registry but I am getting following error once I logged in to data

  • Can't add a planning connection as a favorite in SmartView 11.1.1.3

    I am trying to add a Hyperion Planning connection as a favorite. I am able to add essbase connections without issue, however when I click on the Planning connections (accessed through Common Provider Connections) the option to add as a pre-defined or