Urgent help needed - MSS manage substitution - "This action is not valid for this item"

[Former Member]

Dear All,

We are in the process of HRSP upgrade. The Manage Substitution functionality is not working in MSS. We click on the option and message is displayed stating that "This action is not valid for this item". We upgraded Sandbox and it was working fine there. In development landscape it is not working. The functionality is also working in QEH which is not upgraded.

I am not sure whether this is an upgrade issue or some issues with UWL. Please suggest some solution. We are beginning QEH upgrade tomorrow and needs to fix this to proceed.

Regards,

Rahul Krishna R

[siddharthrajora · Accepted solution]

Do not mention urgent! This is against the policy, just post your query and fellow members will help you!

it can be due to custom XML or connector issues, please follow below steps a. Log on to the portal with an id that has tasks in the UWL and can access the PCD.  Go to Content Administration    > Portal content 1. Content provided by SAP 2. End user content 3. Standard Portal users 4. Iviews 5. com.sap.netweaver.bc.uwl.iviews 6. Open the folder 7. Right click on the Universal Worklist 8. And display a preview. 9. From that preview click on the manage substitution rules from the context menu and let me know if the issue can be reproduced from here. b.Also remove the custom xml file and retest if the issue happens again. c.Kindly check if the adhoc system is active. d. Please ensure that there is 1 to 1 mapping and noredundant user mapping as per SAP Note# 854549. e.Please check personalizations on the UWL for this user.  If the user has personalization, please clear it.

[Former Member · Accepted solution]

Sorry. Siddharth. I was not aware of that. Will take care next time.

I shall ask my portal consultant to try out the same. Thanks.

Rahul

[Former Member · Accepted solution]

Hi Siddharth,

While executing from the content admin also, the preview was not working. We re-started the portal and re-registered the UWL systems. Now Manage Substitution is working. But now UWL item display which was working earlier is throwing the below error:

Application error occurred during request processing. Details:

  com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'com.sap/ess~lea' and application 'LeaveRequestApprover' are not deployed on the server. Please check the used URL for typos.

Exception id: [0021287E414A00180000001F0000695C0004EE7EEDECB8A5]

I am trying to click and display a leave request raised by the employee and a pop-up window is displayed with the error. Kindly provide some inputs on why this could be. Thanks.

Rahul

[siddharthrajora · Accepted solution]

Cause you have wrong entries in SWFVISU and ultimately in the XML of UWL

Maintain as per SAP note 779075

follow the steps and do re register your workitems again from uwl as you did previously

requested deployable object 'com.sap/ess~lea' is wrong!!!!

[Former Member · Accepted solution]

Hi Siddharth,

We made the change. Changed the entry to sap.com. We restarted portal and re-registered the uwl work items. Still it is not working. When I check the uwl.weblow.SAPR3HumanResources xml file, I can still see that sap.com/ess~lea is maintained there. This is not getting updated. What can we do to correct the same?

Regards,

Rahul

[Former Member · Accepted solution]

Hi Siddharth,

After changing the entry in SWFVISU, did you re-register the UWL? Unless you re-register and clear cache after registration, changes will not be effected.

If registration is successful, you'll see the xml file with updated values.

Regards,

Ravi

[Former Member · Accepted solution]

Hi Ravi,

We did this but the xml did not change. What could be the possible reason?

Regards,

Rahul

[Former Member · Accepted solution]

Hi Rahul,

When you re-registered the configuration in UWL, was it successful?

If it was successful, then surely your xml configuration would change. However, may be you have another UWL configuration uploaded manually with high priority. Default configuration is updated with medium priority. Check the date time to ensure that it's updated.

Regards,

Ravi

[Former Member · Accepted solution]

Hi Ravi,

The issue was resolved. You are right. The issue was due to an additional xml file. Thanks anyway.

Regards,

Rahul