How to make transaction editable in Production

[Former Member]

Currently we have transaction /SAPAPO/SDPPLBK as transportable. We need to make it client specific and allow users to update it in production instead of importing it from development to production

Regards

Gurudutt Sawant

[Former Member · Accepted solution]

Hi

In general, it's not recommended to make changes in Production system directly, even if there are way of doing it. Lets say you have a crash or somebody does a mistake and have to recover....it's so expensive to do it in production. Better have a copy of all your production stuff in dev and QA or else at least in QA

But still if you want, please check OSS Note 445837 which recommends to address this need by using the authorizations concept and auth object C_APO_PB.

If this information helps you, please close the thread

Thanks

Amol

[Former Member · Accepted solution]

Hi Amol

Thanks for your reply.

The transaction /SAPAPO/SDPPLBK mentioned above is for assigning planning book for users.

So if there is any movement in user we need to do changes in development system and import it through production.

That's the reason we need to make transaction client specific and allow super users to assign planning book to new users.

Regards

Gurudutt Sawant

[Former Member · Accepted solution]

Hi

Can you try T-code /SAPAPO/SDPUSET - User Settings for Interactive Planning

Hope this would also help you what you are trying do. Here you can copy the setting from one user to other.

If this information helps you, please close the thread How to close a discussion and why

Thanks

Amol

[Former Member · Accepted solution]

Hello Amol

Thanks for your reply. It worked with tcode /SAPAPO/SDPUSET. When we create new user we shall assign setting in above code. If by mistake user tried to log into planning book without this setting then system by default assign random planning book to user.
And then settings in this tcode wont help.

Regards

Gurudutt Sawant