Commit failed or was Canceled on fat client

Hi, this has been common issue if after doing data refreshing from PD to PY, the F00022 next unique key table is not identical between PD and PY.

consider by copying proddta.F00022 
(control table) to crpdta.F00022 , this method would be eliminating the 
need of changing each next unique number with its field in UTB. Oracle 
suspects when doing data refreshing, it didn't include this table. 


In order to copy this table F00022 from production environment, you 
may choose either in SQL tool, or in OMW - Table Design - Table Operation 
- Copy table 
After copying whole table from PD to PY, it does hit the same error, then 
you need to do the steps given earlier. One thing to note that by using 
this method can't guarantee 100% w/o commit fail error because the 
running number of each application might have exceeded the highest number 
in P00022 of PD after you had run the application quite some times. 

The good practise is to make sure this table F00022 in these 2 
environments look identical after data refreshing is done. 

Otherwise, you need to modify the the next unqiue key in P00022 based on the its table's SCUK01 field value.  See attached.