Re: MESSAGE_TYPE_X Dump

Former Member — Wed, 10 Feb 2010 10:02:28 GMT

Hi,

I'm getting message_type_x dump at runtime. I tried changing the code with all possible ways but not able to figure out the issue.

Error analysis

Short text of error message:

Unexpected COMMIT WORK

Long text of error message:

Diagnosis

A COMMIT WORK was executed unexpectedly.

In order processing, a COMMIT WORK may not be carried out until the

save process is finished because otherwise the order data may be

posted incorrectly or incompletely.

Procedure

Contact your SAP Administrator.

Procedure for System Administration

Ensure that you do not execute a COMMIT WORK in a User Exit or BAdI

and that you do not call any SAP functions that execute a COMMIT

WORK from User Exits or BAdIs.

For details on how to proceed, see the long text about the program

termination.

Using transaction OPJB set the type of this message to X (as the

version, enter 00000000 as a default) in your production system.

Technical information about the message:

Message class....... "C2"

Number.............. 295

Trigger Location of Runtime Error

Program SAPLCOZV

Include LCOZVU26

Row 70

Module type (FORM)

Module Name COMMIT_SUPPRESS

Thanks,

Anshuman

Edited by: Rob Burbank on Feb 10, 2010 9:12 AM

Re: Re: MESSAGE_TYPE_X Dump

Former Member — Wed, 10 Feb 2010 10:29:08 GMT

Hi,

Check if exist a user exit or badi making a commit work...

Regards,

Re: Re: MESSAGE_TYPE_X Dump

Former Member — Wed, 10 Feb 2010 14:20:58 GMT

Have you looked for OSS notes? There seem to be a number that may be related.

Rob

Re: Re: MESSAGE_TYPE_X Dump

Former Member — Tue, 10 May 2011 12:44:41 GMT

Closed

topic Re: Re: MESSAGE_TYPE_X Dump in Application Development and Automation Discussions

Re: MESSAGE_TYPE_X Dump

Re: Re: MESSAGE_TYPE_X Dump

Re: Re: MESSAGE_TYPE_X Dump

Re: Re: MESSAGE_TYPE_X Dump