Part Controller - callbacks für Artikel speichern und löschen

[kivitendo-erp.git] / SL / PriceSource.pm

diff --git a/SL/PriceSource.pm b/SL/PriceSource.pm
index ae0017c362a5b62f7cd6f798ab7257876656472c..831f68ebc99a0d035ac07d8053b16ca556b08d2a 100644 (file)
--- a/SL/PriceSource.pm
+++ b/SL/PriceSource.pm
@@ -149,8 +149,12 @@ and it is up to the user to change a price.
 
 =item 2.
 
 
 =item 2.
 

-If a price is set from a source, it is read only. A price edited manually is by
-definition not a sourced price.
+If a price is set from a source then the system will try to prevent the user
+from messing it up. By default this means the price will be read-only.
+Implementations can choose to make prices editable, but even then deviations
+from the calculatied price will be marked.
+
+A that is not set from a source will not have any of this.

 
 =item 3.
 
 
 =item 3.
 


@@ -285,12 +289,6 @@ to be aware of units and price_factors. This is madness.
 
 =item *
 
 
 =item *
 

-A common complaint is that prices from certain vendors are always negotiated
-and should use a default value but must be editable (like free prices) by
-default. This should be orthogonal for all prices.
-
-=item *
-

 The current implementation of lastcost is useless. Since it's one of the
 master_data prices it will always compete with listprice. But in real scenarios
 the listprice tends to go up, while lastcost stays the same, so lastcost
 The current implementation of lastcost is useless. Since it's one of the
 master_data prices it will always compete with listprice. But in real scenarios
 the listprice tends to go up, while lastcost stays the same, so lastcost