There are some cases, where the changes on customizing are very frequent and you want to avoid the whole process of changing the customizing on the test system, release the request and transport to production.
One example is the subcontracting MRP areas customizing, where you may have different vendor numbers on the development and productive system, therefore, the customizing must be adjusted or directly created on the productive system.
Another common example of that is the customizing transaction OMD0, to create and change the MRP controllers. It is a very simple change which can be done directly on the productive system, however, when you try to access this transaction on production, you receive the message below:
TK430: ‘Client &1 has status ‘not modifiable’
The following note explains in detail the procedure to open the customizing for MRP controllers (transaction OMD0), Destination for parallel processing (transaction OMIQ) and Define range of coverage profile (transaction S_ALR_87006546) for changes on the productive system:
SAP Note 388936 – OMD0, OMIQ: maintenance not possible, message TK430
For more details about the procedure to create subcontracting MRP areas and how to transport these changes between systems, see the note below:
SAP Note 317650 – Transporting MRP areas between systems
The following notes provides more detailes about these changes:
SAP Note 356483 – Customizing: Current settings in the test system
SAP Note 135028 – Transfer IMG activity to current setting
SAP Note 77430 – Customizing: Current settings
If you want to open the customizing for create/change planning calendars (transactions MD25 and MD26) on the productive system, the following modification note should be implemented:
SAP Note 133079 – MD25/MD26: Planning calendar as master data