- Mailing Lists
- Contributors
- Re: Multiple customers on Purchase Orders
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Multiple customers on Purchase Orders
> Anyone faced anything similar? I am thinking of using 2 companies to model > it and tinkering with visibility in each according to split. Because where > there is a split, they want to see the document in both. Where there is not > (it belongs to single company), should ony be visible there. However how to > model in a best way that there should be 2 customers (maybe more for future > extensions) on each document? I have a customer with a similar requirement the other way around, where multiple suppliers invoice the same customer: https://github.com/tosccolors/vertical-professional-services/tree/16.0/ ps_partner_multi_relation They solved this by defining a partner relation "consortium", and every time an invoice for a consortium partner is posted, this invoice is split by the weights ("distribution key") on the consortium relation and new invoices are created for the involved partners. This concept should extend quite naturally to the purchase side, where you split the supplier invoices and deliveries according to the distribution key on the partner relation. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 12:32 - 23 Sep 2024
Reference
-
Multiple customers on Purchase Orders
Hello,
I am dealing with a scenario where 2 sister companies share parts of their operations and make purchase orders together with split ratio between them. The way they do it is 3-party agreements, where there are 2 customers and 1 supplier and for purchase orders there are instructions for suppliers on how to split the invoicing (i.e. the supplier sends 2 separate invoices - each to individual company according to the split ratio).
Anyone faced anything similar? I am thinking of using 2 companies to model it and tinkering with visibility in each according to split. Because where there is a split, they want to see the document in both. Where there is not (it belongs to single company), should ony be visible there. However how to model in a best way that there should be 2 customers (maybe more for future extensions) on each document?
Any advice is highly welcome. Thank you very much.
Best regards
Radovan Skolnik
by Radovan Skolnik - 12:06 - 23 Sep 2024-
Re: Multiple customers on Purchase Orders
Thanks Holger,
the idea of "consortium" instead of trying to put multiple customers into PO is a good one and also naturally extendable beyond more than 2 companies.
Best regards
Radovan
On pondelok 23. septembra 2024 12:37:45 CEST Holger Brunn wrote:
> > Anyone faced anything similar? I am thinking of using 2 companies to model
> > it and tinkering with visibility in each according to split. Because where
> > there is a split, they want to see the document in both. Where there is
> > not
> > (it belongs to single company), should ony be visible there. However how
> > to
> > model in a best way that there should be 2 customers (maybe more for
> > future
> > extensions) on each document?
>
> I have a customer with a similar requirement the other way around, where
> multiple suppliers invoice the same customer:
> https://github.com/tosccolors/vertical-professional-services/tree/16.0/
> ps_partner_multi_relation
> They solved this by defining a partner relation "consortium", and every time
> an invoice for a consortium partner is posted, this invoice is split by the
> weights ("distribution key") on the consortium relation and new invoices
> are created for the involved partners.
> This concept should extend quite naturally to the purchase side, where you
> split the supplier invoices and deliveries according to the distribution key
> on the partner relation.
> --
> Your partner for the hard Odoo problems
> https://hunki-enterprises.com
> _______________________________________________
> 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 - 02:46 - 23 Sep 2024 -
Re: Multiple customers on Purchase Orders
> Anyone faced anything similar? I am thinking of using 2 companies to model > it and tinkering with visibility in each according to split. Because where > there is a split, they want to see the document in both. Where there is not > (it belongs to single company), should ony be visible there. However how to > model in a best way that there should be 2 customers (maybe more for future > extensions) on each document? I have a customer with a similar requirement the other way around, where multiple suppliers invoice the same customer: https://github.com/tosccolors/vertical-professional-services/tree/16.0/ ps_partner_multi_relation They solved this by defining a partner relation "consortium", and every time an invoice for a consortium partner is posted, this invoice is split by the weights ("distribution key") on the consortium relation and new invoices are created for the involved partners. This concept should extend quite naturally to the purchase side, where you split the supplier invoices and deliveries according to the distribution key on the partner relation. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 12:32 - 23 Sep 2024
-