cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent: UWL XML Config file

Former Member
0 Kudos

Hi all!

I copied the business object EXTSRV to ZEXTSRV and created a new method zprocess that is mainly a copy of the Process method of the EXTSRV BO just that the creation part of the url is diffirent. I kept the call_browser function.

Then, I assigned this method to a task in the workflow this task is copy of the standard task TS50000075. I added the itemtype to the UWL XML config file and uploaded it to the system successfuly then i cleared the cash.

When i double click on the item in the UWL it partially works. I see the text written in the task but it is supposed to pop up a window. This window doesn't appear.

Can anyone help with that?

Thank you in advance,

Hajar

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks a lot for your answer.

Actually, I found out that the task configuration in the xml config of the UWL was not correct. Now, there is a window that pops up but with the fllowing error message "An internal error has occurred RFC call error: ISR_PORTALCOMP_FOR_NOTIFNO_GET No data found" Do you have any idea about that error?

Thanks,

Hajar

Former Member
0 Kudos

Hi

Just check this out Please do not forget to give points

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.<system_alias> or uwl.alert.<system_alias>.

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 &#8594;&#61472;System Configuration &#8594;&#61472;Universal

Worklist and Workflow &#8594;&#61472;Universal Worklist &#8594;&#61472;UWL Systems Configuration.

2. Create the following system connections:

If you have already registered a suitable connector to the system connected to

the system alias, the existing connector is sufficient and you do not have to

register an additional one.

&#9675; System alias: SAP_ECC_Financials

Connection types:

&#9632; WebFlowConnector

&#9632; AlertConnector

&#9675; System alias: SAP_ECC_HumanResources

Connection type WebFlowConnector

&#9675; System alias: SAP_SRM

Connection type WebFlowConnector

Leave the Web Dynpro Launch System field blank for all system connections.

with regards

subrato

Former Member
0 Kudos

Hi Subrato

Can you please just point to the document where this came from rather than cutting and pasting? It is quite difficult to follow with out proper line breaks etc...

Thanks