Travis, In some ways it is even worse than what you describe. In Honda 856s they sequence the load for a particular truck. We then print a pick list based on what Honda wants on the truck. When Honda wants more on a truck than will fit on a truck, then we have a problem. Our system generates the 856 off of the incorrect data in the pick list as requested by Honda, not what makes it onto the truck. Now my 856 has a part on it that is not on the truck and therefore has missing information required on the LIN segment. Ah, you say, just look in the map for the missing data and then don't generate the LIN segment but that won't work since, when Honda orders parts from an 850 then it won't have those pieces of information but the LIN segment will now be right.
Do you see now why, in this case, i need to fix the backend system to send me the correct data so I can generate the 856? And now, just to throw cold water on your foolishly raised hopes, there is no link back to whether the part was ordered from an 850 or an 862, at least as the system currently stands. The problem all comes back to Honda ordering us to put more parts on a truck than will fit on the truck. Now where did I put my rose colored glasses? John --- In [email protected], Travis Truax wrote: > > Yeah, I suppose my comment *does* just sound like I mean "garbage" to mean > "not easy to map", but I really just meant it as "completely screwed up", > like maybe not the same way every time, etc. Like truly an ugly mess. If he > actually has some pattern to follow, then by all means make a special map > that compensates for the backend quirks- I was under the impression he may > actually be having to correct a bunch of *random* stuff by eye and then > needed a way to rewrite the HLs after he had worked it over by hand. > > Travis- > > ----- Original Message ----- > > From: "Michael Mattias/LS" > To: "EDI-L" > Sent: Wednesday, February 13, 2013 2:13:43 PM > Subject: Re: [EDI-L] Re: 856 HL level removal > > > You seem to be suggesting that it is somehow possible for him to write a > > "garbage-in:sunshine-out" map. > > That's why consultants get the big $$$ > > MCM > > > > ------------------------------------ > > ... > 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] > ------------------------------------ ... 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/
