Universal Worklist refresh delay - Reduce default time

Hi
We would like to reduce the Universal Worklist refresh from the current default of 5 minutes to 1 or 2 minutes.
The items should appear immediately being avaialble in the SAP R/3 System.
Any ideas on how to achieve this in the Portal (EP 7 SP17)?
Regards
Chandu

Hi Chandu,
I think it may not be possible but you can implement delta pull mechanism where you can update uwl for lessthan 1minuite also
have a look
http://help.sap.com/saphelp_nw04s/helpdata/en/eb/101fa0a53244deb955f6f91929e400/frameset.htm
Koti Reddy

Similar Messages

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

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 Refresh Problem

Hi All,
I got a Problem with the Workitem not showing up in the universal worklist. The workitem appears in the backend but its not created in UWL. However it is created when configuration object is delted and uploaded again. But it is not refreshed automatically.
Any help on this will be greatly appreciated.
Thanks ,
Rakesh.

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

How to call / execute BPM process out of portal (Universal Worklist)

Hi,
at the moment I try to get fimilar in working with bpm processes. In this regard, I try to execute a process outside the portal.
I always have to login at the portal, go to the Universal Worklist, refresh the list and execute the previously started process. But in future that would NOT be the prefered way for the user.
May anybody help me?
Thank you.

Hi Martin,
what do you mean exactly? Do you want to start the workflow without using the portal or do you want to start the different human activities outside the portal?
If you mean the first one, you can use a webservice to start the process (see Re: Starting a flow through a web service). As such you can start the process from pretty much everything with webaccess.
For the second one I dont have an answer... You can probably use a different application and check if there are any new tasks via webservice... but thats just a guess
cya,
Matthias

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

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

Cannot open GP process task in universal worklist.

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

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

User roles property, when system alias is configured in universal worklist

Hi,
I am configuring system alias in Universal Worklist Configuration. I have keyed in system alias and connector type and saved the system alias and its working fine.
Apart from system alias and connector type, there are other properties like "User Roles, Delta Pull Channel Refresh Period(in seconds) and Delta Pull Channel Snapshot Refresh Period(in minutes). Can you any let me know what is the use of these properties.
I heard that "Delta Pull Channel Refresh Period(in seconds)" is the time period to refresh the UWL is it correct.
Thanks & Regards,
H.K.Hayath Basha.

Try searching the http://help.sap.com SAP NetWeaver pages for delta pull!

Reducing shutdown time

Hi,
We experience 5 minute shutdown times on 10GB BDB (version 4.1.17), and trying to see if we can reduce this time to under 2 minutes
I have looked around and did not find anything specifically of help. So questions along this line
-- What exactly causes this delay during shutdown? I assume its mainly writing back all the dirtied nodes back to disk.
-- Does some log cleaning also happen to improve space utilization? In most cases, we bring up environment right away during a server bounce. Hence, such an overhead is actually not helping.
In other words, we just want to flush all dirtied nodes in memory changes to disk, during shutdown and be able to get back up again fast. Is there some option/configuration we can leverage?
Thanks
Vinoth

Hi Vinoth,
I can believe that the checkpoint may take a while. But it is strange if you see that exact stack trace often -- removing an item from the hash map in the dirty set -- but maybe that's not what you mean?
The last checkpoint won't be very different than other checkpoints, so the thing to look at is why checkpoints are taking a long time in general.
Are you using cleaner lazy migration (which is on by default in JE 4.1 and earlier)? If so, that's the first thing to do: turn it off. With lazy migration, much of the work of log cleaning is done by the checkpoint.
Also please look at your configured checkpoint interval (env config), and the actual checkpoint interval -- "DbPrintLog -S" will list the checkpoint intervals, and you can use the "-s 0xFILENUMBER" option to only look at the last 10 or 20 files (to speed up the run).
--mark

How to reduce Boot time of 10.8.3

How to reduce Boot time of 10.8.3(Mountain Lion),Have Upgraded from 10.6.x recently,
Dont have any start up items, No Dual Boot, No user accounts not even guest(Turned off)
I really Dont Know what to do, Please help me in this..

Go to the Startup Disk system preferences and select your boot drive in there. This will ensure the system has your main boot drive set in the PRAM as a the default boot device. Without this, the system may pause while it searches for an available boot device.
Do you have FileVault disk encryption enabled? If so then this may increase boot times a touch.
Do you have any system monitors, firewalls, or security software installed? Again these may also increase boot times as they load in the background, especially if they use kernel extensions.
Finally, boot to the OS X Recovery HD partition by holding the Command-R keys at startup. In here, launch Disk Utility and run a permissions fix on the boot drive, followed by running a repair on the boot drive (both done in the First Aid tab). If there are any access permissions or format structure issues on the boot drive then this should fix them.
Is your hard drive relatively full? If you only have a few GB of space left on the drive then you might consider removing some files to give the system breathing room to better manage memory. Additionally, how much RAM do you have installed? If you have less than 4GB then consider upgrading. While older versions of OS X could get away with 1-2GB of RAM, this amount will only bog down Lion and Mountain Lion. 4GB is a recommended minimum.
Some of these things could provide cumulative delays that you might find noticeable at bootup.

Universal Worklist showing cross-linked tasks

This is a really strange problem.
I have a Guided Procedure process that is being heavily utilized in our company. Occasionally, tasks in a user's work list will become 'cross-linked': the description will say one thing, but opening the task will open another similar task. And vise-versa.
For example, say I have processes assigned to a Manager:
- Task for Employee 'A' (example process id 6a1234)
- Task for Employee 'B' (example process id 6a4567)
When 'Task for Employee A' is opened, the task for Employee 'B' is started. And, when 'Task for Employee B' is opened, the task for Employee 'A' is started. Very strange!
I've checked the underlying process data via /nwa, and the process instances are defined correctly: all data assigned to the process is correct. But, where this really get's weird is when you look at the URL's processed when the task from the Universal Worklist is opened.
If you look at the process ID's embedded in the URL's, they're wrong! Using the information above, the URL for the task for Employee 'A' contains the process ID for the task for Employee 'B'. This explains why the wrong back-end document is opened, since the GP run-time is passing the wrong context.
The process id's defined in the actual GP tasks look correct, so this appears to be a presentation issue.
I have not had the employee try to open the task via the GP Workbench, as this roles not assigned to users in general.
Suggestions?
We're on NW 7.0 sp17.

Hi Ken,
Yep, cheers for that. Now, I did find some information from older messages for you, and it appears that sometimes, this works as designed based on how you have defined your roles for GP.
Do you have a group used as a default for the requestor role?
If you want only one user(the initiator) to be a requestor than you
should change the Requestor role to be of type "Initiator". If this is the case
all the users in the group are used as processors and all of them
would have a task in then in the UWL. This is normal behaviour of the GP.
Here is some additional documentation....
http://help.sap.com/saphelp_nw70/helpdata/EN/96/b48c42ee585551e10000000a
1550b0/content.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/43/8acc8f3b682673e10000000a
1553f7/content.htm
Am I understanding you correctly? I also may need to check with a GP colleague on this for clarification...
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***

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.

How to reduce execution time ?

Hi friends...
I have created a report to display vendor opening balances,
total debit ,total credit , total balance & closing balance for the given date range. it is working fine .But it takes more time to execute . How can I reduce execution time ?
Plz help me. It's a very urgent report...
The coding is as below.....
report yfiin_rep_vendordetail no standard page heading.
tables : bsik,bsak,lfb1,lfa1.
type-pools : slis .
--TABLE STRUCTURE--
types : begin of tt_bsik,
        bukrs type bukrs,
        lifnr type lifnr,
        budat type budat,
        augdt type augdt,
        dmbtr type dmbtr,
        wrbtr type wrbtr,
        shkzg type shkzg,
        hkont type hkont,
        bstat type bstat_d ,
        prctr type prctr,
        name1 type name1,
     end of tt_bsik,
     begin of tt_lfb1,
         lifnr type lifnr,
         mindk type mindk,
     end of tt_lfb1,
    begin of tt_lfa1,
        lifnr type lifnr,
        name1 type name1,
        ktokk type ktokk,
    end of tt_lfa1,
    begin of tt_opbal,
        bukrs type bukrs,
        lifnr type lifnr,
        gjahr type gjahr,
        belnr type belnr_d,
        budat type budat,
        bldat type bldat,
        waers type waers,
        dmbtr type dmbtr,
        wrbtr type wrbtr,
        shkzg type shkzg,
        blart type blart,
        monat type monat,
        hkont type hkont,
        bstat type bstat_d ,
        prctr type prctr,
        name1 type name1,
        tdr type dmbtr,
        tcr type dmbtr,
        tbal type dmbtr,
      end of tt_opbal,
     begin of tt_bs ,
        bukrs type bukrs,
        lifnr type lifnr,
        name1 type name1,
        prctr type prctr,
        tbal type dmbtr,
        bala type dmbtr,
        balb type dmbtr,
        balc type dmbtr,
        bald type dmbtr,
        bale type dmbtr,
        gbal type dmbtr,
    end of tt_bs.
************WORK AREA DECLARATION *********************
data : gs_bsik type tt_bsik,
        gs_bsak type tt_bsik,
        gs_lfb1 type tt_lfb1,
        gs_lfa1 type tt_lfa1,
        gs_ageing type tt_ageing,
        gs_bs type tt_bs,
        gs_opdisp type tt_bs,
        gs_final type tt_bsik,
        gs_opbal type tt_opbal,
        gs_opfinal type tt_opbal.
************INTERNAL TABLE DECLARATION*************
data : gt_bsik type standard table of tt_bsik,
        gt_bsak type standard table of tt_bsik,
        gt_lfb1 type standard table of tt_lfb1,
        gt_lfa1 type standard table of tt_lfa1,
        gt_ageing type standard table of tt_ageing,
        gt_bs type standard table of tt_bs,
        gt_opdisp type standard table of tt_bs,
        gt_final type standard table of tt_bsik,
        gt_opbal type standard table of tt_opbal,
        gt_opfinal type standard table of tt_opbal.
ALV DECLARATIONS *******************
data : gs_fcat type slis_fieldcat_alv ,
       gt_fcat type slis_t_fieldcat_alv ,
       gs_sort type slis_sortinfo_alv,
       gs_fcats type slis_fieldcat_alv ,
       gt_fcats type slis_t_fieldcat_alv.
**********global data declration***************
data :   kb type dmbtr ,
          return like bapireturn ,
          balancespgli like bapi3008-bal_sglind,
          noteditems like bapi3008-ntditms_rq,
          keybalance type table of bapi3008_3 with header line,
         opbalance type p.
SELECTION SCREEN DECLARATIONS *********************
selection-screen begin of block b1 with frame .
select-options : so_bukrs for bsik-bukrs obligatory,
                 so_lifnr for bsik-lifnr,
                 so_hkont for bsik-hkont,
                 so_prctr for bsik-prctr ,
                 so_mindk for lfb1-mindk,
                 so_ktokk for lfa1-ktokk.
selection-screen end of block b1.
selection-screen : begin of block b1 with frame.
parameters       : p_rb1 radiobutton group rad1 .
select-options   : so_date for sy-datum .
selection-screen : end of block b1.
********************************ASSIGNING ALV GRID
****field catalog for balance report
gs_fcats-col_pos = 1.
gs_fcats-fieldname = 'BUKRS'.
gs_fcats-seltext_m = text-001.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 2 .
gs_fcats-fieldname = 'LIFNR'.
gs_fcats-seltext_m = text-002.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 3.
gs_fcats-fieldname = 'NAME1'.
gs_fcats-seltext_m = text-003.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 4.
gs_fcats-fieldname = 'BALC'.
gs_fcats-seltext_m = text-016.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 5.
gs_fcats-fieldname = 'BALA'.
gs_fcats-seltext_m = text-012.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 6.
gs_fcats-fieldname = 'BALB'.
gs_fcats-seltext_m = text-013.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 7.
gs_fcats-fieldname = 'TBAL'.
gs_fcats-seltext_m = text-014.
append gs_fcats to gt_fcats .
gs_fcats-col_pos = 8.
gs_fcats-fieldname = 'GBAL'.
gs_fcats-seltext_m = text-015.
append gs_fcats to gt_fcats .
data : repid1 type sy-repid.
repid1 = sy-repid.
INITIALIZATION EVENTS ******************************
initialization.
*Clearing the work area.
clear gs_bsik.
Refreshing the internal tables.
refresh gt_bsik.
******************START OF SELECTION EVENTS **************************
start-of-selection.
*get data for balance report.
perform sub_openbal.
perform sub_openbal_display.
*&      Form sub_openbal
      text
--> p1        text
<-- p2        text
form sub_openbal .
if   so_date-low > sy-datum or so_date-high > sy-datum .
      message i005(yfi02).
     leave screen.
endif.
     select bukrs lifnr gjahr belnr budat bldat
       waers dmbtr wrbtr shkzg blart monat hkont prctr
       from bsik into table gt_opbal
       where bukrs in so_bukrs and lifnr in so_lifnr
       and hkont in so_hkont and prctr in so_prctr
       and budat in so_date .
    select bukrs lifnr gjahr belnr budat bldat
       waers dmbtr wrbtr shkzg blart monat hkont prctr
       from bsak appending table gt_opbal
       for all entries in gt_opbal
       where lifnr = gt_opbal-lifnr
       and budat in so_date .
if sy-subrc <> 0.
message i007(yfi02).
leave screen.
endif.
select lifnr mindk from lfb1 into table gt_lfb1
for all entries in gt_opbal
    where lifnr = gt_opbal-lifnr and mindk in so_mindk.
select lifnr name1 ktokk from lfa1 into table gt_lfa1
for all entries in gt_opbal
   where lifnr = gt_opbal-lifnr and ktokk in so_ktokk.
   loop at gt_opbal into gs_opbal .
     loop at gt_lfb1 into gs_lfb1 where lifnr = gs_opbal-lifnr.
       loop at gt_lfa1 into gs_lfa1 where lifnr = gs_opbal-lifnr.
        gs_opfinal-bukrs = gs_opbal-bukrs.
        gs_opfinal-lifnr = gs_opbal-lifnr.
        gs_opfinal-gjahr = gs_opbal-gjahr.
        gs_opfinal-belnr = gs_opbal-belnr.
        gs_opfinal-budat = gs_opbal-budat.
        gs_opfinal-bldat = gs_opbal-bldat.
        gs_opfinal-waers = gs_opbal-waers.
        gs_opfinal-dmbtr = gs_opbal-dmbtr.
        gs_opfinal-wrbtr = gs_opbal-wrbtr.
        gs_opfinal-shkzg = gs_opbal-shkzg.
        gs_opfinal-blart = gs_opbal-blart.
        gs_opfinal-monat = gs_opbal-monat.
        gs_opfinal-hkont = gs_opbal-hkont.
        gs_opfinal-prctr = gs_opbal-prctr.
        gs_opfinal-name1 = gs_lfa1-name1.
    if gs_opbal-shkzg    = 'H'.
        gs_opfinal-tcr   = gs_opbal-dmbtr * -1.
        gs_opfinal-tdr   = '000000'.
    else.
        gs_opfinal-tdr   = gs_opbal-dmbtr.
        gs_opfinal-tcr   = '000000'.
    endif.
       append gs_opfinal to gt_opfinal.
       endloop.
       endloop.
       endloop.
sort gt_opfinal by bukrs lifnr prctr .
so_date-low = so_date-low - 1 .
loop at gt_opfinal into gs_opfinal.
call function 'BAPI_AP_ACC_GETKEYDATEBALANCE'
exporting
    companycode        = gs_opfinal-bukrs
    vendor             = gs_opfinal-lifnr
    keydate            = so_date-low
   balancespgli        = ' '
   noteditems          = ' '
importing
    return             = return
tables
    keybalance         = keybalance.
clear kb .
loop at keybalance .
   kb = keybalance-lc_bal + kb .
endloop.
      gs_opdisp-balc = kb.
      gs_opdisp-bukrs = gs_opfinal-bukrs.
      gs_opdisp-lifnr = gs_opfinal-lifnr.
      gs_opdisp-name1 = gs_opfinal-name1.
    at new lifnr .
      sum .
      gs_opfinal-tbal = gs_opfinal-tdr + gs_opfinal-tcr .
      gs_opdisp-tbal = gs_opfinal-tbal.
      gs_opdisp-bala = gs_opfinal-tdr .
      gs_opdisp-balb = gs_opfinal-tcr .
      gs_opdisp-gbal = keybalance-lc_bal + gs_opfinal-tbal .
      append gs_opdisp to gt_opdisp.
    endat.
    clear gs_opdisp.
    clear keybalance .
endloop.
delete adjacent duplicates from gt_opdisp.
endform.                    " sub_openbal
*&      Form sub_openbal_display
      text
--> p1        text
<-- p2        text
form sub_openbal_display .
call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                = ' '
I_BUFFER_ACTIVE                   = ' '
      i_callback_program              = repid1
I_CALLBACK_PF_STATUS_SET          = ' '
I_CALLBACK_USER_COMMAND           = ' '
I_CALLBACK_TOP_OF_PAGE            = ' '
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
I_GRID_TITLE                      =
I_GRID_SETTINGS                   =
IS_LAYOUT                         =
      it_fieldcat                     = gt_fcats
IT_EXCLUDING                      =
IT_SPECIAL_GROUPS                 =
IT_SORT                           =
IT_FILTER                         =
IS_SEL_HIDE                       =
I_DEFAULT                         = 'X'
I_SAVE                            = 'X'
IS_VARIANT                        =
   it_events                        =
IT_EVENT_EXIT                     =
IS_PRINT                          =
IS_REPREP_ID                      =
I_SCREEN_START_COLUMN             = 0
I_SCREEN_START_LINE               = 0
I_SCREEN_END_COLUMN               = 0
I_SCREEN_END_LINE                 = 0
IT_ALV_GRAPHICS                   =
IT_HYPERLINK                      =
IT_ADD_FIELDCAT                   =
IT_EXCEPT_QINFO                   =
I_HTML_HEIGHT_TOP                 =
I_HTML_HEIGHT_END                 =
IMPORTING
E_EXIT_CAUSED_BY_CALLER           =
ES_EXIT_CAUSED_BY_USER            =
     tables
       t_outtab                       = gt_opdisp
exceptions
    program_error                     = 1
    others                            = 2
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
endform.                    " sub_openbal_display

I think you are using for all entries statement in almost all select statements but i didnt see any condtion before you are using for all entries statement.
If you are using for all entries in gt_opbal ... make sure that gt_opbal has some records other wise it will try to read all records from the data base tables.
Try to check before using for all entries in the select statement like
if gt_opbal is not initial.
select adfda adfadf afdadf into table
for all entries in gt_opbal.
else.
select abdf afad into table
from abcd
where a = 1
    and b = 2.
endif.
i didnt see anything wrong in your report but this is major time consuming when you dont have records in the table which you are using for all entries.

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 refresh delay - Reduce default time

Similar Messages

Maybe you are looking for