Question:
Hi, all
we want to disable customizing (SPRO)in a client but we want to enable changing in tcode OB52 in a same time, can we this application together with SCC4 and how?
any idea?
thanks a lot,
Answer:
Search OSS for OB52 and SOBJ.
Tarr
Answer:
Set your client to "Production" and set the changes to "no changes Allowed". OB52 will be maintainable but SPRO will be closed ( except tcodes like OB52 that are supose to change when Production is set)
Answer:
But this may be a special case.
It was some time ago I think (I only read about this symptom), but there are some cases when the system is of old heritage and you "discover" working in a closed system or upgraded to a release which makes different checking logic in SPRO customizing tcodes, but the settings for OB52 are not current.
Use SOBJ to set OB52 to a current setting.
Tarr
_________________
Try Search
Else SAPNet
Otherwise It was designed not to work.
____________________
Answer:
Very old systems require a transport to change OB52, Newer systems "convert" OB52 (an tbles like it) to an application when the system is set to production.
SAP's OSS notes explain the changes needed to convert the table to allow maintenance in Production. In general it is to change the delivery class of the table (set in SE11) to type 'L' and reactivate the table.
Answer:
Another solution is to create your own maintenance view of the table and set its parameters to avoid any problematic error messages.
Answer:
thanks John, Tarryn and guest you are right, its work, (SCC4 -production-no changes allowed)
our system is ECC 5.0 and this client must be production
now we can maintain OB52 and SPRO is close, already we use OB52 some end of the mounth.
thanks again,
good work,