SAVE_TEXT problem - it can't lock??

[Former Member]

Hi, ALL.

I use the Function Module 'SAVE_TEXT' in my Zprogram.

It update the Sales long text in MM02.

When a user is in MM02, 'SAVE_TEXT' the Function Module doesn't return error message.

I think it's a LOCK error, but it's not.

Do I need to check LOCK before call function 'SAVE_TEXT' in Zprogram??

If you know that, please let me know.

Regards.

Rie.

[koolspy_ultimate]

This message was moderated.

[RaymondGiuseppi]

Your program must use the same logic than the standard program to manage locks.

- Lock same object(s) (ENQUEUE_Exxxx)

- Use same FMs like SELECT_TEXT, READ_TEXT, INIT_TEXT, SAVE_TEXT or similar tools

Tips: Execute transaction SE30 on MM02 and update a text, then evaluate the performance data file, look for call to FM starting with ENQUEUE or calls containing TEXT in the trace.

Remarks:

- A Save module is a little late to manage lock, no ?

- "I think it's a LOCK error, but it's not", it is a LOCK error, but in your program

- You could use BAPI_MATERIAL_SAVEDATA (table parameter MATERIALLONGTEXT) to update/create text, this one manages locks.

Regards,

Raymond

[Former Member]

Hi Raymond.

Thank you for repry.

I understood very well.

It's very helpful for me.

Regards.

Rie.