BCF is the pain to test, and to be in production with.
We were able to overcome po xref problem by using our product ids to identify
the items on the 850 instead of cust skus, and keeping sln related data on our
edi order tables for later outbound usage.
Asn problems were resolved by imaginative po4 usage, and by outputting
'printable' email version of ASN for bcf dc use.
810 issues were taken care of by letting invalid 810s reject from their
application with 824s, and then having 810 changed manually.
Pls contact me offline if u need more input...
Ilia
This email was send from Blackberry wireless device.
-----Original Message-----
From: <
To: <
Sent: Mon Mar 13 13:47:42 2006
Subject: [BULK] [
EDI-L] Burlington...
Hi all,
I would like to know if any of you are processing edi with Burlington
Coat Stores. Appearantly they do not use the QRS
catalog, and are
using their own internal product numbers. Currently all of our other
trading partners send upc's(from the catalog) that we
convert to our
internal sku's- i.e one conversion table.
If you are, and are a vendor, what is your solution to "efficiently"
process edi from Burlington?
Don
.
Please use the following Message Identifiers as your subject prefix: <
SALES>,
<
JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
[Non-text portions of this message have been removed]
Cart
