dolibarr-tasktrack
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dolibarr-tasktrack] [Task #1738] Add fields to product batch


From: Doliforge
Subject: [Dolibarr-tasktrack] [Task #1738] Add fields to product batch
Date: Sat, 17 Jan 2015 15:46:33 +0100

Doliforge
Ce message ne s'affiche pas correctement?
mettez à jour vos préférences utilisateur.

Add fields to product batch

Dernières modifications

17/01/2015 15:46 (Europe/Paris)
Yes, this is a good a solution also for answering the request of recording more than one barcode per product, and this is the one solution, because, if a barcode is different, so batch should be differnet :)

I've noticed a PR that went merged : https://github.com/Dolibarr/dolibarr/pull/2010/files
Thanks to FHenry but it seems quite "simple" when you compare files...

So for the moment extrafields that could be created for each batch :
-locations (stock's shelve, row, column...etc..)
-barcodes
-colli number
-notes...

Répondre

État

 Détails
Submitted by:  Francis Appels (fappels) Last Modified On:  16/01/2015 12:06
Submitted on:  03/12/2014 18:02 
Summary:  Add fields to product batch
Description:  A received colli can contain more information, as a guideline we can take the EAN-128 code spec (http://www.barcodeisland.com/uccean128.phtml#AI00). There should be at least a 'barcode' field to store the Colli barcode and a 'note' field to store some extra information about the received batch/colli.
Priority:  5 - Medium Open to Any Developer:  No
Subproject:  Module Products-Services Assigned to (multiple):  Aucun
Planned for version:   
 Etat
Start Date:  - End Date:  -
Completion (0-100%):  0 Status:  Open

Commentaires

Andriolo Hubert 17/01/2015 15:46
Yes, this is a good a solution also for answering the request of recording more than one barcode per product, and this is the one solution, because, if a barcode is different, so batch should be differnet :)

I've noticed a PR that went merged : https://github.com/Dolibarr/dolibarr/pull/2010/files
Thanks to FHenry but it seems quite "simple" when you compare files...

So for the moment extrafields that could be created for each batch :
-locations (stock's shelve, row, column...etc..)
-barcodes
-colli number
-notes...
Francis Appels 16/01/2015 12:06
Another extra parameter could be product_barcode.
If we make this a fixed parameter, we can let it override barcode of product, so when you receive a batch and read product barcode wich is different from product barcode the product_barcode field of product batch will be used.
The barcode search box and POS systems will also have to look in product batch.
Andriolo Hubert 14/01/2015 20:32
What can the batch have for useful extra-parameters ?
If I think about it :
-a "colli" tracking number (the supplier's shipment reference)
-its own barcode like, as described in your doc, for example the GS1 128 barcode with expiry date and batch
-its location in stock (could be more than a simple field, could be 3 or more fields like : Row / Shelve / Bin

Nothing more comes to my mind, so, would it be useful to create a dedicated screen for batches and extrafields ?

Off course it could be more user-friendly to let the user define its own "extrafields" if he needs more on this dedicated screen.
But for the moment, I think I haven't seen a module with a dedicated screen that can handle the display of many editable extrafields (except maybe on product card ?)

This functionnality may be over-sized for my own use... but maybe I didn't get the concept ;)
Francis Appels 14/01/2015 19:36
Dispatching products can have a lot of parameters.
So I propose to add extrafields to productbatch and work like this:
In Product Stock Tab: show list of batches with link on batch code.
When clicked, new card is shown with all parameters of batch including created extrafields.
The card will also contain the correctstock and tranfer buttons like the stock card.
In Supplier Dispatch Tab: also add 'batch code with link' to dispatched list.
When clicked also show editable batch card
Add 'return to stock button' or 'return to dispatch button' depending on Source.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]