Contributors mailing list archives

contributors@odoo-community.org

Avatar

Re: Service definition modules

by
Acsone SA/NV, Denis Roussel
- 04/09/2019 08:55:02
Hi Alex,


Great news!

Just a little remark : IMHO, this business process should maybe be a little bit generic as you may want to manage it on customer level for purchases.

On Wed, Sep 4, 2019 at 10:47 AM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
Hello all,

In relation with the WMS modules Camptocamp is currently working on, I'm
working on a set of modules to manage service definition.

The idea is to be able to store a set of service levels agreed on with
the customer, with a number of parameters which are specified, and have
default values, but can be customized for a given customer, or a given
sale order.

Typically the parameters could be:

* management of backorders
* days of delivery
* hour of delivery
* invoicing per order (with order reference) or invoicing per delivey
* packaging details in the invoice
* product grouping preference (e.g. a customer could ask for an order of
10 product1, 10 product2, 10 product3 to be packages in 10 parcels
containing each 1 product1, 1 product2, 1 product3 instead of 3 packages
containing a singe product reference)
* constraints on the delivery truck (max dimension, max weight)...

The basic set of user stories is available in
https://github.com/OCA/stock-logistics-warehouse/issues/694 (this issue
will be moved to a better place once we've answerd the question below)

I'm planning to build this as a base module providing the models
required to define the service definitions, and set this on a customer
and on a sale order (+ propagation to invoices and deliveries), +
different smaller modules related to the different aspects (deliveries,
packaging, invoicing...)

I would like to propose these as alpha modules in the OCA but I'm unsure
what repository to target:

* option 1: new repository oca/sale-service-definition, all the addons
go there
* option 2: in repository oca/sale-workflow, at least for the base
module, but then I'm not comfortable in adding cross repository
dependencies, because some of the other modules would probably live in
the WMS repository, others in sale-workflow, others in some maybe in
stock-logistics-*
* option 3: in repository oca/contract because this is related to sale
contract, but I'd like to avoid polluting a self contained module with
lots of cross dependencies
* elsewhere ?

Dear contributors, what would be the best course of action in your opinion?



-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel    : +352 20 21 10 20 19
Fax   : +352 20 21 10 21
Gsm : +352 691 50 60 88

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

Reference