on 05-03-2006 8:16 AM
Hi ,
Ive been trying to identify how to create long texts for service orders and have not come up with anything.
The following FMs have been identified
CREATE_TEXT
SAVE_TEXT
COMMIT_TEXT
CREATE_TEXT looks like it calls the other two.
Essentially we are uploading long text into service orders.
Ive been trying to manually run these FMs but still havent been able to create a long text. We need to be able to create a long text for a service order that doesnt already have a long text. Therefore there wont be any entries in STXH or STXL which I believe is where they are stored.
Created a new service order by going into IW31
Order type, Plng Plant ,Sold-toParty ,Mn Wk ctr and
Saved
This created a new Service Order without a long text. To find out how the long text affects the table entries, I changed service order with some long text and saw the entries created in STXH or STXL. For some reason trying to re-create using the FMs does not work.
Pls help me to complete this issue.
What parameter need to be passed to this FMs.
Rgds,
Priya
Yes we ran into the same problem, basically it comes down to lenght of the short text. If when creating your order you put more than 40 characters in the short text, it will work and you can view the save to long text via IW33 and Read_text, but if your short text is shorter for some reason it doesn't know to read the long text table thus its not viewable. Kinda sucks as we are on release 4.6c and I don't see any bapis that allow changes to update the order. Supposably they have some in the new release which we are slated for in July.
If anyone had any success with this please let me know
Cheers,
Devlin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Experts,
Even I am facing the same problem,
After creating the long text using SAVE_TEXT followed by COMMIT_TEXT , Long text gets created ( an entry in long text tables ) but doesn't get reflected on the transaction(Dont know why ). if i read the text i created above using READ_TEXT, it returns the text but the same is not getting reflected in the transaction IW32/IW33 .
Any help is Welcome...
Regards
Divakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Priya,
Open the text in the service order in the full screen mode. In the menu Go To--> Header, you will see the parameter values that you need to be pased.
TDOBJECT
TDNAME
TDID
Regards,
Ravi
NOte : Please mark the helpful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi,
I have done create_text, save_text and commit_text.
create_text.
~~~~~~~~~~~~
FID = KOPF
FLANGUAGE = EN
FNAME = 210000050000564 (client,soldparty,service order)
FOBJECT= AUFK
SAVE_DIRECT = X
FFORMAT = *
tdline = THIS IS A LONG TEXT
save_text
~~~~~~~~~
header details :
TDOBJECT AUFK
TDNAME 210000050000564
TDID KOPF
TDSPRAS EN
TDMACODE1 IW32SAPLCOIH
SAVEMODE_DIRECT X
lines : long text 3
long text 2
long text 1
commit _text
~~~~~~~~~~~~
OBJECT AUFK
NAME 210000050000564
ID KOPF
LANGUAGE EN
T_OBJECT-low = AUFK
T_NAME-low = 210000050000564
T_ID-low = kopf
T_LANGUAGE-low = en
I have done the same but not able to see the long text data in the table (aufk-ktext).
-Priya
Priya,
If you are looking at updating the field aufk-ktext, then we are on the wrong track. These functions update the text the SRXH and STXL tables and you can see them either on the Text editor screen or using READ_TEXT. This will not be save in the field aufk-ktext.
For that you will have to find a BAPI/function that updates the order itself where aufk-ktext is also a part of it.
Regards,
Ravi
Note : Please mark the helpful answers
Hi
You should use fms WRITE_TEXT and SAVE_TEXT, here transfer the header data:
TDOBJECT -> Text Object
TDNAME -> Text Name
TDID -> Text ID
TDSPRAS -> Text language
You should know these parameters, they depend on the kind of object (in your case service order).
It's better to transfer the lenght of the line to the header parameter TDLINESIZE.
Transfer the text lines to LINES.
Max
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.