topic Re: Open transaction for changes in Application Development and Automation Discussions

Open transaction for changes

Former Member — Tue, 30 Dec 2008 05:59:22 GMT

Hi,

I would like to know if there is a way to have change mode for below transactions in production system, currently when I try to go to below t-code, I am getting "Client 400 has status 'not modifiable". I have checked with the Basis guy and according to them if we want to change them in production system we need to open the client. However, when opening the client, everything will be opened. We need to know if there is other way to have change mode only for the below without opening the entire client for changes.

OPS6 - Maintain Person Responsible

OPS7 - Maintain Applicants

OPTK - Specify Exempt Cost Element for Availability Control

OAW1 - Reason for Investment

Thanks!

Re: Open transaction for changes

GauthamV — Tue, 30 Dec 2008 06:09:00 GMT

hi,

It is not advisable to directly change anything in PRD.

Better do the changes in DEV and transport.

Re: Open transaction for changes

Former Member — Tue, 30 Dec 2008 06:26:19 GMT

Hi,

As suggested by gautam you should do the changes in Devolopment and then transport the changes to prod.

Regards

Sandipan

Re: Open transaction for changes

Former Member — Tue, 30 Dec 2008 07:32:33 GMT

Hi,

Actually we need those transactions to be open in production system for day to day maintenance like master data. Do you know of any approach that we can use to open those transactions up for edit?

Thanks!

Vivian

Re: Open transaction for changes

Former Member — Tue, 30 Dec 2008 07:48:49 GMT

Hi,

we will use all the transactions in production servers only but what we will do is we will modify that in dev. servers Mostly it is not adivisible to change SAP taransactions if you want to modify those things u have to find ot user exits for that particular transaction code and there you can add u own functionality

even if you try to change those t codes it will ask access code you have to get that one.

Thanks,

Prasad.