We are wanting our purchasing people to be able to enter directives for our stores team to act on when receiving the parts, ideally for us at the line level, possibly at the release level. Example receiving directive for stores: “Give to Clint ASAP”
I started down this path, adding a UD column to erp.poDetail. However that was a little naive, as Receipt Entry deals with erp.rcvDtl and I can’t quite see how to pass the receiving directives through to stores. We are using Mass Receipt, thinking it will involve adding another UD column to dbo.rcvDtl and somewhere copying the receiving directive across, either in a bpm or in app studio itself.
Rather than have stores running around the building delivering stuff, what i have done before is to notify the person needs the items when they arrive so they can go and collect, to achieve this:
Create a new field on the PO Line that allows Procurement to select from Active Employees (Email addresses); then create a Method Directive that sends an email when the items are booked in using either Mass Receipt or Line by Line Receipt
Thanks Sue, good suggestion, however our notes are a bit more varied typically, and a number of the workshop staff don’t have (or don’t use) work email. So I think I will just try to make the notes for receiving available on the receipt screen.
I’m hoping these threads will help me add the column, unfortunately been hauled off onto other jobs in the meantime.
First, I would use releases since a PO line could be sent to different stores.,
Secondly, I consider “Notes” potentially to be an A1 problem. What’s an A1 problem?
If I am an Excel user and I’m entering data, would I put all of the information into the $A$1 cell? This is what often happens when we create a “catch all” field in Kinetic. If we do this in Excel, then we can’t do a lot of automation (formulas, etc.) without messy parsing. The same is true for information stuffed into a note. I’d be more in favor of looking at notes and categorieze the type of usage and use multiple fields and/or data tags to be able to use automation. A DeliveryTo_c field is far more useful than a note to “Deliver To Clint” mixed with other information. YMMV.
I hear you on the release, and we debated that internally and settled on PO line, but I’m also leaning back toward release.
More recent examples, eg when rolls of hand towels (non-stock) are delivered: “Keep 10 here, send 30 rolls to Bush Rd, 5 to Airborne” “Give the frame back when he delivers”
…Its very generic for us. But most will be “DeliverTo” in some form, even the roll example
)