Ahh grasshopper, all is not so complex as it might appear! If I remember correctly, X12C many years ago issued a formal interpretation to the effect that the versions of the interchange envelope and functional group envelopes were independent. In other words, you could pretty much use whatever ISA/IEA version you wanted, regardless of the version specified in the GS segments. That, however, was before repeating data elements so it isn't necessarily true for all cases at present. And, there are obviously some subtleties when you consider the code lists for some of the ID elements in the ISA, but the basic idea still holds.
Cheers, Mike At 01:29 PM 5/4/2005 -0700, Brian Lehrhoff wrote: >your example makes sense. here's what i thought you >were trying to do: > >Bill's Guitars >ISA GARYSID >GS BILLSID >Doc Type 850 >Version 4010 >GS RONSID >Doc Type 850 >Version 3060 > >and, being the true p*** in the a** that i am, i'll >wonder out loud which envelope version would be >correct? > >--- Gary Bligh <[EMAIL PROTECTED]> wrote: > > > > > Basically, its like this: > > > > > > Bill's Guitars > > ISA/GS GARYSID > > ISA/GS BILLSID > > Doc Type 850 > > Version 4010 > > > > Ron's Pcks > > ISA/GS GARYSID > > ISA/GS RONSID > > Doc Type 850 > > Version 3060 > > > > > > ---- Brian Lehrhoff <[EMAIL PROTECTED]> wrote: > > > > > > Have you ever seen two GS - with the same > > functional > > > id and different versions - in the same ISA? > > That's > > > what he's asking for. > > > > > > --- Michael Mattias <[EMAIL PROTECTED]> > > wrote: > > > > > --- Gary Bligh <> wrote: > > > > > > Can Data Stage TX support multiple versions > > per > > > > > > sender ID?> > In other words, under one ID > > (say > > > > GARY-EDI) can I > > > > > > send an 4010 850 to Bill's Guitars and 3060 > > 850 > > > > to > > > > > > Ron's Picks? > > > > > > > > "Brian Lehrhoff" <> wrote > > > > > sure you can ... as long as you make a > > creative > > > > tree > > > > > that contains everything you need. > > > > > > > > > it feels kinda dirty to suggest this ... and > > you > > > > can't > > > > > mix and match if the isa changes (i.e. 4010 > > and > > > > 4030) > > > > > > > > Why does this feel "dirty?" It's real life. > > > > Different partners require different document > > > > versions. And even at that, you don't > > > > really need a terribly creative tree... it's a > > > > pretty straightforward PARTITION'ed output.. > > > > > > > > ..But you don't even need to do that... just > > define > > > > your your output "text", RUN the partner's map > > and > > > > echo the output back..... > > > > > > > > e.g. > > > > > > > > Input > > > > PurchaseOrder(s) <<< some kind of input > > from > > > > user's system, which presumably can be > > identified as > > > > a series of PurchaseOrder > > > > objects > > > > Output > > > > Partner(s) << defined as unlimited text > > > > > > > > Map Rule for output: > > > > Partner(s) = f_eachPO (PurchaseOrder) << > > call > > > > functional map, will run once for each > > PurchaseOrder > > > > in input stream > > > > > > > > ' functional map f_eachPO, input = one (1) > > > > PurchaseOrder object, output = one (1) partner > > > > object > > > > Partner = RUN (LOOKUP (map_for_this_partner), > > > > ECHOIN(1, TEXT(PurchaseOrder)) + " other params > > if > > > > needed " + "-OE1") <echo it > > > > back here > > > > > > > > No muss, no fuss, no bother. No complex trees. > > Easy > > > > maintenance, allowing you to change one > > partner's > > > > map without touching some > > > > "master file of all maps." Yadda, yadda, yadda. > > > > > > > > Here, we assume the partner map is creating a > > single > > > > interchange for each PO. Me, I'd put an extra > > layer > > > > in there to group all POs > > > > for a partner into a single interchange, but > > what's > > > > here seems reasonable enough at least to get Mr > > > > Bligh started. > > > > > > > > Professional assistance available by contacting > > my > > > > office. > > > > > > > > Michael Mattias > > > > Tal Systems, Inc. > > > > Racine WI > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > . > > > > Please use the following Message Identifiers as > > your > > > > subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, > > > > <MISC>, <EVENT>, <OFF-TOPIC> > > > > Access the list online at: > > > > http://groups.yahoo.com/group/EDI-L > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > Brian Lehrhoff > > > EDI Consultant > > > 201-913-4506 > > > > > > > > > > > > __________________________________ > > > Yahoo! Mail Mobile > > > Take Yahoo! Mail with you! Check email on your > > mobile phone. > > > http://mobile.yahoo.com/learn/mail > > > > > > > > > . > > > Please use the following Message Identifiers as > > your subject prefix: <SALES>, <JOBS>, <LIST>, > > <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > > Access the list online at: > > http://groups.yahoo.com/group/EDI-L > > > > > > Yahoo! Groups Links > > > > > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > >Brian Lehrhoff >EDI Consultant >201-913-4506 > > > >Discover Yahoo! >Stay in touch with email, IM, photo sharing and more. Check it out! >http://discover.yahoo.com/stayintouch.html > > >.. >Please use the following Message Identifiers as your subject prefix: ><SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >Access the list online at: http://groups.yahoo.com/group/EDI-L > >Yahoo! Groups Links > > > > --------------------------------------------------------------- Michael C. Rawlins, Rawlins EC Consulting www.rawlinsecconsulting.com Using XML with Legacy Business Applications (Addison-Wesley, 2003) www.awprofessional.com/titles/0321154940 . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> 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/
