2005 Sep 09 10:12 PM
Hi All,
How can I check for Null, line feed, carriage return within a field. My issue is that I am using READ_TEXT function module to get the sales text of a material but SAP returns the followin in the internal table "##################################################'c7" if the text is not found and appends the following
"##################################################yk" if the text is found. Does anyone have any idea what these are and how can I check for the and eliminate these before writing to the table.
Any ideas/suggestions will be greatly appreciated.
Thanks
2005 Sep 10 12:26 PM
Hi Aurang,
I will suggest that you first check a "REAL" text using VA03 transaction and then run the FM READ_TEXT using SE37 for the same Sales Order. Sometimes you text tables gets currupted in text environment due to client copy etc.
If you still have the same problem check the Hex code for these characters by pressing the lens button (details icon) in debug mode. You will get a hint on what is wrong with your text.
Cheers,
Sanjeev
Hi All,
How can I check for Null, line feed, carriage return within a field. My issue is that I am using READ_TEXT function module to get the sales text of a material but SAP returns the followin in the internal table "##################################################'c7" if the text is not found and appends the following
"##################################################yk" if the text is found. Does anyone have any idea what these are and how can I check for the and eliminate these before writing to the table.
Any ideas/suggestions will be greatly appreciated.
Thanks
2005 Sep 09 10:53 PM
Anurag,
Since I never faced this problem before, I am assuming that unless you have weird characters in your textname the internal table doesn't get those.
Go to SO10 enter the textname, text ID and see whether you have any unnecessary characters in that.
Good luck.
2005 Sep 09 10:59 PM
Hi,
check out the length of the fields in internal table.
With regards,
praveen.
2005 Sep 10 12:26 PM
Hi Aurang,
I will suggest that you first check a "REAL" text using VA03 transaction and then run the FM READ_TEXT using SE37 for the same Sales Order. Sometimes you text tables gets currupted in text environment due to client copy etc.
If you still have the same problem check the Hex code for these characters by pressing the lens button (details icon) in debug mode. You will get a hint on what is wrong with your text.
Cheers,
Sanjeev
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |