P4210 - Corrupt Central Object

Dear List,

We are testing ERP 8 in the PY environment and we are having problem with P4210 - it didn't merge correctly. We can do a check out but after we retrofitted the application we can't check it back in. We tried to remerge it again by running R98700 but it still doesn't work. Something must be wrong with the spec in the database. We even did a get from Pristine but still cannot check it back in. The OMW logging mentions something about the spec record count (Source and Target count mismatch). When I looked at the jde.log, it says: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'F98751_PK'. Cannot insert duplicate key in object 'F98751'. - SQLSTATE: 23000. Has anyone seen this before? I'm not sure whether I can go to the spec table and delete P4210. Any advice?

Thanks in advance for your help,
Tet Hadavas

OneWorld Xe, SP 17.1, Windows 2000, SQL 2000 (Production)
ERP 8, SP 20, Windows 2000, SQL 2000 (Prototype)

This sounds like the "orphan" record issue. If you look at the JDEDEBUG
you should get a long alphanumeric key that it is trying to insert.
There is a document on the KG on how to diagnose and fix this issue if it
indeed is your problem. I'll see if I can dig up the doc number.

Jim
On Wed, 19 Mar 2003 13:16:52 -0800 (PST) tet_hadavas

________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com