History helps buyers and suppliers to follow and track every action taken on a PO line. Proposed changes, accepted changes, rejected changes, notes and which user took each action and when. This allows both buyers and suppliers to have full visibility and accountability.
Where can I see the PO History?
PO line history is available in a few areas: from the PO Dashboard, the Accept/Propose window, & within the PO Dashboard.
From the PO Dashboard
The history is available on all tabs as a column on the tables. Within the "History" column, click on "View"
Within the Accept/Propose Changes window. Click on the ellipses button next to View Purchase Order.
The PO History page will note when actions were taken, when POs move from one status to another and gives buyers access to the email history for new POs and cancelations from the ERP.
PO Email Notification History
For POs created after Feb 24, 2025 the New PO email history will also be available in the PO History. Buyers may been to scroll the table to see the Notification History in the right column.
The Notification History will list the email type sent to supplier recipients and the delivery status.
Glossary of terms for PO History
Sometimes the wording in the history section can be confusing. It can help to understand which actions are driven by users, and which are driven by the system. This table will help you to match actions to the values in your history table.
|
Action |
Group |
Description |
|
NULL |
|
|
|
Acknowledge |
Systematic |
Order acknowledged by Supplier |
|
Associated Order Created |
User |
Split PO created |
|
Automatic Push To ERP |
Systematic |
Updated information is pushed from SD to downstream applications (Maestro/E-Req) |
|
Buyer Change |
Systematic |
Change implemented from ERP/PO Pushout |
|
Buyer Created Reminder |
User |
Buyer creates a reminder for an order line |
|
Buyer Noted Purchase Order |
User |
Buyer adds a note to an order line |
|
Buyer Notified |
User |
Supplier sends a notification to the buyer |
|
Buyer Prop Update (PO Exception) |
User |
Update from Planning tool/PO pushout, sent to the supplier |
|
Buyer Reminder |
Systematic |
Reminder set by the buyer is triggered |
|
Canceled |
User |
Order line is canceled |
|
Hot |
User |
User marks an order line as urgent in SD |
|
Late |
Systematic |
Order line due date doesn’t equal need |
|
New PO |
Systematic |
PO enters SD for the first time |
|
Ontime |
Systematic |
Supplier date = desired due date |
|
Order Approval Denied |
Systematic |
Order was denied creation |
|
Order Approved |
Systematic |
PO approved by buyer and is sent to supplier |
|
Order Created In SourceDay |
Systematic |
Split PO created |
|
Order Pending Approval From Manager |
Systematic |
Order is above the threshold of planner $ amount, waiting on manager approval |
|
Partial Shipment |
User |
Partial of total shipment has been executed |
|
PO Moved to Planned |
Systematic |
PO Status was moved to planned within the Buyer ERP |
|
Projected Late |
Systematic |
Order line due date doesn’t equal need |
|
Proposed A Cancellation |
User |
User proposes a cancellation |
|
Removed From Hot |
User |
Order removed from Hot flag categorization |
|
Shipped |
User |
Supplier marks an item as fully shipped |
|
Successful Write to ERP |
Systematic |
Updated information is pushed from SD to downstream applications (Maestro/E-Req) and accepted |
|
Update Accepted |
User |
User accepts an update from the other party |
|
Update Failed |
Systematic |
Update failed to push back to (Maestro/E-Req) |
|
Update Rejected |
User |
Buyer rejects a proposed change from supplier |
|
Update Requested |
Systematic |
Requested update from the other party |
|
Vendor Marked As Unshipped |
User |
Vendor marks an item that was shipped, to unshipped |
|
Vendor Proposed Update |
User |
Supplier proposing a change |
|
Vendor Reopened |
User |
Supplier reopens PO line after requested cancel |
|
Vendor Responded Non-Cancelable |
User |
Supplier will not allow cancellation |