topic Re: doubt in Commit work in Application Development and Automation Discussions

doubt in Commit work

Former Member — Wed, 20 Dec 2006 07:04:26 GMT

I m using BAPI_CHARACT_CREATE to create a characteristcs.

after calling this bapi i have to give commit work.

in that characteristics i m passing some 3 charateristics value.

The problem which i m facing is the characteristics is getting saved 3 times with different internal.char number & the characteristics value is stored onces i.e first characteristics value is stored.

now i want to know where to give the bapi_transaction_commit either inside the loop r outside the loop.

i want to do mass updation. if i give inside the loop means i didnt think it will be mass updation.

Can any one clear me.

Thanks in advance.

Re: doubt in Commit work

Former Member — Wed, 20 Dec 2006 07:26:19 GMT

You have to do commit once only after calling this BAPI. This BAPI is for creating characteristics and not for assigning charachetersitics values....you can assign allowed values, default values etc.

Re: doubt in Commit work

Sathish — Wed, 20 Dec 2006 08:06:31 GMT

Hi,

COMMIT WORK can also be within the loop. It depends on the requirement.

Its better to have commit work once after the loop, but suppose there are going to be huge volume of data then having commit work after the loop would lead to short dump with message 'TIME_OUT'.

But commit work cannot be made in general, this could lead to problems.

There should be a logical end of processing of one loop.

When handling large volume of data can be used like below:

if ld_count gt 1000.

clear ld_count.

commit work.

endif.

endloop.

Re: doubt in Commit work

Former Member — Wed, 20 Dec 2006 09:07:22 GMT

Hi kalpanshri,

1. The problem will not be with commit work.

2. But minor problem may be with the source code.

3. Make sure u are passing different CHARACTDETAIL

in all those 3 calls.

*----

As per the FM documentation,

it is advisable to call commit work,

AFTER EACH call of this FM.

regards,

amit m.