This hardly seems like a good EDI fit. Perhaps the customer and the vendor's accounting departments ought to discuss this first and decide on what they need and how to best share it.
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 _____ From: [email protected] [mailto:[email protected]] On Behalf Of Leah Halpin Sent: Wednesday, March 30, 2011 9:09 PM To: Steven Santillo; EDI-L Subject: Re: [EDI-L] 846 Well, I have a thought, why not ask whoever told you that you would need that info? Leah ________________________________ From: Steven Santillo <[email protected] <mailto:n19667%40yahoo.com> > To: EDI-L <[email protected] <mailto:EDI-L%40yahoogroups.com> > Sent: Wed, March 30, 2011 8:49:00 PM Subject: RE: [EDI-L] 846 The relationship is more than just customer/vendor. We are the vendor but we do have the "power" to demand certain things from our customers. Whats going to happen is I'll ask our customer to send aged inventory and run rate. They'll say "what the hell is that and where do you want it." I'll say "I was hoping you would tell me." --- On Wed, 3/30/11, Jason McMahon <[email protected] <mailto:gutausse%40cinci.rr.com> > wrote: From: Jason McMahon <[email protected] <mailto:gutausse%40cinci.rr.com> > Subject: RE: [EDI-L] 846 To: "'Ken Etter'" <[email protected] <mailto:edispec%40yahoo.com> >, "'Steven Santillo'" <[email protected] <mailto:n19667%40yahoo.com> >, "'EDI-L'" <[email protected] <mailto:EDI-L%40yahoogroups.com> >, "'Michael Mattias/LS'" <[email protected] <mailto:mcmlserve%40talsystems.com> > Date: Wednesday, March 30, 2011, 6:27 PM I have also seen this used to create blanket orders in order to reserve stock. But Key is right, you really need the customer specs in order to map this information. Sincerely, Jason McMahon 8079 Village Drive Cincinnati, OH 45242-4315 <mailto:[email protected] <mailto:gutausse%40cinci.rr.com> > [email protected] <mailto:gutausse%40cinci.rr.com> 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 _____ From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Ken Etter Sent: Wednesday, March 30, 2011 5:11 PM To: Steven Santillo; EDI-L; Michael Mattias/LS Subject: Re: [EDI-L] 846 If you can get the particular customer specs, then yes you can probably start early. But if not, then it really doesn't matter what feedback you get from the group, because we don't know what your customer specs are. And if there are terms you need defined, again the customer really needs to define how you should respond for particular or specific data elements. Some terms are interpretted differently by customers, just as customers can use different EDI documents for the same information (i.e. I've received address updates in both 816's and 864's) Also as others have indicated, I really have never heard of either "aged inventory" or "run rate" contained in an 846. 846 usually gives a snapshot of customer items availability for a particular time period. In some cases it is sent daily, in others it is sent hourly - others on this list may experienced other frequencies. IN my own experience customers will use the 846 to guage against their own demands/needs. Regardless, the frequency of how often you send an 846 is also determined by the customer as well. Ken [email protected] <mailto:edispec%40yahoo.com> <mailto:edispec%40yahoo.com> ________________________________ From: Steven Santillo <[email protected] <mailto:n19667%40yahoo.com> <mailto:n19667%40yahoo.com> > To: EDI-L <[email protected] <mailto:EDI-L%40yahoogroups.com> <mailto:EDI-L%40yahoogroups.com> >; Michael Mattias/LS <[email protected] <mailto:mcmlserve%40talsystems.com> <mailto:mcmlserve%40talsystems.com> > Sent: Wed, March 30, 2011 4:52:50 PM Subject: Re: [EDI-L] 846 These terms are new to me also. I'm just trying to get a jump on a project that is still a couple of months away. I know each customer will have to send this information and the details will be worked out then. Thanks for your response. --- On Wed, 3/30/11, Michael Mattias/LS <[email protected] <mailto:mcmlserve%40talsystems.com> <mailto:mcmlserve%40talsystems.com> > wrote: From: Michael Mattias/LS <[email protected] <mailto:mcmlserve%40talsystems.com> <mailto:mcmlserve%40talsystems.com> > Subject: Re: [EDI-L] 846 To: "EDI-L" <[email protected] <mailto:EDI-L%40yahoogroups.com> <mailto:EDI-L%40yahoogroups.com> > Date: Wednesday, March 30, 2011, 4:06 PM >>Does anyone send or receive this information on a 846? If so what >> segment/element? >>1. Run Rate ( 30 days) by sku and qty >> 2. 60+ (aged inventory) > For argument sake. It's a totally new business requirement. Is anyone > sending or receiving this information. Retail Electronics industry. I have several clients who send an 846 to multiple partners; in all cases those partners are customers. In all cases, my clients and their customers agree on what information is to be sent in what segments and what elements. As long as I have been doing this (25+ years) I have never seen application data in an 846 called "Run Rate" or "Aged Inventory." I never heard either of these terms prior to that either, which was 10+ years in the power transmission and industrial rubber products distribution industry. Age does not matter with these products. (BUT ONLY IF STORED PROPERLY!) (The meaning of "Run Rate" is still a mystery to me). Michael C. Mattias Tal Systems Inc. Racine WI [email protected] <mailto:mmattias%40talsystems.com> <mailto:mmattias%40talsystems.com> [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] [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/
