Automatically Changing the Purchase Order Status Code Tip - Generating PO's

Automatically Changing the Purchase Order Status Code Tip - Generating PO's

To ensure the Purchase Order "Status Code" gets updated from "Planned" to "Order" when generating the Purchase Order, please ensure the 

Post Status Changes tick box is checked before you click on the "Print" button :  (as shown below)



Otherwise you will have to manually change it on the Purchase Order Header.

    • Related Articles

    • Cancelling a Purchase Order Tip - PO Header & Lines Screens

      If you have raised a Purchase Order with a some lines and saved it for later processing and then realised that you want to cancel it, please DO NOT delete it.... The preferred steps would be change the Purchase Order lines quantities to zero & save. ...
    • Check Purchase Orders - Purchase Order Status Report

      There are times when you would like to review the status of your Purchases\Purchase Orders.... This is easy done by running the Purchase Order Status report and selecting the appropriate selection fields - ie Order, Filled or Complete statuses... The ...
    • Creating Purchase Orders Tip - PO Header Screen

      It's easily done when you're in a rush when trying to raise a Purchase Order.... On the Purchase Order header screen ensure that you create the correct type of Purchase Order. - Regular or Blanket You will NOT be able to change to a Blanket Order ...
    • Viewing the Statuses of Purchase Orders Tip - Purchase Order Listing Screen

      To view the status of your Purchase Orders all in one go in a grid format, please open up the Purchase Order Listing form. All the Purchase Orders will be presented to you and then you can filter the list as you please...& export to Excel If required ...
    • How to view the status of a Workflow - Event Status

      This particularly applies to workflows that have been put in place on implementations & was highlighted by the Purchase Order work that exists on the Harman installation - (HAR-013 PO Authorisation Workflow) . - Tkt #484 There was an incident where ...