And that little Web page gets to be a real smart little Web page:
- Cannot have more than x number of cases per pallet. - Cannot add cases whose contents are for different customers. - Cannot add cases whose contents are for different ship dates. - Automatically prints Bill-of-Lading and Commercial Invoices. - Automatically updates inventory upon shipment closing. - Automatically sends ASN 856 documents. Paul From: [email protected] [mailto:[email protected]] On Behalf Of Paul McTeigue Sent: February-08-13 12:17 PM To: [email protected] 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] [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/
