Contributors

contributors@odoo-community.org

Combined view for view List and view Timeline

Hello Contributors,

I would like to see if there are any pointers for the below requirements, thanks in advance.

In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.

but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.

I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.

Have a good weekend!
Sandip
SANDIP MANGUKIYA
TEAM LEAD MANAGER
O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

by Sandip Mangukiya - 01:30 - 29 May 2021
5 replies 5 replies
Re: Combined view for view List and view Timeline

I wonder if you could do something real simple like have a stored functional field called planned_or_unplanned_date / planned_unplanned or something. If it is unplanned set the date to something which is viewable on timeline with its own swim lane, otherwise set it to the planned date. So that way you can see it and drag drop. Have an inverse which sets the planned date when moved.

On Sun, May 30, 2021 at 4:42 AM Sandip Mangukiya <smangukiya@opensourceintegrators.com> wrote:
Hi Pedro, We have put that option on the table as well. Thanks for confirming it as valid :)
SANDIP MANGUKIYA
TEAM LEAD MANAGER
O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Sat, May 29, 2021 at 12:56 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.

The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.

Regards.

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

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

by Graeme Gellatly - 11:16 - 29 May 2021

Re: Combined view for view List and view Timeline

Hi Pedro, We have put that option on the table as well. Thanks for confirming it as valid :)
SANDIP MANGUKIYA
TEAM LEAD MANAGER
O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Sat, May 29, 2021 at 12:56 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.

The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.

Regards.

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

by Sandip Mangukiya - 06:41 - 29 May 2021

Re: Combined view for view List and view Timeline

Thank you, Daniel, I did look at that option and will require work on top of that in order to communicate with each other.

On Sat, May 29, 2021, 12:47 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:
Hello Sandip, you could try the”board” view, that allows to compose several views in the same page.

--dr

No dia 29/05/2021, às 00:31, Sandip Mangukiya <smangukiya@opensourceintegrators.com> escreveu:

Hello Contributors,

I would like to see if there are any pointers for the below requirements, thanks in advance.

In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.

but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.

I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.

Have a good weekend!
Sandip
SANDIP MANGUKIYA
TEAM LEAD MANAGER
O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

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

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

by Sandip Mangukiya - 06:35 - 29 May 2021

Re: Combined view for view List and view Timeline

The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.

The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.

Regards.

by Pedro M. Baeza - 09:55 - 29 May 2021

Re: Combined view for view List and view Timeline

Hello Sandip, you could try the”board” view, that allows to compose several views in the same page.

--dr

No dia 29/05/2021, às 00:31, Sandip Mangukiya <smangukiya@opensourceintegrators.com> escreveu:

Hello Contributors,

I would like to see if there are any pointers for the below requirements, thanks in advance.

In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.

but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.

I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.

Have a good weekend!
Sandip
SANDIP MANGUKIYA
TEAM LEAD MANAGER
O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

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

by Daniel Reis - 09:46 - 29 May 2021

question about payroll and attendance

Hello,

I was wondering if there can be a link between payroll and attendances 
(hr.attendance) in Odoo ? The payroll module has a link with attendance 
(work calendar attendences) but not hr.attendences, AFAICT, so it seems 
weird to not be able to record overtime. But maybe I'm missing something 
obvious?


-- 
Alexandre Fayolle
Senior Software Engineer
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

by Alexandre Fayolle - 11:06 - 27 May 2021

[Compta] Generation des FEC et non assujetti TVA

Hello,

(English below)

J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?

Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?

Cordialement

------- (English version)

I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?

Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?

Regards
--
Mathieu

by mathieu - 10:25 - 27 May 2021
2 replies 2 replies
Re: [Compta] Generation des FEC et non assujetti TVA

Hi Mathieu,

Alexis De lattre (OCA responsible of l10n_france) worked today on that point (it seems) for v14.

Could you review and talk on this PR ? https://github.com/OCA/l10n-france/pull/288

kind regards.

Sylvain LE GAL - Twitter
GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17
Service Informatique : (+33) 09.73.79.64.40
Astreinte Informatique : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)
Web Site | Twitter

Le jeu. 27 mai 2021 à 10:26, Mathieu C. <mathieu@matmicro.net> a écrit :
Hello,

(English below)

J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?

Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?

Cordialement

------- (English version)

I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?

Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?

Regards
--
Mathieu

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

by Sylvain LE GAL - 11:01 - 28 May 2021

Re: [Compta] Generation des FEC et non assujetti TVA

You're right, generating FEC should also work for companies without VAT.
I fixed it in this PR on l10n_fr_fec_oca (the OCA "improved" version to generate FEC) for odoo v14.0 :

https://github.com/OCA/l10n-france/pull/288

You can backport it to v10, it's very easy.

Alexis

Le jeu. 27 mai 2021 à 10:26, Mathieu C. <mathieu@matmicro.net> a écrit :
Hello,

(English below)

J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?

Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?

Cordialement

------- (English version)

I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?

Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?

Regards
--
Mathieu

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

by Alexis de Lattre - 11:01 - 28 May 2021
Problem with fiscal year starting on 1 October to 30 September and Odoo BI Report

Dear community,

For the fiscal year that starts from October and ending September. So, on the Odoo BI view, we expect to see that 2021 / Q1 means 1 October to 31 December.

I think this is not possible in Odoo, as it only use "Date" to interpret the report, right?

To achieve the expected result, I can only think of adding fiscalyear_id, and quarter as computed stored field in every models needed, which is very inefficient.

Anyone have better way to achieve this?

Many thanks,
Kitti U.

by Kitti Upariphutthiphong - 05:01 - 26 May 2021
1 replies 1 replies
Re: Problem with fiscal year starting on 1 October to 30 September and Odoo BI Report

Just for the finding record, OCA has a solution which is based on date_range. Which requires to work model by model.

https://github.com/OCA/account-financial-tools/tree/12.0/account_move_fiscal_month

On Wed, May 26, 2021 at 10:01 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
Dear community,

For the fiscal year that starts from October and ending September. So, on the Odoo BI view, we expect to see that 2021 / Q1 means 1 October to 31 December.

I think this is not possible in Odoo, as it only use "Date" to interpret the report, right?

To achieve the expected result, I can only think of adding fiscalyear_id, and quarter as computed stored field in every models needed, which is very inefficient.

Anyone have better way to achieve this?

Many thanks,
Kitti U.

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

by Kitti Upariphutthiphong - 05:05 - 29 May 2021
v14 accounting changes

Hi all,

We started to take a closer look at the v14 accounting.

We are not delighted…to put it mildly.

We were wondering if any of you had something ongoing or planned to address some of the following points that we have encountered so far:
* Major changes in the taxe logic
* Use of a transit account in the bank reconcile process
* Cancel state of accounting entries
* Creation of entries that are then cancelled when a draft invoice is cancelled

On a more general basis, how do you plan to approach the migration to v14 for the accounting part considering the risk?

Looking forward to hear your insights,

Thanks!

--
Quentin Lavallee - Chargé de projets
NUMIGI SOLUTIONS INC.
quentin.lavallee@numigi.com
(514) 317-7944

Longueuil, Québec, Canada
http://www.numigi.com/

by Quentin Lavallée-Bourdeau - 04:31 - 21 May 2021
3 replies 3 replies
Re: v14 accounting changes

I'm not actually using v14, but I've play with it a little bit some time ago and there were some things that IMHO where a loss (between v13 and v14).
Now a payment only impacts the outstanding account (cash and bank journals). So, to see the actual balance of those journals
you must use statements (I like statements but I don't like to be force to use them on all customers and all journals)
after the v14 release, odoo add a patch that allows you to select the same journal liquidity account as the outstanding account as a way to bypass the outstanding. If you do so:
The journal dashboard gives wrong data
you can't use statements for this journal, and if you decide to use them later you are not going to be able to reconcile any previous payment.
also, the setup to bypass outstanding is not user friendly
payment + reconcile later vs paying from reconciliation
In the previous version, if you pay from a bank statement a bill (black line) or if you create the payment and later reconcile it (blue line) the behaviour was the same, one payment. The only difference was the workflow
on v14, if you create the payment and reconcile later you will have one payment + one statement journal entry. If you pay from the statement you only have one journal entry
I don't like it because:
what odoo is doing is not the same regarding the workflow
If you pay from statements you don't have a payment so you won't see the payment on your payments lists and also you can't send a receipt/payment
If we make the payment before we have 2 journal entries (the one from the payment plus the one from the statement) for the same operation. In previous version being one journal entry was clearer for me
I believe there were some other things but I can't remember them right now.
That's my quick feeback for v14 reconciliation

Ing. Juan José Scarafía
(+54 9 341) 3 278039
twitter: @jjscarafia
github: @jjscarafia

El vie, 21 de may. de 2021 a la(s) 12:27, Oleg Kuryan (oleg.kuryan@xpansa.com) escribió:
I agree with Pedro. I do not see problem statement in an email. Moreover in all above features I see only pluses that finally started to work properly.

On Fri, 21 May 2021 at 17:42, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Unless you specify the problems, I don't see such problems in the new "features", except train users on them.

If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.

Regards.

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

--
///

Best Regards,
Oleg Kuryan

/// CTO | xpansa.com | We create software products and technology companies
/// CEO & COO | ventor.tech | Building Personalized Inventory and Product Management System
/// mail : oleg.kuryan@xpansa.com
/// phone : +375293358638
/// skype : kuryan.oleg

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

by Juan José Scarafía - 12:45 - 23 May 2021

Re: v14 accounting changes

I agree with Pedro. I do not see problem statement in an email. Moreover in all above features I see only pluses that finally started to work properly.

On Fri, 21 May 2021 at 17:42, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Unless you specify the problems, I don't see such problems in the new "features", except train users on them.

If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.

Regards.

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

--
///

Best Regards,
Oleg Kuryan

/// CTO | xpansa.com | We create software products and technology companies
/// CEO & COO | ventor.tech | Building Personalized Inventory and Product Management System
/// mail : oleg.kuryan@xpansa.com
/// phone : +375293358638
/// skype : kuryan.oleg

by Oleg Kuryan - 05:25 - 21 May 2021

Re: v14 accounting changes

Unless you specify the problems, I don't see such problems in the new "features", except train users on them.

If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.

Regards.

by Pedro M. Baeza - 04:40 - 21 May 2021
Migration to Odoo 14: replacing size attribute of Char field

Hi all,
I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:
Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.

The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?

I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.
Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.
I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.

This said, what is a valid alternative to the size=X attribute?

Thanks,
Simone Rubino

by Simone Rubino - 12:56 - 21 May 2021
5 replies 5 replies
Re: Migration to Odoo 14: replacing size attribute of Char field

Thanks all for your suggestions :)
I chose to move the constraint to UI; unfortunately the Char widget did not allow to set the size option so I implemented https://github.com/OCA/web/pull/1952 that allows it.

On Fri, 21 May 2021 at 15:01, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
The warning is from Odoo, not from linters, so #noqa is not valid.

El vie., 21 may. 2021 14:52, Graeme Gellatly <gdgellatly@gmail.com> escribió:
I think if the use case is valid and no convenient good alternative exists then the easiest solution is

# noqa

with a note.

On Sat, May 22, 2021 at 12:16 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:
how about api.onchange ?
it would work on form modification.

On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:
Hi all,
I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:
Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.

The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?

I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.
Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.
I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.

This said, what is a valid alternative to the size=X attribute?

Thanks,
Simone Rubino

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

--
Dominique KON-SUN-TACK  [Project Manager]
Elico Solutions (Singapore/Shanghai/Shenzhen)
Odoo Gold Partner, best Odoo Partner 2014 for APAC

Mobile: + 65 8502 2399
Skype: dominique_elico
Email: dominique.k@elico-corp.com.sg
Website: www.elico-corp.com

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

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

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

by Simone Rubino - 05:26 - 14 Jun 2021

Re: Migration to Odoo 14: replacing size attribute of Char field

The warning is from Odoo, not from linters, so #noqa is not valid.

El vie., 21 may. 2021 14:52, Graeme Gellatly <gdgellatly@gmail.com> escribió:
I think if the use case is valid and no convenient good alternative exists then the easiest solution is

# noqa

with a note.

On Sat, May 22, 2021 at 12:16 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:
how about api.onchange ?
it would work on form modification.

On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:
Hi all,
I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:
Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.

The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?

I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.
Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.
I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.

This said, what is a valid alternative to the size=X attribute?

Thanks,
Simone Rubino

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

--
Dominique KON-SUN-TACK  [Project Manager]
Elico Solutions (Singapore/Shanghai/Shenzhen)
Odoo Gold Partner, best Odoo Partner 2014 for APAC

Mobile: + 65 8502 2399
Skype: dominique_elico
Email: dominique.k@elico-corp.com.sg
Website: www.elico-corp.com

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

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

by Pedro M. Baeza - 03:00 - 21 May 2021

Re: Migration to Odoo 14: replacing size attribute of Char field

I think if the use case is valid and no convenient good alternative exists then the easiest solution is

# noqa

with a note.

On Sat, May 22, 2021 at 12:16 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:
how about api.onchange ?
it would work on form modification.

On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:
Hi all,
I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:
Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.

The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?

I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.
Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.
I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.

This said, what is a valid alternative to the size=X attribute?

Thanks,
Simone Rubino

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

--
Dominique KON-SUN-TACK  [Project Manager]
Elico Solutions (Singapore/Shanghai/Shenzhen)
Odoo Gold Partner, best Odoo Partner 2014 for APAC

Mobile: + 65 8502 2399
Skype: dominique_elico
Email: dominique.k@elico-corp.com.sg
Website: www.elico-corp.com

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

by Graeme Gellatly - 02:51 - 21 May 2021

Re: Migration to Odoo 14: replacing size attribute of Char field

how about api.onchange ?
it would work on form modification.

On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:
Hi all,
I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:
Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.

The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?

I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.
Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.
I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.

This said, what is a valid alternative to the size=X attribute?

Thanks,
Simone Rubino

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

--
Dominique KON-SUN-TACK  [Project Manager]
Elico Solutions (Singapore/Shanghai/Shenzhen)
Odoo Gold Partner, best Odoo Partner 2014 for APAC

Mobile: + 65 8502 2399
Skype: dominique_elico
Email: dominique.k@elico-corp.com.sg
Website: www.elico-corp.com

by dominique.k - 02:11 - 21 May 2021

Re: Migration to Odoo 14: replacing size attribute of Char field

If I don't remember bad, there's a warning logged saying the size is deprecated, and that's why it's included in the migration guide.

I think the alternative is to put it on the view, not on the field.

Regards.

by Pedro M. Baeza - 01:01 - 21 May 2021

Stock valuation by location drilldown

Hello,

I might be stupid not to see how todo that but let me ask. We have locations design in a hierarchical way (as I guess is designed). So for example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this hierarchy (shelfs). Is there a simple way to do stock valuation by some sort of drilldown? Or at least to get stock value of top location including all its children recursively? The need stems from the requirement to compare this calculation to other Inventory software which is to be replaced by Odoo. But first we have to be sure the calculations match.

Thank you. Best regards

	Radovan Skolnik

by Radovan Skolnik - 11:51 - 19 May 2021

6 replies 6 replies

Re: Stock valuation by location drilldown

Aaron,

YES! Not exactly but very close. It reports on product quantity while I need 
value but it is easy to modify. Also uses that magic child_of for searching in 
read_group which I wanted to ask about (had it in my email but deleted it).

Thank you very much! Best regards

	Radovan

On streda 19. mája 2021 14:22:07 CEST Aarón Henríquez Quintana wrote:

> I think this is what you are looking for, isn't it? 

> https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_qua

> ntity_by_location [1] On Wed, 19 May 2021 at 14:07, Radovan Skolnik <

> radovan@skolnik.info [2] > wrote: I guess I understand but: as I described

> in my initial post I need to be able to make the sum of stock.quant values

> recursively. Let's say a single location represents a warehouse or store

> room (first level location), with racks (second level location) and shelfs

> (third level location). Now I need to be able to see value of that top

> level location which should incorporate value of all of its children and

> their children... Hope I am making myself clear.

> Best regards

> Radovan

> 

> On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote:

> > If your context has a warehouse, or a location_id, then all the figures

> > that are computed on product will be contextually constrained based on

> > that context. Exactly what compute figures are available on

> > product.product varies from version to version, but the context should

> > already be enough to achieve what you need.

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > * Richard deMeester *

> > 

> > Senior Development Analyst

> > 

> > * WilldooIT Pty Ltd ** *

> > * E: *  None [1]  richard.demeester@willdooit.com [3]

> > * M: *  +61 403 76 76 76

> > * P: *  +61 3 9135 1900

> > * A: *  10/435 Williamstown Road, Port Melbourne, Vic 3207

> > 

> > 

> > 

> > 

> > 

> > 

> > Making growth through technology easy *

> > 

> > 

> > 

> > *  *

> > * DISCLAIMER *  | This electronic message together with any attachments is

> > confidential. If you are not the recipient, do not copy, disclose, or use

> > the contents in any way. Please also advise us by e-mail that you have

> > received this message in error and then please destroy this email and any

> > of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes

> > made to this message and/or any attachments after sending by WilldooIT

> > Pty.

> > Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all

> > liability for virus or anything similar in this email or attachment.

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > *From:* Radovan Skolnik < radovan@skolnik.info [4] >

> > *Sent:* Wednesday, 19 May 2021 9:47 PM

> > *To:* Contributors < contributors@odoo-community.org [5] >

> > *Subject:* Re: Stock valuation by location drilldown

> > 

> > This idea came to mind (please comment on its viability): in stock_account

> > there is computed field value of stock.quant that calculates the value.

> > stock.location has quant_ids. So it should be easily possible to create a

> > computed field for stock.location that would make sum of its stock.quants

> > as well as its child stock.locations. I guess there could be some magic

> > that would allow to prevent recursive call to sum of stock.location

> > children. Any pointers on how to do that?

> > Thank you. Best regards

> > Radovan Skolnik

> > 

> > On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote:

> > > Hello,

> > > I might be stupid not to see how todo that but let me ask. We have

> > > locations design in a hierarchical way (as I guess is designed). So for

> > > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts

> > > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this

> > > hierarchy (shelfs). Is there a simple way to do stock valuation by some

> > > sort of drilldown? Or at least to get stock value of top location

> > > including all its children recursively? The need stems from the

> > > requirement to compare this calculation to other Inventory software

> > > which

> > > is to be replaced by Odoo. But first we have to be sure the calculations

> > > match. Thank you. Best regards

> > > Radovan Skolnik

> > > 

> > > 

> > > _______________________________________________

> > > Mailing-List:  https://odoo-community.org/groups/contributors-15 [6] [1]

> > > Post to: mailto: contributors@odoo-community.org [7]

> > > Unsubscribe:  https://odoo-community.org/groups?unsubscribe [8] [2]

> > > 

> > > 

> > > 

> > > [1]  https://odoo-community.org/groups/contributors-15 [9]

> > > [2]  https://odoo-community.org/groups?unsubscribe [10]

> > 

> > _______________________________________________

> > 

> > Mailing-List:

> >  https://odoo-community.org/groups/contributors-15 [11] [2]

> > 

> > Post to: mailto: contributors@odoo-community.org [12]

> > 

> > Unsubscribe:

> >  https://odoo-community.org/groups?unsubscribe [13] [3]

> > 

> > _______________________________________________

> > Mailing-List:  https://odoo-community.org/groups/contributors-15 [14] [4]

> > Post to: mailto: contributors@odoo-community.org [15]

> > Unsubscribe:  https://odoo-community.org/groups?unsubscribe [16] [5]

> > 

> > 

> > 

> > [1] mailto: geoff.szentesi@willdooit.com [17]

> > [2]  https://odoo-community.org/groups/contributors-15 [18]

> > [3]  https://odoo-community.org/groups?unsubscribe [19]

> > [4]  https://odoo-community.org/groups/contributors-15 [20]

> > [5]  https://odoo-community.org/groups?unsubscribe [21]

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [22]

> Post to: mailto: contributors@odoo-community.org [23]

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [24]

> 

> --

> Aaron Henríquez Quintana * Technical Consultant  ahenriquez@forgeflow.com

> [25]  Twitter:  /AaronHForgeFlow   |  Linkedin: /

> aaron-henriquez-quintana-84299869 None [26]

> None [27]    None [28]    None [29]    None [30]

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [31]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [32]

> 

> 

> 

> [1]

> https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_qua

> ntity_by_location [2] mailto:radovan@skolnik.info

> [3] mailto:richard.demeester@willdooit.com

> [4] mailto:radovan@skolnik.info

> [5] mailto:contributors@odoo-community.org

> [6] https://odoo-community.org/groups/contributors-15

> [7] mailto:contributors@odoo-community.org

> [8] https://odoo-community.org/groups?unsubscribe

> [9] https://odoo-community.org/groups/contributors-15

> [10] https://odoo-community.org/groups?unsubscribe

> [11] https://odoo-community.org/groups/contributors-15

> [12] mailto:contributors@odoo-community.org

> [13] https://odoo-community.org/groups?unsubscribe

> [14] https://odoo-community.org/groups/contributors-15

> [15] mailto:contributors@odoo-community.org

> [16] https://odoo-community.org/groups?unsubscribe

> [17] mailto:geoff.szentesi@willdooit.com

> [18] https://odoo-community.org/groups/contributors-15

> [19] https://odoo-community.org/groups?unsubscribe

> [20] https://odoo-community.org/groups/contributors-15

> [21] https://odoo-community.org/groups?unsubscribe

> [22] https://odoo-community.org/groups/contributors-15

> [23] mailto:contributors@odoo-community.org

> [24] https://odoo-community.org/groups?unsubscribe

> [25] mailto:judit.valls@forgeflow.com

> [26] https://www.forgeflow.com/

> [27] https://github.com/ForgeFlow

> [28] https://www.linkedin.com/company/2415389

> [29] https://www.youtube.com/channel/UC6tv8_do-x2jg2nDx4H_DnA

> [30] https://twitter.com/ForgeFlow

> [31] https://odoo-community.org/groups/contributors-15

> [32] https://odoo-community.org/groups?unsubscribe

by Radovan Skolnik - 02:36 - 19 May 2021

Re: Stock valuation by location drilldown

I think this is what you are looking for, isn't it? https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_quantity_by_location

On Wed, 19 May 2021 at 14:07, Radovan Skolnik <radovan@skolnik.info> wrote:

I guess I understand but: as I described in my initial post I need to be able 
to make the sum of stock.quant values recursively. Let's say a single location 
represents a warehouse or store room (first level location), with racks (second 
level location) and shelfs (third level location). Now I need to be able to 
see value of that top level location which should incorporate value of all of 
its children and their children... Hope I am making myself clear.

Best regards

	Radovan

On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote:


> If your context has a warehouse, or a location_id, then all the figures that


> are computed on product will be contextually constrained based on that


> context.  Exactly what compute figures are available on product.product


> varies from version to version, but the context should already be enough to


> achieve what you need.


> 


> 


> 


> 


> 


> 


> 


> 


> 


> 


> 


> 


> * Richard deMeester *


> 


> Senior Development Analyst


> 


> * WilldooIT Pty Ltd ** *


> * E: *   None [1] richard.demeester@willdooit.com


> * M: *   +61 403 76 76 76


> * P: *   +61 3 9135 1900


> * A: *   10/435 Williamstown Road, Port Melbourne, Vic 3207


> 


> 


> 


> 


> 


> 


> Making growth through technology easy *


> 


> 


> 


> *   *


> * DISCLAIMER *   | This electronic message together with any attachments is


> confidential. If you are not the recipient, do not copy, disclose, or use


> the contents in any way. Please also advise us by e-mail that you have


> received this message in error and then please destroy this email and any


> of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes


> made to this message and/or any attachments after sending by WilldooIT Pty.


> Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all


> liability for virus or anything similar in this email or attachment.


> 


> 


> 


> 


> 


> 


> 


> *From:* Radovan Skolnik <radovan@skolnik.info>


> *Sent:* Wednesday, 19 May 2021 9:47 PM


> *To:* Contributors <contributors@odoo-community.org>


> *Subject:* Re: Stock valuation by location drilldown


> 


> This idea came to mind (please comment on its viability): in stock_account


> there is computed field value of stock.quant that calculates the value.


> stock.location has quant_ids. So it should be easily possible to create a


> computed field for stock.location that would make sum of its stock.quants as


> well as its child stock.locations. I guess there could be some magic that


> would allow to prevent recursive call to sum of stock.location children.


> Any pointers on how to do that?


> Thank you. Best regards


> Radovan Skolnik


> 


> On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote:


> > Hello,


> > I might be stupid not to see how todo that but let me ask. We have


> > locations design in a hierarchical way (as I guess is designed). So for


> > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts


> > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this


> > hierarchy (shelfs). Is there a simple way to do stock valuation by some


> > sort of drilldown? Or at least to get stock value of top location


> > including all its children recursively? The need stems from the


> > requirement to compare this calculation to other Inventory software which


> > is to be replaced by Odoo. But first we have to be sure the calculations


> > match. Thank you. Best regards


> > Radovan Skolnik


> > 


> > 


> > _______________________________________________


> > Mailing-List: https://odoo-community.org/groups/contributors-15 [1]


> > Post to: mailto:contributors@odoo-community.org


> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]


> > 


> > 


> > 


> > [1] https://odoo-community.org/groups/contributors-15


> > [2] https://odoo-community.org/groups?unsubscribe


> 


> _______________________________________________


> Mailing-List:


> https://odoo-community.org/groups/contributors-15 [2]


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe:


> https://odoo-community.org/groups?unsubscribe [3]


> 


> 


> 


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15 [4]


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe [5]


> 


> 


> 


> [1] mailto:geoff.szentesi@willdooit.com


> [2] https://odoo-community.org/groups/contributors-15


> [3] https://odoo-community.org/groups?unsubscribe


> [4] https://odoo-community.org/groups/contributors-15


> [5] https://odoo-community.org/groups?unsubscribe

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

Aaron Henríquez Quintana

Technical Consultant

ahenriquez@forgeflow.com

Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869

by Aarón Henríquez - 02:21 - 19 May 2021

Re: Stock valuation by location drilldown

I guess I understand but: as I described in my initial post I need to be able 
to make the sum of stock.quant values recursively. Let's say a single location 
represents a warehouse or store room (first level location), with racks (second 
level location) and shelfs (third level location). Now I need to be able to 
see value of that top level location which should incorporate value of all of 
its children and their children... Hope I am making myself clear.

Best regards

	Radovan

On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote:

> If your context has a warehouse, or a location_id, then all the figures that

> are computed on product will be contextually constrained based on that

> context.  Exactly what compute figures are available on product.product

> varies from version to version, but the context should already be enough to

> achieve what you need.

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> * Richard deMeester *

> 

> Senior Development Analyst

> 

> * WilldooIT Pty Ltd ** *

> * E: *   None [1] richard.demeester@willdooit.com

> * M: *   +61 403 76 76 76

> * P: *   +61 3 9135 1900

> * A: *   10/435 Williamstown Road, Port Melbourne, Vic 3207

> 

> 

> 

> 

> 

> 

> Making growth through technology easy *

> 

> 

> 

> *   *

> * DISCLAIMER *   | This electronic message together with any attachments is

> confidential. If you are not the recipient, do not copy, disclose, or use

> the contents in any way. Please also advise us by e-mail that you have

> received this message in error and then please destroy this email and any

> of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes

> made to this message and/or any attachments after sending by WilldooIT Pty.

> Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all

> liability for virus or anything similar in this email or attachment.

> 

> 

> 

> 

> 

> 

> 

> *From:* Radovan Skolnik <radovan@skolnik.info>

> *Sent:* Wednesday, 19 May 2021 9:47 PM

> *To:* Contributors <contributors@odoo-community.org>

> *Subject:* Re: Stock valuation by location drilldown

> 

> This idea came to mind (please comment on its viability): in stock_account

> there is computed field value of stock.quant that calculates the value.

> stock.location has quant_ids. So it should be easily possible to create a

> computed field for stock.location that would make sum of its stock.quants as

> well as its child stock.locations. I guess there could be some magic that

> would allow to prevent recursive call to sum of stock.location children.

> Any pointers on how to do that?

> Thank you. Best regards

> Radovan Skolnik

> 

> On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote:

> > Hello,

> > I might be stupid not to see how todo that but let me ask. We have

> > locations design in a hierarchical way (as I guess is designed). So for

> > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts

> > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this

> > hierarchy (shelfs). Is there a simple way to do stock valuation by some

> > sort of drilldown? Or at least to get stock value of top location

> > including all its children recursively? The need stems from the

> > requirement to compare this calculation to other Inventory software which

> > is to be replaced by Odoo. But first we have to be sure the calculations

> > match. Thank you. Best regards

> > Radovan Skolnik

> > 

> > 

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

> > 

> > 

> > 

> > [1] https://odoo-community.org/groups/contributors-15

> > [2] https://odoo-community.org/groups?unsubscribe

> 

> _______________________________________________

> Mailing-List:

> https://odoo-community.org/groups/contributors-15 [2]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe:

> https://odoo-community.org/groups?unsubscribe [3]

> 

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [4]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [5]

> 

> 

> 

> [1] mailto:geoff.szentesi@willdooit.com

> [2] https://odoo-community.org/groups/contributors-15

> [3] https://odoo-community.org/groups?unsubscribe

> [4] https://odoo-community.org/groups/contributors-15

> [5] https://odoo-community.org/groups?unsubscribe

by Radovan Skolnik - 02:05 - 19 May 2021

Re: Stock valuation by location drilldown

If your context has a warehouse, or a location_id, then all the figures that are computed on product will be contextually constrained based on that context. Exactly what compute figures are available on product.product varies from version to version, but the context should already be enough to achieve what you need.

Richard deMeester

Senior Development Analyst

WilldooIT Pty Ltd

E: richard.demeester@willdooit.com

M: +61 403 76 76 76

P: +61 3 9135 1900

A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

Making growth through technology easy

DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.

From: Radovan Skolnik <radovan@skolnik.info>
Sent: Wednesday, 19 May 2021 9:47 PM
To: Contributors <contributors@odoo-community.org>
Subject: Re: Stock valuation by location drilldown

This idea came to mind (please comment on its viability): in stock_account 
there is computed field value of stock.quant that calculates the value. 
stock.location has quant_ids. So it should be easily possible to create a 
computed field for stock.location that would make sum of its stock.quants as 
well as its child stock.locations. I guess there could be some magic that 
would allow to prevent recursive call to sum of stock.location children. Any 
pointers on how to do that? 

Thank you. Best regards

	Radovan Skolnik

On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote:

> Hello,

> I might be stupid not to see how todo that but let me ask. We have locations

> design in a hierarchical way (as I guess is designed). So for example we

> have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts / RowNo /

> ShelfNo. Now the stock resides at the leaf nodes in this hierarchy

> (shelfs). Is there a simple way to do stock valuation by some sort of

> drilldown? Or at least to get stock value of top location including all its

> children recursively? The need stems from the requirement to compare this

> calculation to other Inventory software which is to be replaced by Odoo.

> But first we have to be sure the calculations match. Thank you. Best

> regards

> Radovan Skolnik

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

> 

> 

> 

> [1] https://odoo-community.org/groups/contributors-15

> [2] https://odoo-community.org/groups?unsubscribe

by "Richard deMeester" <richard.demeester@willdooit.com> - 01:51 - 19 May 2021

2 attachments 2 attachments

Re: Stock valuation by location drilldown

This idea came to mind (please comment on its viability): in stock_account 
there is computed field value of stock.quant that calculates the value. 
stock.location has quant_ids. So it should be easily possible to create a 
computed field for stock.location that would make sum of its stock.quants as 
well as its child stock.locations. I guess there could be some magic that 
would allow to prevent recursive call to sum of stock.location children. Any 
pointers on how to do that? 

Thank you. Best regards

	Radovan Skolnik

On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote:

> Hello,

> I might be stupid not to see how todo that but let me ask. We have locations

> design in a hierarchical way (as I guess is designed). So for example we

> have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts / RowNo /

> ShelfNo. Now the stock resides at the leaf nodes in this hierarchy

> (shelfs). Is there a simple way to do stock valuation by some sort of

> drilldown? Or at least to get stock value of top location including all its

> children recursively? The need stems from the requirement to compare this

> calculation to other Inventory software which is to be replaced by Odoo.

> But first we have to be sure the calculations match. Thank you. Best

> regards

> Radovan Skolnik

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

> 

> 

> 

> [1] https://odoo-community.org/groups/contributors-15

> [2] https://odoo-community.org/groups?unsubscribe

by Radovan Skolnik - 01:46 - 19 May 2021

Accounting PSC Member apply

Hi Community,

I would like to apply for PSC member on Accounting repositories.

Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

You can have a look at my profile https://github.com/HaraldPanten

THX!

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

by Harald Panten Lopez - 10:16 - 19 May 2021
6 replies 6 replies
Re: Accounting PSC Member apply

Hi,

I've added you to the PSC. you should get an invitation soon.

Cheers

On Wed, May 19, 2021 at 10:17 AM Harald Panten Lopez <harald.panten@sygel.es> wrote:
Hi Community,

I would like to apply for PSC member on Accounting repositories.

Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

You can have a look at my profile https://github.com/HaraldPanten

THX!

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi. - 09:36 - 20 May 2021

Re: Accounting PSC Member apply

+1

Il gio 20 mag 2021, 19:12 Enric Tobella <etobella@creublanca.es> ha scritto:
+1

On 20 May 2021 18:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
+1

On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:
Hi Community,

I would like to apply for PSC member on Accounting repositories.

Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

You can have a look at my profile https://github.com/HaraldPanten

THX!

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

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

Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.

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

by Sergio Corato - 07:21 - 20 May 2021

Re: Accounting PSC Member apply

+1

On 20 May 2021 18:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
+1

On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:
Hi Community,

I would like to apply for PSC member on Accounting repositories.

Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

You can have a look at my profile https://github.com/HaraldPanten

THX!

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

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

Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.

by Enric Tobella Alomar - 07:10 - 20 May 2021

Re: Accounting PSC Member apply

+1

On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:
Hi Community,

I would like to apply for PSC member on Accounting repositories.

Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

You can have a look at my profile https://github.com/HaraldPanten

THX!

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

by Kitti Upariphutthiphong - 06:26 - 20 May 2021

Re: Accounting PSC Member apply

OK for me.

by Pedro M. Baeza - 06:20 - 20 May 2021
Project consumable (v14.0)

Hi there,

I've the need to follow the analytic cost of consumables per project.

As far when consumables are purchase we don't know how they will be used and while creating the quotation we don't know how exactly how many consumable to be sale, I'll create a new module probably called project_consumable in oca/project repo that will let users to record used consumable that will create relevant analytic account line linked to the consumable product and project (likes hr_timesheet which record time per project/task). I'll take care we get proper analysis.

I plan later to generate sale order (I know this is not very suitable. Add products in the generated invoice would make more sense in odoo... could be done in different modules anyway ) from some of those account move lines.

Are there already such efforts? I'll be happy to hear your comments :)

regards,

--
Pierre Verkest
06 81 12 25 20
Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

by Pierre Verkest - 10:01 - 19 May 2021
3 replies 3 replies
Re: Project consumable (v14.0)

Ok then if it's very different. I don't see the conversion to account.analytic.line. For me that should be the final result (project.task.material generates account.analytic.line when an analytic account is generated). Also to force consumable instead allowing stockable/consumable is something I don't see.

Regards.

by Pedro M. Baeza - 10:46 - 19 May 2021

Re: Project consumable (v14.0)

I've seen that module and this is why I've chosen to not use it:

* I'm not sure it's the same purpose
* I do not require to enforce consumable to be linked to a specific task only to the project
* I'm not sure we need an extra model (`project.task.material`)
for my needs and I'm a bit afraid about keep consistency between such model
and `account.analytic.line`. Or do you agree that I move `project.task.material` to
use `account.analytic.line` instead ?
If so I can change the behaviour and provide a migration script to smoothly go ahead.

Let me know what you think !

Le mer. 19 mai 2021 à 10:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
I would go with using and expanding if needed project_task_material.

Regards.

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

--
Pierre

by Pierre Verkest - 10:41 - 19 May 2021

Re: Project consumable (v14.0)

I would go with using and expanding if needed project_task_material.

Regards.

by Pedro M. Baeza - 10:26 - 19 May 2021
Manufacturing Order reporting

Hi all,
is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?
If not, which OCA repository could I do a PR?
Thanks

Sergio Corato

by Sergio Corato - 12:31 - 14 May 2021
4 replies 4 replies
Re: Manufacturing Order reporting

Hi David,
The need is for a specific report of a single product manufactured (it has a relevant value), but I'll keep that in mind, thanks!
Sergio Corato

Il giorno lun 17 mag 2021 alle ore 08:57 David Beal <david.beal@akretion.com> ha scritto:
Hi Sergio,

A really partial response here I think, but not finished.
Maybe for inspiration ?

https://github.com/OCA/manufacture/pull/427/files

"pivot table from product which make appears disparity between theoretical component consumption and real component consumption"

Regards

David BEAL
Akretion

Le ven. 14 mai 2021 à 15:42, Sergio Corato <sergiocorato@gmail.com> a écrit :
Hi Harald,
thanks!
Sergio Corato

Il giorno ven 14 mag 2021 alle ore 12:52 Harald Panten Lopez <harald.panten@sygel.es> ha scritto:
I don't remeber any report with such kind of details.

I think that your PR should be in https://github.com/OCA/manufacture-reporting

El vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:
Hi all,
is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?
If not, which OCA repository could I do a PR?
Thanks

Sergio Corato

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

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

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

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

by Sergio Corato - 10:00 - 17 May 2021

Re: Manufacturing Order reporting

Hi Sergio,

A really partial response here I think, but not finished.
Maybe for inspiration ?

https://github.com/OCA/manufacture/pull/427/files

"pivot table from product which make appears disparity between theoretical component consumption and real component consumption"

Regards

David BEAL
Akretion

Le ven. 14 mai 2021 à 15:42, Sergio Corato <sergiocorato@gmail.com> a écrit :
Hi Harald,
thanks!
Sergio Corato

Il giorno ven 14 mag 2021 alle ore 12:52 Harald Panten Lopez <harald.panten@sygel.es> ha scritto:
I don't remeber any report with such kind of details.

I think that your PR should be in https://github.com/OCA/manufacture-reporting

El vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:
Hi all,
is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?
If not, which OCA repository could I do a PR?
Thanks

Sergio Corato

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

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

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

by David BEAL - 08:55 - 17 May 2021

Re: Manufacturing Order reporting

Hi Harald,
thanks!
Sergio Corato

Il giorno ven 14 mag 2021 alle ore 12:52 Harald Panten Lopez <harald.panten@sygel.es> ha scritto:
I don't remeber any report with such kind of details.

I think that your PR should be in https://github.com/OCA/manufacture-reporting

El vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:
Hi all,
is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?
If not, which OCA repository could I do a PR?
Thanks

Sergio Corato

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

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

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

by Sergio Corato - 03:40 - 14 May 2021

Re: Manufacturing Order reporting

I don't remeber any report with such kind of details.

I think that your PR should be in https://github.com/OCA/manufacture-reporting

El vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:
Hi all,
is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?
If not, which OCA repository could I do a PR?
Thanks

Sergio Corato

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

--

Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41
harald.panten@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

by Harald Panten Lopez - 12:50 - 14 May 2021

Account financial reserve naming

Hi all,

We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.

We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.

These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).

If we can have a little feedback from some of you on our future baby name.

Regards,

__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

by Denis Roussel. - 06:35 - 10 May 2021

24 replies 24 replies

Re: Account financial reserve naming

Hello,

A little late response, but by chance I'm working on approximately this
here: <https://github.com/coopiteasy/addons/pull/222>

We're considering to propose it to the OCA.

Le mercredi 06 avril 2022 à 09:21 +0000, Silverstar J a écrit :

> Hello All,

> 

> I am looking for an account wallet module something like this

> https://apps.odoo.com/apps/modules/13.0/odoo_website_wallet/. 

> Using account_wallet by acsone can we achieve something which a paid

> module provides.

> 

> Can you please suggest something.

> 

> 

> 

> On Mon, May 17, 2021 at 1:47 PM Roussel, Denis

> <denis.roussel@acsone.eu> wrote:

> > Oooops, link : https://github.com/OCA/sale-workflow/pull/1583/files

> > 

> > 

> > 

> > On Mon, May 17, 2021 at 10:11 AM Roussel, Denis

> > <denis.roussel@acsone.eu> wrote:

> > > That's not exactly the same purpose (we use both in our project).

> > > 

> > > I think for v14, we can base our thinking on the new voucher

> > > module in that flow (I will do soon a PR with a wallet-voucher or

> > > sth similar).

> > > 

> > > A migration PR for sale_promotion_rule is currently draft there.

> > > IMHO, we need to split the coupon flow accordingly too.

> > > 

> > > On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy

> > > <raphael.reverdy@akretion.com> wrote:

> > > > Hi,

> > > > 

> > > > We addressed a similar need with (oca/sale_workflow)

> > > > sale_promotion_rule.

> > > > The "deposit" is simply a voucher. It can be splitted (partial

> > > > use in a SO), increased, and expiration can be set.

> > > > 

> > > > Ok for account-wallet , may be move sale_promotion_rule there?

> > > > 

> > > > Regards,

> > > > 

> > > > Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail)

> > > > <antoniomaria.vigliotti@gmail.com> a écrit :

> > > > >  +1 account-wallet

> > > > >  

> > > > >  Antonio M. Vigliotti 

> > > > >  Mobile (+39) 342.8740910

> > > > > 

> > > > >  

> > > > >  

> > > > > Il 12/05/21 17:11, Bruno Joliveau ha scritto:

> > > > >  

> > > > > > +1 for account-wallet

> > > > > >     

> > > > > >               Bruno Joliveau - Président

> > > > > > NUMIGI SOLUTIONS INC.

> > > > > > bruno.joliveau@numigi.com

> > > > > > (514) 317-7944

> > > > > > 

> > > > > > Longueuil, Québec, Canada

> > > > > > http://www.numigi.com/

> > > > > > 

> > > > > >        

> > > > > >         

> > > > > >  

> > > > > >  

> > > > > > Le mer. 12 mai 2021 à 11:06, Roussel, Denis

> > > > > > <denis.roussel@acsone.eu> a écrit :

> > > > > >  

> > > > > > > Hi all, 

> > > > > > > 

> > > > > > > 

> > > > > > > I'm requesting the creation of a new repository named

> > > > > > > account-wallet.

> > > > > > > 

> > > > > > > I hope this will help to fulfill people request. I will

> > > > > > > add PR's for 14 soon.

> > > > > > > 

> > > > > > > I think we can add it to accounting-maintainers PSC.

> > > > > > > 

> > > > > > > 

> > > > > > > Thanks all for the little brainstorming.

> > > > > > >  

> > > > > > > On Tue, May 11, 2021 at 2:45 PM Roussel, Denis

> > > > > > > <denis.roussel@acsone.eu> wrote:

> > > > > > >  

> > > > > > > > Yes. 

> > > > > > > > 

> > > > > > > > I think that will not conflict with future Odoo sale

> > > > > > > > gift card (but they change their mind meantime).

> > > > > > > > 

> > > > > > > > Maybe account-wallet (for repo)? 

> > > > > > > >  

> > > > > > > > Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul

> > > > > > > > <stephane.bidoul@acsone.eu> a écrit :

> > > > > > > >  

> > > > > > > > > wallet is an interesting name too.

> > > > > > > > > 

> > > > > > > > > I guess it's best to create a new repo, since this is

> > > > > > > > > a suite of modules covering several areas ?

> > > > > > > > > 

> > > > > > > > > -sbi

> > > > > > > > >  

> > > > > > > > > On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti

> > > > > > > > > (gmail) <antoniomaria.vigliotti@gmail.com> wrote:

> > > > > > > > >  

> > > > > > > > > >  May be intresting for other countries, if I

> > > > > > > > > > understand the request.

> > > > > > > > > >  

> > > > > > > > > >  The financial reserve is a sort of payment down

> > > > > > > > > > but not specific for any order. 

> > > > > > > > > >  

> > > > > > > > > >  In Italy is called "anticipo" (like payment down

> > > > > > > > > > but it is not the same meaning) or portafoglio

> > > > > > > > > > (Italian term for "wallet"). The account should be

> > > > > > > > > > a <credit account type>.

> > > > > > > > > >  We have to develop a module with this feature, can

> > > > > > > > > > we share the thinks ena eventually the code, if you

> > > > > > > > > > agred.

> > > > > > > > > >  

> > > > > > > > > >  Antonio M. Vigliotti 

> > > > > > > > > >  Mobile (+39) 342.8740910

> > > > > > > > > > 

> > > > > > > > > >  

> > > > > > > > > >  

> > > > > > > > > > Il 11/05/21 13:37, Roussel, Denis ha scritto:

> > > > > > > > > >  

> > > > > > > > > > > I like it.

> > > > > > > > > > > 

> > > > > > > > > > > One thing more is the fact that that fund can be

> > > > > > > > > > > partner agnostic. As it can represent a 'gift

> > > > > > > > > > > voucher' which has a certain balance

> > > > > > > > > > > corresponding to the voucher value (if not used

> > > > > > > > > > > yet).

> > > > > > > > > > > 

> > > > > > > > > > > Apart of that consideration, is it a good idea to

> > > > > > > > > > > create a repo for those modules or to go in an

> > > > > > > > > > > existing one ?

> > > > > > > > > > >  

> > > > > > > > > > > On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul

> > > > > > > > > > > <stephane.bidoul@acsone.eu> wrote:

> > > > > > > > > > >  

> > > > > > > > > > > > Hi,

> > > > > > > > > > > > 

> > > > > > > > > > > > Maybe a good name would be account_partner_fund

> > > > > > > > > > > > ?

> > > > > > > > > > > > 

> > > > > > > > > > > > In a nutshell, we have the following concepts

> > > > > > > > > > > > in these modules (as I understand it after a

> > > > > > > > > > > > quick reminder from Cedric, errors and

> > > > > > > > > > > > imprecisions are mine, but the general idea

> > > > > > > > > > > > should be this):

> > > > > > > > > > > > 

> > > > > > > > > > > > - funds (cagnottes) are created

> > > > > > > > > > > > - a balance sheet account is used to track the

> > > > > > > > > > > > funds, with all journal items in this account

> > > > > > > > > > > > having a m2o to the corresponding fund +

> > > > > > > > > > > > partner_id

> > > > > > > > > > > > - funds can be credited with balance sheet

> > > > > > > > > > > > movements (bank to fund, no VAT impact)

> > > > > > > > > > > > - funds can be used as payment means

> > > > > > > > > > > > - when funds expire, there is a debit fund /

> > > > > > > > > > > > credit revenue, and at that moment some VAT is

> > > > > > > > > > > > due

> > > > > > > > > > > > 

> > > > > > > > > > > > Best regards,

> > > > > > > > > > > >  

> > > > > > > > > > > > --

> > > > > > > > > > > > Stéphane Bidoul | @SBidoul

> > > > > > > > > > > >  Acsone sa/nv | http://acsone.eu/ | +32 2 888

> > > > > > > > > > > > 3120

> > > > > > > > > > > >  

> > > > > > > > > > > > On Mon, May 10, 2021 at 6:37 PM Roussel, Denis

> > > > > > > > > > > > <denis.roussel@acsone.eu> wrote:

> > > > > > > > > > > >  

> > > > > > > > > > > > > Hi all, 

> > > > > > > > > > > > > 

> > > > > > > > > > > > > 

> > > > > > > > > > > > > We want to put some modules we did to OCA,

> > > > > > > > > > > > > but before we want to validate naming with

> > > > > > > > > > > > > some native english speakers as some

> > > > > > > > > > > > > translations are ambiguous.

> > > > > > > > > > > > > 

> > > > > > > > > > > > > We want to modelize a financial reserve (we

> > > > > > > > > > > > > named it in French 'cagnotte' - that is

> > > > > > > > > > > > > translated at first sight jackpot or pot(the

> > > > > > > > > > > > > ambiguous one :-) ) through account moves

> > > > > > > > > > > > > that feed a waiting account. 

> > > > > > > > > > > > > 

> > > > > > > > > > > > > These entries should allow to pay invoices

> > > > > > > > > > > > > later (we know the 'wallet' in development on

> > > > > > > > > > > > > Odoo side but this is quite different as

> > > > > > > > > > > > > based on accounting entries).

> > > > > > > > > > > > > 

> > > > > > > > > > > > > If we can have a little feedback from some of

> > > > > > > > > > > > > you on our future baby name.

> > > > > > > > > > > > > 

> > > > > > > > > > > > > 

> > > > > > > > > > > > > Regards,

> > > > > > > > > > > > > 

> > > > > > > > > > > > >  -- 

> > > > > > > > > > > > > __________________________________________

> > > > > > > > > > > > >  Denis Roussel

> > > > > > > > > > > > > Software Engineer

> > > > > > > > > > > > > Acsone SA, Succursale de Liège (Val Benoît)

> > > > > > > > > > > > > Tel    : +32 2 888 31 49

> > > > > > > > > > > > >  Fax   : +32 2 888 31 59

> > > > > > > > > > > > >  Gsm : +32 472 22 00 57 

> > > > > > > > > > > > >  Acsone sa/nv

> > > > > > > > > > > > >  Boulevard de la Woluwe 56 Woluwedal | B-1200

> > > > > > > > > > > > > Brussels  | Belgium

> > > > > > > > > > > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège |

> > > > > > > > > > > > > Belgium

> > > > > > > > > > > > >  Zone Industrielle 22 | L-8287 Kehlen |

> > > > > > > > > > > > > Luxembourg

> > > > > > > > > > > > > www.acsone.eu

> > > > > > > > > > > > >  

> > > > > > > > > > > > > _____________________________________________

> > > > > > > > > > > > > __

> > > > > > > > > > > > >  Mailing-List:

> > > > > > > > > > > > > https://odoo-community.org/groups/contributors-15

> > > > > > > > > > > > >  Post to:

> > > > > > > > > > > > > mailto:contributors@odoo-community.org

> > > > > > > > > > > > >  Unsubscribe:

> > > > > > > > > > > > > https://odoo-community.org/groups?unsubscribe

> > > > > > > > > > > > _______________________________________________

> > > > > > > > > > > >  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 Liège (Val Benoît)

> > > > > > > > > > > Tel    : +32 2 888 31 49

> > > > > > > > > > >  Fax   : +32 2 888 31 59

> > > > > > > > > > >  Gsm : +32 472 22 00 57 

> > > > > > > > > > >  Acsone sa/nv

> > > > > > > > > > >  Boulevard de la Woluwe 56 Woluwedal | B-1200

> > > > > > > > > > > Brussels  | Belgium

> > > > > > > > > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège |

> > > > > > > > > > > Belgium

> > > > > > > > > > >  Zone Industrielle 22 | L-8287 Kehlen |

> > > > > > > > > > > Luxembourg

> > > > > > > > > > > www.acsone.eu

> > > > > > > > > > >  

> > > > > > > > > > > _______________________________________________

> > > > > > > > > > >  Mailing-List:

> > > > > > > > > > > https://odoo-community.org/groups/contributors-15

> > > > > > > > > > >  Post to: mailto:contributors@odoo-community.org

> > > > > > > > > > >  Unsubscribe:

> > > > > > > > > > > https://odoo-community.org/groups?unsubscribe

> > > > > > > > > >  

> > > > > > > > > > _______________________________________________

> > > > > > > > > >  Mailing-List:

> > > > > > > > > > https://odoo-community.org/groups/contributors-15

> > > > > > > > > >  Post to: mailto:contributors@odoo-community.org

> > > > > > > > > >  Unsubscribe:

> > > > > > > > > > https://odoo-community.org/groups?unsubscribe

> > > > > > > > > _______________________________________________

> > > > > > > > >  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 Liège (Val Benoît)

> > > > > > > Tel    : +32 2 888 31 49

> > > > > > >  Fax   : +32 2 888 31 59

> > > > > > >  Gsm : +32 472 22 00 57 

> > > > > > >  Acsone sa/nv

> > > > > > >  Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels 

> > > > > > > | Belgium

> > > > > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium

> > > > > > >  Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

> > > > > > > www.acsone.eu

> > > > > > >  

> > > > > > > _______________________________________________

> > > > > > >  Mailing-List:

> > > > > > > https://odoo-community.org/groups/contributors-15

> > > > > > >  Post to: mailto:contributors@odoo-community.org

> > > > > > >  Unsubscribe:

> > > > > > > https://odoo-community.org/groups?unsubscribe

> > > > > > _______________________________________________

> > > > > >  Mailing-List:

> > > > > > https://odoo-community.org/groups/contributors-15

> > > > > >  Post to: mailto:contributors@odoo-community.org

> > > > > >  Unsubscribe: https://odoo-community.org/groups?unsubscribe

> > > > >  

> > > > > _______________________________________________

> > > > >  Mailing-List:

> > > > > https://odoo-community.org/groups/contributors-15

> > > > >  Post to: mailto:contributors@odoo-community.org

> > > > >  Unsubscribe: https://odoo-community.org/groups?unsubscribe

> > > > 

> > > > 

> > > > -- 

> > > > Raphaël Reverdy

> > > > Mobile +33 6 38 02 03 93

> > > > Fixe +33 4 82 53 84 60

> > > > _______________________________________________

> > > >  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 Liège (Val Benoît)

> > > Tel    : +32 2 888 31 49

> > > Fax   : +32 2 888 31 59

> > > Gsm : +32 472 22 00 57 

> > > 

> > > Acsone sa/nv

> > > Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium

> > > Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium

> > > Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

> > > www.acsone.eu

> > > 

> > 

> >

by Carmen Bianca Bakker - 11:06 - 29 Apr 2022

Re: Account financial reserve naming

Hello All,

I am looking for an account wallet module something like this https://apps.odoo.com/apps/modules/13.0/odoo_website_wallet/.

Using account_wallet by acsone can we achieve something which a paid module provides.

Can you please suggest something.

On Mon, May 17, 2021 at 1:47 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Oooops, link : https://github.com/OCA/sale-workflow/pull/1583/files

On Mon, May 17, 2021 at 10:11 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:
That's not exactly the same purpose (we use both in our project).

I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).

A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.

On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
Hi,

We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.
The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.

Ok for account-wallet , may be move sale_promotion_rule there?

Regards,

Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :
+1 account-wallet

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 12/05/21 17:11, Bruno Joliveau ha scritto:

+1 for account-wallet

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

I'm requesting the creation of a new repository named account-wallet.

I hope this will help to fulfill people request. I will add PR's for 14 soon.

I think we can add it to accounting-maintainers PSC.

Thanks all for the little brainstorming.

On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Yes.

I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).

Maybe account-wallet (for repo)?

Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :

wallet is an interesting name too.

I guess it's best to create a new repo, since this is a suite of modules covering several areas ?

-sbi

On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:

May be intresting for other countries, if I understand the request.

The financial reserve is a sort of payment down but not specific for any order.

In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 11/05/21 13:37, Roussel, Denis ha scritto:

I like it.

One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).

Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?

On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hi,

Maybe a good name would be account_partner_fund ?

In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):

- funds (cagnottes) are created

- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id

- funds can be credited with balance sheet movements (bank to fund, no VAT impact)

- funds can be used as payment means

- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due

Best regards,

--

Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Hi all,

We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.

We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.

These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).

If we can have a little feedback from some of you on our future baby name.

Regards,

--

__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

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

--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

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

by Silverstar - 11:21 - 6 Apr 2022

Re: Account financial reserve naming

Oooops, link : https://github.com/OCA/sale-workflow/pull/1583/files

On Mon, May 17, 2021 at 10:11 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:

That's not exactly the same purpose (we use both in our project).

I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).

A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.

On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
Hi,

We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.
The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.

Ok for account-wallet , may be move sale_promotion_rule there?

Regards,

Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :
+1 account-wallet

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 12/05/21 17:11, Bruno Joliveau ha scritto:

+1 for account-wallet

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

I'm requesting the creation of a new repository named account-wallet.

I hope this will help to fulfill people request. I will add PR's for 14 soon.

I think we can add it to accounting-maintainers PSC.

Thanks all for the little brainstorming.

On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Yes.

I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).

Maybe account-wallet (for repo)?

Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :

wallet is an interesting name too.

I guess it's best to create a new repo, since this is a suite of modules covering several areas ?

-sbi

On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:

May be intresting for other countries, if I understand the request.

The financial reserve is a sort of payment down but not specific for any order.

In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 11/05/21 13:37, Roussel, Denis ha scritto:

I like it.

One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).

Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?

On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hi,

Maybe a good name would be account_partner_fund ?

In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):

- funds (cagnottes) are created

- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id

- funds can be credited with balance sheet movements (bank to fund, no VAT impact)

- funds can be used as payment means

- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due

Best regards,

--

Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Hi all,

We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.

We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.

These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).

If we can have a little feedback from some of you on our future baby name.

Regards,

--

__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

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

--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

by Denis Roussel. - 10:16 - 17 May 2021

Re: Account financial reserve naming

That's not exactly the same purpose (we use both in our project).

I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).

A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.

On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:

Hi,

We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.
The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.

Ok for account-wallet , may be move sale_promotion_rule there?

Regards,

Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :
+1 account-wallet

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 12/05/21 17:11, Bruno Joliveau ha scritto:

+1 for account-wallet

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

I'm requesting the creation of a new repository named account-wallet.

I hope this will help to fulfill people request. I will add PR's for 14 soon.

I think we can add it to accounting-maintainers PSC.

Thanks all for the little brainstorming.

On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Yes.

I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).

Maybe account-wallet (for repo)?

Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :

wallet is an interesting name too.

I guess it's best to create a new repo, since this is a suite of modules covering several areas ?

-sbi

On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:

May be intresting for other countries, if I understand the request.

The financial reserve is a sort of payment down but not specific for any order.

In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 11/05/21 13:37, Roussel, Denis ha scritto:

I like it.

One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).

Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?

On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hi,

Maybe a good name would be account_partner_fund ?

In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):

- funds (cagnottes) are created

- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id

- funds can be credited with balance sheet movements (bank to fund, no VAT impact)

- funds can be used as payment means

- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due

Best regards,

--

Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Hi all,

We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.

We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.

These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).

If we can have a little feedback from some of you on our future baby name.

Regards,

--

__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

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

--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60

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

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

by Denis Roussel. - 10:16 - 17 May 2021

Re: Account financial reserve naming

Hi,

We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.

The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.

Ok for account-wallet , may be move sale_promotion_rule there?

Regards,

Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :

+1 account-wallet

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 12/05/21 17:11, Bruno Joliveau ha scritto:

+1 for account-wallet

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

I'm requesting the creation of a new repository named account-wallet.

I hope this will help to fulfill people request. I will add PR's for 14 soon.

I think we can add it to accounting-maintainers PSC.

Thanks all for the little brainstorming.

On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Yes.

I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).

Maybe account-wallet (for repo)?

Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :

wallet is an interesting name too.

I guess it's best to create a new repo, since this is a suite of modules covering several areas ?

-sbi

On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:

May be intresting for other countries, if I understand the request.

The financial reserve is a sort of payment down but not specific for any order.

In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 11/05/21 13:37, Roussel, Denis ha scritto:

I like it.

One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).

Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?

On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

Hi,

Maybe a good name would be account_partner_fund ?

In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):

- funds (cagnottes) are created

- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id

- funds can be credited with balance sheet movements (bank to fund, no VAT impact)

- funds can be used as payment means

- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due

Best regards,

--

Stéphane Bidoul | @SBidoul

Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Hi all,

We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.

We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.

These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).

If we can have a little feedback from some of you on our future baby name.

Regards,

--

__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

_______________________________________________
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 Liège (Val Benoît)
Tel    : +32 2 888 31 49
Fax   : +32 2 888 31 59
Gsm : +32 472 22 00 57

Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium

Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

www.acsone.eu

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

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

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

Raphaël Reverdy

Mobile +33 6 38 02 03 93

Fixe +33 4 82 53 84 60

by Raphaël Reverdy - 10:06 - 17 May 2021

Sale Order -> Payment -> Invoice

Hello,

I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.

AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.

Did I miss anything on my search?

Thank you

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

by Daniel Reis - 10:06 - 6 May 2021

5 replies 5 replies

OCA RFQ: Communication Strategy Expert - closes 12th May

Hello OCA Contributors

Just a reminder that our latest OCA RFQ closes on the 12th May.

We are looking for a Communication Strategy Expert to help define our Communication Strategy for the next 3 years.

To find out about the work schedule and deliverables please see here: https://drive.google.com/file/d/19EL646MjjpI4lN47v4P18tHMk2q_1ktR/view

If you have any questions please email: rfq@odoo-community.org

Warmest regards,
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association

by Rebecca Gellatly - 02:26 - 5 May 2021

Shipping Costs

Hello,

I found this requirement that I don't see existing features to support it.
Target version is Odoo 14.

A Sales order has a shipping costs line.
There is a shipping price charged to the customer, that is zero in most cases.
And there is an actual cost, that should depend on the delivery method we end up using.

The first gap is that the "Update Shipping Cost" button on the Sales Order updates the *price*, and not the cost.

The second gap is that, if you do set an amount on the SO line cost field, it is not carried over to the invoice.
The account_invoice_margin module solves this, but then, when posting the invoice this cost information is not used for the posting, and is not recorded in the accounting entries.

I'm ready to create a module to support this case, but I'm wondering if I am missing something here.
Am I thinking through this right?

Thanks!

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

by Daniel Reis - 05:01 - 29 Apr 2021

5 replies 5 replies

Re: Shipping Costs

to add shipping as cost in accounting, you need to have a vendor bill. a cost must have a contra in the balance sheet (e.g payable or cash)

the sales module only look at the revenue side.

On Fri, 30 Apr 2021 at 5:12 PM, Daniel Reis <dreis@opensourceintegrators.com> wrote:

This is is concerned with outgoing stock and COGS.
I could be wrong, but I think that landing costs is for incoming stock, and their stock valuation.

Correct?

On 30/04/2021 08:57, Antonio M. Vigliotti (gmail) wrote:

Did you see the landing cost module?

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

Dominique KON-SUN-TACK [Project Manager]

Elico Solutions (Singapore/Shanghai/Shenzhen)

Odoo Gold Partner, best Odoo Partner 2014 for APAC

Mobile: + 65 8502 2399

Skype: dominique_elico

Email: dominique.k@elico-corp.com.sg

Website: www.elico-corp.com

by dominique.k - 03:50 - 30 Apr 2021

Re: Shipping Costs

Yes it is correct but I think the concept should be used to evaluate actual value in documents.
We wrote an experimental module that lands costs in every line of document, so any module can use this value per it own purpose.

Give mi some time and i write an pratical example

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 30/04/21 11:12, Daniel Reis ha scritto:

This is is concerned with outgoing stock and COGS.
I could be wrong, but I think that landing costs is for incoming stock, and their stock valuation.

Correct?

On 30/04/2021 08:57, Antonio M. Vigliotti (gmail) wrote:

Did you see the landing cost module?

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Antonio M. Vigliotti - 03:36 - 30 Apr 2021

3 attachments 3 attachments

Re: Shipping Costs

This is is concerned with outgoing stock and COGS.
I could be wrong, but I think that landing costs is for incoming stock, and their stock valuation.

Correct?

On 30/04/2021 08:57, Antonio M. Vigliotti (gmail) wrote:

Did you see the landing cost module?

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

by Daniel Reis - 11:11 - 30 Apr 2021

Re: Shipping Costs

Did you see the landing cost module?

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 29/04/21 17:02, Daniel Reis ha scritto:

Hello,

I found this requirement that I don't see existing features to support it.
Target version is Odoo 14.

A Sales order has a shipping costs line.
There is a shipping price charged to the customer, that is zero in most cases.
And there is an actual cost, that should depend on the delivery method we end up using.

The first gap is that the "Update Shipping Cost" button on the Sales Order updates the *price*, and not the cost.

The second gap is that, if you do set an amount on the SO line cost field, it is not carried over to the invoice.
The account_invoice_margin module solves this, but then, when posting the invoice this cost information is not used for the posting, and is not recorded in the accounting entries.

I'm ready to create a module to support this case, but I'm wondering if I am missing something here.
Am I thinking through this right?

Thanks!

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Antonio M. Vigliotti - 09:56 - 30 Apr 2021

3 attachments 3 attachments

Re: Shipping Costs

Cost of 1. Use quantity. Would be my simple workaround.

On Fri, 30 Apr 2021, 3:02 am Daniel Reis, <dreis@opensourceintegrators.com> wrote:

Hello,

I found this requirement that I don't see existing features to support it.
Target version is Odoo 14.

A Sales order has a shipping costs line.
There is a shipping price charged to the customer, that is zero in most cases.
And there is an actual cost, that should depend on the delivery method we end up using.

The first gap is that the "Update Shipping Cost" button on the Sales Order updates the *price*, and not the cost.

The second gap is that, if you do set an amount on the SO line cost field, it is not carried over to the invoice.
The account_invoice_margin module solves this, but then, when posting the invoice this cost information is not used for the posting, and is not recorded in the accounting entries.

I'm ready to create a module to support this case, but I'm wondering if I am missing something here.
Am I thinking through this right?

Thanks!

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Graeme Gellatly - 09:06 - 29 Apr 2021

Confirm unsubscription to Contributors

Your Channel Contributors

Hello,

You have requested to be unsubscribed to the mailing list Contributors.

To confirm, please visit the following link: https://odoo-community.org/groups/unsubscribe/15/16398/2eb67cc745fb1534875df5daebaf9183.

If this was a mistake or you did not requested this action, please ignore this message.

Odoo Community Association (OCA)

info@odoo-community.org | http://odoo-community.org

by info@odoo-community.org - 09:51 - 29 Apr 2021

30 Checkout Operations per Minute A job for Odoo or not ?

Hi Folks, 

i have a project proposal on my desk that will ultimately end up in
approx. 30 checkout transactions per minute. Has anybody got a project
with that order volume done with a relatively recent version of Odoo
and provide a good reference. Please bear in mind that the project
ahead involves a similarly high volume of stock moves.

Any suggestion / comment like (but not limited to) 

Odoo is the wrong technology for that, forget it, because....

over

You can do it but, a), b), c) ....

to

If you really want that beast flying involve us over here because we
are among the few ones that already did soemthing similar

would be appreciated. 

From our load intensive projects at initOS i know that 10000 orders a
day can be handled but almost 50000 is a different story and thats why
i am asking the most experienced resource out there ;-)

Thanks in advance for your replay

Cheers Frederik

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

by Frederik Kramer. - 10:16 - 28 Apr 2021

14 replies 14 replies

Re: 30 Checkout Operations per Minute A job for Odoo or not ?

El jue, 6 may 2021 a las 5:02, Frederik Kramer (<frederik.kramer@initos.com>) escribió:

Hi Moises, 

Am Freitag, den 30.04.2021, 16:02 +0000 schrieb Moises Lopez:


> Hi Frederik


> 


> A customer requested to support 5k concurrent sale.order (1 or 2


> lines of products) in Odoo.


> The process that we followed were: test, measure, fix, test...

haha, yes thats what works well if you have a customer that well
endorses this "agile" and "pivoting" style of work. Apart from all
economic considerations this is probably also something that isolated
leads to quite solid solutions

Well, we are talking about 5k concurrent VUs in this special case.

The cost vs benefit demands this.



> 


> The first time that we tested the checkout process supported 15


> concurrent virtual users (VUs)


> The measure said that it had heavy custom functions in the same


> transaction of checkout but it could be executed in background (cron,


> queue)


> and there were slow queries because of indexes issues or too many


> queries executed because of python code

did you use any specific profiling tools here? Or the ones that rcollet
often proposes in his talks about the matter ?

Watch my talk in SFO

I used the same tools



> 


> Note: Be careful with the base_automation if you can migrate them to 


> code it is better.

Thanks for the hint, i think we experienced that also quite some times
in the past and learned that lesson already ;-)



> 


> After fix them the next iteration supported 400 VUs


> So good but so far from the focus.


> 


> The next iteration we found that there were methods that could be


> using LRU-cache (e.g. prices, website that don't change)


> Now we needed to check where the cache was clearing too frequently


> and fix it.

How did you measure LRU cache hit rates vs. code parts in a good way.
Any tooling suggestion here ?

For the case of the price in the website our reasoning was:

- The value don't change in a long time for this customer (each 6 months)

- It couldn't be a stored field in the database because it depends on:

- date

- quantity

- currency rate (if your have multi-currency)

- partner

- Supplier price (if your price depends on it)

- product category

- Adding LRU-Cache with these keys will work fine and faster

Even the website the most of request came from public user

I share you the output of the following command in production:

- kill -SIGUSR1 WORKER-PID

It shows the hit rates:

- 19715 hit 91.5% ratio for website._get_cached_values

- 3507 hit 75.8% ratio for website.get_pricelist_available_cached



> 


> We implemented CDN


> e.g. The sentence "/web/image/company.logo" runs 10 queries


> (prefetching fields, translating fields...) for each user opening the


> page


> After using CDN 0 queries are executed.

But you just used Odoos standard CDN function or any specific measure
here ?



> 


> We removed soft process that running with many users it is heavy


> e.g. the random image that odoo assign when you create a res.partner


> e.g. computed fields moved to cron

Also here which analysis tools do you prefer to do so ?



> 


> After that we detected concurrent update issues


> It is hell for performance matter.


> e.g. updating the same record at the same time from many users,


> e.g. allowing pressing the same button too many times


> e.g. sequences using no-gap in the main process, and so on


> 


> After finishing all the hints of performance issues in the code and


> database the next steps were to improve the hardware.


> 


> Now, It supports 5k concurrent VUs doing checkout process (choose 2


> products, type address, payment card info and confirm)

In what time frame ?



> 


> So, Odoo will support those users but you will need to test, measure,


> fix, test...


> Stress testing tools helps us a lot here


> python profilers and query analyzers too


> 


> Maybe you are interest to watch our talk in SFO about:


>  - https://youtu.be/kiREZqg3JQg

I will definitely have a look at this

Thanks a lot for your extensive insight.

Cheers from rainy Germany to sunny Mexico ;-)

Frederik



> 


> El mié, 28 abr 2021 a las 15:35, Frederik Kramer (<


> frederik.kramer@initos.com>) escribió:


> > Hi Folks, 


> > 


> > i have a project proposal on my desk that will ultimately end up in


> > approx. 30 checkout transactions per minute. Has anybody got a


> > project


> > with that order volume done with a relatively recent version of


> > Odoo


> > and provide a good reference. Please bear in mind that the project


> > ahead involves a similarly high volume of stock moves.


> > 


> > Any suggestion / comment like (but not limited to) 


> > 


> > Odoo is the wrong technology for that, forget it, because....


> > 


> > over


> > 


> > You can do it but, a), b), c) ....


> > 


> > to


> > 


> > If you really want that beast flying involve us over here because


> > we


> > are among the few ones that already did soemthing similar


> > 


> > would be appreciated. 


> > 


> > From our load intensive projects at initOS i know that 10000 orders


> > a


> > day can be handled but almost 50000 is a different story and thats


> > why


> > i am asking the most experienced resource out there ;-)


> > 


> > Thanks in advance for your replay


> > 


> > Cheers Frederik


> > 


> > 


> > -- 


> > Dr.-Ing. Frederik Kramer


> > Geschäftsführer


> >         


> > initOS GmbH


> > An der Eisenbahn 1


> > 21224 Rosengarten


> >         


> > Phone:  +49 4105 56156-12


> > Fax:    +49 4105 56156-10


> > Mobil:  +49 179 3901819


> >         


> > Email: frederik.kramer@initos.com


> > Web:   www.initos.com


> >         


> > Geschäftsführung:


> > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke


> > 


> > Sitz der Gesellschaft: Rosengarten – Klecken


> > Amtsgericht Tostedt, HRB 205226


> > Steuer-Nr: 15/200/53247


> > USt-IdNr.: DE815580155


> > 


> > _______________________________________________


> > Mailing-List: https://odoo-community.org/groups/contributors-15


> > Post to: mailto:contributors@odoo-community.org


> > Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 


> 


-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

Moisés López Calderón

Mobile: (+521) 477-752-22-30

Twitter: @moylop260

hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner

Twitter: @vauxoo

by Moisés López Calderón - 05:21 - 14 May 2021

Re: 30 Checkout Operations per Minute A job for Odoo or not ?

El jue, 6 de may. de 2021 a la(s) 05:02, Frederik Kramer (frederik.kramer@initos.com) escribió:

Hi Moises, 

Am Freitag, den 30.04.2021, 16:02 +0000 schrieb Moises Lopez:


> Hi Frederik


> 


> A customer requested to support 5k concurrent sale.order (1 or 2


> lines of products) in Odoo.


> The process that we followed were: test, measure, fix, test...

haha, yes thats what works well if you have a customer that well
endorses this "agile" and "pivoting" style of work. Apart from all
economic considerations this is probably also something that isolated
leads to quite solid solutions

That was our biggest measured customer (a recovered project) they know their KPI very well, on simpler customers, we try from a commercial perspective to explain exactly what Moises does (in a more extensive/commercial way) to try to teach them how to buy technology.

At the end if you try let's say Shopify (the king of marketed e-commerce) with those numbers you mentioned or this ones they will offer you more **Enterprise** services (note the services not the software) because almost everybody works on this way even the order on which your usual customers make click on the website can change the outcome and bring performance/consistency problems, i.e: click twice a button in an slow process that by mistake land an specific day on your code).

Then what's important IMHO is to clarify to the customer that set technically solid e-commerce is 30% software product 50% the right team.

If this was not the case, we would have millions of amazon stores, Don't you think?



> 


> The first time that we tested the checkout process supported 15


> concurrent virtual users (VUs)


> The measure said that it had heavy custom functions in the same


> transaction of checkout but it could be executed in background (cron,


> queue)


> and there were slow queries because of indexes issues or too many


> queries executed because of python code

did you use any specific profiling tools here? Or the ones that rcollet
often proposes in his talks about the matter ?

Be careful here, they are a lot, and in my honest experience that's more the person using the tool than the tool itself.



> 


> Note: Be careful with the base_automation if you can migrate them to 


> code it is better.

Thanks for the hint, i think we experienced that also quite some times
in the past and learned that lesson already ;-)



> 


> After fix them the next iteration supported 400 VUs


> So good but so far from the focus.


> 


> The next iteration we found that there were methods that could be


> using LRU-cache (e.g. prices, website that don't change)


> Now we needed to check where the cache was clearing too frequently


> and fix it.

How did you measure LRU cache hit rates vs. code parts in a good way.
Any tooling suggestion here ?

1. log-sql and a strong test setup that emulates the production environment is required.

2. We use some SQL analyzer tools as well.

But again, it is a matter of having the right team doing the job because it is not theoretical work, it is practice, test, read, practice, learn, fix, start again. and a little bit of good luck on some cases and being stubborn to solve the issues ;-)



> 


> We implemented CDN


> e.g. The sentence "/web/image/company.logo" runs 10 queries


> (prefetching fields, translating fields...) for each user opening the


> page


> After using CDN 0 queries are executed.

But you just used Odoos standard CDN function or any specific measure
here ?

Standard! we simply use Odoo's CDN functionality.



> 


> We removed soft process that running with many users it is heavy


> e.g. the random image that odoo assign when you create a res.partner


> e.g. computed fields moved to cron

Also here which analysis tools do you prefer to do so ?



> 


> After that we detected concurrent update issues


> It is hell for performance matter.


> e.g. updating the same record at the same time from many users,


> e.g. allowing pressing the same button too many times


> e.g. sequences using no-gap in the main process, and so on


> 


> After finishing all the hints of performance issues in the code and


> database the next steps were to improve the hardware.


> 


> Now, It supports 5k concurrent VUs doing checkout process (choose 2


> products, type address, payment card info and confirm)

In what time frame ?

With the real use case and in a production environment giving the problems more or less 60 days between First work and release into production ready for the action.



> 


> So, Odoo will support those users but you will need to test, measure,


> fix, test...


> Stress testing tools helps us a lot here


> python profilers and query analyzers too


> 


> Maybe you are interest to watch our talk in SFO about:


>  - https://youtu.be/kiREZqg3JQg

I will definitely have a look at this

Thanks a lot for your extensive insight.

I summarize with:

The team is the key to success here, every single piece in any e-commerce on this use case was given by different persons and led by Moisés because problems are in all layers: BD, Server, Sizing, Odoo, JS, OCA....

It is not just one single pill!

Cheers from rainy Germany to sunny Mexico ;-)

Frederik



> 


> El mié, 28 abr 2021 a las 15:35, Frederik Kramer (<


> frederik.kramer@initos.com>) escribió:


> > Hi Folks, 


> > 


> > i have a project proposal on my desk that will ultimately end up in


> > approx. 30 checkout transactions per minute. Has anybody got a


> > project


> > with that order volume done with a relatively recent version of


> > Odoo


> > and provide a good reference. Please bear in mind that the project


> > ahead involves a similarly high volume of stock moves.


> > 


> > Any suggestion / comment like (but not limited to) 


> > 


> > Odoo is the wrong technology for that, forget it, because....


> > 


> > over


> > 


> > You can do it but, a), b), c) ....


> > 


> > to


> > 


> > If you really want that beast flying involve us over here because


> > we


> > are among the few ones that already did soemthing similar


> > 


> > would be appreciated. 


> > 


> > From our load intensive projects at initOS i know that 10000 orders


> > a


> > day can be handled but almost 50000 is a different story and thats


> > why


> > i am asking the most experienced resource out there ;-)


> > 


> > Thanks in advance for your replay


> > 


> > Cheers Frederik


> > 


> > 


> > -- 


> > Dr.-Ing. Frederik Kramer


> > Geschäftsführer


> >         


> > initOS GmbH


> > An der Eisenbahn 1


> > 21224 Rosengarten


> >         


> > Phone:  +49 4105 56156-12


> > Fax:    +49 4105 56156-10


> > Mobil:  +49 179 3901819


> >         


> > Email: frederik.kramer@initos.com


> > Web:   www.initos.com


> >         


> > Geschäftsführung:


> > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke


> > 


> > Sitz der Gesellschaft: Rosengarten – Klecken


> > Amtsgericht Tostedt, HRB 205226


> > Steuer-Nr: 15/200/53247


> > USt-IdNr.: DE815580155


> > 


> > _______________________________________________


> > Mailing-List: https://odoo-community.org/groups/contributors-15


> > Post to: mailto:contributors@odoo-community.org


> > Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 


> 


-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com vauxoo.com/contactus

by Nhomar Hernández - 08:01 - 10 May 2021

Re: 30 Checkout Operations per Minute A job for Odoo or not ?

Hi Moises, 

Am Freitag, den 30.04.2021, 16:02 +0000 schrieb Moises Lopez:

> Hi Frederik

> 

> A customer requested to support 5k concurrent sale.order (1 or 2

> lines of products) in Odoo.

> The process that we followed were: test, measure, fix, test...

haha, yes thats what works well if you have a customer that well
endorses this "agile" and "pivoting" style of work. Apart from all
economic considerations this is probably also something that isolated
leads to quite solid solutions


> 

> The first time that we tested the checkout process supported 15

> concurrent virtual users (VUs)

> The measure said that it had heavy custom functions in the same

> transaction of checkout but it could be executed in background (cron,

> queue)

> and there were slow queries because of indexes issues or too many

> queries executed because of python code

did you use any specific profiling tools here? Or the ones that rcollet
often proposes in his talks about the matter ?


> 

> Note: Be careful with the base_automation if you can migrate them to 

> code it is better.

Thanks for the hint, i think we experienced that also quite some times
in the past and learned that lesson already ;-)


> 

> After fix them the next iteration supported 400 VUs

> So good but so far from the focus.

> 

> The next iteration we found that there were methods that could be

> using LRU-cache (e.g. prices, website that don't change)

> Now we needed to check where the cache was clearing too frequently

> and fix it.

How did you measure LRU cache hit rates vs. code parts in a good way.
Any tooling suggestion here ?


> 

> We implemented CDN

> e.g. The sentence "/web/image/company.logo" runs 10 queries

> (prefetching fields, translating fields...) for each user opening the

> page

> After using CDN 0 queries are executed.

But you just used Odoos standard CDN function or any specific measure
here ?


> 

> We removed soft process that running with many users it is heavy

> e.g. the random image that odoo assign when you create a res.partner

> e.g. computed fields moved to cron

Also here which analysis tools do you prefer to do so ?


> 

> After that we detected concurrent update issues

> It is hell for performance matter.

> e.g. updating the same record at the same time from many users,

> e.g. allowing pressing the same button too many times

> e.g. sequences using no-gap in the main process, and so on

> 

> After finishing all the hints of performance issues in the code and

> database the next steps were to improve the hardware.

> 

> Now, It supports 5k concurrent VUs doing checkout process (choose 2

> products, type address, payment card info and confirm)

In what time frame ?


> 

> So, Odoo will support those users but you will need to test, measure,

> fix, test...

> Stress testing tools helps us a lot here

> python profilers and query analyzers too

> 

> Maybe you are interest to watch our talk in SFO about:

>  - https://youtu.be/kiREZqg3JQg

I will definitely have a look at this

Thanks a lot for your extensive insight.

Cheers from rainy Germany to sunny Mexico ;-)

Frederik


> 

> El mié, 28 abr 2021 a las 15:35, Frederik Kramer (<

> frederik.kramer@initos.com>) escribió:

> > Hi Folks, 

> > 

> > i have a project proposal on my desk that will ultimately end up in

> > approx. 30 checkout transactions per minute. Has anybody got a

> > project

> > with that order volume done with a relatively recent version of

> > Odoo

> > and provide a good reference. Please bear in mind that the project

> > ahead involves a similarly high volume of stock moves.

> > 

> > Any suggestion / comment like (but not limited to) 

> > 

> > Odoo is the wrong technology for that, forget it, because....

> > 

> > over

> > 

> > You can do it but, a), b), c) ....

> > 

> > to

> > 

> > If you really want that beast flying involve us over here because

> > we

> > are among the few ones that already did soemthing similar

> > 

> > would be appreciated. 

> > 

> > From our load intensive projects at initOS i know that 10000 orders

> > a

> > day can be handled but almost 50000 is a different story and thats

> > why

> > i am asking the most experienced resource out there ;-)

> > 

> > Thanks in advance for your replay

> > 

> > Cheers Frederik

> > 

> > 

> > -- 

> > Dr.-Ing. Frederik Kramer

> > Geschäftsführer

> >         

> > initOS GmbH

> > An der Eisenbahn 1

> > 21224 Rosengarten

> >         

> > Phone:  +49 4105 56156-12

> > Fax:    +49 4105 56156-10

> > Mobil:  +49 179 3901819

> >         

> > Email: frederik.kramer@initos.com

> > Web:   www.initos.com

> >         

> > Geschäftsführung:

> > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

> > 

> > Sitz der Gesellschaft: Rosengarten – Klecken

> > Amtsgericht Tostedt, HRB 205226

> > Steuer-Nr: 15/200/53247

> > USt-IdNr.: DE815580155

> > 

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe

> 

> 

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

by Frederik Kramer. - 12:01 - 6 May 2021

Re: 30 Checkout Operations per Minute A job for Odoo or not ?
Hi Frederik

A customer requested to support 5k concurrent sale.order (1 or 2 lines of products) in Odoo.
The process that we followed were: test, measure, fix, test...

The first time that we tested the checkout process supported 15 concurrent virtual users (VUs)
The measure said that it had heavy custom functions in the same transaction of checkout but it could be executed in background (cron, queue)
and there were slow queries because of indexes issues or too many queries executed because of python code

Note: Be careful with the base_automation if you can migrate them to code it is better.

After fix them the next iteration supported 400 VUs
So good but so far from the focus.

The next iteration we found that there were methods that could be using LRU-cache (e.g. prices, website that don't change)
Now we needed to check where the cache was clearing too frequently and fix it.

We implemented CDN
e.g. The sentence "/web/image/company.logo" runs 10 queries (prefetching fields, translating fields...) for each user opening the page
After using CDN 0 queries are executed.

We removed soft process that running with many users it is heavy
e.g. the random image that odoo assign when you create a res.partner
e.g. computed fields moved to cron

After that we detected concurrent update issues
It is hell for performance matter.
e.g. updating the same record at the same time from many users,
e.g. allowing pressing the same button too many times
e.g. sequences using no-gap in the main process, and so on

After finishing all the hints of performance issues in the code and database the next steps were to improve the hardware.

Now, It supports 5k concurrent VUs doing checkout process (choose 2 products, type address, payment card info and confirm)

So, Odoo will support those users but you will need to test, measure, fix, test...
Stress testing tools helps us a lot here
python profilers and query analyzers too

Maybe you are interest to watch our talk in SFO about:
- https://youtu.be/kiREZqg3JQg

El mié, 28 abr 2021 a las 15:35, Frederik Kramer (<frederik.kramer@initos.com>) escribió:
Hi Folks, i have a project proposal on my desk that will ultimately end up in approx. 30 checkout transactions per minute. Has anybody got a project with that order volume done with a relatively recent version of Odoo and provide a good reference. Please bear in mind that the project ahead involves a similarly high volume of stock moves. Any suggestion / comment like (but not limited to) Odoo is the wrong technology for that, forget it, because.... over You can do it but, a), b), c) .... to If you really want that beast flying involve us over here because we are among the few ones that already did soemthing similar would be appreciated. From our load intensive projects at initOS i know that 10000 orders a day can be handled but almost 50000 is a different story and thats why i am asking the most experienced resource out there ;-) Thanks in advance for your replay Cheers Frederik -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155

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

--
Moisés López Calderón
Mobile: (+521) 477-752-22-30
Twitter: @moylop260
hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner
Twitter: @vauxoo
by Moisés López Calderón - 06:00 - 30 Apr 2021

Re: 30 Checkout Operations per Minute A job for Odoo or not ?

Hello Frederik, may be you could consider this module from Akretion for a RESTFul asynchronous import bus:

https://github.com/akretion/sale-import

It is using the OCA/queue module.

At the moment it is for sale orders but the same could be done with invoices directly.

Good luck.

On Thu, Apr 29, 2021, 7:47 AM Frederik Kramer <frederik.kramer@initos.com> wrote:

Hi Joe, 

thanks for the valuable feedback. Indeed i wasn't too specific on the
scenario but its quite unlikely that an order in that business case is 
more than 10 items (standard only 1-2 is guess). However all
considerations with decoupling checkout from logisics and financial
fail in our case (a least without further design changes) because the
entire physical / financial transaction needs to be accomplished and
book in less than 10min. But of course a solid message broker
architektur would be something that would be really helpful for the
Odoo ecosystem. Which Message bus do you prefer in your scenarios and
for what reason, if i may ask

Best Frederik

Am Donnerstag, den 29.04.2021, 10:37 +0000 schrieb Joerg Lorenz:


> Hi Fred: 


> 


> instead of looking into the amount of orders, I would rather look


> into the amount of lines per order containing items (excluding the


> one lines that are just informational), first.


> This is the key performance measure.


> If the order line volume is resonable (1-3 on average on an online


> order), then die 30 to 50 a minute is a hands down job, because,


> there is no posting involved, just stock reservation. Question still


> is, what the response time shall be for each order?


> 


> Also a question would be for your scenario, if those really need to


> be put as ORDERs, instead of QUOTEs - which are even simpler to


> consume. 


> 


> If you like we can talk more on your requirements by phone. 


> 


> N.B.


> In very high volume sceanrios we did, like with some 20000 orders a


> minute, we usually just consumed, the orders with an message broker


> first, then preprocessed there, confirmed (if no error), queued and


> batched in the the ERP for processing (we did this for DHL for all


> barcode scanners of Deutsche Post service men in Germany, rond trip


> was supposed to be less than 5 seconds to get confirmation to the


> barcode scanner). 


> 


> Best Joe


> 


> Von: "frederik kramer" <frederik.kramer@initos.com>


> An: "Odoo Community Association, (OCA) Contributors" <


> contributors@odoo-community.org>


> Gesendet: Donnerstag, 29. April 2021 09:52:11


> Betreff: Re: 30 Checkout Operations per Minute A job for Odoo or not


> ?


> 


> Hi Joel, hi Jordi, 


> 


> thanks for your valuable answers. For the time being we don't really


> know about the real scenarios as this is a bolt pitch claim of a VC


> driven startup for now. But from the business model it seems


> reasonably


> realistic for me to ask before claiming something that doesn't hold


> true if it materialized. 


> 


> I am pretty sure that - given the business model - there will be rush


> hours. So yes, i could even conceive 50 instead of 30 orders a


> minute. 


> 


> In similar use cases that you just explained, we have been applying


> both of the strategies you mention


> 


> 1.) Decoupling stock moves


> 2.) Batch processing in off-peak times


> 


> In the use case at stake both does not really work as the entire


> transaction from Checkout to Delivery (incl. Picking) is supposed to


> take less then 10 min incl. pyhsical transport. 


> 


> Nevertheless i think all of that may be doable but, i will certainly


> not claim "without hassle and much invest".


> 


> Thanks for your answers


> 


> Am Donnerstag, den 29.04.2021, 07:32 +0000 schrieb Joël Grand-


> Guillaume:


> 


> 


> > Hi Frederik,


> 


> 


> > 


> 


> 


> > 


> 


> 


> > Yes this is a big number ! Look, first before anything else, how


> many


> 


> 


> > lines on average for those orders ? According to my XP, this


> matters


> 


> 


> > a lot.


> 


> 


> > 


> 


> 


> > Second question is: Are there rushing hours and more calm hours ? 


> 


> 


> > 


> 


> 


> > In our XP we could not record more than 10 orders per minute. Was


> on


> 


> 


> > V 12 though, so it might have improved a bit by now. In our case,


> we


> 


> 


> > had a rush and calm hour. So the jobs could be recorded during rush


> 


> 


> > hours and processed during calm ones. It worked well, but that was


> 


> 


> > for not that many numbers...


> 


> 


> > 


> 


> 


> > An idea would be to decoule the order confirmation from the stock


> 


> 


> > move generation and do this in two different times. You could


> ensure


> 


> 


> > the reservation using our stock allocation module.


> 


> 


> > 


> 


> 


> > Cannot really help much at this stage,


> 


> 


> > 


> 


> 


> > Joël


> 


> 


> > 


> 


> 


> > 


> 


> 


> > On Thu, Apr 29, 2021 at 1:32 AM Jordi Ballester Alomar <


> 


> 


> > jordi.ballester@forgeflow.com> wrote:


> 


> 


> > > We have a use case with approx 5000/day. I can see how 50000/day


> 


> 


> > > can become a hell. Imagine recomputing a field, or migrating


> 


> 


> > > between versions.


> 


> 


> > > 


> 


> 


> > > It's a challenge, I give you that.


> 


> 


> > > 


> 


> 


> > > On Wed, Apr 28, 2021 at 10:35 PM Frederik Kramer <


> 


> 


> > > frederik.kramer@initos.com> wrote:


> 


> 


> > > > Hi Folks, 


> 


> 


> > > > 


> 


> 


> > > > i have a project proposal on my desk that will ultimately end


> up


> 


> 


> > > > in


> 


> 


> > > > approx. 30 checkout transactions per minute. Has anybody got a


> 


> 


> > > > project


> 


> 


> > > > with that order volume done with a relatively recent version of


> 


> 


> > > > Odoo


> 


> 


> > > > and provide a good reference. Please bear in mind that the


> 


> 


> > > > project


> 


> 


> > > > ahead involves a similarly high volume of stock moves.


> 


> 


> > > > 


> 


> 


> > > > Any suggestion / comment like (but not limited to) 


> 


> 


> > > > 


> 


> 


> > > > Odoo is the wrong technology for that, forget it, because....


> 


> 


> > > > 


> 


> 


> > > > over


> 


> 


> > > > 


> 


> 


> > > > You can do it but, a), b), c) ....


> 


> 


> > > > 


> 


> 


> > > > to


> 


> 


> > > > 


> 


> 


> > > > If you really want that beast flying involve us over here


> because


> 


> 


> > > > we


> 


> 


> > > > are among the few ones that already did soemthing similar


> 


> 


> > > > 


> 


> 


> > > > would be appreciated. 


> 


> 


> > > > 


> 


> 


> > > > From our load intensive projects at initOS i know that 10000


> 


> 


> > > > orders a


> 


> 


> > > > day can be handled but almost 50000 is a different story and


> 


> 


> > > > thats why


> 


> 


> > > > i am asking the most experienced resource out there ;-)


> 


> 


> > > > 


> 


> 


> > > > Thanks in advance for your replay


> 


> 


> > > > 


> 


> 


> > > > Cheers Frederik


> 


> 


> > > > 


> 


> 


> > > > 


> 


> 


> > > > 


> 


> 


> > > > -- 


> 


> 


> > > > Dr.-Ing. Frederik Kramer


> 


> 


> > > > Geschäftsführer


> 


> 


> > > >         


> 


> 


> > > > initOS GmbH


> 


> 


> > > > An der Eisenbahn 1


> 


> 


> > > > 21224 Rosengarten


> 


> 


> > > >         


> 


> 


> > > > Phone:  +49 4105 56156-12


> 


> 


> > > > Fax:    +49 4105 56156-10


> 


> 


> > > > Mobil:  +49 179 3901819


> 


> 


> > > >         


> 


> 


> > > > Email: frederik.kramer@initos.com


> 


> 


> > > > Web:   www.initos.com


> 


> 


> > > >         


> 


> 


> > > > Geschäftsführung:


> 


> 


> > > > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke


> 


> 


> > > > 


> 


> 


> > > > Sitz der Gesellschaft: Rosengarten – Klecken


> 


> 


> > > > Amtsgericht Tostedt, HRB 205226


> 


> 


> > > > Steuer-Nr: 15/200/53247


> 


> 


> > > > USt-IdNr.: DE815580155


> 


> 


> > > > 


> 


> 


> > > > _______________________________________________


> 


> 


> > > > Mailing-List: https://odoo-community.org/groups/contributors-15


> 


> 


> > > > Post to: mailto:contributors@odoo-community.org


> 


> 


> > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 


> 


> > > 


> 


> 


> > > 


> 


> 


> > > -- 


> 


> 


> > > Jordi Ballester Alomar


> 


> 


> > > CEO & Founder | ForgeFlow


> 


> 


> > > (+34) 629530707 | jordi.ballester@forgeflow.com | 


> 


> 


> > > https://www.forgeflow.com


> 


> 


> > > Twitter: https://twitter.com/jordibforgeflow | Linkedin: 


> 


> 


> > > https://www.linkedin.com/in/jordiballesteralomar


> 


> 


> > > _______________________________________________


> 


> 


> > > Mailing-List: https://odoo-community.org/groups/contributors-15


> 


> 


> > > Post to: mailto:contributors@odoo-community.org


> 


> 


> > > Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 


> 


> > 


> 


> 


> > 


> 


> 


> -- 


> Dr.-Ing. Frederik Kramer


> Geschäftsführer


>         


> initOS GmbH


> An der Eisenbahn 1


> 21224 Rosengarten


>         


> Phone:  +49 4105 56156-12


> Fax:    +49 4105 56156-10


> Mobil:  +49 179 3901819


>         


> Email: frederik.kramer@initos.com


> Web:   www.initos.com


>         


> Geschäftsführung:


> Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke


> 


> Sitz der Gesellschaft: Rosengarten – Klecken


> Amtsgericht Tostedt, HRB 205226


> Steuer-Nr: 15/200/53247


> USt-IdNr.: DE815580155


> 


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe


> 


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe


-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

by "Raphaël Valyi" <rvalyi@akretion.com> - 04:26 - 30 Apr 2021

Rename a module with migration script

Hello all!
We are trying to rename a module. The main purpose is to change the
name of the module itself, as well as xmlids, models and tables.

Preliminary step:
- Add a pre-migrate script like this one in new_name_module (bumping
the version number):
https://github.com/OCA/l10n-italy/pull/2220/commits/d6c790525e1892be1d04391054ccb779092c354c#diff-a86bc87cb07b27f04908e90baeb089a9182ad568d8e7205f40f3e689272bb76c

Test steps:

1) old_name module installation
2) add/change some data in Odoo
3) checkout to commit containing new_name module, migration script and
version bumped
4) launch old_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u old_name_module --stop-after-init

Output:
old_name_module: not installable, skipped

In fact pre-migrate script is not triggered.


As an alternative to 4), we tried this:
4) launch new_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u new_name_module --stop-after-init

But it didn't work as well.


The only way (we have found so far) to trigger pre-migrate script is this:

1) old_name module installation
2) add/change some data
3) checkout to commit containing new_name module, migration script and
version bumped
4) execute odoo shell
    >>> from openupgradelib import openupgrade
    >>> openupgrade.update_module_names(env.cr, [('old_name_module',
'new_name_module'),], merge_modules=False,)
    >>> env.cr.commit()
5) launch new_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u new_name_module --stop-after-init


Do you know a way to trigger the migration script without using odoo shell?

Thanks in advance.
S.

by Sergio Zanchetta - 10:16 - 28 Apr 2021

1 replies 1 replies

RFQ - Communication Strategy for the next 3 years - share this please
Dear OCA Contributors,
We hope your week's have started well.

Late last week we shared through our social media our latest RFQ. To share further please find the information below.

The OCA is looking for a Communication Strategy Expert to help define our Communication Strategy for the next 3 years.

To find out about the work schedule and deliverables please see here: https://drive.google.com/file/d/19EL646MjjpI4lN47v4P18tHMk2q_1ktR/view

If you have any questions please email: rfq@odoo-community.org

Warmest regards,
Rebecca & Virginie
by Virginie Dewulf. - 10:16 - 28 Apr 2021
RFQ - OCA Communication Strategy Expert

Dear Contributors,

I hope your week's have started well.

Late last week we shared through our social media our latest RFQ. To share further please find the information below.

The OCA is looking for a Communication Strategy Expert to help define our Communication Strategy for the next 3 years.

To find out about the work schedule and deliverables please see here: https://drive.google.com/file/d/19EL646MjjpI4lN47v4P18tHMk2q_1ktR/view

If you have any questions please email: rfq@odoo-community.org

Warmest regards,
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association

by Rebecca Gellatly - 10:15 - 28 Apr 2021
1 replies 1 replies
RFQ - OCA Communication Strategy Expert

Dear OCA Contributors,

I hope your week's have started well.

Late last week we shared through our social media our latest RFQ. To share further please find the information below.

The OCA is looking for a Communication Strategy Expert to help define our Communication Strategy for the next 3 years.

To find out about the work schedule and deliverables please see here: https://drive.google.com/file/d/19EL646MjjpI4lN47v4P18tHMk2q_1ktR/view

If you have any questions please email: rfq@odoo-community.org

Warmest regards,
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association

by Rebecca Gellatly - 10:15 - 28 Apr 2021
Enable Github Discussions for l10n-brazil

Hi

Someone with permission to configure OCA´s projects, could kindly activate the github discussions of the Brazilian Localization project?

https://github.com/oca/l10n-brazil

Thanks in advance

Luis Felipe Miléo
CEO
phone: +55 11 3090-9303
mobile: +55 35 988 763 663
R. Coronel Renó, 07 - Sala PC.2.3.01
Itajubá - MG
kmee.com.br

by Luis F Miléo - 10:15 - 28 Apr 2021

Archives

Contributors

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López

Harald Panten López