Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from MASchumacher on Jan 17 at 10:59 AM Sorry I didn't understand the problem is setting the flag on the object that will tell the screen program to go look for the long text.
I've done that in QM using the functions to load the long text then updating the Notification flag via functions: 'IQS4_GET_NOTIFICATION', 'IQS1_FILL_BUFFER_FROM_WA' and 'IQS1_POST_NOTIFICATION'.
Do you have similar functions for the maintenance objects (read, update, post)?
You could set the language in the __END_OF_TRANSACTION__ section of the LSMW using those functions and you might want to include locking/unlocking. Note that the update of the language flag would occur during the Conversion Step before Start Direct Input so if it fails then I don't know what the screen maintenance would do when attempting to show a long text that doesn't exist.
Another Idea would to use LSMW to create 2 lines of long text for each maintenance object via a BDC that will set the Language flag then use the Long Text load to overwrite the 2 blank lines.
Margaret
| | | ---------------Original Message---------------
From: Maria Grazia
Sent: Tuesday, January 17, 2012 9:51 AM
Subject: LSMW - Upload of Long Texts
I set correctly all things and using the lsmw I didn't have any problems.
If I use function READ_TEXT i see exactly what I saved in long text.
I saw the note 138012 and it specifies that you have to update PLPO-TXTSP field after import (using a z-program) or : in the field assignment/mapping an update is coded on the respective table.
I would know if it is possible directly in LSMW or I must create a custom program.
Thanks,
MG |
| Reply to this email to post your response. __.____._ |  _.____.__ |
