OOSB is disabled

[former_member182098]

Hi,

When the User went to transaction code OOSB and trying to assign authorization profiles to Users, it is disabled. It is saying the system is not modifiable in Quality. I have compared the setting in SCC4 for both quality and production systems. Both are exactly the same and there is no difference at all. However, in production system it is allowing to assign the authorization profiles to Users, whereas not in Quality System.

Please let me know what could be the probable reasons?

Thanks in Advance,

Ravi

[manohar_kappala2]

Hi,

Verify if

in SE11 for Table T77UA the in the Attributes Sub Screen the Check Box for

Table Maintainence Allowed is selected or not.

If its not selected then it might be the reason why u are not able to maintain in the QA system

Manohar

[Former Member]

Hello,

Has anyone found the solution for this problem? I too have the same problem. I can add users to OOSB transaction and assign structural profiles in Production, but receive a message in Test system that client is not modifiable.

I've searched all through OSS Notes and cannot find a solution.

And, I do not see any check box on the Attributes Tab of Table T77UU.

Thanks,

Penny

[Former Member]

Correction on the last message:

It is table T77UA and I compared the table and settings for ALL the tabs between test and Prodution. Both are the same, but I cannot maintain users in OOSB in Test Environment.

Thanks,

Penny

[Former Member]

As the current setting functions are restricted to Production clients only, we cannot change the T77UA table entries in QA system without opening the client.

To avoid this, we can follow any one of the below options.

1. Change the client role of the client in Quality system to Production.

2. Deactivate the transport connection to the table T77UA by following the below procedure.

- Call transaction SE54

- Enter the Customizing object (view or table)

- Select "Generated objects"

- Choose "Create/change"

- Select "no, or user, recording routine" in the bottom part of the screen

- Save the change

For more details, refer the Note.356483.

[Former Member]

Hello all:

I am having the same problem. I had seen the note and tried the option with SE54 but when I change 'recording routine' option to no, or user, recording routine then I get a message 'You are changing a function group which does not belong to you' and the change is not effective.

How can you avoid this message? I can see the function group on the technical dialog section is 0H00 but it is greyed out I can not change.

Thanks,

NT

[Former Member]

'You are changing a function group which does not belong to you' its olny warning.

If you press enter after this message occur, you'll prompt to type te request number for save.

Rgards

[Former Member]

>

> Hi,
> 
> When the User went to transaction code OOSB and trying to assign authorization profiles to Users, it is disabled. It is saying the system is not modifiable in Quality. I have compared the setting in SCC4 for both quality and production systems. Both are exactly the same and there is no difference at all. However, in production system it is allowing to assign the authorization profiles to Users, whereas not in Quality System.
> 
> Please let me know what could be the probable reasons?
> 
> Thanks in Advance,
> 
> Ravi

This is definitely a setting in SCC4, it should be set to "Changes to Repository and cross-client Customizing allowed". This is a horrible approach in PROD and even in QA, you should not allow customizing changes on these environments without approvals.

Why not just assign the profiles to the positions via PO13 then run PFUD or RHPROFLO? The user will get added in OOSB without any customizing unlocks to the client. This is assuming you are running HR position based security.

Edited by: John Navarro on Oct 8, 2008 5:26 PM