LOL

We joke about putting an instruction in the 204 to tell the driver to stop at 
WaWa for coffee before gating into the Wal-mart DC. 

---
Sent from my iPhone. Replies may be delayed.

On Aug 27, 2010, at 9:09 AM, "Leah Halpin" <[email protected]> wrote:

> since it's Friday, the donkey thing was in Mexico.  Supplier and customer 
> quite 
> literally across the "street" (a dirt road) from each other, parts were 
> delivered by a guy pulling a hand truck.  Getting that ASN in on time was a 
> challenge, since supplier and customer systems were both thousands of miles, 
> a 
> few time zones and two VANs away.  Resolution:  tell the guy to walk 
> sloooowwwwwly......
> 
> Happy Friday!
> 
> Leah
> 
> 
> 
> 
> 
> ________________________________
> From: "Hurd, Richard [SLCUS]" <[email protected]>
> To: Leah Halpin <[email protected]>
> Cc: enrio600 <[email protected]>; [email protected]
> Sent: Fri, August 27, 2010 9:04:18 AM
> Subject: Re: [EDI-L] A mapping question for Inovis Catalyst experts
> 
> 
> Although we've not faced donkeys (yet,) we have many of the same issues. We 
> also 
> have multiple DCs serving our customers so lanes are highly customized by 
> source 
> and destination DC. 
> 
> We can go from multiple day transit times to tens of minutes - in one case, 
> our 
> DC and Wal-mart's are within the same town. 
> 
> Plus pick times can vary based upon the orders. 
> 
> All said, it's much more a job for your logistics execution team than for 
> your 
> EDI team. 
> 
> ---
> Sent from my iPhone. Replies may be delayed.
> 
> On Aug 27, 2010, at 8:52 AM, "Leah Halpin" <[email protected]> wrote:
> 
> 
> We frequently use "route" times in the automotive industry to calculate 
> EXPECTED 
> delivery date/time.  As you mention, weather, strikes, international borders, 
> construction, or in one quaint case, donkeys in the road, can change these 
> times.  The routes, however, are calculated and maintained in the ERP, where 
> they can also be changed by the user should they be aware of a particular 
> issue 
> that might affect the normal delivery time.  I agree with Richard it's not a 
> good idea, especially for an ASN to calculate the delivery date in your EDI 
> system.  You did mention you were mapping an 810 and, depending on the 
> industry, 
> I'd think there might be some flexibility for delivery dates in that 
> document.  
> Still not best practice, though, get it from your ERP, that's the way to go 
> (at 
> the very  least, they can't point the finger at you, then).
>> 
>> Leah
>> 
>> 
>> 
>> 
>> 
>> 
> ________________________________
> From: "Hurd, Richard [SLCUS]" <[email protected]>
>> To: enrio600 <[email protected]>
>> Cc: [email protected]
>> Sent: Fri, August 27, 2010 8:21:10 AM
>> Subject: Re: [EDI-L] A mapping question for Inovis Catalyst experts
>> 
>> 
>> Your stuff always has the same transit time?  Wow. 
>> 
>> With that flippant comment I'm showing why doing this kind of calculation in 
>> EDI 
>> may not be the optimal solution. Plus Leah's calendar/business date question 
>> deserves consideration also. 
>> 
>> 
>> ---
>> Sent from my iPhone. Replies may be delayed.
>> 
>> On Aug 26, 2010, at 5:25 PM, enrio600 <[email protected]> wrote:
>> 
>>> Here is question for thow who are experts in trusted link mapping tool
>>> I'm trying to build a formula where I can add a fixed number of days (5) to 
>>> DTM02 date of 810 transaction, what I'm trying to accomplish is to 
>>> calculate a 
>>> delivery date based on a ship date
>>> By adding 5 days to a ship date (DTM02).
>>> I know some of people here are awesome with mapping and maybe can help with 
>>> the 
>>> formula for this problem.
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> ...
>>> 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
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]
> 
> 
> 
> ------------------------------------
> 
> ...
> 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
> 
> 
> 
> 


------------------------------------

...
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:
    [email protected] 
    [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/

Reply via email to