This is exactly right, Travis. Having that additional data can be helpful and maybe you'll change WM systems or AP systems or something that has a space for that data at a future date.
And again, the few extra KCs are nothing - usually pennies.... We've never even hit our KC limit, let alone come within about 5000 KC of it. And I think our "overage" is like 3 cents per KC.... When I translate the data into our user files, I just do not translate the additional information that the vendor sends; I do not populate our system with the extra stuff... And also, the Mandatory and Optional segment/element values come into play here.... Our spec includes a LOT of information.... and maybe half is "mandatory".... but it is appreciated sometimes to have that "optional" information around if needed. We may use it. Also, the more vendor specific maps you have around - i.e. using My Coleman example way up there ^^^ - if Coleman had to have specific ASN maps for each vendor, there would probably be quite a few that can work off of the same "generic" map but then there would be quite a few that would be very vendor specific and could cause some confusion down the line.... "hmmm... which ASN format do I use and who is it for...?" I'm a big believer in the old K I S S mantra (keep it simple, stupid) and only have one spec and one translation format for each of My documents.... If I make a change to one of My specs (say, for example, our outbound 850 PO), then it will be a change that will go to ALL vendors.... Case in point - when we first developed out 850 PO spec, on the PO1 segment, we only included our SKU and the UPC for item identification, plus quantity order, UOM, cost, case/pack, etc..... But for the actual item info - it was just our SKU and the UPC. Some vendors fill their orders off of UPC and some dont... Some work from their own Vendor Style number.... When I changed our 850 PO for that element - I added a generic description element, the vendor style element, a size element (if applicable).... This was to assist some of our vendors that filled orders based upon a vendor style and used, for example, the size (clothing, shoes, etc.) as a secondary check. But I didn't create an entirely new map/spec for apparel or shoe vendors.... Everybody still gets the same map, but with the new data.... it's on them to either use or not use that additional information. There needs to be SOME flexibility between trading partners (hence the term PARTNER) when it comes to the spec and how you implement it and how partners comply with the spec and how you enforce said compliance. As I mentioned in an early post - as long as you meet the basic requirements, any additional data is not an issue. Craig Dunham EDI Coordinator Big 5 Sporting Goods --- In [email protected], Travis Truax <[EMAIL PROTECTED]> wrote: > > > 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- > ... 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/
