K1000 - Purchase Orders

Is anyone using the K1 to enter and track PO information? If so, how are you doing it? We are considering abandoning our current ticketing system in lieu of the Kace service desk. We currently enter POs and print them out from our old system. Not seeing how I could print out a PO form. Only thing I can think of is attaching one to an asset but that means manually filling in the form, printing it out, then attaching it. Let me know what you may be doing out there in your own environments...

1 Comment   [ + ] Show comment
  • How's this working for you Chuck?
    We are embarking on this same idea. Looking for what folks have done to build out a KACE PO generator and order tracking system. - Yippeekayaye 1 year ago
    • It's still working well for us. If I was building it today I would probably use the now included "Purchases" asset type instead of rolling my own. Otherwise there isn't a lot I would change. If you like I can post some of the rules I have running that handle some of the math involved (purchased item costs, total cost) and logic for closing tickets automatically (when all items are marked as received), etc. - chucksteel 1 year ago

Answers (1)

Posted by: chucksteel 5 years ago
Red Belt
We have a queue configured for purchasing. As part of the configuration I created an asset called "Purchased Assets" and those can be selected when our purchaser makes purchases. Custom rules pull in data from the asset such as price and enters those in the ticket. Each individual purchased item is a child on a parent ticket. This makes the ticket view a little complicated because the parent ticket includes the fields for the individually purchased items.

When a user enters a purchase request we supply what needs to be purchased in the comment and set the required fields. The purchaser then creates child tickets for each purchase. When items are received our receiving folks update the child ticket's status to indicate that to the requestor. 

Another thing I did was create a custom rule that adds the ticket number to a field in the Purchased Items asset so you can look at a purchased item and find on which tickets that item has been purchased. 

One thing we can't do with this system is generate an actual printed purchase order but our institution has a separate system tied to our central accounting system (Banner) that provides that functionality. Where an actual PO is required our purchaser generates it in that system and can attach it to the ticket. She also attaches any paperwork from vendors to tickets so it is easy to go back and reference in the future.

  • LOL I hope that's your work number and not your cellphone on the screenshot. - h2opolo25 5 years ago
    • Yes, that was my work number. Thanks. - chucksteel 5 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ