Le 28/10/2017 à 11:27, Cédric Krier a écrit :
On 2017-10-28 06:48, Richard PALO wrote:
Le 28/10/2017 à 01:12, Cédric Krier a écrit :
On 2017-10-27 22:27, Richard PALO wrote:
So do not fill it. You do not need to have the supplier price, it is
there for information.
?? I thought that stock
On 2017-10-28 06:48, Richard PALO wrote:
> Le 28/10/2017 à 01:12, Cédric Krier a écrit :
> > On 2017-10-27 22:27, Richard PALO wrote:
> >>> So do not fill it. You do not need to have the supplier price, it is
> >>> there for information.
> >>>
> >>
> >> ?? I thought that stock receptions used the
Le 28/10/2017 à 01:12, Cédric Krier a écrit :
On 2017-10-27 22:27, Richard PALO wrote:
So do not fill it. You do not need to have the supplier price, it is
there for information.
?? I thought that stock receptions used the order prices (not the invoiced
price) for stock
valuation on the
On 2017-10-27 22:27, Richard PALO wrote:
> > So do not fill it. You do not need to have the supplier price, it is
> > there for information.
> >
>
> ?? I thought that stock receptions used the order prices (not the invoiced
> price) for stock
> valuation on the stock move. Has this changed, or
Le 26/10/2017 à 10:09, Cédric Krier a écrit :
On 2017-10-26 07:19, Richard PALO wrote:
Le 25/10/2017 à 13:57, Cédric Krier a écrit :
On 2017-10-25 13:47, Richard PALO wrote:
I believe there should be some additional things to consider, typically for
suppliers
where instead of communicating
On 2017-10-26 07:19, Richard PALO wrote:
> Le 25/10/2017 à 13:57, Cédric Krier a écrit :
> > On 2017-10-25 13:47, Richard PALO wrote:
> >> I believe there should be some additional things to consider, typically
> >> for suppliers
> >> where instead of communicating net prices to their
I believe as well that supplier purchase categories could or
should probably relate to purchase.product_supplier as opposed to
being dumped on product.template
cheers
--
Richard PALO
--
You received this message because you are subscribed to the Google Groups
"tryton" group.
To view this
Le 25/10/2017 à 13:57, Cédric Krier a écrit :
On 2017-10-25 13:47, Richard PALO wrote:
I believe there should be some additional things to consider, typically for
suppliers
where instead of communicating net prices to their [professional] clients,
there are:
We don't try to compute instead
On 2017-10-25 13:47, Richard PALO wrote:
> I believe there should be some additional things to consider, typically for
> suppliers
> where instead of communicating net prices to their [professional] clients,
> there are:
We don't try to compute instead of the supplier because you do not know
Le 25/10/2017 à 10:43, Cédric Krier a écrit :
On 2017-10-24 08:29, Gonzalo wrote:
The problem is complex, I will try to explain it the best I can.
We are trying to use Tryton + GNU Health for a clinic. The clinic has
a kind of subscription/insurance where you paid an amount per month
and you
On 2017-10-25 10:30, Sergi Almacellas Abellana wrote:
> El 24/10/17 a les 17:29, Gonzalo ha escrit:
> > So should be able to know the amount of this products/services uses by a
> > person in the last month, and the price will depend on this. >
> The sale_promotion [2] module can be used to
On 2017-10-24 08:29, Gonzalo wrote:
> The problem is complex, I will try to explain it the best I can.
> We are trying to use Tryton + GNU Health for a clinic. The clinic has
> a kind of subscription/insurance where you paid an amount per month
> and you get an amount of services to use (for
El 24/10/17 a les 17:29, Gonzalo ha escrit:
First, sorry for my english.
The problem is complex, I will try to explain it the best I can.
We are trying to use Tryton + GNU Health for a clinic. The clinic has a kind of
subscription/insurance where you paid an amount per month and you get an
First, sorry for my english.
The problem is complex, I will try to explain it the best I can.
We are trying to use Tryton + GNU Health for a clinic. The clinic has a kind of
subscription/insurance where you paid an amount per month and you get an amount
of services to use (for example, 3
14 matches
Mail list logo