Is the SAP Inbox and the universal worklist on the portal linked ?

Hi,
I am using the FM SO_DOCUMENT_SEND_API1 to send emails to SAP inbox. This successfully sends emails. My question is whether these mails that I send to the SAP inbox will be seen at the universal worklist on the portal also.
Thanks,
Mukul

If Universal Worklist is connected with your SAP inbox, then yes, you can see the work items in universal worklist also.
For more Details, Check out this:
http://www.sap-hefte.de/download/dateien/1461/146_leseprobe.pdf

Similar Messages

How to download adobe form in sap inbox and process it

Hello experts,
I have a query like how we can download the adobe forms in sap inbox and process process the forms using some program which will convert form data in to XML.
thanks in advance.

Hello Samad arif,
May be you can reuse the code that placed in this document to covert the PDF form to XML format.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2567f2b-0b01-0010-b7b5-977cbf80665d
Thanks,
Bharath.K

Read Attachment from SAP inbox and Transfer to Application Server Folder

Hi
I have one requirement . I have to developed one background program to read the all the attachment in SAP inbox and transfer all this attachment to sap application server folder.
Thanks and Regards
Shyam

Hi Rajendra ,
please try this code snippet , here we call a selection screen that allows us to browse the file name .
PARAMETER : p_file TYPE localfile OBLIGATORY .
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file .
data: user_action type i, filename type filetable, result type i,
        fn type file_table.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
EXPORTING
    WINDOW_TITLE            = 'SELECT FILE'
   DEFAULT_EXTENSION       =
   DEFAULT_FILENAME        =
   FILE_FILTER             =
   INITIAL_DIRECTORY       =
   MULTISELECTION          =
CHANGING
    FILE_TABLE              = filename
    RC                      = result
    USER_ACTION             = user_action
EXCEPTIONS
    FILE_OPEN_DIALOG_FAILED = 1
    CNTL_ERROR              = 2
    ERROR_NO_GUI            = 3
    NOT_SUPPORTED_BY_GUI    = 4
    others                  = 5
if user_action = cl_gui_frontend_services=>action_ok.
    clear p_file.
    loop at filename into fn.
      p_file = fn-filename.
    endloop.
endif.
Hopefully it helps

SAP Press book on Universal Worklist

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

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

SAP BW and BO Universe on HANA

Hi Experts,
I'm trying to teach myself SAP HANA and want to clarify few questions I have with what I have studied so far :
1) Can one HANA unit/Appliance be used as a data source for both BW and BO Universe where the data is coming from a number of SAP and non SAP source systems ?
2) Do we yet have the ability to use non SAP reporting tools on HANA ?
and the next question has confused me the most
3) difference between HANA as a Data Source for BW and BW as a source system for HANA ?
Any help on this will be really appreciated .
Thanks
Gaurav

Hi Mohammed,
SSO is not compulsory in a set up where SAP BW is backend and reporting front end is SAP BO. For eg:- in a company where very few business users alone are using BO reports, we can create enterprise users and define our security model in SAP BO.
But normally when you have common users in SAP BW and SAP BO who access particular data mart data alone, in your case different regional managers, implementing SSO would make security model easier. When a particular manager is having access only to particular regional or application datamart, you can import same roles and users to SAP BO and assign the same to the user so that he will be restricted with the data from only assigned datamart.
In first case where you create separate users in BO, you will have to define your separate security model in SAP BO and assign the same to users. SSO will make your data security model easier and it will be sync with SAP BW model. You have the option to use both models simultaneously in your set up, provided you should have security model defined for the same.
Refer below link for more details on implementing SSO.
http://wiki.scn.sap.com/wiki/display/BOBJ/Setup+of+SAP+SSO+Service+in+SAP+BO+BI4.0+CMC
Regards,
Nikhil Joy

SAP INBOX and Portal UWL Error

Hi One and All,
I have configured leave request process and activated the workflow 12300111.
I applied leave from ESS and it is giving a message leave request is processed.
The work item through workflow is reflecting in SAP R/3 managers inbox. It is not reflecting in Portal UWL.
Can any help me how can i get that work item in portal?
Is there other way to approve leave request from portal apart from UWL?
Regards,
Sanj K.

Thank you all for your great help.
Siddharth I checked System connection test it is failed, and I correctec that and configured UWL in poratl.
Its Working fine.
Regards,
K Sanj.

SAP inbox and UWL

Hi
We are using SAP ESS and MSS. When we create a leave request or raise a travel request , the notifications comes in UWL and SAP inbox. Is there a particular way of disabling sending of mails/notifications to SAP inbox ( SBWP).
Regards
PN

Thank you all for your great help.
Siddharth I checked System connection test it is failed, and I correctec that and configured UWL in poratl.
Its Working fine.
Regards,
K Sanj.

Execute workitem outside the SAP Inbox.

Hi Friends,
Please answer my querries if you can -
When any work item comes to the SAP Inbox, usually the requirement revolves around 2 things -
(1) How to send notification of the Workitem to the agent once work item appears in his inbox.
But my question is can i send notification to external mail id like YAHOO, GMAIL,REDIFFMAIL etc. by maintaining the agent's mailid in SU01 and scheduling the RSWUWFML2 report ?
(2) How to execute the work item in outlook
We can send the sap link for the work item to the outlook and when the user clicks on the link it is directed to sap inbox and then he can take the action.
But My question is How the agent can take decision in the oulook itself ? I mean just like sap inbox he can approve and reject in outlook itself. The agent doesnot have to go to the SAP business workplace for this purpose.
(3) How the point2 functionality can be achieved for external mail (GMAIL, YAHOO etc.) as well
Regards,
Debi

Hi Rick,
Thanks a lot.
You mean to say -
(1) Just like RSWUWFML2 we can also send notification to outlook and any other email (like GMAIL etc.) throgh Extended notification. Right ?
(2) Outlook supports the button (approve/reject), so we can integrate that with the SAP Inbox using Duet (as suggested in my previous forum). That means, the agent will take an action from outlook itself and the same will be communicated to SAP. Right? If yes, then please mention the procedure how to integate the outlook with SAP.
(3) Since GMAIL etc. does not support this button(approve/reject), so we just cant do anything for the requirement -> Agent will take an action (approve / reject) in GMAIL and the same will be communicated to sap InBox.
My requirement is that my client wants to take action from external mail id. Is this possible ? If not then atleast can we do the same in outlook.
Regards,
Debi

How can i autoforward that mail from SAP INBOX to the outlook

Hi ,
My Requirement is that,
I have to send an email to outlook, whenever PO Created in SRM System
I have created custom workflow, i have added a sendmailtask step, i given the SAP userid to send SAP Mail to the user.
It is sending SAP Mail to the User to his inbox perfectly.
Now, how can i autoforward that mail from SAP INBOX to the outlook. This is has to work for all users.
Please give some suggestions. ot it can be achived any other way.
Note: This is Email Message not a workitem.
I have doubt that RSWW program will work only for workitems.*
Thanks & Regards,
Suresh.

Hi ST,
what I understand from your requirement is that you are able to send messages using SendMail Step to SAP Inbox and now you want it to be sent to users Outlook.
Here you need to create a container which would store users email address of Outlook (which would be stored in SU01 or in a ztable), use this container in your Send Mail step and in the Recepient Type as email.
Hope it helps.
Aditya

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

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

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

Universal Worklist 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>

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

hello,
i am trying to configurate the universal worklist in my portal and every tutorial sends me to: system administration-> system configuration->knowledge management-> universal worklist...
the problem is that in km i only have content management, collaboration and index administration
can anyone tell me what to do?
irina

Hi,
This is helpful for you.
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm">Using Universal Worklist - Workflow</a>
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=184256">Configuring Universal Worklist for EP 7.0</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/57/5b781705184211a4ba344387a992e5/frameset.htm">Workflow Notification Settings</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/ac/6e48a0a389422983f7bac5c111c731/frameset.htm">Workflow for Portal Display Configuration</a>
Regards
Senthil K

Universal Worklist - Administration Error --

Hi Gurus,
When iam clikcing on Sys Admin>Sys Configuration>universal worklist and workflow>universal worklist-Administartion Iam getting the following error.
The initial exception that caused the request to fail, was:
java.lang.SecurityException: Access denied (System admin or super admin role required)
at com.sap.netweaver.bc.uwl.ui.admin.util.ServiceHelper.initializeUserContext(ServiceHelper.java:166)
at com.sap.netweaver.bc.uwl.ui.admin.util.ServiceHelper.<init>(ServiceHelper.java:59)
at com.sap.netweaver.bc.uwl.ui.admin.config.ConfigurationView.wdDoInit(ConfigurationView.java:148)
at com.sap.netweaver.bc.uwl.ui.admin.config.wdp.InternalConfigurationView.wdDoInit(InternalConfigurationView.java:374)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks inadvance,
Sriram

Are you using the J2EE_ADMIN uis?
Thanks,
Lye

Is the SAP Inbox and the universal worklist on the portal linked ?

Similar Messages

Maybe you are looking for