[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

Re: Gander Mountain 856 changes

From: Earl Wertheimer <earlw@...>
Date: Wed Mar 10, 2004  9:32 pm
Subject: Re: [EDI-L] Gander Mountain 856 changes
Sandy

> We were notified on March 1st that Gander Mountain is changing its
> specs for the 856 cross-dock effective March 19th. Instead of
> putting the store number at the pack level, they now want it at the
> order level. This means if I'm shipping to the warehouse for 10
> stores, I'll have to repeat the order level information 10 times.
> Only the store number will change in each loop.
>
> Has anyone else looked into this? I asked SPS Commerce/EDI Solutions
> (since Gander has outsourced EDI to them), and they told me to repeat
> the other order information once for each store or to send a separate
> ASN for each store. Am I missing something here? How have others
> dealt with this?

It's normal to have to 'explode' a multi-store 850 PO (SDQ) into multiple
internal orders, since the items for each store have to be grouped together.
Each internal order is for a different Store.

When building the 856 ASN, you need to order the info by Store first, so that
all products for the same store will be together (in 1 or many cartons).

How are you processing other Trading Partners whose incoming 850s have SDQ
segments?
Gander Mountain should be the same as those..





 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.