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

Re: <sales> 753 / 754 capabilities

From: "Earl Wertheimer" <earlw@...>
Date: Thu Oct 14, 2004  12:39 pm
Subject: Re: [EDI-L] <sales> 753 / 754 capabilities
Ilia

> With all due respect the only way to make the tms (753/754) work is to
integrate
> it with your own erp, tms and wms systems. No one can come in with a boxed edi
> solution without understanding your own ops.

Not completely. We sell a simple app that builds a database with the incoming
POs (850). The Routing Requests (753) can be built from the existing orders.
The incoming Routing Instructions (754) are used to update the original orders
and shipment (if it has been created). Then we print UCClabels & send out ASNs
(856) and Invoices (810).

The system is standalone and pretty inexpensive.

I actually think that JCPs TMS process is simpler than the routing nightmare in
the past, where the routing depended on weight, and most stores had alternate
shipto codes and addresses. Now there are no decisions required. You tell JCP
what is ready to go, and they tell you how and where to ship it.

I agree that the other issues can be overwhelming.. especially with the
reduction in shipping time demanded by JCP. JIT manufacturing and JIT shipping
can result in premature gray hair.

I sometimes think that JCP would make more money by getting out of the selling
business and concentrating on their new source of revenue - chargebacks &
penaltys <bg>



Earl Wertheimer
http://www.spe-edi.com




 
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.