At a place as widespread as The Ohio State University, staying organized and informed is crucial for success. For students navigating life and classes at Ohio State, the Ohio State mobile app has become an important tool,...
Customer deposit transactions created and submitted on or after Friday, December 1 will have a transaction ID generated called "Customer Deposit ID." The Customer Deposit ID will be like other transaction IDs within Workday and will uniquely identify the deposit. The Customer Deposit ID will be preceded by "CD" and it will be followed by 8 numeric digits. The new Customer Deposit ID will be displayed on various deposit-related reports. Multiple cash sales can continue to be tied to a single customer deposit transaction. In such a scenario, the Customer Deposit ID will appear on all of the associated cash sale transactions under “Deposit Detail” section.
As part of our continuing efforts to respond to the needs of our users, the Digital Union: Work Studio in Hagerty Hall has added a new podcast studio for students, instructors and staff. While the Digital Union already has an audio studio at the Digital Union: Recording Studio located in Denney...
A new Workday access request form is now available in ServiceNow. The new form introduces features to help you find the right Workday role, including the ability to filter available roles by business area and user audience. The form also allows you to see a mapping of common Workday activities and the access needed to complete them.
Navigate to the form using ServiceNow Self Service (go.osu.edu/it) and then follow the path: Order Services, Access Management, Workday Access Request.
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.
In preparation for Position Control enhancements, a new "Central Review Required" field has been added to the output of the "Cost Center – FDM Values" report. This field will be used to identify whether a cost center will require central review within the job requisition business process.
Find Purchase Order Summary – OSU:
The "Find Purchase Order Summary – OSU" report has been enhanced with two new additional fields to the report output. The new fields are “Initiator of BP” and "Last Activity Date." The "Initiator of the BP" (Business Process) identifies who initiated the business process while the "Last Activity Date" field was added to help end users find purchase orders that have not had recent activity.
Find Purchase Order Details – OSU:
The "Find Purchase Order Details – OSU" report has been enhanced with two new additional fields in the report output. The new field names are “Last Invoice Date,” and "Last Activity Date." These fields were added to help end users find purchase orders that have not had recent activity. This allows end users to identify which purchase orders may need to remain open and which ones can be closed.
A new filter has been added to the "Historical Paid Vouchers (APU111DW)" tableau report. Users now have the option to select PO ID in Historical Paid Vouchers dashboard filter tab along with the other filters.
Exceptions Reporting:
To accommodate changes to policy exception tracking in Requisitions and SIRs, there are several reporting changes pertaining to Exceptions which are further detailed in the full NewsLink post.
If an email message documents university business, it must be managed as a university record. The legal implications of smart email management are the most important reason to establish good habits. In addition to the legal implications of email management, there are storage considerations as well. To prepare for the future, we need to consider our email footprint now, and make changes to ensure that storage is being used for business items that are a priority for the university.
BuckeyePass , powered by Duo Security, is Ohio State’s method of multi-factor authentication (MFA), assisting in keeping our systems safe and helping us stay ahead of security threats. New passkey authentication methods are now available, making it...
Shortly after the September 2023 release, in some cases, when a Period Activity Pay is initiated as part of a hire or add job, an error message may occur during the Cost Center Manager approval step.
The message displayed is “The entered information does not meet the restrictions defined for this field.” Cost Center Managers are unable to bypass the message. A ticket has been logged with Workday.
In the meantime, the workaround is to have the initiator of the period activity pay cancel it. Once it has been canceled, the hire or add job is completed and the period activity pay can be reinitiated as a standalone transaction. The error message will not appear, and the Cost Center Manager can approve as usual.
Apologies for any inconvenience this may cause. An update will be provided when Workday have delivered a fix.
A new Workday access request form will be launched on Monday, November 13 . The new form introduces features to help you find the right Workday role including filters and a list of common Workday activities mapped to the access needed to complete them.
