Header texts saving issue in module pool

[Former Member]

Hi Experts,

I am working on a module pool. For the transaction, I have created a separate text object and text ids for storing header texts in se75.

For the header texts, I have created a screen in which I am displaying the text types on the left and the users can enter the text in the text editor on the left.

When the users move from one text type to other, I am saving the texts using SAVE_TEXT. This is so that I can recall any changes if the user goes back to the same text type.

All of it works fine. But if the user exits the screen by using /n then the changes get saved. I want to know how do I save it to the buffer without saving it.

One option is to call COMMIT_TEXT while saving the transaction. But then how do I recall the changes if the user changes text type A then goes to text type B and then goes back to A.

Read_Text does not call this text till it is saved.

Thanks,

Abdullah Ismail.

[Former Member]

Hi Abdullah,

Instead of saving the texts when user switches around the screens, just put the values for each header in an external table.. modify it when the user modifies it and show it thru that internal table when user comes back to the screen .. but in database save only when user clicks on the save button..

Regards

Palak

[Former Member]

Hi Palak,

I am not able to figure out how I will be able to store each text type texts into a table. Can you please elaborate.

Thanks,

Abdullah

[Former Member]

In the internal table create two fields, one of the name of the type of header and the other by text.. and clear the internal table only in the beginning of the program. otherwise just modify it on the basis of the values given by the user

[Sandra_Rossi]

I'm not sure to understand, but maybe the text object you use is defined in save mode "dialog" (check it in SE75), so SAVE_TEXT function module immediately saves text to database (commit_text is not needed in that case). If you change the text object save mode to "update", then the update will be done via commit_text (except if you use save_text parameter savemode_direct = 'X')