‎2008 Nov 06 1:49 PM
Hi All,
VT02N is dumpling.
in dump analysis it's showing comiit work is not aloowed in update function module.
that is standard program but cutmization has been done through BADI.
Can anyone tell me how cope with this error?
let me know any suggestion.
Thanks in advance.
‎2008 Nov 06 2:10 PM
you have the error messgae, and the dump will give you the source code where it is happening. Just fix the custom code you applied to it.
‎2008 Nov 06 2:10 PM
you have the error messgae, and the dump will give you the source code where it is happening. Just fix the custom code you applied to it.
‎2008 Nov 12 12:38 PM
HI MxG,
Actually i tried a lot but help less.
The standard program is enhanced with BADI code.
It's giving in dump in update Function COMMIT is not allowed.
what has to do for the same?
I will appriciate any suggesstion.
Thanks & Regards,
Flavya
‎2008 Nov 12 2:59 PM
Hi
Please check the BADI where the custom code is written. There probably some custom/standard function module is being called in update task and if custom FM is being called then check whether that particular Function Module is having any commit work at the end or NOT. If not then check whether in that BADI any explicit COMMIT is placed or NOT.
This is a common mistake in enhancement to put explicit Commit WORK with in BADI or User EXit which is just dangerous !!
Update task module gets called when the immediate commit work gets triggered. In this case the function module gets started but along with that its facing some COMMIT.
You also can check the CALL LIST once you are getting the short dump and see whether any system commit gets triggered or NOT. If any explicit COMMIT is placed just remove that. No need to worry about the commit SAP will handle that.
Cheers,
Somnath
‎2008 Nov 06 3:16 PM
hi flavya
u do one thing use the OSS Notes ur problem will salve.
‎2008 Nov 12 12:36 PM
But can u suggest me any notes apllicable for VT02N Tcode?
Regards.
Flavya