Revision fd6f0f82
Von Kivitendo Admin vor mehr als 9 Jahren hinzugefügt
| SL/PriceSource.pm | ||
|---|---|---|
| 71 | 71 |
Each algorithm can access details of the record to realize dependencies on |
| 72 | 72 |
part, customer, vendor, date, quantity etc, which was previously not possible. |
| 73 | 73 |
|
| 74 |
=head1 BACKGROUND AND PHILOSOPY |
|
| 74 |
=head1 BACKGROUND AND PHILOSOPHY
|
|
| 75 | 75 |
|
| 76 | 76 |
sql ledger and subsequently Lx-Office had three prices per part: sellprice, |
| 77 | 77 |
listprice and lastcost. At the moment a part is loaded into a record, the |
| 78 |
applicable price is copied and after that free to be changed. |
|
| 78 |
applicable price is copied and after that it is free to be changed.
|
|
| 79 | 79 |
|
| 80 |
Later on additional things joined. Various types of discount, vendor pricelists
|
|
| 80 |
Later on additional things were added. Various types of discount, vendor pricelists
|
|
| 81 | 81 |
and the infamous price groups. The problem is not that those didn't work, the |
| 82 |
problem is, that they had to guess to much when to change a price with the |
|
| 83 |
available price from database, and when to leave the user entered price. |
|
| 82 |
problem is, that they had to guess too much when to change a price with the
|
|
| 83 |
available price from the database, and when to leave the user entered price.
|
|
| 84 | 84 |
|
| 85 | 85 |
Unrelated to that, users asked for more ways to store special prices, based on |
| 86 | 86 |
qty (block pricing, bulk discount), based on date (special offers), based on |
Auch abrufbar als: Unified diff
Typos in PriceSource Doku