We're much smaller than Walmart and my husband has a serious grass fed beef habit
On Thu, May 5, 2011 at 1:14 PM, Leah Halpin <[email protected]> wrote: > You'd need it to be a nickel? > Leah > > ------------------------------ > *From:* Samantha Scott <[email protected]> > *To:* Leah Halpin <[email protected]> > *Cc:* Ben Kenoyer <[email protected]>; [email protected] > *Sent:* Thu, May 5, 2011 1:10:43 PM > *Subject:* Re: [EDI-L] Re: Effect of adding a new segment > > If I had a nickel for every segment I received during a day that was not > used by either party I could retire on just the traffic received between 7 > and 9am on a Tuesday. > > On Thu, May 5, 2011 at 1:02 PM, Leah Halpin <[email protected]> wrote: > > > > > > > Ben brings up an excellent point. Why send data that doesn't need to be > > used? > > Leah > > > > ________________________________ > > From: Ben Kenoyer <[email protected]> > > To: [email protected] > > Sent: Thu, May 5, 2011 12:54:59 PM > > Subject: [EDI-L] Re: Effect of adding a new segment > > > > > > Jim: > > I would say close to 0% would not have to make any changes to their data > > structure and/or map. My system will more than likely ignore an > unexpected > > [new/additional] segment, even if it's within a repeating loop. So, if > the > > gorilla sends a new/unexpected segment, the file may process through my > > system > > successfully, but without mapping that new value to a destination field > in > > my > > internal database or ERP, it doesn't benefit either partner if the data > is > > not > > being "used". > > > > Sounds like the gorilla should work on its vocabulary and spell out its > > intended > > segment and definition to all affected TPs ;-) > > > > --- In [email protected], Samantha Scott <mossmuncher@...> wrote: > > > > > > 100% of the smart ones who defined it as the spec defines it > > > > > > On Thu, May 5, 2011 at 12:34 PM, jimdivoky <jim.divoky@...> wrote: > > > > > > > > > > > > > > > Scenario: > > > > 800 pound gorilla sends an outbound message using established EDI > > standards > > > > like X12 and EDIFACT. They add a second REF/RFF segment within a > > repeating > > > > REF/RFF segment loop which currently contains one mandatory segment > as > > > > specified in their IG. The recipient does not need to do anything > with > > the > > > > new segment. > > > > > > > > Question: > > > > What percentage of the TPs receiving the message with the additional > > > > REF/RFF segment would not have to make any changes to their data > > structure > > > > and/or map? > > > > > > > > Thanks, > > > > Jim Divoky > > > > > > > > > > > > > > > > > > > > > [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 <*> 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/
