Notice: Effective November 1, 2024, travelfeedback@ucr.edu and epayfeedback@ucr.edu will be retired. To request services or assistance from the Accounts Payable/Travel team, users must submit a ticket through Finance and Administration Support (service-now.com).
Please begin preparing for the transition now, as inquiries sent to either email after 10/31 will not receive a response.
On 12/7/2023 a new auto-rejection rule for PCard Records in Procurement was deployed. This was to ensure that these records used for tracking PCard requests were entered correctly to prevent incorrect encumbrances from being created and causing downstream issues. The rule did not allow for Project COA’s to be used on PCard requests. As a result, this change has been rolled back. We apologize for any inconvenience this may have caused you.
The Impact23 Project Team will ensure that the new solution, expected around 12/15/2023 will allow for Project COA’s to be used prior to deployment.
As a reminder, if you have access to a PCard and are documenting purchases in Oracle Procurement, please ensure that the requisition has:
- Select PCard as the supplier
- The PCard number selected from the dropdown on the requisition
Reminder: this is not the actual card number, but a system identifier for the card.
When this is implemented in the future, the following outcomes will occur:
|
|
PCARD # |
SUPPLIER “PCARD” |
OUTCOME |
|
1 |
Selected |
PCARD |
Requisition Record will be Created |
|
2 |
MISSING |
PCARD |
Requisition Auto-rejected |
|
5 |
Selected |
Other Supplier Selected |
Requisition Auto-rejected |