RE: Specifying Processing Time Across Transactions

["Blantz, Mary Kay" <mblantz@netfish.com>]

In addition (my two cents), while some customers demand that the
ASN arrive before the goods are received, other implementations are
not so rigid.  This is something that the trading partners (or do
we now call them collaborators) can agree upon in advance.  Perhaps
in the CPA?

The other scenario, which is unfortunately too common in some
business sectors, is that there is no response given for an
incoming message.  (I suspect this is based on saving money, and
on the false belief that no news is good news.  In fact, it may
mean that no news was received in the first place and that the
process is broken.)  In this case, if the sender is the more
subordinate partner, 'requiring' a response may be good business,
but not in their power to control.

MK

-----Original Message-----
From: Welsh, David [mailto:David.Welsh@nordstrom.com]
Sent: Tuesday, March 13, 2001 5:16 PM
To: 'William J. Kammerer'; ebxml-ccbp-analysis (E-mail)
Subject: RE: Specifying Processing Time Across Transactions


Hi William,
To be so bold, I think Brian was asking about the general case of a sending
process 'requiring' 1 or more responses back in a preset time period.
Something like PO Request (say with multiple line items) and their
corresponding multiple PO confirmations (say per line item till all line
items have been confirmed back off the original PO Request) back to the
original PO request itself where all the PO Request/PO Response
collaboration cycle from start to finish must be done within 24hrs. (or some
other type of business process like that where response time is crtitical
for whatever reason  !)

Dave


> -----Original Message-----
> From: William J. Kammerer [mailto:wkammerer@foresightcorp.com]
> Sent: Tuesday, March 13, 2001 2:23 PM
> To: ebxml-ccbp-analysis (E-mail)
> Subject: Re: Specifying Processing Time Across Transactions
> 
> 
> Brian Hayes asks "...how do you enforce a relationship between a
> document in one transaction with a document in another?... how do you
> specify that a ASN must be sent within 48 hours of an accepted
> [purchase] order?" with respect to Spec Schema 0.90.
> 
> The Advance Ship Notice (or Despatch Advice) isn't generally 
> sent until
> right before the supplier is ready to ship the goods, or even 
> sometimes
> just as the truck leaves the dock.   In any event, the only real
> requirement is that the ASN arrive before the actual goods 
> do!  Besides,
> there may be multiple ASNs if the order has to be split among 
> different
> shipments.
> 
> So asking for the ASN to be delivered within a particular 
> time period is
> kind of a roundabout - and not especially efficient - way of 
> saying when
> you want the goods to be shipped or to arrive.  This should be
> application data sent in the business message.  Sometimes you'll even
> give a narrow window for arrival - so you can ready your own loading
> docks.  Why would it ever be desirable to have application level stuff
> like this encased in concrete within the specification schema?  Did I
> say that right? - I really haven't read the Spec Schema 0.90!
> 
> As an aside, the ASN may have a business acknowledgement 
> requirement of
> a Receipt Advice (i.e., something to say I did indeed receive some or
> all of the stuff).   Applying timing requirements to the 
> Receipt Advice
> vis a vis the ASN might be reasonable, though.
> 
> William J. Kammerer
> FORESIGHT Corp.
> 4950 Blazer Pkwy.
> Dublin, OH USA 43017-3305
> +1 614 791-1600
> 
> Visit FORESIGHT Corp. at http://www.foresightcorp.com/
> "accelerating time-to-trade"
> 
> 
> 
> 
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: 
> ebxml-ccbp-analysis-request@lists.ebxml.org
> 

------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-ccbp-analysis-request@lists.ebxml.org