UWL Substitution error. No Update on HRUS_D2

[Former Member]

Hello Experts!
We have an issue regarding UWL (using ESS/MSS) with the following releases:

• SAP EP 7.31
• ECC 6 EHP4
• BP 1.41 (WD Java)

When  we have a look of substitution rules, we always get an error message: "Problems reported (repairable)" --> "Substitution rule is not defined in the system". When we push "retry" the substitution rule is successfully registered again.
However, after we push the refresh button, the error message occurs again!

There is also an impact on the substitution rules:
We can create new substitutions HRUS_D2 is updated successfully,  but we can not delete substitutions.The entry disappears in the Substitution overview (Portal) but within HRUS_D2 the entry is still available!

In the system settings all connectors are working fine. No error message. And also the workflow (without substitution) works fine!

I read already about the issue "Problems reported (repairable)" but still couldnt find any solution for it…

Thanks in advance!

[Former Member · Accepted solution]

Hi

Can you please check KBA 1577579  - Facts and Limitations about

substitution in the UWL. When substitution is invoked on the portal

side it happens on all connectors. Please read this KBA and if you

have any further queries regarding this please return to my side.

Thanks and Regards

Sharanya Rajagopal

[Former Member · Accepted solution]

Thanks for your answser!

We only have one backend-system (ECC 6.4) connected to UWL.

Creating a new rule works fine!

Although we get a message:  "Problems reported (repairable)" --> "Substitution rule is not defined in the system".

But we can not delete or deactivate the rule.

The entry disappears in the Substitution overview (UWL) but within HRUS_D2 the entry is still available!

So the substitute can still work with the items...

Any hint?

[kiruthika_s · Accepted solution]

Hi,

I hope that you are creating substitution only from portal and not in backend

As you mentioned is the new rules are working fine without any error?

Check the note 1133821 whether destintions are maintained correctly

If you are using also substitution functionality in R/3, please only

maintain your substitution from the portal.

What is the profile you are using for substitution is it anything other than "All"

1. Go to System Administration->System Configuration->
Universal Worklist
& Workflow->Universal Worklist - Administration and for all the R/3
systems that are registered there go and delete the records for
substitutions in all the HRUS_D2 tables connected to
the user that is experiencing the problem - as substituting and as
substituted users.

2. Delete all the records in the java engine's database table:
KMC_WF_SUBSTITUTE, that are connected to the user
that is experiencing the problem.

3. Clear the cache for all system from the Universal Worklist -
Administration.

4. Restart the engine

Regards,

Kiruthika

[Former Member · Accepted solution]

hi

I would add that when cleaning substitutions connected to deleted users
should not be done only on ALL the backend systems, but also on all
systems that UWL is connecting to # JWF, Galaxy, etc.
The thing is that the substitutions are kept in the systems, not in the
UWL and when it is created/deleted/updated # this is done on all systems
simultaniousely.#

This means that removing from HRUS_D2 from ALL backends have to be done,
but it is not sufficient. The problematic
substitution(s) should be deleted as well from the portal table
KMC_WF_SUBSTITUTE

Hope this clarifies your doubt.

Thanks and Regards

Sharanya Rajagopal

[Former Member · Accepted solution]

Thanks for your  help!

We are creating substitutions only from portal side, not from backend.

I tried to debug SAP_WAPI_SUBSTITUTE_DELETE but it seems that this function module doesn't get called, once we want to delete or deactivate a substitution...

[Former Member · Accepted solution]

Hi ,

This WAPI has to be called if not I would like you to reproduce the issue and check the traces

for error and let me know the details.

Best Regards

Sharanya Rajagopal

[Former Member · Accepted solution]

Thanks for your help!

These are the log-errors from NWA:

...and there is one warning:

Any hint?

[Former Member · Accepted solution]

Problem solved.

Backend Authorization object was missing!

[Former Member · Accepted solution]

Hi Max,

I have similar problem in  our system for some users, Please do let me know which Authorization object was missing.

Thanks in advance,

Raja.

[Former Member · Accepted solution]

Hi Raja,

we had to add the following backend authorizations:

If you have any further questions, let me know!