Textpool Change

[Former Member]

Hi All,

If I create a new text symbol in the text pool of a standard program(INSERT TEXTPOOL command), then does this mean that I am modifying the standard program and removing the support of SAP during upgradation ?

Thanks & Regards,

Srinivas Rao.

[MarcinPciak]

I believe so. Anyhow resigning from SAP support should be explicitly pointed, namely by not importing particular support package which changes this development. This way you keep your changes but may skip those critical i.e business logic ones. So the benefit in using one and removing the second should always be considered.

Regards

Marcin

[Former Member]

Thanks Marcin

I have a question here.

I believe that INSERT TEXTPOOL directly creates an entry in the database/cluster for the program. If this is the case, we are not changing anything at the program code level netiher are we using acess key for anything.

How would the upgradation process identify that the program textpool has been modified ?

Thanks & Regards,

Srinivas Rao.

[MarcinPciak]

I think this happens by comparing current version of the program and the one which is being imported. Considering the fact that report is not just pure code but have parts like screens, GUI screens, textpools, it seems that each of those mentioned are compared separately. If the version changes in some point then the replacement takes place. This works similary to transports. When you do the change the code residing the in DB b/w two systems differs and this makes the changes being imported to target sys.

I guess your are asking how the change is seen even it wasn't recorded. You can do a sample test. Try modifying textpool directly for some other test report (so it creates transport entry for this object). Then do a change by means of INSERT TEXTPOOL and import the changes to target system. If you see the textpool in target sys in this modified version you know that these changes are compared at DB level. I think it is happening so.

Regards

Marcin

[Former Member]

I can totally connect with what you want to say. If the program parts viz screens, GUI, textpools are compared separately and if the comparsion is done at the database level then in my case all the program parts would be supported and only the "textpool support" would fail. Let me know if my understanding is rite? (I have no experience in upgrade projects)

My entire task scenario is:

1. New select option in the standard selection screen. (Achieved using implict enhancement implementation)

2. Now, the select option text has to be modified. It cannot be kept as S_* or something.

Step 2 made me think of the option of changing text pool to have new entry as LOOPING over the screen table and modifying it is also not possible as there is no implicit enhancement option in the event AT SELECTION-SCREEN OUTPUT.

Thanks & Regards,

Srinivas Rao.

[matt]

I would not do such a change by using INSERT TEXTPOOL - if you're doing that, you are effectively circumventing the standard procedures for repairing SAP objects. There's no record of what's been done in the system, no repair flag is set. To my mind, this will leave you in a worse place than if you register the object properly. It's the same as if you used READ / INSERT REPORT to make changes to the ABAP of a standard SAP program. Certainly, if I was development lead in your project, I'd forbid such practice.

If you do make a change to SAP standard, and then a problem occurs, then the most likely scenario is that the SAP support will ask you to reverse your change before they investigate. Which you'll have to do for your enhancement in anycase.

I've often had to combine enhancements with repairs,since, though the enhancement concept is really useful, it doesn't cover everything. In any case, the enhancement framework is an improved way of handling changes to SAP standard. The same dangers still exist as if you did a repair.

matt