Maintaining SAP-standard OTR texts in an upgradeable way?

[Former Member]

Quite often I'm asked to change a SAP standard OTR-text

I have been tought to never change SAP-standrad to make the system upgradeable.

Sometimes I want to change only i.e. one header text and the way I'm working now is that in BSP_WD_WORKBENCH I copy the whole view and it's corresponding components and in the html-code a point to my own OTR-text. This is of course not good when upgrading - probably some part is changed.

Is there a better way to work or is there a better way that we are supposed to work? (Note that I'm not stopped by the system to maintain texts like I'm when trying to maintain SAP standard ABAP-code.)

/Mikael

[raja_thangamani]

Mikael,

If I'm not wrong, if you modify the stardard OTR during upgrade it would cause an issue. It would be better to copy & modify the OTR.

<i>* Reward each useful answer</i>

Raja T

[Former Member]

I do not understand:

1. You copy "TXTORG" and create a new tex called "ZTXTORG" which is used in i.e. a header.

2. Now you have to change the html-view and using "ZTXTORG" instead of " TXTORG". I have to copy the html-code.

3. You also have to copy the controllerclass and the other components just to change one header.

Now I have copied far too much. Using the old technique with CMOD is much more useful.

It will end (almost) with a copy of almost the whole system and now I have lost the advantage of a standard system.

[raja_thangamani]

You dont have any other option apart of coping it into custom object...

Raja T

[Former Member]

Hmm not too much attention here. Still it is important to keep down the modified/copied code.

I want clearify it: If you go to transaction CMOD you can change descriptions and texts related to i.e domains in the data dictinoary. I can't find a good way to this for OTR-texts.

/Mikael