UWL Issue after Ehp4

[Murali_Shanmu]

Hi,

We recently upgraded to Ehp4. We followed the Note 1133821 and setup an RFC destination with the name SAP_ECC_Financials$WebFlowConnector and tested it.

But when we re-register the UWL system (SAP_ECC_Financials), we are able to see an error message from the UWL Logs

uwl/service/connector/webflow#sap.com/tc_wddispwda#com.sap.netweaver.bc.uwl.core.connect.webflow.R3ItemTypeManager#BergheiG#34121##

#SAPEngine_Application_Thread[impl:3]_12##0#0#Warning#1#com.sap.netweaver.bc.uwl.core.connect.webflow.R3ItemTypeManager#Plain###Launch Handler not found in SAP_ECC_Financials.

Existence of function module <SWF_VMD_METADATA_GET_ALL> for system SAP_ECC_Financials:java.lang.Exception: Problem occured while creating JCO client for destination: SAP_ECC_Financials#

The cutom tasks registered in SWFVISU are not showing up in the UWL too.

Can someone share their experiences with the upgrade.

Thanks,

Murali.

[Former Member]

Hi,

I've followed all the above mentioned steps. But still this din't work. Please suggest any other solution that might strike you.

I am thinking of raising an OSS message with SAP as a last resort. If there isnt any other solution then its the only thing that I can do.

Shall share the findings once I get any other solution.

Thanks a ton for your inputs

Regards,

Anurag

[Former Member]

Hi,

We are facing a similar issue wherin after implementation of EHP4 the user is not able to open up the tasks or the line items in his UWL.

We have also created a new connector(Destination Name) with small 'f' as suggested in the above post but it did not work for me.

I just want to know what other things need to be done from the portal end apart from creating a connector service in the VA.

My previous connector is also there and the only change in the two connectors (Destination Names) is the letter f.

The system alias is already registered there in the UWL-Administration with the old connector type and I want to know how to use the new connector which I've created in the VA in the portal since the same system alias is using two different connectors (one with small f and one with caps F).

Please assist.

Thanks & regards,

Anurag Gwari

[Murali_Shanmu]

Hi,

I would suggest that you use only one connector. The small 'f' was for only a certain patch level. So this may not work for you.

Proposed Solution:

Implement Note: 1133821

u2022 Open the Visual Administrator.

u2022 Navigate to the Cluster -> <INSTANCE ID> -> Server <SERVER NAME> -> Services -> Destinations.

u2022 Double click on Destinations node.

u2022 Under Destinations select RFC node.

u2022 Click on "New" button.

u2022 In the "Enter destination name:" input dialog give as destination name the following: <SYSTEM ALIAS>$<UWL CONNECTOR TYPE>

(e.g.: BXTCLNT100$WebFlowConnector )

u2022 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.)

u2022 Click on the "Save and Test" button

u2022 "Successfully connected to system <SYSTEM ID> as user <Username>" info dialog has to appear.

Steps performed:

1) Create UWL_SERVICE1 user from SU01

2) From VA > Destinations => Create a destination with the name SAP_ECC_Financials$WebFlowConnector. Provide the credentials of UWL_SERVICE1 user and Test the connection. Here SAP_ECC_Financials is my system alias.

3) Delete the existing configuration from UWL Administration.

4) Clear the cache from UWL Administration

5) Restart the service System Administration > Support > Portal Runtime > Application Console

6) Recreate the System Alias from UWL Administration. In my case, it is SAP_ECC_Financials

7) Re-register the System from UWL Administration.

😎 Test the Work items as an MSS user

Troubleshooting Tips:

u2022 Refer note 1161197 for helps on error message

u2022 Check the Host file/Service file/JCo connections

If this still doesnt work, please open an OSS Message with SAP. Please share your findings.

Regards

Murali

[Murali_Shanmu]

Note 1133821 is the correct one.

SAP suggested us to use small 'f' in the WebFlowConnector and it worked. They said it had to be done only for the SP level we were on. Strange thou.

Cheers