[
https://issues.apache.org/jira/browse/OFBIZ-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457491#comment-16457491
]
Swapnil Shah edited comment on OFBIZ-10372 at 4/28/18 9:35 AM:
---------------------------------------------------------------
As we are dealing it on Time dimension, it would be worthwhile to make it honor
the working (or holiday) calendars at shipper's or shipping carrier's or for
that matter even at receiver's end. For instance many a times there may be
fixed working days/hours to dispatch the goods from shipper's end or to pick up
the shipments at carrier's end or to receive the goods at receiver's end. In
such cases promising Est. Delivery Date (EDD) merely based on lead time may not
be so accurate.
Currently one of possible ways to manage calendars could be using
CustomTimePeriod, if that is true then 'ShipmentTimeEstimate' can be extended
by adding the 'customTimePeriodId' and enahance the code to honor it as well
while deriving EDD.
was (Author: swash78):
As we are dealing it on Time dimension, it would be worthwhile to make it honor
the working (or holiday) calendars at shipper's or shipping carrier's or for
that matter even at receiver's end. For instance many a times there may be
fixed working days/hours to dispatch the goods from shipper's end or to pick up
the shipments at carrier's end or to receive the goods at receiver's end. In
such cases promising Est. Delivery Date (EDD) merely based on lead time may not
be so accurate.
Currently one of possible ways to manage calendars could be using
CustomTimePeriod, if that is trun then 'ShipmentTimeEstimate' can be extended
by adding the 'customTimePeriodId' and enahance the code to honor it as well
while deriving EDD.
> Calculate estimated shipment delivery time
> ------------------------------------------
>
> Key: OFBIZ-10372
> URL: https://issues.apache.org/jira/browse/OFBIZ-10372
> Project: OFBiz
> Issue Type: New Feature
> Components: order
> Affects Versions: Trunk
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Major
> Labels: order, shipment, time
> Attachments: OFBIZ-10372.patch
>
>
> Currently when you pass an order in ofbiz you can select the shipment method
> to delivery finish good and obtains an amount cost but you have nothing to
> indicate how the delivration will during.
> We have a good example with ship by plane or boat and for road the time is
> different between the Portugal to Spain and Portugal to Slovenia.
> With this information, we can planned the estimated delivery date with the
> estimated date to produce finish good and the time to delivery them
> To fill this gap, we introduce a new entity ShipmentTimeEstimate modelled as
> ShipmentCostEstimate to define the estimated time for a shipment method, a
> carrier and two geo location:
> {code:java}
> <entity entity-name="ShipmentTimeEstimate"
> package-name="org.apache.ofbiz.shipment.shipment"
> title="Shipment Time Estimation Entity">
> <field name="shipmentMethodTypeId" type="id"/>
> <field name="partyId" type="id"/>
> <field name="roleTypeId" type="id"/>
> <field name="geoIdTo" type="id"/>
> <field name="geoIdFrom" type="id"/>
> <field name="fromDate" type="date-time"/>
> <field name="thruDate" type="date-time"/>
> <field name="leadTime" type="fixed-point"/>
> <field name="leadTimeUomId" type="id"/>
> <prim-key field="shipmentMethodTypeId"/>
> <prim-key field="partyId"/>
> <prim-key field="roleTypeId"/>
> <prim-key field="geoIdTo"/>
> <prim-key field="geoIdFrom"/>
> <prim-key field="fromDate"/>
> ...
> {code}
> We have two asks related to this issue on users
> [1|https://lists.apache.org/thread.html/de58aa36744804c28eccef6fc7ebc8f0311f65b0dc6b17f1fa5234d4@%3Cuser.ofbiz.apache.org%3E]
>
> [2|https://lists.apache.org/thread.html/1d79dd9f42fc256e5986271e9e0447bde2980bf0310c4b5f04a35e9f@%3Cuser.ofbiz.apache.org%3E]
>
> The first patch made in collaboration with Leila Mekika lays bricks to
> implement this idea
> All remark and suggest are welcome to continue it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
