Archives
Contributors
-
Re: Have you organised your 2024 OCA membership yet?
Hi Michel,I suspect the list will soon be expanded by quite a bit since I can imagine other companies having done the same as we did: process the due invoice on Membership near the end of January via PO, meaning OCA accounting now has to reconcile quite the number of transactions :-)In any case, depending on whether or my colleagues and I are all filed away under the same country, we might see an 1100% increase on that NL list!If you’re anywhere near Amersfoort we’d be glad to treat you to a coffee.Met vriendelijke groet, Sincerely,Gijs-Jan OttenTherp BV | gjotten@therp.nl |+31 20 309 30 93On 5 Feb 2024, at 21:21, Michel Stroom <notifications@odoo-community.org> wrote:
Dear OCA-ers and Odooers,Read the latest OCA news item about the 2024 OCA membership and purchase process.If you haven’t purchased the 2024 OCA membership yet, help yourself through the website.I’m looking forward to seeing more OCA members in the Netherlands folder directory soon.Would like to collaborate and increase the Odoo popularity in the Netherlands together with other OCA members in 2024. Please feel free to contact me in the meantime.Best regards,Michel Stroom_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Gijs-Jan Otten - 10:41 - 5 Feb 2024 -
Have you organised your 2024 OCA membership yet?
Dear OCA-ers and Odooers,Read the latest OCA news item about the 2024 OCA membership and purchase process.If you haven’t purchased the 2024 OCA membership yet, help yourself through the website.I’m looking forward to seeing more OCA members in the Netherlands folder directory soon.Would like to collaborate and increase the Odoo popularity in the Netherlands together with other OCA members in 2024. Please feel free to contact me in the meantime.Best regards,Michel Stroom
by Michel Stroom - 09:21 - 5 Feb 2024 -
Re: Mounting location of part upon production
On 2/5/24 16:02, Daniel Reis wrote: > Option 3 looks similar to Lot/Serial usage. What if you (ab)used Lot > numbers for this? Good idea in theory, but in my case we're already using serial numbers to track the parts
by Tom Blauwendraat - 05:41 - 5 Feb 2024 -
Re: Mounting location of part upon production
Hi Tom,
Option 2 will be problematic as it introduces artificial restrictions on component usage.
Option 3 looks similar to Lot/Serial usage. What if you (ab)used Lot numbers for this?
On 05/02/2024 11:57, Tom Blauwendraat wrote:
Hello, I'm dealing with a situation where upon production, the mounting location of the parts needs to be registered. Imagine a chair with 4 identical legs, but it needs to be registered which leg is placed where: front right, front left, rear right or rear left. Is there something for this case in Odoo? What I could come up with is: - Requiring work orders for "leg mounting", and specifying the mount location on the work order - Having separate products eg "Left rear leg" and producing these from "Leg" (seems a bit of a hassle) - Adding a required field on stock move line in case certain products are produced, where the mount location is filled in; also enforce 1.0 as a quantity - ... -Tom
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
by Daniel Reis - 04:00 - 5 Feb 2024 -
Re: Please approve PR [17.0][MIG] stock_mts_mto_rule: Migration to 17.0
No access is needed to do reviews, it's a public functionality in Github.
On 2/5/24 14:37, Aleksander Milinkevich wrote:
Hi,
I would be happy to, but I don’t have the reviewer access.
Could you help?
BR,
Aleksander Milinkevich
From: Enric Tobella Alomar <notifications@odoo-community.org>
Date: Monday, 5 February 2024 at 14:22
To: Contributors <contributors@odoo-community.org>
Subject: Re: Please approve PR [17.0][MIG] stock_mts_mto_rule: Migration to 17.0I would recommend to do some reviews and ask the author of the reviewed PR to do the same for you (Quid pro quo)
Kind regards,
El lun, 5 feb 2024 a las 14:07, Aleksander Milinkevich (<notifications@odoo-community.org>) escribió:
Hello,
Please approve my Pull Request
https://github.com/OCA/stock-logistics-warehouse/pull/1932
It will take you just 2 minutes!
BR,
Aleksander Milinkevich
_______________________________________________
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 Tom Blauwendraat - 03:36 - 5 Feb 2024 -
Re: Please approve PR [17.0][MIG] stock_mts_mto_rule: Migration to 17.0
Hi,
I would be happy to, but I don’t have the reviewer access.
Could you help?
BR,
Aleksander Milinkevich
From: Enric Tobella Alomar <notifications@odoo-community.org>
Date: Monday, 5 February 2024 at 14:22
To: Contributors <contributors@odoo-community.org>
Subject: Re: Please approve PR [17.0][MIG] stock_mts_mto_rule: Migration to 17.0I would recommend to do some reviews and ask the author of the reviewed PR to do the same for you (Quid pro quo)
Kind regards,
El lun, 5 feb 2024 a las 14:07, Aleksander Milinkevich (<notifications@odoo-community.org>) escribió:
Hello,
Please approve my Pull Request
https://github.com/OCA/stock-logistics-warehouse/pull/1932
It will take you just 2 minutes!
BR,
Aleksander Milinkevich
_______________________________________________
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 aleksander - 02:35 - 5 Feb 2024 -
Re: Please approve PR [17.0][MIG] stock_mts_mto_rule: Migration to 17.0
I would recommend to do some reviews and ask the author of the reviewed PR to do the same for you (Quid pro quo)Kind regards,El lun, 5 feb 2024 a las 14:07, Aleksander Milinkevich (<notifications@odoo-community.org>) escribió:Hello,
Please approve my Pull Request
https://github.com/OCA/stock-logistics-warehouse/pull/1932
It will take you just 2 minutes!
BR,
Aleksander Milinkevich
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 02:22 - 5 Feb 2024 -
Mounting location of part upon production
Hello, I'm dealing with a situation where upon production, the mounting location of the parts needs to be registered. Imagine a chair with 4 identical legs, but it needs to be registered which leg is placed where: front right, front left, rear right or rear left. Is there something for this case in Odoo? What I could come up with is: - Requiring work orders for "leg mounting", and specifying the mount location on the work order - Having separate products eg "Left rear leg" and producing these from "Leg" (seems a bit of a hassle) - Adding a required field on stock move line in case certain products are produced, where the mount location is filled in; also enforce 1.0 as a quantity - ... -Tom
by Tom Blauwendraat - 12:57 - 5 Feb 2024 -
Re: Prepaid Services & Timesheets
Hi Daniel,
i am not sure at the moment if this can be adressed like exected.
At this point, for me it looks like the best apporach is to solve this by creating appropriate timesheet entries (positive and negative).
I will attack this issue more in detail end of next week and hope to get a more precise idea of what will come up to do this.
All the best
Nils
Von: Daniel Reis <notifications@odoo-community.org>
Antworten an: OCA Contributors <contributors@odoo-community.org>
Datum: Donnerstag, 1. Februar 2024 um 19:13
An: OCA Contributors <contributors@odoo-community.org>
Betreff: Re: Prepaid Services & TimesheetsACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Can an upfront Advance Payment address this?
On 01/02/2024 14:31, Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:
Hi OCA Contributors,
i was asked, if it is possible to manage prepaid service hours in the following way..
Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.
If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.
Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…
All the best
Nils
Mit freundlichen Grüßen
Nils Coenen
--------
Nils Coenen
Inhaber
NICO SOLUTIONS - ENGINEERING & IT
Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal
Tel. +49 (0)4298-4667492Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 12:02 - 4 Feb 2024 -
Re: Travis sunset
Nice progress, Stephane!
This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:
--> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)
Should we:
A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos
B. Refuse complex PR's; manually merge in smaller or bugfix PR's
C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews
D. Any of the above, as agreed as a policy between the PSC's of the particular repo
I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?
-Tom
On 2/3/24 11:22, Stéphane Bidoul wrote:
Hi everyone,
As previously announced we have cancelled the OCA Travis subscription.
This means Travis CI tests will stop working in OCA repos mid February.
Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.
Best regards,
-Stéphane
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 11:59 - 4 Feb 2024 -
Travis sunset
Hi everyone,As previously announced we have cancelled the OCA Travis subscription.This means Travis CI tests will stop working in OCA repos mid February.Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.Best regards,-Stéphane
by Stéphane Bidoul - 11:21 - 3 Feb 2024 -
Re: Prepaid Services & Timesheets
Can an upfront Advance Payment address this?
On 01/02/2024 14:31, Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:
Hi OCA Contributors,
i was asked, if it is possible to manage prepaid service hours in the following way..
Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.
If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.
Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…
All the best
Nils
Mit freundlichen Grüßen
Nils Coenen
--------
Nils Coenen
Inhaber
NICO SOLUTIONS - ENGINEERING & IT
Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal
Tel. +49 (0)4298-4667492Website | Map | Email Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender. _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
by Daniel Reis - 07:13 - 1 Feb 2024 -
Re: Prepaid Services & Timesheets
Hi Nils,
probably not, no. If your customer starts out with Enterprise Subscription than you might be tied into changing this. But this part underwent substantial changes in Enterprise throughout previous versions.
Best Frederik
Am 01.02.24 um 15:56 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
Hi Frederik,
thanks for your prompt reply…
It is quite clear to me, that this is nothing for „hey, lets dattack this right now and it will work tomorrow“.
I do have an idea of the complexity. But as time is a rare good at the moment… (due to another project ;P) I decided to ask you before approaching anything.
So if this a common need for many users… a proper project seem to make sense…
As the customer wants to use the enterprise subscription app…. I dont know if contract is the right place to start…
But i´ll start diving into it.
Schöne Grüße aus dem Norden ;P
All the best
Nils
Von: Graeme Gellatly <notifications@odoo-community.org>
Antworten an: OCA Contributors <contributors@odoo-community.org>
Datum: Donnerstag, 1. Februar 2024 um 15:47
An: OCA Contributors <contributors@odoo-community.org>
Betreff: Re: Prepaid Services & Timesheets
ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hi Nils,
afaik exactly such a function doesn't exist so far. I would be interested in something similar though as well / or lets say in expierence how to set that up with a minimal set of additional modules.
I think that is also a quite common requirement, though differs in detail from service company to service company.
Furthermore you need to consider what type of module to reflect the "recurrency" and the downstream invoice generation (in detail your requirement is more complex than you might think).
Ususally you proably would start out with something from https://github.com/OCA/contract to build this process.
Best Frederik
Am 01.02.24 um 15:31 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
Hi OCA Contributors,
i was asked, if it is possible to manage prepaid service hours in the following way..
Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.
If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.
Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…
All the best
Nils
Mit freundlichen Grüßen
Nils Coenen
--------
Nils Coenen
Inhaber
NICO SOLUTIONS - ENGINEERING & IT
Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal
Tel. +49 (0)4298-4667492Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.
_______________________________________________
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
Innungsstraße 7
21244 Buchholz i.d.N.
Tel: +49 (0) 4181 13503 12
Fax: +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819
Email: frederik.kramer@initos.com
Internet: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247
_______________________________________________
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 Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 04:13 - 1 Feb 2024 -
Re: Prepaid Services & Timesheets
Hi Frederik,
thanks for your prompt reply…
It is quite clear to me, that this is nothing for „hey, lets dattack this right now and it will work tomorrow“.
I do have an idea of the complexity. But as time is a rare good at the moment… (due to another project ;P) I decided to ask you before approaching anything.
So if this a common need for many users… a proper project seem to make sense…
As the customer wants to use the enterprise subscription app…. I dont know if contract is the right place to start…
But i´ll start diving into it.
Schöne Grüße aus dem Norden ;P
All the best
Nils
Von: Graeme Gellatly <notifications@odoo-community.org>
Antworten an: OCA Contributors <contributors@odoo-community.org>
Datum: Donnerstag, 1. Februar 2024 um 15:47
An: OCA Contributors <contributors@odoo-community.org>
Betreff: Re: Prepaid Services & TimesheetsACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hi Nils,
afaik exactly such a function doesn't exist so far. I would be interested in something similar though as well / or lets say in expierence how to set that up with a minimal set of additional modules.
I think that is also a quite common requirement, though differs in detail from service company to service company.
Furthermore you need to consider what type of module to reflect the "recurrency" and the downstream invoice generation (in detail your requirement is more complex than you might think).
Ususally you proably would start out with something from https://github.com/OCA/contract to build this process.
Best Frederik
Am 01.02.24 um 15:31 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
Hi OCA Contributors,
i was asked, if it is possible to manage prepaid service hours in the following way..
Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.
If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.
Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…
All the best
Nils
Mit freundlichen Grüßen
Nils Coenen
--------
Nils Coenen
InhaberNICO SOLUTIONS - ENGINEERING & IT
Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal
Tel. +49 (0)4298-4667492Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.
_______________________________________________
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
Innungsstraße 7
21244 Buchholz i.d.N.
Tel: +49 (0) 4181 13503 12
Fax: +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819
Email: frederik.kramer@initos.com
Internet: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 03:56 - 1 Feb 2024 -
Re: Prepaid Services & Timesheets
Hi Nils,
afaik exactly such a function doesn't exist so far. I would be interested in something similar though as well / or lets say in expierence how to set that up with a minimal set of additional modules.
I think that is also a quite common requirement, though differs in detail from service company to service company.
Furthermore you need to consider what type of module to reflect the "recurrency" and the downstream invoice generation (in detail your requirement is more complex than you might think).
Ususally you proably would start out with something from https://github.com/OCA/contract to build this process.
Best Frederik
Am 01.02.24 um 15:31 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
Hi OCA Contributors,
i was asked, if it is possible to manage prepaid service hours in the following way..
Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.
If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.
Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…
All the best
Nils
Mit freundlichen Grüßen
Nils Coenen
--------
Nils Coenen
Inhaber
NICO SOLUTIONS - ENGINEERING & IT
Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal
Tel. +49 (0)4298-4667492Website | Map | Email Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender. _______________________________________________
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 Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 03:46 - 1 Feb 2024 -
Prepaid Services & Timesheets
Hi OCA Contributors,
i was asked, if it is possible to manage prepaid service hours in the following way..
Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.
If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.
Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…
All the best
Nils
Mit freundlichen Grüßen
Nils Coenen
--------
Nils Coenen
Inhaber
NICO SOLUTIONS - ENGINEERING & IT
Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal
Tel. +49 (0)4298-4667492Website | Map | Email Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.
by Nils Coenen - 03:31 - 1 Feb 2024
