[Supplier-Product] - How can apply more than one price for a product and a supplier.

[thangnguyen.Olbius]

Hi everyone!
In my case, at the same time we can have more than one prices for a product
and a supplier. The difference depends on something special, may be
quantity_uom_id.
How can we get that ?

--
*THANG NGUYEN (Mr)*

*OLBIUS DEVELOPER**Email:* [hidden email]
<[hidden email]>| *Mobile:* ([phone]

*OLBIUS., JSC*
*Tel:* ([phone]
*Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
*Website:* http://olbius.com

[taher]

Hello Thang,

There are probably multiple ways to achieve this. I think perhaps for your
situation you can use price rules ->
https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules

Taher Alkhateeb

On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]> wrote:

> Hi everyone!
> In my case, at the same time we can have more than one prices for a product
> and a supplier. The difference depends on something special, may be
> quantity_uom_id.
> How can we get that ?
>
> --
> *THANG NGUYEN (Mr)*
>
> *OLBIUS DEVELOPER**Email:* [hidden email]
> <[hidden email]>| *Mobile:* ([phone]
>
> *OLBIUS., JSC*
> *Tel:* ([phone]
> *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> *Website:* http://olbius.com
>

[thangnguyen.Olbius]

Thanks Taher!
If we use product_price_rule it will not map that rules with suppliers. Do
you have other ways ?

On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <[hidden email]
> wrote:

> Hello Thang,
>
> There are probably multiple ways to achieve this. I think perhaps for your
> situation you can use price rules ->
> https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
>
> Taher Alkhateeb
>
> On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]> wrote:
>
> > Hi everyone!
> > In my case, at the same time we can have more than one prices for a
> product
> > and a supplier. The difference depends on something special, may be
> > quantity_uom_id.
> > How can we get that ?
> >
> > --
> > *THANG NGUYEN (Mr)*
> >
> > *OLBIUS DEVELOPER**Email:* [hidden email]
> > <[hidden email]>| *Mobile:* ([phone]
> >
> > *OLBIUS., JSC*
> > *Tel:* ([phone]
> > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > *Website:* http://olbius.com
> >
>

--
*THANG NGUYEN (Mr)*

*OLBIUS DEVELOPER**Email:* [hidden email]
<[hidden email]>| *Mobile:* ([phone]

*OLBIUS., JSC*
*Tel:* ([phone]
*Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
*Website:* http://olbius.com

[taher]

Hi Thang.

Are you sure it won't map? What would stop you from defining in the
conditions a role type of supplier, and then the quantity and whatever
other conditions you have?

I think you can assign a role type of supplier with the specific supplier
partyId and a certain quantity in the price rules, that should do the job
no?

Taher Alkhateeb

On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <[hidden email]>
wrote:

> Thanks Taher!
> If we use product_price_rule it will not map that rules with suppliers. Do
> you have other ways ?
>
> On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
> [hidden email]
> > wrote:
>
> > Hello Thang,
> >
> > There are probably multiple ways to achieve this. I think perhaps for
> your
> > situation you can use price rules ->
> > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
> >
> > Taher Alkhateeb
> >
> > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]>
> wrote:
> >
> > > Hi everyone!
> > > In my case, at the same time we can have more than one prices for a
> > product
> > > and a supplier. The difference depends on something special, may be
> > > quantity_uom_id.
> > > How can we get that ?
> > >
> > > --
> > > *THANG NGUYEN (Mr)*
> > >
> > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > <[hidden email]>| *Mobile:* ([phone]
> > >
> > > *OLBIUS., JSC*
> > > *Tel:* ([phone]
> > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > > *Website:* http://olbius.com
> > >
> >
>
>
>
> --
> *THANG NGUYEN (Mr)*
>
> *OLBIUS DEVELOPER**Email:* [hidden email]
> <[hidden email]>| *Mobile:* ([phone]
>
> *OLBIUS., JSC*
> *Tel:* ([phone]
> *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> *Website:* http://olbius.com
>

[thangnguyen.Olbius]

That right, If made that way too complex. I thinks i should generate some
new entities to store that data.

On Wed, Sep 7, 2016 at 12:21 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hi Thang.
>
> Are you sure it won't map? What would stop you from defining in the
> conditions a role type of supplier, and then the quantity and whatever
> other conditions you have?
>
> I think you can assign a role type of supplier with the specific supplier
> partyId and a certain quantity in the price rules, that should do the job
> no?
>
> Taher Alkhateeb
>
> On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <[hidden email]>
> wrote:
>
> > Thanks Taher!
> > If we use product_price_rule it will not map that rules with suppliers.
> Do
> > you have other ways ?
> >
> > On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
> > [hidden email]
> > > wrote:
> >
> > > Hello Thang,
> > >
> > > There are probably multiple ways to achieve this. I think perhaps for
> > your
> > > situation you can use price rules ->
> > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
> > >
> > > Taher Alkhateeb
> > >
> > > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]>
> > wrote:
> > >
> > > > Hi everyone!
> > > > In my case, at the same time we can have more than one prices for a
> > > product
> > > > and a supplier. The difference depends on something special, may be
> > > > quantity_uom_id.
> > > > How can we get that ?
> > > >
> > > > --
> > > > *THANG NGUYEN (Mr)*
> > > >
> > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > <[hidden email]>| *Mobile:* ([phone]
> > > >
> > > > *OLBIUS., JSC*
> > > > *Tel:* ([phone]
> > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> VietNam
> > > > *Website:* http://olbius.com
> > > >
> > >
> >
> >
> >
> > --
> > *THANG NGUYEN (Mr)*
> >
> > *OLBIUS DEVELOPER**Email:* [hidden email]
> > <[hidden email]>| *Mobile:* ([phone]
> >
> > *OLBIUS., JSC*
> > *Tel:* ([phone]
> > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > *Website:* http://olbius.com
> >
>

--
*THANG NGUYEN (Mr)*

*OLBIUS DEVELOPER**Email:* [hidden email]
<[hidden email]>| *Mobile:* ([phone]

*OLBIUS., JSC*
*Tel:* ([phone]
*Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
*Website:* http://olbius.com

[taher]

Hi Thang,

Sure, but if you define new entities then you should fix all the screens
and add services and business logic to handle it. I think this would be
much more work than defining price rules. I think of price rules sort of
like email filters, just a bunch of conditions to make a price, nothing too
difficult.

Anyway, if you do decide to go with new entities make sure of fixing the
order screens appropriately for the price retrieval logic.

Taher Alkhateeb

On Sep 7, 2016 8:33 AM, "thang nguyen" <[hidden email]> wrote:

> That right, If made that way too complex. I thinks i should generate some
> new entities to store that data.
>
> On Wed, Sep 7, 2016 at 12:21 PM, Taher Alkhateeb <
> [hidden email]
> > wrote:
>
> > Hi Thang.
> >
> > Are you sure it won't map? What would stop you from defining in the
> > conditions a role type of supplier, and then the quantity and whatever
> > other conditions you have?
> >
> > I think you can assign a role type of supplier with the specific supplier
> > partyId and a certain quantity in the price rules, that should do the job
> > no?
> >
> > Taher Alkhateeb
> >
> > On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <[hidden email]>
> > wrote:
> >
> > > Thanks Taher!
> > > If we use product_price_rule it will not map that rules with suppliers.
> > Do
> > > you have other ways ?
> > >
> > > On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
> > > [hidden email]
> > > > wrote:
> > >
> > > > Hello Thang,
> > > >
> > > > There are probably multiple ways to achieve this. I think perhaps for
> > > your
> > > > situation you can use price rules ->
> > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
> > > >
> > > > Taher Alkhateeb
> > > >
> > > > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]>
> > > wrote:
> > > >
> > > > > Hi everyone!
> > > > > In my case, at the same time we can have more than one prices for a
> > > > product
> > > > > and a supplier. The difference depends on something special, may be
> > > > > quantity_uom_id.
> > > > > How can we get that ?
> > > > >
> > > > > --
> > > > > *THANG NGUYEN (Mr)*
> > > > >
> > > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > > <[hidden email]>| *Mobile:* ([phone]
> > > > >
> > > > > *OLBIUS., JSC*
> > > > > *Tel:* ([phone]
> > > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> > VietNam
> > > > > *Website:* http://olbius.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > *THANG NGUYEN (Mr)*
> > >
> > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > <[hidden email]>| *Mobile:* ([phone]
> > >
> > > *OLBIUS., JSC*
> > > *Tel:* ([phone]
> > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > > *Website:* http://olbius.com
> > >
> >
>
>
>
> --
> *THANG NGUYEN (Mr)*
>
> *OLBIUS DEVELOPER**Email:* [hidden email]
> <[hidden email]>| *Mobile:* ([phone]
>
> *OLBIUS., JSC*
> *Tel:* ([phone]
> *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> *Website:* http://olbius.com
>

[Jacopo Cappellato-5]

Hi Thang ,

the SupplierProduct entity was designed to support multiple prices for the
same product and supplier based on different ordered quantity or different
currency; see the primary key:

<prim-key field="productId"/>
<prim-key field="partyId"/>
<prim-key field="currencyUomId"/>
<prim-key field="minimumOrderQuantity"/>
<prim-key field="availableFromDate"/>

Unfortunately the design of the SupplierProduct entity is far from being
clean and nice, and I am not sure if it is worth of modifying its
definition to support also prices for different UOMs as in your
requirements.
Maybe it would be better to enhance the Agreement* data model to define a
price list between the buyer and the seller (the supplier) and enhance
AgreementProductAppl to support different uoms; or you could define one
AgreementItem per UOM and list all the product with prices in that UOM as
AgreementProductAppl.

Regards,

Jacopo

On Wed, Sep 7, 2016 at 7:33 AM, thang nguyen <[hidden email]>
wrote:

> That right, If made that way too complex. I thinks i should generate some
> new entities to store that data.
>
> On Wed, Sep 7, 2016 at 12:21 PM, Taher Alkhateeb <
> [hidden email]
> > wrote:
>
> > Hi Thang.
> >
> > Are you sure it won't map? What would stop you from defining in the
> > conditions a role type of supplier, and then the quantity and whatever
> > other conditions you have?
> >
> > I think you can assign a role type of supplier with the specific supplier
> > partyId and a certain quantity in the price rules, that should do the job
> > no?
> >
> > Taher Alkhateeb
> >
> > On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <[hidden email]>
> > wrote:
> >
> > > Thanks Taher!
> > > If we use product_price_rule it will not map that rules with suppliers.
> > Do
> > > you have other ways ?
> > >
> > > On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
> > > [hidden email]
> > > > wrote:
> > >
> > > > Hello Thang,
> > > >
> > > > There are probably multiple ways to achieve this. I think perhaps for
> > > your
> > > > situation you can use price rules ->
> > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
> > > >
> > > > Taher Alkhateeb
> > > >
> > > > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]>
> > > wrote:
> > > >
> > > > > Hi everyone!
> > > > > In my case, at the same time we can have more than one prices for a
> > > > product
> > > > > and a supplier. The difference depends on something special, may be
> > > > > quantity_uom_id.
> > > > > How can we get that ?
> > > > >
> > > > > --
> > > > > *THANG NGUYEN (Mr)*
> > > > >
> > > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > > <[hidden email]>| *Mobile:* ([phone]
> > > > >
> > > > > *OLBIUS., JSC*
> > > > > *Tel:* ([phone]
> > > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> > VietNam
> > > > > *Website:* http://olbius.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > *THANG NGUYEN (Mr)*
> > >
> > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > <[hidden email]>| *Mobile:* ([phone]
> > >
> > > *OLBIUS., JSC*
> > > *Tel:* ([phone]
> > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > > *Website:* http://olbius.com
> > >
> >
>
>
>
> --
> *THANG NGUYEN (Mr)*
>
> *OLBIUS DEVELOPER**Email:* [hidden email]
> <[hidden email]>| *Mobile:* ([phone]
>
> *OLBIUS., JSC*
> *Tel:* ([phone]
> *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> *Website:* http://olbius.com
>

[thangnguyen.Olbius]

Thanks!
We still use last_price in supplier_product as default price. The new
entities only using for special cases and we need setting up some trigger
before order to save time. About screens, i'll take options for end user
choosing, inside price will be calculate automatic and not change logical
of order services.

On Wed, Sep 7, 2016 at 12:39 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hi Thang,
>
> Sure, but if you define new entities then you should fix all the screens
> and add services and business logic to handle it. I think this would be
> much more work than defining price rules. I think of price rules sort of
> like email filters, just a bunch of conditions to make a price, nothing too
> difficult.
>
> Anyway, if you do decide to go with new entities make sure of fixing the
> order screens appropriately for the price retrieval logic.
>
> Taher Alkhateeb
>
> On Sep 7, 2016 8:33 AM, "thang nguyen" <[hidden email]> wrote:
>
> > That right, If made that way too complex. I thinks i should generate some
> > new entities to store that data.
> >
> > On Wed, Sep 7, 2016 at 12:21 PM, Taher Alkhateeb <
> > [hidden email]
> > > wrote:
> >
> > > Hi Thang.
> > >
> > > Are you sure it won't map? What would stop you from defining in the
> > > conditions a role type of supplier, and then the quantity and whatever
> > > other conditions you have?
> > >
> > > I think you can assign a role type of supplier with the specific
> supplier
> > > partyId and a certain quantity in the price rules, that should do the
> job
> > > no?
> > >
> > > Taher Alkhateeb
> > >
> > > On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <
> [hidden email]>
> > > wrote:
> > >
> > > > Thanks Taher!
> > > > If we use product_price_rule it will not map that rules with
> suppliers.
> > > Do
> > > > you have other ways ?
> > > >
> > > > On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
> > > > [hidden email]
> > > > > wrote:
> > > >
> > > > > Hello Thang,
> > > > >
> > > > > There are probably multiple ways to achieve this. I think perhaps
> for
> > > > your
> > > > > situation you can use price rules ->
> > > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
> > > > >
> > > > > Taher Alkhateeb
> > > > >
> > > > > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]>
> > > > wrote:
> > > > >
> > > > > > Hi everyone!
> > > > > > In my case, at the same time we can have more than one prices
> for a
> > > > > product
> > > > > > and a supplier. The difference depends on something special, may
> be
> > > > > > quantity_uom_id.
> > > > > > How can we get that ?
> > > > > >
> > > > > > --
> > > > > > *THANG NGUYEN (Mr)*
> > > > > >
> > > > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > > > <[hidden email]>| *Mobile:* ([phone]
> > > > > >
> > > > > > *OLBIUS., JSC*
> > > > > > *Tel:* ([phone]
> > > > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> > > VietNam
> > > > > > *Website:* http://olbius.com
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > *THANG NGUYEN (Mr)*
> > > >
> > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > <[hidden email]>| *Mobile:* ([phone]
> > > >
> > > > *OLBIUS., JSC*
> > > > *Tel:* ([phone]
> > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> VietNam
> > > > *Website:* http://olbius.com
> > > >
> > >
> >
> >
> >
> > --
> > *THANG NGUYEN (Mr)*
> >
> > *OLBIUS DEVELOPER**Email:* [hidden email]
> > <[hidden email]>| *Mobile:* ([phone]
> >
> > *OLBIUS., JSC*
> > *Tel:* ([phone]
> > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > *Website:* http://olbius.com
> >
>

--
*THANG NGUYEN (Mr)*

*OLBIUS DEVELOPER**Email:* [hidden email]| *Mobile:* (+84)
1674636641

*OLBIUS., JSC*
*Tel:* ([phone]
*Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
*Website:* http://olbius.com

[thangnguyen.Olbius]

Hi Jacopo ,
I think using Agreement is ok with my case. But in small business, the
agreement sometime not enough flexibility, transaction between the seller
and the buyer only base on invoice and payment. The agreements only
contains some rules basically. I will try. Thanks!

On Wed, Sep 7, 2016 at 12:52 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Hi Thang ,
>
> the SupplierProduct entity was designed to support multiple prices for the
> same product and supplier based on different ordered quantity or different
> currency; see the primary key:
>
> <prim-key field="productId"/>
> <prim-key field="partyId"/>
> <prim-key field="currencyUomId"/>
> <prim-key field="minimumOrderQuantity"/>
> <prim-key field="availableFromDate"/>
>
> Unfortunately the design of the SupplierProduct entity is far from being
> clean and nice, and I am not sure if it is worth of modifying its
> definition to support also prices for different UOMs as in your
> requirements.
> Maybe it would be better to enhance the Agreement* data model to define a
> price list between the buyer and the seller (the supplier) and enhance
> AgreementProductAppl to support different uoms; or you could define one
> AgreementItem per UOM and list all the product with prices in that UOM as
> AgreementProductAppl.
>
> Regards,
>
> Jacopo
>
> On Wed, Sep 7, 2016 at 7:33 AM, thang nguyen <[hidden email]>
> wrote:
>
> > That right, If made that way too complex. I thinks i should generate some
> > new entities to store that data.
> >
> > On Wed, Sep 7, 2016 at 12:21 PM, Taher Alkhateeb <
> > [hidden email]
> > > wrote:
> >
> > > Hi Thang.
> > >
> > > Are you sure it won't map? What would stop you from defining in the
> > > conditions a role type of supplier, and then the quantity and whatever
> > > other conditions you have?
> > >
> > > I think you can assign a role type of supplier with the specific
> supplier
> > > partyId and a certain quantity in the price rules, that should do the
> job
> > > no?
> > >
> > > Taher Alkhateeb
> > >
> > > On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <
> [hidden email]>
> > > wrote:
> > >
> > > > Thanks Taher!
> > > > If we use product_price_rule it will not map that rules with
> suppliers.
> > > Do
> > > > you have other ways ?
> > > >
> > > > On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
> > > > [hidden email]
> > > > > wrote:
> > > >
> > > > > Hello Thang,
> > > > >
> > > > > There are probably multiple ways to achieve this. I think perhaps
> for
> > > > your
> > > > > situation you can use price rules ->
> > > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price+Rules
> > > > >
> > > > > Taher Alkhateeb
> > > > >
> > > > > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]>
> > > > wrote:
> > > > >
> > > > > > Hi everyone!
> > > > > > In my case, at the same time we can have more than one prices
> for a
> > > > > product
> > > > > > and a supplier. The difference depends on something special, may
> be
> > > > > > quantity_uom_id.
> > > > > > How can we get that ?
> > > > > >
> > > > > > --
> > > > > > *THANG NGUYEN (Mr)*
> > > > > >
> > > > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > > > <[hidden email]>| *Mobile:* ([phone]
> > > > > >
> > > > > > *OLBIUS., JSC*
> > > > > > *Tel:* ([phone]
> > > > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> > > VietNam
> > > > > > *Website:* http://olbius.com
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > *THANG NGUYEN (Mr)*
> > > >
> > > > *OLBIUS DEVELOPER**Email:* [hidden email]
> > > > <[hidden email]>| *Mobile:* ([phone]
> > > >
> > > > *OLBIUS., JSC*
> > > > *Tel:* ([phone]
> > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
> VietNam
> > > > *Website:* http://olbius.com
> > > >
> > >
> >
> >
> >
> > --
> > *THANG NGUYEN (Mr)*
> >
> > *OLBIUS DEVELOPER**Email:* [hidden email]
> > <[hidden email]>| *Mobile:* ([phone]
> >
> > *OLBIUS., JSC*
> > *Tel:* ([phone]
> > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> > *Website:* http://olbius.com
> >
>

--
*THANG NGUYEN (Mr)*

*OLBIUS DEVELOPER**Email:* [hidden email]| *Mobile:* (+84)
1674636641

*OLBIUS., JSC*
*Tel:* ([phone]
*Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
*Website:* http://olbius.com

[thangnguyen.Olbius]

I decided using minimumOrderQuantity to check and apply price for
order_item. Thanks all!

Cheers!

On Wed, Sep 7, 2016 at 1:29 PM, thang nguyen <[hidden email]>
wrote:

> Hi Jacopo ,
> I think using Agreement is ok with my case. But in small business, the
> agreement sometime not enough flexibility, transaction between the seller
> and the buyer only base on invoice and payment. The agreements only
> contains some rules basically. I will try. Thanks!
>
> On Wed, Sep 7, 2016 at 12:52 PM, Jacopo Cappellato <jacopo.cappellato@
> hotwaxsystems.com> wrote:
>
>> Hi Thang ,
>>
>> the SupplierProduct entity was designed to support multiple prices for the
>> same product and supplier based on different ordered quantity or different
>> currency; see the primary key:
>>
>> <prim-key field="productId"/>
>> <prim-key field="partyId"/>
>> <prim-key field="currencyUomId"/>
>> <prim-key field="minimumOrderQuantity"/>
>> <prim-key field="availableFromDate"/>
>>
>> Unfortunately the design of the SupplierProduct entity is far from being
>> clean and nice, and I am not sure if it is worth of modifying its
>> definition to support also prices for different UOMs as in your
>> requirements.
>> Maybe it would be better to enhance the Agreement* data model to define a
>> price list between the buyer and the seller (the supplier) and enhance
>> AgreementProductAppl to support different uoms; or you could define one
>> AgreementItem per UOM and list all the product with prices in that UOM as
>> AgreementProductAppl.
>>
>> Regards,
>>
>> Jacopo
>>
>> On Wed, Sep 7, 2016 at 7:33 AM, thang nguyen <[hidden email]>
>> wrote:
>>
>> > That right, If made that way too complex. I thinks i should generate
>> some
>> > new entities to store that data.
>> >
>> > On Wed, Sep 7, 2016 at 12:21 PM, Taher Alkhateeb <
>> > [hidden email]
>> > > wrote:
>> >
>> > > Hi Thang.
>> > >
>> > > Are you sure it won't map? What would stop you from defining in the
>> > > conditions a role type of supplier, and then the quantity and whatever
>> > > other conditions you have?
>> > >
>> > > I think you can assign a role type of supplier with the specific
>> supplier
>> > > partyId and a certain quantity in the price rules, that should do the
>> job
>> > > no?
>> > >
>> > > Taher Alkhateeb
>> > >
>> > > On Wed, Sep 7, 2016 at 7:46 AM, thang nguyen <
>> [hidden email]>
>> > > wrote:
>> > >
>> > > > Thanks Taher!
>> > > > If we use product_price_rule it will not map that rules with
>> suppliers.
>> > > Do
>> > > > you have other ways ?
>> > > >
>> > > > On Wed, Sep 7, 2016 at 10:48 AM, Taher Alkhateeb <
>> > > > [hidden email]
>> > > > > wrote:
>> > > >
>> > > > > Hello Thang,
>> > > > >
>> > > > > There are probably multiple ways to achieve this. I think perhaps
>> for
>> > > > your
>> > > > > situation you can use price rules ->
>> > > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Price
>> +Rules
>> > > > >
>> > > > > Taher Alkhateeb
>> > > > >
>> > > > > On Sep 7, 2016 4:47 AM, "thang nguyen" <[hidden email]
>> >
>> > > > wrote:
>> > > > >
>> > > > > > Hi everyone!
>> > > > > > In my case, at the same time we can have more than one prices
>> for a
>> > > > > product
>> > > > > > and a supplier. The difference depends on something special,
>> may be
>> > > > > > quantity_uom_id.
>> > > > > > How can we get that ?
>> > > > > >
>> > > > > > --
>> > > > > > *THANG NGUYEN (Mr)*
>> > > > > >
>> > > > > > *OLBIUS DEVELOPER**Email:* [hidden email]
>> > > > > > <[hidden email]>| *Mobile:* ([phone]
>> > > > > >
>> > > > > > *OLBIUS., JSC*
>> > > > > > *Tel:* ([phone]
>> > > > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
>> > > VietNam
>> > > > > > *Website:* http://olbius.com
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > *THANG NGUYEN (Mr)*
>> > > >
>> > > > *OLBIUS DEVELOPER**Email:* [hidden email]
>> > > > <[hidden email]>| *Mobile:* ([phone]
>> > > >
>> > > > *OLBIUS., JSC*
>> > > > *Tel:* ([phone]
>> > > > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City,
>> VietNam
>> > > > *Website:* http://olbius.com
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > *THANG NGUYEN (Mr)*
>> >
>> > *OLBIUS DEVELOPER**Email:* [hidden email]
>> > <[hidden email]>| *Mobile:* ([phone]
>> >
>> > *OLBIUS., JSC*
>> > *Tel:* ([phone]
>> > *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
>> > *Website:* http://olbius.com
>> >
>>
>
>
>
> --
> *THANG NGUYEN (Mr)*
>
> *OLBIUS DEVELOPER**Email:* [hidden email]| *Mobile:* (+84)
> 1674636641
>
> *OLBIUS., JSC*
> *Tel:* ([phone]
> *Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
> *Website:* http://olbius.com
>

--
*THANG NGUYEN (Mr)*

*OLBIUS DEVELOPER**Email:* [hidden email]| *Mobile:* (+84)
1674636641

*OLBIUS., JSC*
*Tel:* ([phone]
*Address: *25th Fl., No 91, Nguyen Chi Thanh St., Ha Noi City, VietNam
*Website:* http://olbius.com