Susan, You are correct that this is the method that I would have implemented if I had been around when this was coded but I wasn't so that is water under the bridge.
I have since found out that there is a correct procedure that has been done in the past but the person who did that recently left our employ so the new guy is puzzling out how to do this properly. Yet another case of a lack of proper (any) documentation. In the meantime, I will continue to manually fix the rapidly decreasing number of bad 856s. John --- In [email protected], "Susan Stecklair" <stecklair@...> wrote: > > Hi - > > It appears to me that you need to generate the 856 extract at the manifest > level, rather that the pic level. You might want to look at a software > solution. Conceptually, you could import your current 856 data into their > software, use the software to generate your pallets or manifest. Then > generate the 856 to your customer from that. There is a company out of > Michigan called e-SupplyLink that you might wish to call & see if their > solution would work for your company. http://www.e-supplylink.com/ > > > > Regards, > > Susan Stecklair > > > > From: [email protected] [mailto:[email protected]] On Behalf Of John > Sent: Wednesday, February 13, 2013 10:32 AM > To: [email protected] > Subject: [EDI-L] Re: 856 HL level removal > > > > > > Alex, > > Thanks for the thoughts and you are right that a correct solution would be > to use Gentran Windows to fix the HL loops. However, that would not fix the > data in our MRP which is why it is not a valid long term solution. In order > to fix the MRP data we need to perform quite a few steps which, > unfortunately, our guy on the shipping dock does not have access to at 1:00 > am. So the long term fix is to change the process, that will then create > correct EDI. In the meantime, Honda gets a lot of bad 856s, they get mad at > us and go looking for a new supplier then I get to go look for a new job! > All in all, it seems best to manually fix a few 856s while we fix the > process the right way. > > One other note, I could create a Data Entry map in Gentran, then bring in > the EDI and remove the bad HL loops and then let it fix the HL numbering but > it seems easier to me to fix the EDI and save me the time it would take to > create and debug and test a Date Entry map. > > John > > --- In [email protected] <mailto:EDI-L%40yahoogroups.com> , Alexander > Luss wrote: > > > > John, > > > > Based on your description, the band-aid solution (renumbering all HLs in > > already produced X12 files) seems to me being a lot harder than permanent > > solution in map to produce the correct numbers to begin with. > > > > I don't know the method you use to number your HL segments. However, in my > > opinion, the most efficient, dynamic and easy to use concept of numbering > > HLs is via using the counter standard rules. Even if you remove some > parent > > levels, all what it takes is to re-assign from the removed one to the new > > parent level. > > > > Let me know if you need some help with this approach. > > > > *Thank you, > > Alex Luss > > ________ > > * > > > > > > [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/
