‎2007 Sep 04 10:36 AM
Hello,
We have a business requirement that calls for regular update of the purchasing release strategies. This frequent update has led the business to ask if there is a possibility of changing the "configuration status", since release strategy is part of img customizing, to be a "master data table"? The objective is to directly make release strategy changes in production, not in development and updated through transport request, because the frequency of change we make daily is quite a lot.
Our immediate plans are as follows;
1. Direct updates in production.
2. Changes in production are replicated in development and quality. Can this through ALE? Or any suggestion?
We hope that this is something possible. We also need advise what kinds of precautions we need to watch out?
Thanks and regards.
‎2007 Sep 04 11:46 AM
Hi,
It is not a good method to change the customising settings directly in Production.
In turn it should be first done in developement , tested in quality and move to production.
This is because , the transactions that you execute in productions are real time and any small mistake can lead to hazardous effects.
Thanks,
Anoop
‎2007 Sep 04 3:35 PM
hi
follow this links it is helpfull to you.
http://help.sap.com/saphelp_nw04/helpdata/en/7e/c81ebb52c511d182c50000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a3/30ad6096b511d384bb0060975b04f3/content.htm
http://pubs.logicalexpressions.com/Pub0009/LPMArticle.asp?ID=519
Regards,
Santosh
‎2007 Sep 04 6:12 PM
Hi,
It's possible to change any configuration object to allow it to be changed in a production system while keeping the client settings locked;
The following is taken from SAPnet note 77430
"As of Release 4.6 you can maintain the corresponding indicator directly from within the IMG.
Go to the IMG, and display the IMG structure. Position the cursor on the corresponding IMG activity and select the menu options "Edit -> Display IMG activity". On the following screen, select the tab page "Maint.objects". There you can see a list of the assigned Customizing objects. By double-clicking on the corresponding line, you navigate to the Customizing object and can directly set the flag 'Current settings' there.
As an alternative you can also call Transaction SOBJ. There, you must directly enter the Customizing object and can then set the flag directly."
This will allow the config to be changed in production provided it is set as a production system in SCC4. All other clients in the landscape the config will behave and any other configuration.
You will need to create an authorisation role to allow access to this customising transaction in production, it way also be worth creating a customer transaction code that just goes straight to this item in the IMG rather than giving people access to SPRO.
You may also want to switch on recording of customising so that all changes made are logged. Set profile parameter rec/client and check the technical settings of the config table(s) are set to 'log data changes'. Without this you'll not be able to audit what has been changed.
To your second question, getting these changes back across the system landscape. There are possibly ways using transports, but as these will need to go against the 'flow' of your transport system they may be complex and untidy. As this config will cover a finite set of tables it may be earier to write some ABAP to extract the tables from production and update the other systems in the landscape.
Regards,
Nick