Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAVE_TEXT IA01

Former Member
0 Likes
1,148

Hi,

I am using SAVE_TEXT function module for updating Long Texts in IA01. The problem here is that it is working fine only when the long text indicator has been created manually via Tcode. But if no long text indicator is present it does not work.

Let me explain this.

1 .I create a tasklist with no long text indicator at header level. I then use SAVE_TEXT with all the proper values and it does not work.

2. I Add a long text indicator via the TCODE IA01 and then use SAVE_TEXT and it perfectly modifies to the values passed in the FM.

I want it to work in scenario one.

in scenario 1 tables STXH , STXL are also getting updated but no effect when displayed via Tcode.

Any help would be great.

Thanks in advance.

Devrath Sampat

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
973

Not sure I understand what you are asking...  Generally, SAP does not display long text if the long text indicator has not be turned on (X) in the appropriate field in the correct table.  Look for fields named like LTEX (?) or that seem to be a long text existence indicator.  You should be able to turn that on with a simple BDC session that does an update of something in the transaction and then presses save (without actually having to mark the box).   In my experience, SAP would usually recognize that the text existed and update that column automatically after the text had been created and the transaction saved, then the document subsequently reopened and changed via an update to some field on the screen...

Not sure I understand what you are asking...  Generally, SAP does not display long text if the long text indicator has not be turned on (X) in the appropriate field in the correct table.  Look for fields named like LTEX (?) or that seem to be a long text existence indicator.  You should be able to turn that on with a simple BDC session that does an update of something in the transaction and then presses save (without actually having to mark the box).   In my experience, SAP would usually recognize that the text existed and update that column automatically after the text had been created and the transaction saved, then the document subsequently reopened and changed via an update to some field on the screen...

5 REPLIES 5
Read only

former_member189779
Active Contributor
0 Likes
973

May be try doing it with text more than one line. Check what happens. I think in your case SAP treats it as short text and does not update anything.

Read only

0 Likes
973

after CALL FUNCTION 'SAVE_TEXT' you must call CALL FUNCTION 'COMMIT_TEXT'

Read only

0 Likes
973

ive done that too... it only happpens when it has to be modified.

i have done commit_text also.

also i have kept insert = 'X' and save_mode = 'X"

Read only

Former Member
0 Likes
974

Not sure I understand what you are asking...  Generally, SAP does not display long text if the long text indicator has not be turned on (X) in the appropriate field in the correct table.  Look for fields named like LTEX (?) or that seem to be a long text existence indicator.  You should be able to turn that on with a simple BDC session that does an update of something in the transaction and then presses save (without actually having to mark the box).   In my experience, SAP would usually recognize that the text existed and update that column automatically after the text had been created and the transaction saved, then the document subsequently reopened and changed via an update to some field on the screen...

Read only

0 Likes
973

True Agree with you... thats the case.. is there any other way other than BDC to do that. whats the use of create_text then???