Leah, you know very well that the top-down method cannot enter the trailer number automatically. For that, we would need to steal a feature from the bottoms-up method. (Phew, all this talk about tops down and bottoms up on a Friday is getting me in a state. I think I’ll get some saltpeter for my fries.)
From: [email protected] [mailto:[email protected]] On Behalf Of Leah Halpin Sent: February-08-13 2:32 PM To: Paul McTeigue; [email protected] Subject: Re: [EDI-L] ASN Generation Can it enter the trailer number, too, please? Leah ________________________________ From: Paul McTeigue [email protected] <mailto:paul_mcteigue%40msn.com> > To: [email protected] <mailto:EDI-L%40yahoogroups.com> Sent: Friday, February 8, 2013 2:23 PM Subject: RE: [EDI-L] ASN Generation I hear ya Trav - too much scanning and codes and butcher tickets and RFID tags. Well, let's get rid of this messy, error-prone, bottom-up process altogether. We are going top-down!! I'll give you one-button on the Web page that says, "Prepare all of my shipments for today please." The system will then sort all of the PO's by customer, calculate how many cases and pallets are required, do a final check on inventory availability, send instructions to the pickers (robots) on what to pick and what pallet to put it on, spit out the case labels and bill-of-ladings and commercial invoices, prepare the 856 and inventory updates and wait for your final command to close the shipment. No muss, no fuss. All you need is to tell me how big your cases are and the dimensions of your items - but you probably already got that. Paul www.icefan.ca From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Travis Truax Sent: February-08-13 1:51 PM To: Paul McTeigue Cc: [email protected] <mailto:EDI-L%40yahoogroups.com> Subject: Re: [EDI-L] ASN Generation Yes, we do have scannable cartons, and I totally get your concept, as it's similar to how the typical bolt-on "scan & pack" ASN application would function. The rub there is that our ERP *does* actually have a mobile shipping component- it just sucks, and doesn't do everything needed to actually facilitate ASNs, so the dock workers are already having to scan this stuff once with handheld scanners. Unless I found a way to dump that process, I would be making their lives more difficult, and the clerks are the ones that would be better to train, as the dock personnel can sometimes be temporary staff, etc. Some of those other complexity notes you brought up are handled by the existing ERP. I really don't want to try to "roll my own" complete shipping system, but just velcro something to the side of the existing stuff until we ditch this ERP. These things are completely manual right now: - Automatically prints Bill-of-Lading and Commercial Invoices. - Automatically sends ASN 856 documents. So, worst case scenario this part is no better, but I think I could probably take care of both of them with some stored procedures and db triggers, once all the processing is taking place in one place. Travis- ----- Original Message ----- From: "Paul McTeigue" [email protected] <mailto:paul_mcteigue%40msn.com> > To: [email protected] <mailto:EDI-L%40yahoogroups.com> Sent: Friday, February 8, 2013 11:17:03 AM Subject: RE: [EDI-L] ASN Generation << Since I think the only piece of data that's missing is the relationship between cases and pallets>> You probably have a scannable code on your cases. So, here's what you do: 1. Affix a pallet sticker that has a scannable code to the pallet. (Just like a butcher shop ticket but scannable.) 2. Your little Web page then has an input for Pallet code and an input for Case code. You can now build your complete palletized ASN with zero manual effort. Paul From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Travis Truax Sent: February-08-13 12:01 PM To: EDI-L EDI-L Subject: [EDI-L] ASN Generation This is just a request of a sanity check on my plan to handle outbound ship notices. I realize this process is very dependent on our specific business processes, and nobody can tell me if this will be successful, but I thought there may be a chance someone might share some ideas or similar projects they have been through. I also thought there was a chance someone would say OMG, why don't you just do _____ because you've overcomplicated this 3 times over. BACKGROUND: We have an ERP system that doesn't retain a relationship between specific cases and pallets in the database. We still use an antiquated ASN application that's a parallel process with the rest of our shipping procedures in the ERP. Besides being a monumentally crappy setup, it's fragile, arcane, and very labor intensive. I'm even leaving out a bunch of steps for brevity, and for fear my post will be considered a friday joke. MY VERY SUMMARIZED PLAN: Since I think the only piece of data that's missing is the relationship between cases and pallets, and our shipping crew actually scribbles a pallet ID number on each line of the pick sheet as they are palletizing the shipment, I was considering creating an internal webpage that a shipping clerk could scan the shipment number on the pick sheet after it has been "turned in" as ready to be loaded, and it could default to placing all cartons on the first pallet ID (for small orders), and the clerk could update which pallet each line's cartons were packed on for larger orders, mirroring what the pickers have jotted down on the pick sheet. This part is very manual, but it would remove an entire other system that they currently use and simplify our EDI system as a whole significantly. I'm sure I've left plenty out, so if anyone has any questions, I'll fill in the blanks. Make any sense? Sound ridiculous? Thanks for reading, Travis- [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: , , , , , , Job postings are welcome, but for job postings or requests for work: IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
