Effective January 15 , the sheet and report user interface within Adaptive Planning will be updated. The blue banner will be removed on all report and sheet pages and all search fields and data tables will have rounded corners. Additionally, the Add New button will move to a new location below the top menu bar on the report overview and sheet overview pages. The functionality on these pages will remain the same. See the full post to preview the new look.
A new report group, Financial Transactions Awaiting Action, has been released. This report includes three different reports that provide a list and the status of journal, accounting adjustment, and asset transactions that are awaiting an approval or to-do step. To run this report group, users can go to the "Schedule a Report" task and search for "Financial Transactions Awaiting Action." Once the prompts are entered and the report group runs, all reports will be available in one Excel spreadsheet.
In preparation for the combined federal and state filing changes, the Payee Setup Form along with the Miscellaneous Payee and Miscellaneous Payment Request tasks will be updated to include additional address prompts for 1099 income reporting when the state in which work is performed differs from the state associated with the payee’s primary address. The changes listed in the full post will occur on January 17.
Please do not begin entering FY26 blanket purchase orders until April 14, 2025. More information and detailed instructions on creating FY26 blanket purchase orders is forthcoming.
The field "Reference ID" has been added to the output of the "Find Miscellaneous Payment Request Summary - OSU" report. This change aids those needing the field to perform mass actions on miscellaneous payment requests.
The field "Inventory Stock Request Line" has been added to the output of the "Find Requisition Details - OSU" report. This change allows end users to identify the specific inventory stock request number to which the requisition was sourced.
During the week of January 27 , a new interface will be released for Payroll Accounting Adjustments (PAA) for retroactive payroll posted on a paycheck. Once this change is made, if there is a retro pay period associated with the earnings needing to be moved, PAA Specialists will now need to select the correct retro period.
Prior to this change, budget date was the main driver of associating payroll with the pay period for which the earnings were intended. Moving forward, the Retro Period Date will associate the PAA with a pay period. The budget date will default to the budget date of the retro period. See the full post for links to job aids, a Tips and Tricks page, and a new BuckeyeLearn module.
New hosted catalogs for drop-off and full-service catering and event equipment rental services are now in Buckeye Buy. These catalogs have replaced "The Catering Marketplace" supplier website which was removed from Buckeye Buy at the close of business on Friday, December 27 . See the full post for answers to common order placement questions.
New prompts have been added to the "Find Suppliers - OSU" report. Users can now prompt on the "Last Updated On or After" and "Last Updated On or Before" dates. The "Last Updated Date" has also been added as a column on the output of the report.
To assist with the year-end procurement roll-forward process, the Controller’s Office will be analyzing and closing out old internal and external Purchase Orders (PO) which meet the parameters listed below.
POs that are over two years old which have not been invoiced in the previous year (excluding POs for multiyear service contracts that are only billed annually, those related to construction projects beginning with "PJOSU," OAKS type POs, and those that are FD520 grant related).
This will occur the last week of December 2024. As a reminder, this process occurs on a 6-month closure cadence (during the last week of December and the first week of June each year). To see what POs will be closed as part of this process, run the "Find Purchase Order Details – OSU" report, and filter using the above parameters and the "last invoice date" column.
Once POs are mass closed, if there is a true need, they can be reopened by the service center if the transaction is within the same fiscal year. If you see that a PO is closed and believe it was closed in error, review the process history of the PO and contact the user who closed it. Users with the Spend Analyst security role can view who closed POs in the PO process history.
While this is a semi-annual cleanup effort, units are still required to work with service centers to close POs on a regular basis and once it is apparent the PO will no longer be used.