31,034
edits
mNo edit summary Tag: 2017 source edit |
m (→Usage) Tag: 2017 source edit |
||
| Line 35: | Line 35: | ||
If you set a product to need such a number (whatever is a lot or a serial number), no stock movement will be allowed if you don't enter also this number/numero. | If you set a product to need such a number (whatever is a lot or a serial number), no stock movement will be allowed if you don't enter also this number/numero. | ||
The first time a lot/serial is known by Dolibarr, this lot/serial is recorded into table llx_product_lot with the date of creation. This record will remain indefinitely into this table. Also if you enter a Sell-by date or a Eat-by date, this date(s) will also be recorded into this table. This date are specific to a lot. So when making future stock movement, you don't have to re-enter this dates, the lot/serial number is enough. If you try to make a stock movement with an already existing lot and you try to force the Date Sell-by or Eat-by with a different date, the stock movement will be denied. Dates are expected only the first time a new lot appear, then they must be similar to the one defined the first time or they must not be provided. | The first time a lot/serial is known by Dolibarr, this lot/serial is recorded into table llx_product_lot with the date of creation. This record will remain indefinitely into this table. Also if you enter a Sell-by date or a Eat-by date, this date(s) will also be recorded into this table. This date are specific to a lot. So when making future stock movement, you don't have to re-enter this dates, the lot/serial number is enough. If you try to make a stock movement with an already existing lot and you try to force the Date Sell-by or Eat-by with a different date, the stock movement will be denied. Dates are expected only the first time a new lot appear, then they must be similar to the one defined the first time, or they must not be provided. | ||