Gary,
Isn't the agent billing by shipment not customer generated order
number? Why would the customer or agent of themself, restrict billing
or HB creation by completed customer order? Reminds me of a trick in the
old days when companies supplied free shipping over $5k you just order
something that is obsolete and you are sure will be on backorder for
over $5k along with your goods you want shipped for free.
There's no problem having a partial ship with multiple packs, two
shipments, two HBs against one customer order, one customer PO and one
Master HB.
One thing we don't want to confuse is end user customer or shipper
generated and used numbers/references PO Number, Order Num, Customer
generated Shipment ID, Delivery Num, Packing slip num, etc. With
Logistics generated numbers HB, MHAWB, Container ID, Railway BOL, etc.
To add to the confusion sometimes LSPs provide a block of HB's for the
shipper to assign.
Regards,
-Steve
Gary D. Bligh wrote:
> Steve,
>
> Not necessarily. Yes, it is possible for an agent to use its FCR as
> its HBL.
> Yet this is not the case when an order is received over multiple
> deliviries.
>
> For example, let say the shipper fulfills an order over two days.
> Truck one
> brings the first load on day 1, then agent issues a fright receipt
> (FCR 1).
> Then, the second load from the same shipper for the same order, is
> received
> the on day 2, then the agent issues another freight receipt 2 (FCR 2).
>
> Thee are several possibilities here. In this example, items for the
> same PO
> are received over two days. What does the agent do? Have two House
> Bills for
> the same order? That is indeed possible. Or, would the agent wait for
> completion of the booked order. This too is possible. It is also possible
> for several orders to be combined under one house.
>
> So, it all goes back to SOPs.
>
> This is why I enjoy the Transportation field.
>
> Gary
>
> -----Original Message-----
> From: [email protected] <mailto:EDI-L%40yahoogroups.com>
> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com>] On
> Behalf Of
> Steve
> Sent: Saturday, August 26, 2006 4:33 AM
> To: Karl
> Cc: [email protected] <mailto:EDI-L%40yahoogroups.com>
> Subject: Re: [EDI-L] Forwarders Cargo Receipt
>
> What you are referring to is called the House Bill or House AirWay Bill
> (HAWB) or Master House Airway Bill (MHAWB) number for freight. This is
> like the tracking number for parcel. Internally where I worked it's
> referred by the House Bill, but many times is broken /databased down for
> the customer using their reference number like Customer Shipment ID.
> What you are asking can be broken down into a database or business
> process question instead of a ASN or Packing list question as these are
> tools to execute the business process.
> a MHAWB can contain multiple HAWBs, ( to oversimplify a HAWB is a
> shipment).
>
> Your first question: Typically the LSP would serve a large Multi
> National Corporation which has allready built applications referring to
> shipments with their unique number and LSPs are able to cater the
> information to their specifications. If you asked a LSP to give me what
> you they got in their generic message, One ASN would contain one
> shipment. If their were multiple shipments their would be a master
> shipment number or shipment consolidation number with individual
> shipment numbers tied under it.
>
> Your second qeustion: Yes you can have a packing list or master packing
> list contain more than one shipment. It's just a matter of a single
> packing list number being tied to two shipment ids.
>
> Your third question: The HAWB number.
>
> What you typically won't see is a single ASN reporting on a
> 'shipment(s)' over multi modes air/ocean/truck/rail/parcel/warehousing
> and distribution. Unless it is specifically requested by the customer
> for consolidated reporting.
>
> Alot of these situations depends on what side of the table your are
> sitting on and wether it is a round table or a triangle shaped table ie
> you are a big customer or a small customer.
>
> Regards,
> -Steve
>
> Karl wrote:
>
> > The Forwarders Cargo Receipt (FCR) is generally delivered via the 856.
> > Just
> > in case "FCR" is too-specific, I mean this in the most general sense
> > i.e. a
> > "logistics service provider (LSP) ASN message, confirming receipt
> (back to
> > the shipper / vendor) of cargo".
> >
> > I am interested in hearing about use-cases and real-life practices
> of this
> > message in the international shipping arena, where this message is
> > delivered
> > from a logistics provider / forwarder to a shipper / vendor. In this
> type
> > of supply chain, a vendor can commonly issue multiple packing lists
> for a
> > single ocean / air "main shipment". This raises (at least) the following
> > questions:
> >
> > 1. Does such a message always confirm one and only one ocean / air
> > shipment? Would the shipper ever receive a single FCR with information
> > about multiple shipments? If so, what does this mean? Does it mean, for
> > example, that there are actually multiple FCRs w/i message, each
> > identified
> > by a hierarchical level (probably the "Shipment" level)?
> >
> > 2. Is it possible for a packing list to appear on multiple FCRs i.e.
> to be
> > split across FCRs?
> >
> > 3. IN PRACTICE, what references does an LSP reiterate to the shipper
> so he
> > may reconcile / tie to documents in his system?
> >
> > Thanks and Regards,
> > Karl
> > --
> > Email: [EMAIL PROTECTED] <mailto:KarlJWolf%40Gmail.com>
> <mailto:KarlJWolf%40Gmail.com>
> >
> > [Non-text portions of this message have been removed]
> >
> >
>
> [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
>
>
[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
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> 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/
