1. Will all purchasing requisitions (reqs) and purchase orders (POs) in Cloud transfer to the new Oracle Cloud (Redwood UX)?
Yes. All existing purchasing requisitions and purchase orders will carry over to Oracle Cloud and be available in the updated Redwood user experience (UX).
2. Will I still be able to use the previous Oracle Cloud interface for purchasing requisitions after September 1?
No. After September 1, purchasing requisitions must be entered in Oracle Cloud using the Redwood user experience (UX).
3. Will draft purchasing requisitions created in Cloud transfer to Oracle Cloud (Redwood UX)?
No. Draft purchasing requisitions will not transfer.
- All FY25 purchasing requisitions must be submitted by July 18.
- FY26 purchasing requisitions will begin with a 26-9XXXX number.
- Anything created for FY25 will not be process in FY26.
4. Can I submit Emergency purchasing requisitions?
Not at this time. The Emergency checkbox should not be selected, as the system currently does not support Emergency purchasing requisitions. Doing so may cause delays.
5. Will anything change with Receiving when we switch to Oracle Cloud (Redwood UX)?
Not immediately. However, future changes may occur due to Oracle's quarterly system updates.
6. Why does Oracle change so often?
Oracle releases quarterly updates, many of which must be implemented. As a result, changes can happen even if we do not expect them. We adjust as needed.
7. What if my account approver is on vacation--how can I make sure our purchasing requisitions get approved?
Approvers should set up vacation rules before their time off. This ensures purchasing requisitions are routed to the next available approver without delay.
8. What happens if my approver forgets to set their vacation rule--can someone else step in?
No. Approvers are pre-assigned in the system and cannot be changed manually.