Last updated on FEBRUARY 17, 2016
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Project Costing > Utilities > Interest Calculation
PeopleSoft 9.2 - PeopleTools 8.54 - PUM 11
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 be corrected via SQL intervention.
SQL error. Stmt #: 1703 Error Position: 0 Return: 805 - ORA-00001:
1. Create journal entry to affect project for which Interest calculation has been set up. Include in the entry, 2 different deptids,
2. Post the journal,
3. Run the GL to PC process to bring the transactions into Project Costing
4. Run the Interest Calculation process.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms