gsw would do it, but i prefer mercator :) and i could even knock this out in a very simple iway map.
actually, if i was going to do it in a mercator map, i'd probably read it into a structure and then rewrite it. as someone pointed out earlier today, the real issue isn't pointing down but pointing up. if i extract and remap, then i have the same as i had when i started ... and i just need to know where the truck doors closed. and then i had a creative user that decided to use HL04 in the 856. why??????? Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ________________________________ From: Travis Truax <[email protected]> To: Brian Lehrhoff <[email protected]> Cc: [email protected] Sent: Friday, February 15, 2013 10:15 AM Subject: Re: [EDI-L] Re: 856 HL level removal I suppose that's always an option. How much does it matter? When I was faced with the problem, the script sounded like a much quicker endeavor compared with a GSW map. Maybe you're a better mapper than I, or like you said, you're a mapper at heart- so you see things that way. In our case, the data was constructed by another system which had pre-built maps that only the EDI SW vendor had control over. The data was structured properly, but contained things we didn't want to send. Running that 856 through Gentran after the other system created it, and then removing segments based on another file that contains "hints" on what should be removed, and then renumbering all the HLs, didn't sound like something I could handle under pressure in a couple of hours. Hello text find & replace. Travis- ----- Original Message ----- From: "Brian Lehrhoff" <[email protected]> To: "Martin Morrison" <[email protected]>, "Susan Stecklair" <[email protected]>, [email protected] Sent: Friday, February 15, 2013 8:42:04 AM Subject: Re: [EDI-L] Re: 856 HL level removal you know ... i'm just thinking out loud as a mapper (at least at heart) ... why can't you write a map to do this? it's got to be safer than doing it manually and can't be that difficult regardless of the mapper you're using. Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ________________________________ From: "Morrison, Martin" <[email protected]> To: Susan Stecklair <[email protected]>; [email protected] Sent: Thursday, February 14, 2013 8:20 PM Subject: RE: [EDI-L] Re: 856 HL level removal Who, among us hasn't had to write an HL renumbering script at one point or another in their career. It's really fun on big, ugly 837 files from large medical groups that can't fix their systems for several months (or years). Thanks, ” ” ” Martin Morrison ” From: [email protected] [mailto:[email protected]] On Behalf Of Susan Stecklair Sent: Wednesday, February 13, 2013 3:50 PM To: [email protected] Subject: RE: [EDI-L] Re: 856 HL level removal 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:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of John Sent: Wednesday, February 13, 2013 10:32 AM To: [email protected] <mailto:EDI-L%40yahoogroups.com> 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] [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 [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 [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 [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/
