On 15/09/11 11:51 +0200, Korbinian Preisler wrote: > I think we have the following dates to track on a sale: > * the quotation date (the date when the sale is set to state > 'quotation')
It is for separate module as this date will not be used later in the workflow (KISS). > * the order date (the date when the sale is set to state 'confirmed') It should be the sale_date as it is managed for purchase (if not set today). > * the planned date of the customer shipment I think it must be computed as it is for purchase with the delivery time of supplier. > For the moment i am not sure which one of theses dates is the 'sale > date' in the current module. > > The planned date of the customer shipment can depend on many things: > * the customer could state a custom delivery date This is a custom module that could override the computation. > * as you say there could be need for a preparation time This should be managed by the delivery time. > * the planned date can depend on a production process I think such things will be computed from the product delivery time as first estimation. And could be later improved when the computation of the production is done. But all those stuffs are company policies. > So IMHO we would need: > * a date field for the quotation date Not really required. And also quotation can comes back to draft etc. > * a date field for the order date Will be the sale date. > * a function to compute the planned shipment date compute_delivery_date on product > * a date field for defining a custom shipment date (but this may be a > custom need) yes custom. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpnTjfxJOrv0.pgp
Description: PGP signature
