Custom PO Approval Steps

Kinetic ERP
1

We would like to send PO approval for specific vendors to a different approver. I think I could hack this together with a method directive. I am curious if anyone else has already solved this problem with a more clever solution.

The goal is:
If PO is for customer X, Y, Z, then send PO to ToolGuy for review and approval. Otherwise, send the PO along it’s normal approval path (based on amount).
Thanks for your time!
Nate

2

Make a new buyer with that approver. Assign the buyer to all the parts you buy from those vendors.

1 Like
3

We might not have all the parts that we buy from the vendor in the system (if we have to buy new parts). I think this is why they wanted it based just on the vendor, so it would flag every part from the vendor regardless of if we have it marked in the system. :thinking:

4

Also this would require our buyer to switch “buyer” based on where they buy the tools. The buyer may not know that what they are buying is something that needs to be approved by the tool guy.

5

Use the Requisition functionality to control it before it gets to purchasing.

1 Like
6

Since we still use paper reqs, can you expound on this a bit? I have been pushing to get our reqs in the system for along time.

My understanding of the flow:
Milling guy gives the buyer a list of tools needed for an upcoming job.
Buyer creates POs for the tools.
(Insert step here for tool guy to review POs)
Buyer sends POs to supplier, purchasing the tools.

7

It is not the greatest tool in the system, but it does provide everything needed for a good audit trail.

The requisitions generally work this way.

  • An employee enters a requisition for parts/services. They can either be parts in the master or they can enter whatever they want.
  • Once they have completed entering the req, they need to know if it needs to be reviewed and approved.
  • If it does not need to be, they can submit to purchasing.
  • If it does, they need to know who it needs to go to and send it to them for approval.
  • Once all approvals are received, the last person submits to purchasing.
  • A PO Suggestion is created for the req for purchasing to buy and the buyer can see all of the approvals that it received. If the submitter did not get the correct ones, it can be rejected back to a req noting it needs approval.

Kind of clunky, but it does work.

1 Like
8

We created a new action called “Review”. We would use this when the tooling guy needs to review the req before purchasing. When we mark a req as needs tooling review (as the “Action”), where does the next person review and approve the req?

Also, we need to run generate PO suggestions at some point for this to work, right?

9

I forget, it might just show up in PO Suggestions once it is sent to purchasing. There is a screen in Requisition Entry where approvals appear for users.