Menu Content/Inhalt
Home arrow Marlow's EDI Done Right arrow Marlow Has Issues
Marlow Has Issues PDF Print E-mail
Written by Marlow Atticus   
Sunday, 06 July 2008

So EDI fans; this month I thought I’d do a little follow up on a couple of previous articles to see if we have any progress on these topics and provide a few more examples/facts.

Using Multiple Sendor/ID’s-

A couple of articles ago I commended on how much of a hassle trading partners have with their connecting partners that use oodles and oodles of Sendor/receivers ID’s. There is still one Retailer that is on the top of my list, JC Penney with this effort, but this month I was introduced to a new player Caterpillar – Manufacturing plants.

Those of you who work with JC Penney may already be aware of this, but here are some facts on them –

  • JCP supports 12 different EDI transactions
  • JCP has 47 different EDI ID’s. There is one for outbound per division, and another for inbound per division. Unfortunately, some of the return transactions have the same ID for a given return transaction, so there is not truly a one-to-one association to the ID number used by JCP when sending orders.
  • JCP has 20 different published business units, however there are inconsistencies with what they call each division/business unit between the published lists, what’s indicated in the EDI guidelines business rules and examples, and how they are known by the supplier base.
  • JCP has 7 different shipping labels based on PO type, ship to location, content of cartons or pallets, size of cartons, and placement of the label on those cartons.

Also, word's out last week that JC Penney’s is now requiring the 869 and 870 transactions for some of their business units. Where Penneys is using these transactions in the typical manor, I thought you’d want to be aware of the business requirements of the 870.

For those of you familiar with the 870, you’ll know that it's used as a response to the 869, or as an unsolicited notification of the change in the status of the order. Did you know that JC Penney requires an unsolicited 870 if you are not shipping a given order complete? That’s true. The expectation is that you send the 856 including what you're shipping, and you are to follow up with an 870 on the items/quantities that are not included in the order. Also, you should know that if your 856 does not include all items on the order, and/or if the order/items or any other order are past the ship date.. JC Penney will be sending you an 869.

So just a reminder, make sure you respond to that 869 with an 870… or you’ll be in trouble…….!!!

So lets’ talk about Caterpillar; many of you are in the Retail space, but for those in manufacturing… Beware…. I just started with working with a couple of their suppliers, and found that Caterpillar has a separate ID for each of their ship to location/plants. Did you know that they have nearly 200 of them? Yep, I believe that they do centralized EDI, yet suppliers are expected to assist in the routing of the data to the various plant business applications, rather than mapping internally. If there is anyone out there listening from Caterpillar.. Help your suppliers… do this work not them…

Cross Dock

Several months ago I wrote on the topic of standardizing how cross docking is supported within EDI. In those articles I mentioned that we have retailers like Macy’s, where they send Cross Dock orders with not Ship To, only Store Allocation at the item level, and that the suppliers are expected to know which stores are supported by which of the Macy’s Distribution Centers. Then I talked about Anna's Linens, where they send a separate PO per Store, with the Ship To address being the Store address. Suppliers are asked to Ship to a consolidator by the Ship To address, but the shipping label needs to be the store address. And now we have a new player that will be doing the same as Anna’s... Stop and Shop Prepared foods.

For Macy’s; when are you going to start sharing the DC routing address requirements on an 816? Or even better, create PO’s by DC that would include the appropriate stores, and send the DC address in the PO header as the Ship To like everyone else?

I think through the process of using a consolidation point, perhaps sending store addresses at the PO header level as the Ship To, is the correct way to do this as long as all shipments are picked up by the consolidator, and there is no LTL or Truck Load carrier involved (they actually care about the Ship To address on the label). Another way would be to have the Consolidator as the Ship To, and have the Store address as Buying Party, with the Shipping label having the Store address within the Market For zone of the label. Burlington Coat Factory does this. They use a dedicated fleet for outbound freight to their stores from the DC, and that carrier knows to use the Market For address as the ultimate destination Ship To address.

Thanks for reading. Let me know what you think. Are you having issues with how your trading partners handle their EDI documents? Tell me about it!

Marlow

Marlow Atticus
About the author:
Comments
Add NewSearchRSS
Only registered users can write comments!
 

Member Login