SCUL entries in CUA

[Former Member]

Recently we have changed the CUA_PARAMETER_CHECK value from 'I' to 'S' in the table PRGN_CUST in CUA to correct the entries with "parameter does not exist" message.After we tried SCUL flushing,the entries are still struck up in CUA with warning 'W'for "parameter does not exist" messsage.The default value is W which was displayed before. But now that we changed it to ‘S’ it must show ‘S’ (successful).

Any help is appreciated.

[Former Member]

Hi,

What is the SCUM setting for parameters? Global, Local, Proposal?

With the value = I and the SCUM setting as Proposal then this should be enough to stop the error message.

[Former Member]

Thanks for your reply.

Before changing the value to S, we had SCUM setting for parameter as Proposal and value- I. Now with value - S and Proposal in SCUM we still get the error message for some child systems.

[Bernhard_SAP]

Hello Sowmya,

did you change the parameter in teh child system?
Keep in mind, that SCUL shows the messages issued from the child system....
By the way, if the user exists already in the child, and scum is set to proposal, the transferred

values will be ignored anyway.

b.rgds, Bernhard

[Former Member]

The issue was CUA_PARAMETER_CHECK  missing in the table PRGN_CUST for the child systems.

Issue got rssolved by creating the CUA_PARAMETER_CHECK entry in child systems.

In redistribute, the data can be maintained both centrally and locally. So, each time the user is created/changed in child systems, it is redistributed to the central system and then to other child systems. Since the parameter CUA_PARAMETER_CHECK does not exist in child systems, the changes get overwritten in CUA thereby removing the parameter CUA_PARAMETER_CHECK from CUA too.