Hi, it's been common to have those unique key ID duplicated or violated. Eg, UKID
This could be due to possibility that data refreshing from 1 environment to another..But some of the tables are not refreshed / copied over. Eg. F00022 against F43199
Let's take this example : Progress Payment Error
User hits a web exception error when doing his/her progress payment.
Based on the debug log : We found
Oct 15 11:03:39.312002 - 3460/3052 WRK:Starting jdeCallObject OCI0000179 - Error - ORA-00001: unique constraint (CRPDTA.F43199_PK) violated
Oct 15 11:03:39.312006 - 3460/3052 WRK:Starting jdeCallObject JDB3400009 - Failed to perform Insert for F43199
Solution will be:
1. Open up P00022 Next Unique Number and check if the number for F43199 is bigger than the last record stored in crpdta.F43199
If not, pls change the next unique number in P00022 to higher number to avoid PK violation.
This could be due to possibility that data refreshing from 1 environment to another..But some of the tables are not refreshed / copied over. Eg. F00022 against F43199
Let's take this example : Progress Payment Error
User hits a web exception error when doing his/her progress payment.
Based on the debug log : We found
Oct 15 11:03:39.312002 - 3460/3052 WRK:Starting jdeCallObject OCI0000179 - Error - ORA-00001: unique constraint (CRPDTA.F43199_PK) violated
Oct 15 11:03:39.312006 - 3460/3052 WRK:Starting jdeCallObject JDB3400009 - Failed to perform Insert for F43199
Solution will be:
1. Open up P00022 Next Unique Number and check if the number for F43199 is bigger than the last record stored in crpdta.F43199
If not, pls change the next unique number in P00022 to higher number to avoid PK violation.
No comments:
Post a Comment