> If the extra data comes in and just sits there > then aren't you paying transmission costs for that unused data > (through your van)?
We don't have what anyone would call a high volume of documents, but I do think a certain level of "partnership" is a healthy thing. I mean, we could just strip out every bit of non-essential markup and end up with a custom format for each (no delimiters, no headers, etc.) And the communication fees would be even less. If there are a few extra characters, I just don't see the point in making someone remove them. I come from the supplier side - so I'm used to having to to do all kinds of rediculous stuff for some of our customers. But if the tables were turned, I don't think I would be so strict. It will be even more annoying to your suppliers if a year later, you rollout a new system that needs that data, and then you mandate they make another change, in effect- "doing what they wanted to do all along." Travis- -----Original Message----- From: Earl Wertheimer [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 12:55 PM To: w_cohen99; [email protected] Subject: Re: [EDI-L] Re: ASN - pack vs. item level differences? Walter > Is there a reason for not requesting a customized map for your ASN > from the seller? Yes. Generic maps already exist. It's much easier to copy an existing map and just remove the unused segments. These maps are already in production with many big TPs. Deviating from the existing maps is going to cause more problems and is only justified if you have a specific requirement or problem. > If the extra data comes in and just sits there > then aren't you paying transmission costs for that unused data > (through your van)? Not if you use ftp or AS2. The VAN kchar prices are pretty low. If you have a huge volume going through your VAN, then yes, remove whatever is extraneous (but still within the standard). Most IGs show mandatory and optional segments. You can always remove all the optional ones... > --- In [email protected], "Dunham Craig E." <[EMAIL PROTECTED]> wrote: > > > > Thanks, Todd.... I'm pretty sure that a lot of retailers use > similar > > maps and only stray from the "norm" for specific information that > they > > require.... Like Walter and the grocery company needing not only > the > > UPC for the items but also the UPC for the carton level (at least > that's > > what I think I remember reading from the posts)... He also needs > > specific information about the product on his ASNs that we don't > need. > > Each retailer/buyer will have needs and requirements that may OR > may NOT > > be the same as others - even within their own industries. > > > > Basically, however, it will be different for each retailer or > supplier > > or company.... EDI is to make it easier to communicate between > > suppliers & vendors, simplifying the transactions. But each case > will > > be unique and different... > > > > For example, I receive ASNs from Coleman and, while the provide > all of > > the information that our system requires, there are many additional > > segments and elements that Coleman uses for their ASNs that we do > not > > use. The "extra data" just sits out there - unused - and is never > > migrated from our EDI system into our purchasing and warehouse > > management systems. > > > > > > Craig E. Dunham > > EDI Coordinator > > EYE Analyst > > Big 5 Sporting Goods > > > > > > > > > > > > ________________________________ > > > > From: Todd LaBonte [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, September 19, 2007 9:37 AM > > To: Dunham Craig E.; [email protected] > > Subject: RE: [EDI-L] Re: ASN - pack vs. item level differences? > > > > > > > > Craig, > > > > > > > > It seems most of the major retailers agree with you. > > > > > > > > Todd LaBonte > > > > e-SupplyLink ... exceptional Supply Chain Solutions > > > > > > > > > > > > > > > > [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 > > > > > __________ NOD32 2540 (20070919) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > Earl Wertheimer [EMAIL PROTECTED] http://www.spe-edi.com ... 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 ... 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: mailto:[EMAIL PROTECTED] mailto:[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/
