Skip to main content
Skip table of contents

View PO Approval History Log

Content was last updated in 06.23.07-00

Revision History

  Version No.

  Reference No.

  Changes

  06.23.07-00

  R2-20689

  View the Purchase Order's Approval History Log

Introduction

PO Approvals are often subjective to stringent scrutiny and protocols. Every PO owner would want to know why and what happened to the Purchase Orders raised by them.

The easier way is to keep a log (chronological history):

  1. When was the PO submitted for approval?

  2. How many levels of approval it went through?

  3. Who was supposed to approve it at each specific level?

  4. What was the approval result at each of these levels?

  5. Was the PO re-submitted for approval again? If Yes, when?  

  • And the response to question 1-4 again for each round of re-submission.

 

All the above information is displayed in a read-only table.

Want to view the table? Click on the 'Approval History Log' button on the 'Approvals' tab in the Purchase Order Window.

 

The columns in the table can moved around and re-arranged.

See sample Approval History Log Table below...

 

The above grid has the following columns...

Table 1.0: Approval History Log Grid fields

Field name

Description

Submitted On

The date on which the PO (this iteration) was submitted for approval.

Level

The specific level of PO which is up for approval.

Amount

The upper limit of the PO Amount for approval.

Transaction Amount

The amount for which the approval was request.

Approver Type

To 'What category' of approver was this level submitted to.

Department

The 'Department' to which the current level's approver belong.

Mandatory (Y/N)

Whether the approval at current level was mandatory or not.

Approval Status

The outcome of the current level approval submission.

Remarks

The remarks/comments given by the approver at the time of approval/rejection

 

 

 

 

 

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.