2010 Feb 10 10:02 AM
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
2010 Feb 10 2:20 PM
Have you looked for OSS notes? There seem to be a number that may be related.
Rob
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
2010 Feb 10 10:29 AM
Hi,
Check if exist a user exit or badi making a commit work...
Regards,
2010 Feb 10 2:20 PM
Have you looked for OSS notes? There seem to be a number that may be related.
Rob
2011 May 10 1:44 PM
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |