Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SCUM fields are disabled

Sankar_Aravind
Participant
0 Kudos

Hi All,

Actually we are facing an issue like, Our landscape has almost 12 systems in CUA. all the roles and user admin we do through Central system. But the issue is, after system refresh all the CUA is disturbed. However we corrected that. But the SCUM settings are automatically disabled. We have to change the "lock" "roles" and "profiles" settings in SCUM. But it is not allowing me to do that. They are inactive in state.

So kindly suggest me. I have read some threads for this issue but those are not resolved this issue.

Please write in case of any additional information required.

Thanks.

1 ACCEPTED SOLUTION

jimguo
Advisor
Advisor
0 Kudos

Hi,

As recommended by Bernhard, there should be problem with table USRFLD*.

Please check data in table USRFLDSEL. The value of UFLAG should be set to an allowed value as defined in table USRFLDVAL. otherwise, the field will be disabled.

Possible solution could be:

1. fix the inconsistant data in USRFLDSEL table manually.

2. remove complete CUA with report RSDELCUA and then recreate the CUA model via SCUA.

Thanks.

Jim

12 REPLIES 12

shivraj_singh2
Active Participant
0 Kudos

Sankar,

Please check this link

Setting Up Field Distribution Parameters

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6a/b1b13bb3acd607e10000000a11402f/content.htm

Regards,

Raj

Bernhard_SAP
Employee
Employee
0 Kudos

Hi,

it is possible to open the change mode only in the central system.....

If it still does not work, check the CUA definition again - is the central system really recognized as central system?

Another check you can perform is to check if the USRFLD*-tables are correct (not empty).

b.rgds, Bernhard

0 Kudos

Thanks Bernhard.

I checked all the above things. CUA is correct. In change mode also fields are inactive. All USRFLD* tables are not empty.

I want set the distribution parameter to Global. But the field in deactivated in change mode also.

Thanks,

Sankar.

jimguo
Advisor
Advisor
0 Kudos

Hi,

As recommended by Bernhard, there should be problem with table USRFLD*.

Please check data in table USRFLDSEL. The value of UFLAG should be set to an allowed value as defined in table USRFLDVAL. otherwise, the field will be disabled.

Possible solution could be:

1. fix the inconsistant data in USRFLDSEL table manually.

2. remove complete CUA with report RSDELCUA and then recreate the CUA model via SCUA.

Thanks.

Jim

0 Kudos

Thanks for the reply.

But we did this earlier also. Still the same thing.

Recently, systems undergone refresh activity. Before that the role assignment worked properly.

But Now the fields are disabled because of which we unable to do role assignment/password reset/profile assignment...for the satellite systems.

Thanks,

Sankar.

0 Kudos

Hello,

Could you attach a picture to describe how SCUM looks like please?

And please also let me know the values of UFLAG in table USRFLDSEL where

LOG_FIELD=ACTIVITYGROUPS, PROFILES, PASSWORD.

Please make sure you get the data from CUA central systm.

Thanks.

Jim

Thanks.

Jim

0 Kudos

hi,

if you have correct entries in USRFLDSEL like Jim mentioned before, the only thing I can imagine is, that the CUA definition is inconsistent after your 'refresh activity' (whatever you mean by that). probably the system does not recognize itself as central system of the CUA and therfore does not allow changes in scum.

Fastest way to check this out: debug the start of scum. There you will find the checks for central system and landscape....

maybe you did not set the correct logical system name again after your 'refresh activity' or similar.

b.rgds, Bernhard

Former Member
0 Kudos

This can happen if customizing is maintained with SE16N.

Check table se16n_cd_keys for entries of the USRFLDSEL table.

You might want to check tcode SPAU and SM12 as well, just to be safe.

Cheers,

Julius

0 Kudos

Thanks,

Please see the below screen shot.

ACTIVITYGROUPS  =  G

Profile  = G

Password = C

If the last name and first name will enable also will resolve my issue. Because of this issue, we unable to create new IDs in child systems.

Former Member
0 Kudos

setting "last name" to local is illogical, but the user bapis will set it to the same value as xubname it it is initial.

it is a mandatory field so setting it to local is strange.

you should have set the 2nd names to local or the first name if you wanted to use alternate names for the same identity in the logical systems.

you definately have blocked the cua here, but that it does not use the same logic as the bapis is suspect.

which release are you on?

Julius

0 Kudos

Hello,

Please check UFLAG of the following entries in USRFLDSEL:

BOROBJECT = USER

LOG_FIELD = ADDRESS_NAME_FIRST(and ADDRESS_NAME_LAST)

They are set with value "L", but this is not allowed.

Please set them to "G" using database tool or SE16. After that the field should be enabled.

Thanks.

Jim

Former Member
0 Kudos

Jim Guo wrote:

Please set them to "G" using database tool or SE16.

That is probably how they got in there in the first place...

Cheers,

Julius