[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: drop ship v 8 for discussion
Bob, It's been my experience, when setting up the 'b2b relation', that getting thru the syntactic signal/message issues is manageable, but getting the semantic 'triggers' / economic events dow to work the right way is what it's all about; that makes a successful b2b relationship work over time. (it's like putting a set of gears connecting 2 company's together, each gear driven by each company internal business process (& system(s)), and when the 2 gears connect cleanly then there's a clear 'company business process state to the other company business state' ... economic event !!) -- strange ... gears in a digital economy ! Dave > > -----Original Message----- > > From: Bob Haugen [mailto:linkage@interaccess.com] > > Sent: Monday, March 19, 2001 2:56 PM > > To: 'Welsh, David'; ebxml-ccbp-analysis@lists.ebxml.org > > Subject: RE: drop ship v 8 for discussion > > > > > > David, > > > > These are critical ideas. They are the same as the issues > > around recognition of economic events, that is, the "trigger point" > > is when the economic event officially can be recognized. > > > > It is also clear that the business process must declare the > > trigger points - they can't be determined unambiguously from > > document type or content, they're part of the agreed-upon rules > > of collaboration. > > > > <David Welsh> > > 'trigger points' that occur within the business processes at the > > transaction level. For example : > > 1. in Order Fulfillment, in the drop ship scenario, the point > > of sale occurs > > when the DSVendor sends back the PO Ack to the Retailer; and > > not earlier. > > This may be more of a general business condition on the whole > > (round trip) > > transaction itself. > > 2. in Ship Goods, again in the scenario, the > > "Shipper.Shipment Instruction" > > needs to be made well in advance of actual transport of > > export of goods > > (well it's supposed to be but the carrier's sales guy might tell you > > something else if your a big shipper). > > 3. in Order Fulfillment, with "Shipper.Notify of Advanced > > shipment", to > > really get compatible transactions between the 2 parties, it > > must be clear > > as to which point in the shipper's process the 'signal' is > > 'triggered' to > > inform the Retailer of product shipment. ie. after the > > product has been > > picked/packed and shipped which is desirable, or only after > > the pick list > > has been printed which can lead to inventory discrepancies and other > > problems for this business model. > > </David Welsh> > > > > -Bob Haugen > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC