Supplier makes part 12345 for us. Black metal bracket, should have 4 holes in it.
They only put 3 holes in it
We don’t have time to send it back; they were late on the delivery already
So we drill the 4th hole on 50 pieces
We do this on a job and track the hours spent (using a higher rate than normal; our “vendor rework rate” meant to envelop the admin costs and disruption of service, etc.)
Question
Now we want to send a bill to the supplier for the rework. Is there a nifty way to tie the job to the AP debit memo (that we are requesting)?
Thoughts
This is screaming “DMR process” to me.
But I tried to work through this in dev and I can’t quite get it.
So, to my mind,
Bad parts should be on a DMR already
a. Not the DMR for the debit memo - I’m not there yet
The rework job should be for producing part 12345 (qty 50)
Job should also have material of part 12345 (1 per)
a. The material should be issued from the DMR of step 1
When complete, the good reworked parts get received to inventory
Then… magic. All the labor $$ somehow goes to another DMR which somehow goes to a debit memo, something something.
I could list my failures, but I think that’s plenty for now.
Point is, I can envision procedures to do various permutations of 3/5 of the steps, but never all of them.
What do you all do in this situation? Just do the job separate from the AP stuff?
Your process is pretty much what we do except once the parts are reworked, Quality would use Job Tracker to total up the labor hours, multiply by the rework rate, and then enter the debit memo request on the original DMR for AP to then process. We wouldn’t create a new DMR just for the debit memo.
Right. Quality would enter a New Debit Memo in DMR Processing which then shows as open in a few different reports for AP and lets AP pick the DMR in Invoice Entry > Actions > Get DMR Debit Memos.
It’s a little bit tricky if you use ECM and the supplier sends in the credit memo. We’re still working through the best way for AP to see those and know to match it to a DMR before processing.
So in the end the DMR is the central hub to track stuff down (by BAQ - ain’t no way a person could follow the trail out of the box). I was mentally centering it on the job.
Believe it or not, I was actually not sarcastic for once - Visio seems actually useful at long last.
I mean, it’s not “Wow this is so modern”; it’s “Hey, you finally caught up to the early 2000’s!”
Last time I used Visio - a year ago - I remember thinking it was easier to do a flowchart by just making boxes and arrows in Word or PowerPoint. Because I did that:
But now (in M365 anyway) the canvas is infinite and you can kind of rescale it. By default the font is 8 pt (WHY?) but that is easy enough to overcome. And the arrows connect cleanly. It’s lightyears ahead of whatever I tried to use last year.
If I was really a cool-kid, I’d be typing the markdown, but mostly I’m chatting w Copilot about something and I’m like ‘flowcart that proces for me’ and the output is mermaid.js flavored markdown. But either way, I like no drag-n-drop-n-drag-drop-again and connect n click n type n resize, etc, etc. Plus when you commit a md file it’s text so your flowchart diffs are SCM friendly. and AI 'understands them so next chat it knows whats we’re talking about, etc etc. Plus it’s free but yeah visio has gotten better, I agree.
EDIT: does this site render mermaid md?
flowchart TD
A[Christmas] -->|Get money| B(Go shopping)
B → C{Let me think}
C -->|One| D[Laptop]
C -->|Two| E[iPhone]
C -->|Three| F[fa:fa-car Car]
@JasonMcD s the widget guy? Got it. I like that but can we get him to get them to drop the word widget from the lexicon entirely? I mean they’re components and actions. Thats what they are not toys.
