commit fail errors when entering POs

JDE List,

I am wondering if someone can shed some light on a fix for the issue my
client is having?

Randomly, users are receiving "order has been cancelled - commit failed -
view JDE log" when attempting to enter POs. Not all users get this but
once a user gets it once they get it repeatedly.

I have added the line - OracleServerHandleReuse=0 to the [DB SYSTEM
SETTINGS] stanza of their jde.ini and this doesn't seem to help.

Any insight, input or feedback is welcome.

Thanks,
James

ERP8 SP22 Update1
Oracle 8 running on HP Tru64
Windows2000 App Servers
Windows2000 TSE/Citrix for all clients (no 'fat' clients)

We have users experiencing the same issue.

Purchase Order processing uses Transaction Processing. That is a OneWorld
mechanism for doing commitment control. Your commit error is probably related
to Transaction Processing. Using an AS/400 enterprise server we received the
same commit error as a result of having the wrong release of an ODBC driver on
the client side. We also have received these commit errors as a result of an
incorrect IP configuration that added too much delay to the client receiving a
response from the database. There is a JDE.INI setting for how long the
client will wait for a response from the database. A good way to start testing
this error is to increase this setting and see at what point do the errors
cease. This tells you how much lag time you are experiencing in Transaction
Processing. Capturing job logs and running them through Performance Analyzer can
also help in diagnosing this problem.

Patrick Conlon
Allegheny County
XE U4 SP20, AS/400, Terminal Server, Citrix, Java Server, fat clients

You might also switch on debug, as I assume you aren't getting any info in
your jde.log. I had a similar issue and it related to a lock table that OW
maintained. There was junk data in there causing the commit failed error.
You may want to check some of the tables referenced in the jdedebug.log prior
to the error appearing.
Regards,
Kieran Fitzgerald

Also, when a user gets the error, check the c:jde.log file. When I've had these errrors in the past, I've seen ODBC errors specific to tables. Some of the messages pointed at tables that were missing and needed to be generated. For PO processing we've also had a problem with trying to add duplicate records to the supplier/relationship table due to a user changing the long item number for an item in the Item Master.