topic Re: The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX ! in Application Development and Automation Discussions

The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX !

Former Member — Tue, 04 May 2010 22:52:27 GMT

Ok guys - someone has to "come clean" here and tell me what's what.

There are a million threads here which tell you that if you want to create equipment long text, you can use the FM's

INIT_TEXT, SAVE_TEXT, and CDMMIT_TEXT for object EQUI and ID LTXT.

So far so good - I have used these FM's to create long text for a piece of equioment created via BAPI_EQUI_CREATE.

But this sequence of FM's does NOT update EQKT-KZLTX (the long text indicator.)

What FM can I use to tupdate EQKT-KZLTX safely ?????

Thanks in advance.

Re: The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX !

Former Member — Wed, 05 May 2010 00:25:30 GMT

Hi David,


What FM can I use to tupdate EQKT-KZLTX safely ?????

For lack of a SAP system I don't have a good answer and I'm not sure whether there is an officially released function module for doing that. But just in case nobody comes forward with a nice way do it, here's one suggestion that should work if you have the enhancement framework (e.g. if you're on ECC 6.0)...

As far as I remember creating equipments via transaction or BAPI results in a call to EQUIPMENT_SAVE. Here you could easily create an implicit enhancement and set the long text flag (of course there should be some conditions to prevent setting it when it's not required).

The function modules you've quoted for text handling are basically universal function modules that are utilized in SAP whenever we have long texts associated with an object. Not all objects have some long text indicator and instead the application just checks if a long text exists; unfortunately though for equipments this is different as you already observed. Since the text function modules are generic, obviously any utility for setting the long text flag for an equipment record should be found in PM/CS area...

Now, if you choose to go ahead with an implicit enhancement I'd suspect that you might even get away with calling INIT_TEXT (or maybe EDIT_TEXT?) within the BAPI for adding the text. I think there should be logic in EQUIPMENT_SAVE to deal with any long texts that are present, so saving/commit should be handled by EQUIPMENT_SAVE automatically. However, due to lack of system access this is more or less speculation, but you can test this easily...

In the end I hope somebody else has a clean method to offer, but just in case you don't get any good response I thought this might help (especially since this should allow you to use one update instead of several).

Cheers, harald

Re: The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX !

Former Member — Wed, 05 May 2010 00:49:11 GMT

Hi Harald

You read my mind - I was just about ready to decide to use an enhancement point for the following reason.

After I create my piece of equipment via BAPI_EQUI_CREATE and store some long text for it via INIT_TEXT/SAVE_TEXT/COMMIT_TEXT, I go into EQKT and see that the KZLTX flag is NOT set.

But then, if I go into IE02 on the equipment number I just created, bring up the long text, and then do a save - then voila! the flag is now set.

This tells me that the setting of the flag is in some piece of code in the SAPMIEQ0 module pool or the ITO0 , and that this piece of code is NOT part of the text functions per se.

And if this is the case, then I'm going to have to use a judiciously placed enhancement.

Thanks for taking the time to reply and reinforcing my own opinion.

Best regards

djh

Re: The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX !

Former Member — Wed, 05 May 2010 01:03:33 GMT

Harald -

One afterthought - since I know that an IE02 save after visiting the long text will force the flag to be set, I may just write a BDC that just does these two keystrokes and see what happens. If the BDC overhead was greater, it would bother me, but a two key-stroke recording isn't going to kill anybody. (Assuming, of couse, that I can do a BDC which includes a visit to the long text editor ...)

Best

djh

Re: The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX !

Former Member — Wed, 05 May 2010 01:19:49 GMT

BDC will work. Didn't want to suggest that though, because I felt the (ugly) solution with implicit enhancement probably would allow one to post all the data in one transaction. I've done similar things in the past (e.g. partner updates where partners were not part of the function's interface) and despite the bad taste such odd solutions leave, I really do appreciate the ability not having to deal with error handling and recovery for partial updates...

Re: The INIT_TEXT/SAVE_TEXT/COMMIT_TEXT FM Sequence Doesn't Update EQKT-KZLTX !

Former Member — Wed, 05 May 2010 01:26:24 GMT

I think the potential solutions (two) have both been identified ...