[ 
https://issues.apache.org/jira/browse/OFBIZ-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043211#comment-17043211
 ] 

Pierre Smits commented on OFBIZ-7610:
-------------------------------------

It can be so that a new price is set in the supplier price in the product, even 
though there is an agreement which states an initial price. We have to keep in 
mind that there may be conditions in the agreement (or even outside of the 
agreement) that are applicable to the future purchase price of a product of the 
supplier. And that can be set in the 
https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductSuppliers?productId=GZ-1000

With given solution, when a purchase order is create, it only looks at the 
purchase price of the product in the agreement. IMO, this is to strict.

> Product Price set based on 'Purchase Price Agreement' isn't honoured while 
> same is used during ordering
> -------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-7610
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7610
>             Project: OFBiz
>          Issue Type: Bug
>          Components: order
>    Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, 
> Release Branch 18.12
>            Reporter: Swapnil Shah
>            Assignee: Suraj Khurana
>            Priority: Major
>             Fix For: 17.12.01, 18.12.01
>
>         Attachments: OFBIZ-7610.patch, SA_1.png, SA_2.png, SA_3.png, 
> SA_4.png, SA_5.png
>
>
> Once any Purchase Agreement is created with supplier for certain products at 
> pre-determined price, its get successfully transformed into SupplierProduct. 
> But at the time of Purchase order creation is same agreement is enforced then 
> agreement prices for products are ignored while setting the price on cart and 
> eventually on order itself.
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to