Unique Constraint on AFUDC Calculation

When calculating AFUDC in Project Costing, a unique constraint error is occurring because an erroneous deptid was added to a journal in GL.  The functional fix would be to reverse the journal entry and re-enter the journal with the correct ChartFields.  Unfortunately, this correction seems to only continue the error.  The app-engine, PC_INTEREST, in Section: 10000000, Step: INSERT1, Action: SQL, builds a temporary table based on "A.PROJECT_ID %Concat A.ACTIVITY_ID %Concat A.BUSINESS_UNIT_GL %Concat A.CALC_TYPE".  On the surface this appears as fine, but any error in other 'required' ChartFields used by the business will create a unique constraint error that can only