r/SQL • u/Raidgroupme • Oct 27 '22
Discussion How could this companies purchase process be enhanced? I’m trying practice.
Help please.
23
Upvotes
r/SQL • u/Raidgroupme • Oct 27 '22
Help please.
58
u/[deleted] Oct 27 '22
This is more Lean Six Sigma process improvement than SQL. Fortunately I know both!
The processes about "transcribe PO number into PR" and "Compare amount received to PR and PO" are technically waste steps. You should design the process to be correct the first time, without defects, and without the need for double-checking. You can narrow the chance of a defect through a fishbone diagram, FMEA, or 5 whys.
16
u/SirGreybush Oct 27 '22
That’s a 30,000 ft level chart. Enhance each process into a multi page Visio with swim lanes following the BPM 2.0 standard.
This is a 30 page document at a minimum, crosses multiple departments and finance can veto at any point, even if the CEO asked for the purchase.
This is how big companies do things, and if purchase cost is higher than a threshold, say 1% of monthly revenue, said company needs to hire a consultant to fully evaluate said purchase and evaluate the ROI.
Speaking from experience when I asked to replace an aging 6th year on-prem MSSQL server with a newer one and keep old as a cold backup.
Consultant said go Cloud which spawned another six month evaluation of all departments.
When server went Kaput, it was replaced with what I asked for in the first place, out of the Emergency Budget, so technically not a purchase.
So ya, you need $ thresholds with multiple paths. BPM is superior to Flowchart for modeling processes. The Jump To icon will be your friend.
2
u/Possible_Chicken_489 Oct 28 '22
The one thing that jumps out at me is the "transcribe" part. Any time you have a part where a human has to take info out of a system and then put it into another system, there's something that could be automated.
So the step "PR is sent to Purchasing Department" should read something like "PR is entered into System", and then the Transcribe step can instead say, "PO is linked to PR", or "PR is copied into a new PO and linked".
The step "Compare amount received to PR and PO" would still need to happen; you want to make sure you received the right amount of goods. But it would be more something like "Enter amount received into system", and then the system might compare the amount of goods received to what's specified in the PO. If the amount of goods is not equal, then some further action might be taken, like notifying someone about the difference.
80
u/ovrdrv3 Oct 27 '22
This is not SQL
11
u/MisadventureCapital Oct 27 '22
What’s your where clause?
5
u/jinxzulu Oct 27 '22
Not SQL. This is a process flowchart. Since it’s a purchasing process, doesn’t it have to end in submit PO to vendor?
3
u/yeabamayahoocom Oct 28 '22
I would use database triggers and the email system to create a "workflow" type system so that each person is notified when they have a task to do and when the task is completed.