c2c-oerpscenario team mailing list archive

[Jonathan Wilson <786081@xxxxxxxxxxxxxxxxxx>]

HI Olivier

Thanks for the input...I have replied on
launchpad<https://bugs.launchpad.net/bugs/786081>
.

Hope all is well with you and at OpenERP. Activity is picking up here.

Best regards
Jon

On 9 June 2011 20:33, Olivier Dony (OpenERP)
<786081@xxxxxxxxxxxxxxxxxx>wrote:

> @Mayur: perhaps we should wait for handling this bug until we are clear
> on the desired behavior. I'm setting the status to "Triaged" to indicate
> that it is being escalated and discussed.
>
> @Jon:
> Hi :-)  As you noticed yourself, this is the current expected behavior of
> the system and is consistent with the general rule, which is: every
> pricelist should have a set of versions that makes it valid at any moment it
> is used.
>
> The system blocks your action because you may not be aware that the
> pricelist has now expired, so using another one silently may not be what
> you expect either. I think you could have instead copied the A-V1
> pricelist to make a variation A-V2 with the promotion, restricting the
> date ranges of both versions so they do not overlap.
>
> However, I agree that this is not very flexible. What about this: perhaps
> we should allow overlapping pricelist versions, and add a sequence number on
> the versions. Having several overlapping versions would mean that we can try
> the next version in the order of the sequence if no rule matched in the
> previous one.  The idea is almost like having pricelist rules that can be
> directly limited in time, but here we'd still wrap them in pricelist
> versions because we'd need to keep the current concept of versions, as some
> companies need to use them that way.
> With this, it means you could just add a temporary version of your
> pricelist with just the rule for the promotion, and the rest would stay the
> same. Your temporary pricelist would then expire automatically, with no
> further consequences.  I think this makes it more explicit than using
> different pricelists: in your example pricelist B makes no sense on its own,
> it's hard to guess what price is going to be applied for other products or
> when it becomes expired. Pricelist A also becomes more difficult to read.
>
> Opinions?
>
> ** Changed in: openobject-addons
>       Status: In Progress => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/786081
>
> Title:
>  Pricelist versions with overlapping dates do not locate correct
>  version
>
> Status in OpenERP Modules (addons):
>   Triaged
>
> Bug description:
>  Steps to reproduce:
>  1) Create price list (A) version 1 (A-V1) that (say) gives 10% off all
> products for all dates - Line A-V1.1(sequence =5)
>  2) Create another price list (B) version 1 (B-V1) that gives a fixed price
> on one product (P1) for a date range (promotion pricing)
>  3) On price list A-V1 insert a line that references price list B so that
> for the nominated date range on B price list B will apply for the selected
> item in B. Make sure the promotional pricing line has a sequence number to
> make it the first line selected when looking for a price - Line
> AV1.2(sequence=1)
>  4) Enter a sales order and create a line selling the promotional item P1.
> Make sure the sales order date is outside the promotional date range
> specified on B-V1 price list
>
>  Result observed:
>  OpenERP displays the error message "At least one price list has no active
> version!" (In fact it does not matter which item is ordered the same message
> is displayed)
>
>  Expected result:
>  The system should NOT fail on looking up a price on the Line
> AV1.2(sequence=1) (promo line). It should keep looking on the price list
> going to Line A-V1.1(sequence =5) which would give the normal 10% discount.
>
>  If this a "by design" rather than a bug, then I suggest we call it a
>  bug since if the system behaved as I expected it would make it much
>  more flexible for doing promotional pricing, i.e. the system should
>  only give an error message if all lines on the price list have failed
>  to deliver a price, not fail on the first line that references a price
>  list that has expired.
>
>  Version: addons 6 trunk  rev 4577
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/786081/+subscriptions
>


-- 
Jonathan Wilson
www.WillowIT.com.au
mob: 04 000 17 444

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/786081

Title:
  Pricelist versions with overlapping dates do not locate correct
  version

Status in OpenERP Modules (addons):
  Triaged

Bug description:
  Steps to reproduce:
  1) Create price list (A) version 1 (A-V1) that (say) gives 10% off all products for all dates - Line A-V1.1(sequence =5)
  2) Create another price list (B) version 1 (B-V1) that gives a fixed price on one product (P1) for a date range (promotion pricing)
  3) On price list A-V1 insert a line that references price list B so that for the nominated date range on B price list B will apply for the selected item in B. Make sure the promotional pricing line has a sequence number to make it the first line selected when looking for a price - Line AV1.2(sequence=1)
  4) Enter a sales order and create a line selling the promotional item P1. Make sure the sales order date is outside the promotional date range specified on B-V1 price list

  Result observed:
  OpenERP displays the error message "At least one price list has no active version!" (In fact it does not matter which item is ordered the same message is displayed)

  Expected result:
  The system should NOT fail on looking up a price on the Line AV1.2(sequence=1) (promo line). It should keep looking on the price list going to Line A-V1.1(sequence =5) which would give the normal 10% discount. 

  If this a "by design" rather than a bug, then I suggest we call it a
  bug since if the system behaved as I expected it would make it much
  more flexible for doing promotional pricing, i.e. the system should
  only give an error message if all lines on the price list have failed
  to deliver a price, not fail on the first line that references a price
  list that has expired.

  Version: addons 6 trunk  rev 4577

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/786081/+subscriptions