Last updated on MARCH 09, 2017
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 9 to 9.1 [Release 9]
Information in this document applies to any platform.
When a purchase order (PO) is rolled over, Project Costing creates a CCA commitment adjustment row to offset the remaining balance of the PO. A new COM commitment row is then created in the current year for that same remaining amount since that represents the rolled over PO amount. If a new line is subsequently added to the PO in Purchasing and the integration to Project Costing is completed, the accounting date on the original COM row in the PS_PROJ_RESOURCE table gets updated to the current year, matching the new COM row.
What should happen instead is that once the PO has been rolled over and integrated to Project Costing, the original COM row should not be updated at all.
The issue can be reproduced at will with the following steps:
1. Create a purchase order.
2. Run PC_PO_TO_PC
3. Roll over the PO in Purchasing.
4. Run PC_PO_TO_PC/PC_POADJUST
5. Add a new line to the rolled over PO
6. Run PC_PO_TO_PC/PC_POADJUST
Due to this issue, year end reports for the prior year are now incorrect because the PO lines for which COM rows were originally created now appear to be in the following year because the original COM row dates have been updated to the current year.
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