I haven't asked. I don't remember our community here designating an official acronym for it, but I know "Talk to your partner" is often vocalized on the list. Sort of the RTFM of this list...
The thing is (and I actually don't mean any insult with this comment) that many of the EDI contacts we have with our partners are "less than capable" of answering some of the *why* questions we sometimes have. Not to say they're Homer Simpson setting at their console at the power plant, just that many are not EDI, application, or integration experts- they just work off of a que sheet, punch out at the end of the day, and don't ponder the intricacies of why, as long as it matches the que sheet. Travis- ----- Original Message ----- From: "Leah Halpin" <[email protected]> To: "Earl Wertheimer" <[email protected]>, [email protected], "Travis Truax" <[email protected]> Sent: Friday, March 1, 2013 10:07:51 AM Subject: Re: [EDI-L] Segregation in Interchanges Earl, You're almost certainly correct on the outbound side. It's the business process and ERP system timing that controls what goes in an envelope, simply by when the data is created and passed to the translator for the supplier. Inbound, I'll stand by my thoughts, the translator should come first, then the routing of the data. Otherwise, if the gateway comes first, it's passing EDI to many different translators and that doesn't often happen. Mostly, that occurs when businesses merge and they keep separate systems. When they do that, they also usually keep different ID's. Maintaining multiple EDI systems for long periods of time is counter to the purpose of merging. Travis, have you ever asked them why? Leah From: Earl Wertheimer <[email protected]> To: [email protected]; Travis Truax <[email protected]> Sent: Friday, March 1, 2013 10:35 AM Subject: Re: [EDI-L] Segregation in Interchanges Travis > We have a partner who pitches a fit if they receive an ISA that > contains more than one transaction set type. Send 810s by themselves, > send 997s by themselves, etc.. > > Just curious if this is common or strange. I haven't dealt with anyone > else similar in 15 years, but we don't have a huge trading community, > either. I've never seen different document types with the same Interchange. I think it reflects the different procedures that are required to generate the documents. The 850s would be created by an Inventory Planning program that calculates replenishment levels. The 820s would be created by something in Accounts Payable. Sears Canada sends 850 information and 864 information for the same set of POs. They are sent in 2 interchanges, and have to be matched up in order to print their custom labels. I just deal with what they want. Earl Wertheimer [email protected] http://www.spe-edi.com [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/
