|
Use the History tab to view information about actions performed on an
order by the builder or supplier. Examples of actions include: when an
order was submitted or when an order was marked as complete as well as
any notes entered.
The History tab gives users detailed information as to the history of
the order, including the date, user change (Action
taken), user making the change, BuildPro and SupplyPro status, and any
notes associated with the change. This helps decrease communication problems
between builders and suppliers by keeping order information and statuses
consistent between BuildPro and SupplyPro.
Users can view read receipts for notes sent to SupplyPro. When a note
is sent from BuildPro to SupplyPro, a read receipt will appear on the
History tab showing when the supplier read the note. Also, when the builder
reads a note from SupplyPro, a read receipt appears on the SupplyPro History
tab showing when the builder read the note.
To access the History tab:
Click on the Jobs
tab. Click on a Job Name
link. The Job Actions page opens. Click on the Job Management
– Express link on the Field Actions
tab. The JME page opens. Choose from the filters, and click the Show
Tasks button. Click on a PO Status
link next to a task. The Order Detail page opens. Click on the History
tab.
History
Tab Columns
From
- User that performed the action. An icon will appear to the left of the
user's name indicating the user is a BuildPro or SupplyPro user. Action
– Action taken by the BuildPro or SupplyPro
user. BP
Status – Status of the order in BuildPro after the action was taken. SP
Status – Status of the order in SupplyPro.
If the SupplyPro user reschedules, displays ’r;Pending BP Confirmation.’ Notes
– Any notes entered and sent with the
action. Date
– Date and time the action was taken.
User
Actions
All of the actions listed in the table below describe what the user
(BuildPro or SupplyPro) can do to an order. These actions and the way
they display on the History tab are consistent across BuildPro and SupplyPro.
Most of the possible actions are listed in sequence, following the usual
life cycle of an order.
Order
Submitted – Builder starts the task and submits the order to the
supplier. Order
Acknowledged – Supplier acknowledges/receives the order. Change
Order Requested – Supplier requests a change order. Order
Re-transmitted – Builder re-transmits a task to the supplier. Order
Rescheduled by Builder – Builder reschedules a task. Order
Rescheduled by Supplier – Supplier requests a reschedule. Order
Reschedule Accepted by Builder – Builder accepts supplier reschedule. Order
Reschedule Accepted by Supplier – Supplier accepts builder reschedule. Order
Reschedule Declined – Builder declines supplier reschedule request. Order
Partially Shipped – Supplier partially ships order. Order
Partially Received – Builder partially receives order. Order
Completed by Supplier – Supplier marks order as complete. Order
Cancelled – Builder cancels order. Order
Completed by Builder – Builder marks order/task as complete. Order
Completed With Exception – Builder marks order/task as complete
with exceptions. Order
Exception Removed – Builder removes exceptions. Order
Undo Complete Builder – Builder undo’s order/task completion. Order
Undo Complete Supplier – Supplier undo’s order completion. Note
Sent – Builder or supplier sends a note to the other without taking
any other action. Note
Read Receipt – Indicates that the builder or supplier has read
the note sent by the other. Integration
Changes – Changes were made to the schedule by the builder's back-office
system.
|