Knowledge Management

Question:
Hello all,
I need to do an LSMW data load into a custom transaction,
that has a call to a bapi followed by a "commit work" .
The batch job kicks out when it reaches the commit work.
How do I get around this?
Should the Bapi call/commit work routine be called as an
"in update task" routine?
thanks
svish
Answer:
interesting question... you need to provide more info. I assume you did the LSMW mapping, and generated the conversion programs. Now, how are you converting the LSMW programs into a btach job?
Are you using DMV0, the Batch Input Monitor, to schedule the job? If so, be aware that it has its own internal methods of dealing with COMMIT WORK.
Are you using SXDA to schedule the job? Again, there are a lot of issues that SAP is still working out with these special batch jobs.
I stongly recommend you contact lsmw@sap.com
- they are very helpful with this kind of question - but provide full details!