I understand that the IG can cover all contingencies, however, the DATA should contain only relevant information. Data, as we all know, comes from ERP systems (or other, similar applications). IMO, a properly set up and maintained ERP system should not generate extraneous or irrelevant or worse, inaccurate or misleading information.
Leah ________________________________ From: Ken Etter <[email protected]> To: Jason McMahon <[email protected]>; "[email protected]" <[email protected]> Sent: Thu, May 5, 2011 2:32:40 PM Subject: Re: [EDI-L] Re: Effect of adding a new segment And it simplifies mapping on the sender side... Can you imagine having to do a separate 850 map for each TP of the 800lb gorilla?? Ken [email protected] From: Jason McMahon <[email protected]> To: [email protected] Sent: Thursday, May 5, 2011 1:15 PM Subject: RE: [EDI-L] Re: Effect of adding a new segment Simple. TPs often create the same document format to cover all known requirements and send them to everyone on their list. The other reason is to satisfy ERP requirements. I work with a vendor who has no pick ups. Everything is shipped. But I receive any number of 850s with pick up dates. All the TPs know the vendor has no pick ups but that doesn't stop them from sending the segment. Sincerely, Jason McMahon 8079 Village Drive Cincinnati, OH 45242-4315 <mailto:[email protected]> [email protected] http://gutausse.weebly.com/articles.html <http://gutausse.blogspot.com> http://gutausse.blogspot.com <http://www.linkedin.com/pub/jason-mcmahon/11/743/51b> http://www.linkedin.com/pub/jason-mcmahon/11/743/51b You may be only one person in the world, but you may also be the world to one person. _____ From: [email protected] [mailto:[email protected]] On Behalf Of Leah Halpin Sent: Thursday, May 05, 2011 1:03 PM To: Ben Kenoyer; [email protected] Subject: Re: [EDI-L] Re: Effect of adding a new segment Ben brings up an excellent point. Why send data that doesn't need to be used? Leah ________________________________ From: Ben Kenoyer <[email protected] <mailto:bkenoyer%40scvl.com> > To: [email protected] <mailto:EDI-L%40yahoogroups.com> 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] <mailto:EDI-L%40yahoogroups.com> , 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] [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/
