Effective the week of November 13 , new exception fields will be created for Requisitions and Supplier Invoice Requests to help users with their exception tracking.
In "Requisitions," Service Centers will now be able to:
Select any of the following exception reasons that apply to the associated requisition: Improper Signature on Agreement After the Fact Meal and Alcohol Exceptions Non-Contract Spend Special Approval Missing Other Use a free-form Exception Explanation text field to explain what happened in more detail
In "Supplier Invoice Requests," Service Centers will now be able to:
Use a free-form text field to note the exception and explanation of why it occurred
It is recommended that end users with exceptions leverage Business Process comments to enter why the exception occurred so that Service Centers will be able to enter that information in the new exception fields.
To improve transparency into the supplier invoice request process, the Service Center Lead Approval step will be moved up in the business process from the supplier invoice where it currently resides to the supplier invoice request, keeping it streamlined within the same business process. This change is to improve transparency and align with other similar financial transactions in Workday.
These changes are targeted to be implemented into Workday on November 1 . If transactions are not approved in a timely manner there could be a period of time where they will not have the Service Center Lead approval. Units are requested to review and cancel "draft" supplier invoice requests that are no longer needed by October 31 . Additionally, units should request to move "in progress" transactions along to ensure all approvals are met. The OTDI Enterprise Business Solutions (EBS) team will also be granting Service Centers access to close supplier invoice requests effective October 26 .
As part of a standardization project, the business teams have been reviewing notifications for the Requisition and Purchase Order Business Processes to help create consistency across each process. These enhancements will be completed on Monday, October 9 . The change described below will be made to help improve the end user experience.
The “Requested on behalf of” will be notified if someone else (the initiator) starts a requisition on behalf of them. The requisition requester (and Requested on behalf of if applicable) will be notified if the amount of the requisition is changed by someone downstream. The requisition requester (and Requested on behalf of if applicable) will be notified if anyone other than the requester of a requisition cancels or denies the requisition. For Requisitions, only PCard, Inventory Replenishment and Change Order Requisitions the system will notify the requester (and Requested on behalf of if applicable) at completion of the business process. For everything else notification will go out at the issuance of a Purchase Order. Prior approvers will all now be notified if a subsequent approver denies the requisition.
See the full post for a reminder about how Workday notifies initiators, reviewers and approvers as a Workday transaction moves through a business process.
New tips and tricks information on the Requisitions process has been added to the Business and Finance website . This provides users with an overview of the business process and a crosswalk to additional resources.
New Inbox Filters for Workday were created mid-June for use on requisitions, match exceptions, supplier invoice requests, supplier invoices, spend authorizations, expense reports, and miscellaneous payment requests. The filters are specifically for tasks within the CCH8 cost center hierarchy. Additional explanation about the filter naming conventions along with a link to a “Create, Edit, and Apply an Inbox Filter” job aid can be found in the full NewsLink post.
OSU Surplus now offers a catalog in Buckeye Buy for small, medium, and large internal transfer deliveries to Columbus campus locations. A special request line is also available in the catalog. Contact OSU Surplus at firstname.lastname@example.org with questions.