SAVE_TEXT for Routing

[Former Member]

Hello

I am using the SAVE_TEXT for loading long texts for Rate routings at Operation level. The tables STXH etc are updated correctly and if I use the FM READ_TEXT I see the values that were loaded. But I do not see it thru. the transaction CA21. I also tried using COMMIT_TEXT after SAVE_TEXT.

[Former Member]

I've seen this problem before, the problem in that case was that the transaction actually was looking at a flag in the database that indicates that long text exists. If this is the same case, of course you are not updating this flag in the DB, hence the program does not do the READ_TEXT to get the long text. Again, if this is your problem, the fix would be to update this flag in the DB. Yes, direct database updatation to a standard table is not suggested, but a simply flag may not be a big deal.

Regards,

Rich Heilman

[RichHeilman]

I've seen this problem before, the problem in that case was that the transaction actually was looking at a flag in the database that indicates that long text exists. If this is the same case, of course you are not updating this flag in the DB, hence the program does not do the READ_TEXT to get the long text. Again, if this is your problem, the fix would be to update this flag in the DB. Yes, direct database updatation to a standard table is not suggested, but a simply flag may not be a big deal.

Regards,

Rich Heilman

[Former Member]

Thanks Rich. I was just going thru. your previous post related to that. I will give it a shot.

[RichHeilman]

I was just debugging a little, I think that this is the problem, the field PLPO-TXTSP is being check for a value, if not filled, then it is giving the message that long text does not exists. I think that if you put an 'E'(english) in this field, that it will work.

Regards,

Rich heilman

[Former Member]

Thank you Rich. That did the trick.