Known Issue information: PPM Projects Missing POETAF Details on Project Based Purchases.
We want to inform you about an issue concerning project-based purchase orders. A problem arose after Oracle go-live, allowing buyers to allocate project-based funding using a COA chartstring instead of the Project Number, and related POETAF details would not populate (refer to the screenshot below).
Safeguards have been implemented to auto-rejected requisitions and purchase orders when this scenario arises, however, a few existing project-based purchase orders lack POETAF details and are currently being corrected. Additionally, an issue is being addressed regarding change orders because those orders are not being auto-rejected.
As a friendly reminder, when creating project-based requisitions and POs, ensure the Project Number value is entered. This guarantees that all related POETAF details are populated based on that project code. Avoid copying/pasting the COA chartstring in the Charge Account field for project-based funding.
Update - Where possible impacted purchase orders were canceled and a new purchase order was created.
PI Impact - Low - small number impacted
Expected Resolution: TBD