Changing FTXP, OB08, OB52, OB58, OA02, GGB0 and GGB1

[former_member8971]

Hi

How is it possible to make changes to FTXP, OB08, OB52, OB58, OA02, GGB0 and GGB1 directly in a test system that is closed for changes without changing the role to productive and without having to open the client for changes every time a change is needed?

I have checked OSS note 356483 but it only describes how to make it work for pure view maintenance transaction V or S tables and not all the transactions above are that or does perhaps consists of other non view maintenance tables as well.

Regards,

Caroline

[Former Member · Accepted solution]

Hi Caroline,

I'm not sure but, this is what i do when i dont want a customizing dont ask for request. But im not sure if this makes a customizing table open for customizing in test enviroment. But you can try fi you want.

At SE54,

Enter table's behind the customizing tcodes. (For example V_T011 for OB58)

And check Generated objects.

click Create/Change

At next screen, you need to check No, or user, recording routine

by this way, it will not ask for request when you make a change.

[former_member8971 · Accepted solution]

Hi Melih

Thanks for your reply, much appreciated 🙂

Yes I intent to try this but it will only work on S_ or V_ tables.

So I'm going to test this on the following:
OB08 – Assigned object - V_TCURR, object type V
0B58 – Assigned object V_T011, objects type V (but there might be another table involved RFDT involved and then it might not work, OSS note 557503 mentions this but it's very old so not sure it's applicable)
OA02 – Assigned object V_T093SB_2

FTXP for instance has not got object type V assigned to it

Neither does OB52, it's assigned object is IMGDUMMY, object type D.

So I will test for OB08, OB58, OA02 but it will not work for FTXP or OB52.

Any ides how to do it for FTXP or OB52?

Regards,

Caroline

[Former Member · Accepted solution]

For OB52 There are 2 versions,

V_T001B_COFIB (OB52 if asking variant with popup)

V_T001B_COFI (OB52 if not asking variant with popup)

Need to check FTXP because its also as itselfs hard to make transport 🙂

[former_member8971 · Accepted solution]

Thanks again Melih. I will check V_T001B_COFIB and V_T001B_COFI! 🙂

Regards,

Caroline

[iklovski]

Hi,

You have to change the settings in SOBJ for the relevant objects.

Along with the note you mentioned, you can equally consult 77430 and 135028.

Regards,

Eli

[former_member8971]

Hi Eli

Thank you! I will try this!

Regards,

Caroline

[former_member8971]

Hi Eli

I went into SOBJ and set the flag "current setting" for FTXP but when we try the transaction FTXP now, we still get the message

Client role Test and set to no chnages allowed and No chnages to repository and cross-client sut. objs

Regards,

Caroline

[iklovski]

I forgot to mention that all these settings would be applicable only if your system is set to Production in SCC4. Is it the case for you? If 'yes', then it should work. Specifically for FTXP, you can consult this note:

2535941 - FTXP | TK430 | Client xxx has status 'not modifiable' | Production

[former_member8971]

Hi Eli

No that is the issue. We do not want to have the client as productive as it's a DEV system, test client and we want to be able to use SCC1 transaction.

Is this the case for all the other transactions too, the client role need to be production? In that case I think I need to create a message to SAP.

Thanks.

Regards,

Caroline

[iklovski]

Oh, sorry... I didn't see that you want to have it in your Test client.

Though, in my current Test system, FTXP in particular, is modifiable. So, I guess, it is still can be done. But, it is always this tricky combination of view/object settings. Consult this general note:

2336175 - SPRO | modifiable | unwanted

...and try to do the opposite from what it says.

[former_member8971]

OK, thanks I will have a look.

Regards,

Caroline

[former_member8971]

You have got it working in the test system and you have not got the client role set to prodution in SCC4?

[former_member8971]

Hi again

Sorry for the many messages. I just checked 2336175 and unfortunately it only describes how to remove the option "Current setting" that the other OSS notes told me to set to make it work :S

And in production we do not have the current setting set but we are still able to modify the transaction codes which is a contradiction to start with as the notes say you need to have "Current setting" set to be able to modify.

I try OSS note 356483 which suggests to set the "no, or user, recording routine" on maintenance views. But FTXP is not a maintenance view so it' not applicable to FTXP.

Regards,

Caroline

[iklovski]

2336175 shows how to switch off the modifiability of the object. So, that's why I said 'act in the opposite direction'. But, yes, I have FTXP modifiable in Test system, i.e. it is not marked as Production.