UWL not appear - SAP inbox also did not had the leave request.

[Former Member]

We are having problem with our portal.

When submit leave, the leave request is not appear in the sap inbox, thus is not appearing in the UWL.

Our workflow is just using the standard workflow WS12300111 with the agent is set as general

I read some in the forum and that guy solve because The RFC destination background user was locked.

How to check this? Or is it anywhere i had miss.

[Former Member · Accepted solution]

Hi,

When you create the leave request, do you get any work items in SWI1 (=does the workflow even start?). If yes, try to open the log and find possible error messages there?

Check SWU3 also - is the RFC destination green? Also check that WF-BATCH user is not locked?

Regards,

Karri

[Former Member · Accepted solution]

in SWI1, it had the status ready for the staff.

and also the user of WF-BATCH is okay and not lock. The setting in SWu3 also is green.

Here is what is been done.

- We also had set the permission for Everyone.

- We had try the start verification in the SWu3 and it appear in the sap inbox.

- The WEBAS, ITS, and connector test are okay.

It happen only in production, in development is okay.

I had tried to compare the result and config but unsuccessful.

What else that i had miss it

[Former Member · Accepted solution]

Hi,

Did you get the work item in business workplace?

Are you the the approval task has been set up as general task? If you know the task ID, you can check this in PFTC - from menu: Maintain Agent Assignment.

Regards,

Karri

[Former Member · Accepted solution]

Hi Karri

The leave request is not appear in the work item in business workplace.

When we view the display document in ptarq-->Display document.

The next agent is available, the task had WS12300111, and the workflow status is started.

for the workflow, we only use the WS12300111 and we just change the Attributes and Change the task to General task to allow every user to start this task as what is describe in the config guide.

I had read in this thread. It said that

"UWL by default only shows the r3 workitem tasks and not the r3 inbox If you also need to show the r3 inbox in your UWL........"

Is it true that UWL is just ready from the workitem tasks document?

Another thing, is the standard workflow WS12300111 must successfull send email 1st then it will appear in the UWL.

In SOST the mail send is fail, our basis will fix it next week, so i just want to confirm the the UWL will appear after the email is successfully send.

[Former Member · Accepted solution]

Hi,

This is now actually a workflow problem - not an UWL problem that much. It is clear that there is something wrong in the workflow, since the work item does not arrive to business workplace. Check the approval task TS12300097 and see if it is also a general task. If not, set it as general task. => Every user is then able to execute the task. You might later want to restrict this with some role(s)...

>I had read in this thread. It said that

>"UWL by default only shows the r3 workitem tasks and not the r3 inbox If you also need to show the r3 inbox in your UWL........"

>Is it true that UWL is just ready from the workitem tasks document?

>

This sounds just nonsense. Or at least is not very clearly explained. You can use UWL for the work items. If you want to display the "notifications", then you will need the Sonic connector. But this has nothing to do with your problem.

>Another thing, is the standard workflow WS12300111 must successfull send email 1st then it will appear in the UWL.

>In SOST the mail send is fail, our basis will fix it next week, so i just want to confirm the the UWL will appear after the email is successfully send.

The email sending will not have an effect to the workflow. Just first try to make the work items to appear in business workplace. Then when you have them there, you can start looking if they appear in UWL and if you will have a problem there.

Regards,

Karri

Edited by: Karri Kemppi on Jul 8, 2010 9:54 AM

[Former Member]

Hello,

To check the RFC destination user, please see the steps in note number 1133821.

Some people use the UWL_SERVICE user for this task. Others use another user that has the authority as the UWL_SERVICE user.

1. Open the Visual Administrator.

2. Navigate to the Cluster -> <INSTANCE ID> -> Server <SERVER NAME> ->

Services -> Destinations.

3. Double click on Destinations node.

4. Under Destinations select RFC node.

5. Click on "New" button.

6. In the "Enter destination name:" input dialog give as destination

name the following: <SYSTEM ALIAS>$<UWL CONNECTOR TYPE>

(e.g.: BXTCLNT100$WebFlowConnector )

-> HERE YOU SHOULD SEE THIS USER<-

7. Fill in the following fields: System ID, Message Server, Logon Group,

Language, Client, Username, Password. The other fields remain default.

(Make sure the user you specify has "SAP_BC_UWL_SERVICE" role assigned.

This is needed to fetch the technical informations from the backend.)

8. Click on the "Save and Test" button

9. "Successfully connected to system <SYSTEM ID> as user <Username>"

info dialog has to appear.

10. In other cases check the settings again and check the connection to

the backend system.

Also another thing to check is that you have the system set up in the UWL administration.

Log on to the portal and go to

System admin --> system config --> Universal Worklist and Workflow --> Universal Worklist administration.

Check first that you have set up the system here and also in the system landscape directory in the portal.

If you have done both of these steps, navigate to the UWL main iview that youare using. At the context menu (looks like this ---

--

-)

on the far right hand side of the page, click on the context menu and display connection status. Do you receive an error next

to the connectors status? Or is it successful?

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 ***