Several Purchase Order suggestions
I'm going to be dumping a list of suggestions for purchase ordering under service desk plus.
I'll try to put all the items here, and hope I can do so without adding pictures or losing the meaning as I describe them.
1) (Repeat) Selectable approval person for purchase orders, based on $$ approval levels. This name should also get automatically selected for email when seeking approval, and be able to allow additional names for mailing out if desired.
2) Do NOT classify all P.O's as being assets. We need to be able to select if it's an intangible (ie, contract or service) Be able to tie these PO's to the contracts, assets or not at all (one time situations)
3) When a PO is closed, the shipped assets can be included into maintenance contract, but you cannot see the entire field (we couldn't see the PO# it was tied to).
4) When looking at assets, it would be WONDERFUL if we could search for some text (description, workstation name, product type, etc) or filter by asset name, PO#, user, dept., site, etc.
5) When creating a purchase order, have a list of selectable shipping addresses or selectable/default billing addresses to send it to (site-wise), instead of having to type it over and over. Obviously, we'd have to enter or select the name for the delivery person, but we have regular sites/delivery locations. Why re-type them?
6) For PO's, we need to be able to distinguish between consumables and real assets. Don't transfer paper, pens, white boards, etc. to assets upon receipt. The type of asset selection should be based on whether or not it's a consumable. And there should be a list of pre-selected consumables that could be chosen (like asset type is implemented now).
7) Allow for multiple signatures for approval (for instance, on creating the purchase order, and one for approval to actually pay it upon receipt of all assets or services).
8 ) Allow for PO additional fields, with the ability to label the fields and have selectable check boxes, not just listed options. (We want yes/no options) If yes, additional field MUST be filled out. For any fields added, we want to be able to optionally display these fields, search on them, sort according to them, etc. much like you can for requests. We'll want to order these fields to reflect steps in the process to ensure that all parts are completed before saying the PO is actually closed (ie, to show that all asset types have been assigned barcode #'s, have maintenance contract info entered, payment sent, etc.)
9) Purchase order log to indicate the date/time stamps for the progress of the purchase order, including when mail is sent off to the vendor, through payment, etc.
10) Automatic generation of purchase order # upon approval by signature authority instead of doing it up front. What if two purchase orders are being entered at the same time, and both show the prior PO #, and they each select the next number. Do you have to re-enter the entire PO under the current PO process? (This number is currently being entered manually at the beginning of the PO process - preapproval) What happens if there's a clash?
11) It would be good to have approvers be able to say "yes" without having to use up a license. We would want to be able to select that capability to select Requesters, and also put in a max dollar value they can approve.
I'll come up with more, I'm sure...
Justin
I'll try to put all the items here, and hope I can do so without adding pictures or losing the meaning as I describe them.
1) (Repeat) Selectable approval person for purchase orders, based on $$ approval levels. This name should also get automatically selected for email when seeking approval, and be able to allow additional names for mailing out if desired.
2) Do NOT classify all P.O's as being assets. We need to be able to select if it's an intangible (ie, contract or service) Be able to tie these PO's to the contracts, assets or not at all (one time situations)
3) When a PO is closed, the shipped assets can be included into maintenance contract, but you cannot see the entire field (we couldn't see the PO# it was tied to).
4) When looking at assets, it would be WONDERFUL if we could search for some text (description, workstation name, product type, etc) or filter by asset name, PO#, user, dept., site, etc.
5) When creating a purchase order, have a list of selectable shipping addresses or selectable/default billing addresses to send it to (site-wise), instead of having to type it over and over. Obviously, we'd have to enter or select the name for the delivery person, but we have regular sites/delivery locations. Why re-type them?
6) For PO's, we need to be able to distinguish between consumables and real assets. Don't transfer paper, pens, white boards, etc. to assets upon receipt. The type of asset selection should be based on whether or not it's a consumable. And there should be a list of pre-selected consumables that could be chosen (like asset type is implemented now).
7) Allow for multiple signatures for approval (for instance, on creating the purchase order, and one for approval to actually pay it upon receipt of all assets or services).
8 ) Allow for PO additional fields, with the ability to label the fields and have selectable check boxes, not just listed options. (We want yes/no options) If yes, additional field MUST be filled out. For any fields added, we want to be able to optionally display these fields, search on them, sort according to them, etc. much like you can for requests. We'll want to order these fields to reflect steps in the process to ensure that all parts are completed before saying the PO is actually closed (ie, to show that all asset types have been assigned barcode #'s, have maintenance contract info entered, payment sent, etc.)
9) Purchase order log to indicate the date/time stamps for the progress of the purchase order, including when mail is sent off to the vendor, through payment, etc.
10) Automatic generation of purchase order # upon approval by signature authority instead of doing it up front. What if two purchase orders are being entered at the same time, and both show the prior PO #, and they each select the next number. Do you have to re-enter the entire PO under the current PO process? (This number is currently being entered manually at the beginning of the PO process - preapproval) What happens if there's a clash?
11) It would be good to have approvers be able to say "yes" without having to use up a license. We would want to be able to select that capability to select Requesters, and also put in a max dollar value they can approve.
I'll come up with more, I'm sure...
Justin
