topic Re: Dump COMMIT_IN_PERFORM_ON_COMMIT in Application Development and Automation Discussions

Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Mon, 22 Feb 2010 12:19:02 GMT

Hi,

I am getting Dump COMMIT_IN_PERFORM_ON_COMMIT on saving user ID 0105 suty 0001. The dump occurs at commitwork in a BADI.

when doing this through a customised workbench it gives the dump. Doing the same on thru PA30 diesnt cause a problem. Plz help.

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Thu, 25 Feb 2010 11:47:34 GMT

the following thread Naila Ubaidulla face same issue so please see the thread

Edited by: Krupaji on Feb 25, 2010 12:51 PM

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Thu, 25 Feb 2010 11:47:39 GMT

if you are using this FM in the user exit or enhancement, please set the value of NOCOMMIT as 'X'.

because COMMIT WORK is not allowed within a FORM, which is called using PERFORM ... ON COMMIT.

Edited by: Krupaji on Feb 25, 2010 12:54 PM

Edited by: Krupaji on Feb 25, 2010 12:56 PM

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Thu, 25 Feb 2010 11:50:11 GMT

Hi,

You have to avoid COMMIT WORKs in Badis and User exits!

This is a general proposal of SAP.

regards,

Chris

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Fri, 26 Feb 2010 07:07:26 GMT

Thanks for all your response.

Is it necessary to use a COMMIT WORK after an insert?

INSERT /virsa/int_trig FROM l_int_trig.

IF NOT sy-subrc IS INITIAL.

CALL FUNCTION 'POPUP_WITH_WARNING'

EXPORTING

textline1 = text-e01

textline2 = text-e02

titel = text-e05.

EXIT. " Do not continue processing w/o trig number

ENDIF.

COMMIT WORK.

Also, it is puzzling that through PA30 this dump doesnot occur buth through the customised workbench the dump comes?

Any idea?

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Mon, 29 Mar 2010 05:43:49 GMT

any idea?

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Mon, 29 Mar 2010 06:40:20 GMT

Hi,

PERFORM XYZ ON COMMIT is an update module(V1) and hence you should not have any statements that might invoke Implicit or explicit COMMIT. Your changes will get committed to the DB without you needing to invoke a explicit COMMIT.

Also, take off the POP_UP_TO_CONFIRM FM, this will again cause an update termination.

If you are worried about duplicate records error, use modify.

regards,

Chen

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Mon, 29 Mar 2010 06:45:59 GMT

Thanks will try that out and let u know.

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Former Member — Mon, 29 Mar 2010 10:27:08 GMT

is there a limit to the number of commit works as per SAP standards?

Re: Dump COMMIT_IN_PERFORM_ON_COMMIT

Sandra_Rossi — Mon, 29 Mar 2010 22:22:17 GMT

What do you mean? You need one commit work to commit your updates. Or more if you experience performance issues (for example, committing after 1 million updates is generally not a good idea!) Ask your DB administrator, he will explain you.