why geoIdTo in ShipmentCostEstimate

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

why geoIdTo in ShipmentCostEstimate

Divesh Dutta
Hello all,
          I am not getting purpose of geoIdFrom and geoIdTo in ShipmentCostEstimate entity.What I guess is it simply specifies source and destination for shipment.If this is the case then how will we handle the case if shipment is in part.I mean if I want to ship data from warehouse to customer's home.In this case geoIdFrom=warehouse and  geoIdTo=customer's home.But what if there are two or three terminals in between.
Thanks in advance
Regards
Divesh Dutta
Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

Vivek Mishra-2
Hi Divesh,

I think split shipping which is implemented in Quick Checkout(three page
chekout) would serve the solution.

Kind Regards,
--
Vivek Mishra

Divesh Dutta wrote:
> Hello all,
>           I am not getting purpose of geoIdFrom and geoIdTo in ShipmentCostEstimate entity.What I guess is it simply specifies source and destination for shipment.If this is the case then how will we handle the case if shipment is in part.I mean if I want to ship data from warehouse to customer's home.In this case geoIdFrom=warehouse and  geoIdTo=customer's home.But what if there are two or three terminals in between.
> Thanks in advance
> Regards
> Divesh Dutta
>  

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

Sumit Pandit-3
Vivak,

Split shipping does not solve this problem. Split shipping is used when Order have more then one delivery point. Like if you have 2 products in your order and you want to ship each of them at separate location then at that time we split the order into two and assign the desire destination for each product.
So splitting works when the items from the same order ship to more then one location. Not in case is shipment is passes from terminals.

Concept is same as one to many : one order many destination.

Thanks
Sumit Pandit





----- Original Message -----
From: "Vivek Mishra" <[hidden email]>
To: [hidden email]
Sent: Tuesday, December 9, 2008 8:49:36 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: Re: why geoIdTo in ShipmentCostEstimate

Hi Divesh,

I think split shipping which is implemented in Quick Checkout(three page
chekout) would serve the solution.

Kind Regards,
--
Vivek Mishra

Divesh Dutta wrote:
> Hello all,
> I am not getting purpose of geoIdFrom and geoIdTo in ShipmentCostEstimate entity.What I guess is it simply specifies source and destination for shipment.If this is the case then how will we handle the case if shipment is in part.I mean if I want to ship data from warehouse to customer's home.In this case geoIdFrom=warehouse and geoIdTo=customer's home.But what if there are two or three terminals in between.
> Thanks in advance
> Regards
> Divesh Dutta
>
Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

David E Jones-3

The concept closest to this in OFBiz is handled by the  
ShipmentRouteSegment and related entities. There is nothing in the  
checkout process for the customer to specify such information, and I'm  
not sure if you'd want the customer to specify such things.

When manually creating a Shipment for an order in the Facility Manager  
you can specify multiple route segments with different carriers,  
tracking codes, and the works.

-David


On Dec 9, 2008, at 9:00 PM, Sumit Pandit wrote:

> Vivak,
>
> Split shipping does not solve this problem. Split shipping is used  
> when Order have more then one delivery point. Like if you have 2  
> products in your order and you want to ship each of them at separate  
> location then at that time we split the order into two and assign  
> the desire destination for each product.
> So splitting works when the items from the same order ship to more  
> then one location. Not in case is shipment is passes from terminals.
>
> Concept is same as one to many : one order many destination.
>
> Thanks
> Sumit Pandit
>
>
>
>
>
> ----- Original Message -----
> From: "Vivek Mishra" <[hidden email]>
> To: [hidden email]
> Sent: Tuesday, December 9, 2008 8:49:36 PM GMT +05:30 Chennai,  
> Kolkata, Mumbai, New Delhi
> Subject: Re: why geoIdTo in ShipmentCostEstimate
>
> Hi Divesh,
>
> I think split shipping which is implemented in Quick Checkout(three  
> page
> chekout) would serve the solution.
>
> Kind Regards,
> --
> Vivek Mishra
>
> Divesh Dutta wrote:
>> Hello all,
>> I am not getting purpose of geoIdFrom and geoIdTo in  
>> ShipmentCostEstimate entity.What I guess is it simply specifies  
>> source and destination for shipment.If this is the case then how  
>> will we handle the case if shipment is in part.I mean if I want to  
>> ship data from warehouse to customer's home.In this case  
>> geoIdFrom=warehouse and geoIdTo=customer's home.But what if there  
>> are two or three terminals in between.
>> Thanks in advance
>> Regards
>> Divesh Dutta
>>

Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

Sumit Pandit-3
In reply to this post by Divesh Dutta
Hello Divesh,

Regarding to your case, I am not sure that this functionality already exist in OFBiz or not.
But the logic should be like that :

For example track from source to destination is like :
Source (S) --> Terminal1(t1) --> Terminal2(t2) --> Terminal3(t3) --> Destination(D)

Now for such case we can calculate the shipment cost of each break point and then collectively get the cost of S to D.

Total cost(shipment) = cost(S to t1) + cost (t1 to t2) + cost (t2 to t3) + cost (t3 to D).

I think it would work, Also I will really appreciate that if any from dev provide better option to solve this problem.

Thanks And Regards
Sumit Pandit.



----- Original Message -----
From: "Divesh Dutta" <[hidden email]>
To: "user" <[hidden email]>
Sent: Tuesday, December 9, 2008 7:31:31 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: why geoIdTo in ShipmentCostEstimate

Hello all,
I am not getting purpose of geoIdFrom and geoIdTo in ShipmentCostEstimate entity.What I guess is it simply specifies source and destination for shipment.If this is the case then how will we handle the case if shipment is in part.I mean if I want to ship data from warehouse to customer's home.In this case geoIdFrom=warehouse and geoIdTo=customer's home.But what if there are two or three terminals in between.
Thanks in advance
Regards
Divesh Dutta
Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

Sumit Pandit-3
In reply to this post by David E Jones-3


Ah David !

You are amazing, I really missed the route segment concept. It can handle the problem of Divesh.

Thank you very much.

--
Regards
Sumit Pandit

----- Original Message -----
From: "David E Jones" <[hidden email]>
To: [hidden email]
Sent: Wednesday, December 10, 2008 9:35:59 AM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: Re: why geoIdTo in ShipmentCostEstimate


The concept closest to this in OFBiz is handled by the
ShipmentRouteSegment and related entities. There is nothing in the
checkout process for the customer to specify such information, and I'm
not sure if you'd want the customer to specify such things.

When manually creating a Shipment for an order in the Facility Manager
you can specify multiple route segments with different carriers,
tracking codes, and the works.

-David


On Dec 9, 2008, at 9:00 PM, Sumit Pandit wrote:

> Vivak,
>
> Split shipping does not solve this problem. Split shipping is used
> when Order have more then one delivery point. Like if you have 2
> products in your order and you want to ship each of them at separate
> location then at that time we split the order into two and assign
> the desire destination for each product.
> So splitting works when the items from the same order ship to more
> then one location. Not in case is shipment is passes from terminals.
>
> Concept is same as one to many : one order many destination.
>
> Thanks
> Sumit Pandit
>
>
>
>
>
> ----- Original Message -----
> From: "Vivek Mishra" <[hidden email]>
> To: [hidden email]
> Sent: Tuesday, December 9, 2008 8:49:36 PM GMT +05:30 Chennai,
> Kolkata, Mumbai, New Delhi
> Subject: Re: why geoIdTo in ShipmentCostEstimate
>
> Hi Divesh,
>
> I think split shipping which is implemented in Quick Checkout(three
> page
> chekout) would serve the solution.
>
> Kind Regards,
> --
> Vivek Mishra
>
> Divesh Dutta wrote:
>> Hello all,
>> I am not getting purpose of geoIdFrom and geoIdTo in
>> ShipmentCostEstimate entity.What I guess is it simply specifies
>> source and destination for shipment.If this is the case then how
>> will we handle the case if shipment is in part.I mean if I want to
>> ship data from warehouse to customer's home.In this case
>> geoIdFrom=warehouse and geoIdTo=customer's home.But what if there
>> are two or three terminals in between.
>> Thanks in advance
>> Regards
>> Divesh Dutta
>>

Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

Divesh Dutta
In reply to this post by Divesh Dutta
Hello All,
           Thank you much for your answers.I just went through ShipmentRouteSegment entity.By this i can handle Distributed shipments.But my problem is to calculate shipment cost.And I find no relation between  ShipmentCostEstimate entity and ShipmentRouteSegment entity.And I still didnt got the reply for my first mail.Purpose of geoIdTo ? Is it mean destination here? Thanks again to all of you.

Regards
Divesh Dutta


----- "Sumit Pandit" <[hidden email]> wrote:

| Ah David !
|
| You are amazing, I really missed the route segment concept. It can
| handle the problem of Divesh.
|
| Thank you very much.
|
| --
| Regards
| Sumit Pandit
|
| ----- Original Message -----
| From: "David E Jones" <[hidden email]>
| To: [hidden email]
| Sent: Wednesday, December 10, 2008 9:35:59 AM GMT +05:30 Chennai,
| Kolkata, Mumbai, New Delhi
| Subject: Re: why geoIdTo in ShipmentCostEstimate
|
|
| The concept closest to this in OFBiz is handled by the
| ShipmentRouteSegment and related entities. There is nothing in the
| checkout process for the customer to specify such information, and I'm
|
| not sure if you'd want the customer to specify such things.
|
| When manually creating a Shipment for an order in the Facility Manager
|
| you can specify multiple route segments with different carriers,
| tracking codes, and the works.
|
| -David
|
|
| On Dec 9, 2008, at 9:00 PM, Sumit Pandit wrote:
|
| > Vivak,
| >
| > Split shipping does not solve this problem. Split shipping is used
| > when Order have more then one delivery point. Like if you have 2
| > products in your order and you want to ship each of them at separate
|
| > location then at that time we split the order into two and assign
| > the desire destination for each product.
| > So splitting works when the items from the same order ship to more
| > then one location. Not in case is shipment is passes from terminals.
|
| >
| > Concept is same as one to many : one order many destination.
| >
| > Thanks
| > Sumit Pandit
| >
| >
| >
| >
| >
| > ----- Original Message -----
| > From: "Vivek Mishra" <[hidden email]>
| > To: [hidden email]
| > Sent: Tuesday, December 9, 2008 8:49:36 PM GMT +05:30 Chennai,
| > Kolkata, Mumbai, New Delhi
| > Subject: Re: why geoIdTo in ShipmentCostEstimate
| >
| > Hi Divesh,
| >
| > I think split shipping which is implemented in Quick Checkout(three
|
| > page
| > chekout) would serve the solution.
| >
| > Kind Regards,
| > --
| > Vivek Mishra
| >
| > Divesh Dutta wrote:
| >> Hello all,
| >> I am not getting purpose of geoIdFrom and geoIdTo in
| >> ShipmentCostEstimate entity.What I guess is it simply specifies
| >> source and destination for shipment.If this is the case then how
| >> will we handle the case if shipment is in part.I mean if I want to
|
| >> ship data from warehouse to customer's home.In this case
| >> geoIdFrom=warehouse and geoIdTo=customer's home.But what if there
| >> are two or three terminals in between.
| >> Thanks in advance
| >> Regards
| >> Divesh Dutta
| >>
Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

David E Jones-3

There's a big difference between estimated and actual costs, and  
separate entities for them.

The basic reality is that if something doesn't support something, and  
you need/want it, then you'll have to write something to support that.  
The shipment estimates are fairly simple.

Stepping back a little, it sounds like you need to do more thorough  
requirements gathering (preferably organized by process) and then  
design. It's tough to do that on a mailing list as it requires lots of  
time and full disclosure of details... and if the details aren't  
complete the ideas and solutions proposed are almost certain to be  
flawed.

-David


On Dec 9, 2008, at 9:31 PM, Divesh Dutta wrote:

> Hello All,
>           Thank you much for your answers.I just went through  
> ShipmentRouteSegment entity.By this i can handle Distributed  
> shipments.But my problem is to calculate shipment cost.And I find no  
> relation between  ShipmentCostEstimate entity and  
> ShipmentRouteSegment entity.And I still didnt got the reply for my  
> first mail.Purpose of geoIdTo ? Is it mean destination here? Thanks  
> again to all of you.
>
> Regards
> Divesh Dutta
>
>
> ----- "Sumit Pandit" <[hidden email]> wrote:
>
> | Ah David !
> |
> | You are amazing, I really missed the route segment concept. It can
> | handle the problem of Divesh.
> |
> | Thank you very much.
> |
> | --
> | Regards
> | Sumit Pandit
> |
> | ----- Original Message -----
> | From: "David E Jones" <[hidden email]>
> | To: [hidden email]
> | Sent: Wednesday, December 10, 2008 9:35:59 AM GMT +05:30 Chennai,
> | Kolkata, Mumbai, New Delhi
> | Subject: Re: why geoIdTo in ShipmentCostEstimate
> |
> |
> | The concept closest to this in OFBiz is handled by the
> | ShipmentRouteSegment and related entities. There is nothing in the
> | checkout process for the customer to specify such information, and  
> I'm
> |
> | not sure if you'd want the customer to specify such things.
> |
> | When manually creating a Shipment for an order in the Facility  
> Manager
> |
> | you can specify multiple route segments with different carriers,
> | tracking codes, and the works.
> |
> | -David
> |
> |
> | On Dec 9, 2008, at 9:00 PM, Sumit Pandit wrote:
> |
> | > Vivak,
> | >
> | > Split shipping does not solve this problem. Split shipping is used
> | > when Order have more then one delivery point. Like if you have 2
> | > products in your order and you want to ship each of them at  
> separate
> |
> | > location then at that time we split the order into two and assign
> | > the desire destination for each product.
> | > So splitting works when the items from the same order ship to more
> | > then one location. Not in case is shipment is passes from  
> terminals.
> |
> | >
> | > Concept is same as one to many : one order many destination.
> | >
> | > Thanks
> | > Sumit Pandit
> | >
> | >
> | >
> | >
> | >
> | > ----- Original Message -----
> | > From: "Vivek Mishra" <[hidden email]>
> | > To: [hidden email]
> | > Sent: Tuesday, December 9, 2008 8:49:36 PM GMT +05:30 Chennai,
> | > Kolkata, Mumbai, New Delhi
> | > Subject: Re: why geoIdTo in ShipmentCostEstimate
> | >
> | > Hi Divesh,
> | >
> | > I think split shipping which is implemented in Quick  
> Checkout(three
> |
> | > page
> | > chekout) would serve the solution.
> | >
> | > Kind Regards,
> | > --
> | > Vivek Mishra
> | >
> | > Divesh Dutta wrote:
> | >> Hello all,
> | >> I am not getting purpose of geoIdFrom and geoIdTo in
> | >> ShipmentCostEstimate entity.What I guess is it simply specifies
> | >> source and destination for shipment.If this is the case then how
> | >> will we handle the case if shipment is in part.I mean if I want  
> to
> |
> | >> ship data from warehouse to customer's home.In this case
> | >> geoIdFrom=warehouse and geoIdTo=customer's home.But what if there
> | >> are two or three terminals in between.
> | >> Thanks in advance
> | >> Regards
> | >> Divesh Dutta
> | >>

Reply | Threaded
Open this post in threaded view
|

Re: why geoIdTo in ShipmentCostEstimate

BJ Freeman
In reply to this post by Divesh Dutta
yes geoIDto means destination.
1) you have to define all the transportation parties
2) define their shipping costs in the tables.
and /or link realtime to the shipper for estimates.
3) write a couple of services that break down the routes and shippers
used, then estimate the cost per segment.
4) Save the lump sum of the calculation in the estimate.



Divesh Dutta sent the following on 12/9/2008 8:31 PM:

> Hello All,
>            Thank you much for your answers.I just went through ShipmentRouteSegment entity.By this i can handle Distributed shipments.But my problem is to calculate shipment cost.And I find no relation between  ShipmentCostEstimate entity and ShipmentRouteSegment entity.And I still didnt got the reply for my first mail.Purpose of geoIdTo ? Is it mean destination here? Thanks again to all of you.
>
> Regards
> Divesh Dutta
>
>
> ----- "Sumit Pandit" <[hidden email]> wrote:
>
> | Ah David !
> |
> | You are amazing, I really missed the route segment concept. It can
> | handle the problem of Divesh.
> |
> | Thank you very much.
> |
> | --
> | Regards
> | Sumit Pandit
> |
> | ----- Original Message -----
> | From: "David E Jones" <[hidden email]>
> | To: [hidden email]
> | Sent: Wednesday, December 10, 2008 9:35:59 AM GMT +05:30 Chennai,
> | Kolkata, Mumbai, New Delhi
> | Subject: Re: why geoIdTo in ShipmentCostEstimate
> |
> |
> | The concept closest to this in OFBiz is handled by the
> | ShipmentRouteSegment and related entities. There is nothing in the
> | checkout process for the customer to specify such information, and I'm
> |
> | not sure if you'd want the customer to specify such things.
> |
> | When manually creating a Shipment for an order in the Facility Manager
> |
> | you can specify multiple route segments with different carriers,
> | tracking codes, and the works.
> |
> | -David
> |
> |
> | On Dec 9, 2008, at 9:00 PM, Sumit Pandit wrote:
> |
> | > Vivak,
> | >
> | > Split shipping does not solve this problem. Split shipping is used
> | > when Order have more then one delivery point. Like if you have 2
> | > products in your order and you want to ship each of them at separate
> |
> | > location then at that time we split the order into two and assign
> | > the desire destination for each product.
> | > So splitting works when the items from the same order ship to more
> | > then one location. Not in case is shipment is passes from terminals.
> |
> | >
> | > Concept is same as one to many : one order many destination.
> | >
> | > Thanks
> | > Sumit Pandit
> | >
> | >
> | >
> | >
> | >
> | > ----- Original Message -----
> | > From: "Vivek Mishra" <[hidden email]>
> | > To: [hidden email]
> | > Sent: Tuesday, December 9, 2008 8:49:36 PM GMT +05:30 Chennai,
> | > Kolkata, Mumbai, New Delhi
> | > Subject: Re: why geoIdTo in ShipmentCostEstimate
> | >
> | > Hi Divesh,
> | >
> | > I think split shipping which is implemented in Quick Checkout(three
> |
> | > page
> | > chekout) would serve the solution.
> | >
> | > Kind Regards,
> | > --
> | > Vivek Mishra
> | >
> | > Divesh Dutta wrote:
> | >> Hello all,
> | >> I am not getting purpose of geoIdFrom and geoIdTo in
> | >> ShipmentCostEstimate entity.What I guess is it simply specifies
> | >> source and destination for shipment.If this is the case then how
> | >> will we handle the case if shipment is in part.I mean if I want to
> |
> | >> ship data from warehouse to customer's home.In this case
> | >> geoIdFrom=warehouse and geoIdTo=customer's home.But what if there
> | >> are two or three terminals in between.
> | >> Thanks in advance
> | >> Regards
> | >> Divesh Dutta
> | >>
>
>