on 06-18-2010 8:23 AM
Hi!
We are running ECC 6 with ehp 4 and are using the closing cockpit.
The financial people are updating their templates on a regular basis.
To do this they are using t-code CLOCOC and According to the standard process this is made in the development system and from there transported to the production system.
This process is time consuming and needs a BASIS resource to be completed (transports).
To avoid this we have tried to make CLOCOC config modifiable in a nonmodifiable client (production) by setting the "current settings" checkbox for CLOCOC on SOBJ and transported this to production. Unfortunately this hasnu2019t helped us.
We are still getting the error "Client 100 has status 'not modifiable'".
So now Iu2019m in a desperate need of a solution. In worst case we will continue using the standard process.
Kind Regards
Efe Efeoglu
Edited by: Efe Efeoglu on Jun 18, 2010 9:24 AM
Hello,
did someone solve this problem in the meantime?
CLOCOC maintenance directly on a productive server?
regards
Simon R.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Andre,
We have similar requirement. We did same as you. In SOBJ for object CLOCOC we checked the current settings check box and chose No Transport option in the Transport Dropdown. But When we try to create/change a Template in transaction CLOCOC, the system throws Client XXX has status not modifiable.
Did you make changes to your production client Settings in SCC4 to allow modifications to Client Specific Objects?
Thank you for your time.
Best Regards
Satish Reddy
Hi Andre, hi Satish,
we are facing the same problem at the moment.
CLOCOC, TSCMA and SCMATREE are all marked as current settings using SOBJ. Client status is "productive".
I have found some information about a pilot note dealing with the problem, but the note is in development since 2011 and is still not released (OSS 1179482).
Have you find any solution to this problem?
Regards, Daniel
Hello Daniel,
We raised this issue with SAP and SAP asked us to apply the same note. We applied it in Sandbox.
However due to other reasons we didn't got with closing cockpit.
The option I considered was to implement an enhancement spot for method Transport of class CFC and exit at the beginning of the method. It did work as well.
Best Regards
Satish
Hi Satish,
Thank you! Your solution works perfectly!
Just one additional "return" in method Transport and so far everything is working fine. We also added an additional client status check so we can still create transports in the development system. Testing now, but seems perfect so far.
Regards, Daniel
User | Count |
---|---|
101 | |
14 | |
10 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.