cancel
Showing results for 
Search instead for 
Did you mean: 

Unexpected number of substitution rules

Former Member
0 Kudos

Hi

We want to delete the substitution rules set for a specific id and are unable to do the same. The error is as below. We are on NWCE 7.3 SP7 version. We use BPM UWL connector. We tried checking the KMC_WF_SUBSTITUTE and did not find any entries for the specific ids that we were searching for. Any idea on how to resolve this error and to enable us to successfully delete the substitution rules.

#2.0^H#2012 08 20 13:40:29:924#0-

400#Error#com.sap.bpem.uwlconn.provider.subst.SubstitutionRequestHandler#

com.sap.BPM.him_uwl.000524#BC-BMT-BPM-

DSK#sap.com/tc~bpem~him~uwlconn~provider~ear#C000A559B9770C85000000010000

6BA9#252516351000000004#sap.com/tc~bpem~him~uwlconn~provider~ear#com.sap.

bpem.uwlconn.provider.subst.SubstitutionRequestHandler#zreq1#443##046B64F

4EAE711E1939000000F0D17FF#046b64f4eae711e1939000000f0d17ff#046b64f4eae711

e1939000000f0d17ff#0#Thread[HTTP Worker

[@81176996],5,Dedicated_Application_Thread]#Plain##

Unexpected number of substitution rules:

[Lcom.sap.bpem.tm.substitution.ISubstitutionRule;@36156613#

Thanks,

KN. Padmarajan.

Accepted Solutions (0)

Answers (3)

Answers (3)

troy_cronin2
Active Contributor
0 Kudos

Dear KN. Padmarajan

I hope you are well and many thanks for using the SAP Discussion Forums

In relation to the scenario that you have described you mentioned the following:

  • You want to delete the substitution rules set for a specific id and are unable to do the same.
  • You are on NWCE 7.3 SP7 version and use BPM UWL connector.
  • You tried checking the KMC_WF_SUBSTITUTE and did not find any entries for the specific ids that you were searching for.

Ok firstly with regard to the scenario in its entirety and the deletion of substitution rules from a general perspective there are some important points to highlight.

When substitution is invoked on the Manage Substitution UI, it happens for all connectors.  So if you have 7 systems set up in the Universal Worklist Administration there will be 7 calls to each respective system to try to invoke a substitution. If there is any issue whatsoever, with the id, password, network, etc, substitution will not work and will not be set up.  You will see a link called Problems reported repairable in the rule activation column.  In this case there is no mapped user to the backend user:

  • Please ensure that there is 1 to 1 mapping and no redundant user mapping.

Also if you could kindly view the following SAP Note: 854549 which provides more information regarding the scope and behaviour of substitution in the UWL.

If you are maintaining substitution from the UWL, the rules should *ONLY* be deleted from the UWL. It does not support to mix subsitution maintaince between the UWL and the backend. Kindly take a look over the documentation and steps provided and see does this bring about a resolution to the issue.

SAP Note: 1577579 - Facts and limitations about Substitution in the UWL

SAP Note: 854549 - Scope and behaviour of UWL

The general method to delete a substitution revolves around checking the entries in Database table KMC_WF_SUBSTITUTE in Portal DB and then subsequently deleting any entries against the user. In your case despite manual removal it still appears.

**** Substitutions are kept in all systems ****

So a method of manual deletion must be done for every system that the UWL (Universal Worklist) is connecting to.I have provided a walkthrough below for your convenience:

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 deleted users and 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 deleted users and the userthat is experiencing the problem.

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

4. Restart the engine

5. If the problem is no longer reproducible, recreate the substitution rules for the user that is experiencing the problems using UWL's ManageSubstitution Rules.  Please ensure that the connection to the backend system is working ok, as this is one of the prerequisites to
substitution.

Kindly update me as per your findings.

Kind Regards & All The Best

Troy Cronin - Enterprise Portal Support Engineer

demetrius_pfoo
Explorer
0 Kudos

Hello,

we also have the same failure.

Is there allready a solution for this problem?

Thanks

D. Pfoo

Former Member
0 Kudos

Hello

We have the same failure on the same SAP Release.

Thanks

R. Blatter