Going by what you said let us analyse this problem. I would recommend giving it a good thought for this is going to be something that you would be using for a long time any haste in deciding the defining fields would later lead to a lot of problem.
Now coming back to the defining fields for the stones:
- Material : Granite/ Marble etc
- Color: White/ Red/Green/Black etc
- hardness: Shore hardness?
- Thickness: in mm (Float or Int) (Use mm instead of inches this is easier)
- Width : again use mm (Float or Int)
- Length : agains use mm (float or int)
Now if there are other fields as well then do add the fields in the system by using the custom fields. The type of field has been mentioned. Now once the fields are defined you could make them as mandatory and then make a naming series where you would define all sizes and when a new size comes you can just copy an existing item code.
Suggested naming convention for your item or stones would be G-WH-H-0000-0000-0000 where:
- G= Granite (Material)
- WH = White (Color)
- H = Hardness (define hardness in ranges)
- 0000 = Thickness, width and length (You could have less fields)
Though I would like to inform you that if you are thinking of getting away with making item codes then take my word for it and that is there is no running away from that, I myself have been finding a way to get away from this thing but now I am reconciled to the fact that we need to make item code.
On Friday, April 12, 2013 10:27:59 AM UTC+5:30, Satish wrote:
We are a stone trading and processing company. We buy stone slabs in lots. One lot might consist of 15 to 20 slabs. Though the stone in lot is similar in its properties like colour, hardness, thickness etc., there could be different dimension for each slab in the lot. Lets say slab number 1 is 48"x72", slab number 2 is 50"x84" and so on. How possibly can we manage such high variations in sizes in items. I have read a post where it was suggested that unique items be created for each item. Say a red shirt should be different from a green shirt even though the size is same. This may not be applicable in an item like stone. I believe that even industries which deal in items like sheet metals etc may be facing the same problem. Besides, I don’t see any place to enter the dimensions of the item.
Another problem is the thickness and finishes of the stone. Same stone might be available in various thicknesses, finishes. When combined with variations in sizes, this may create n number of combinations for which it might not be practically possible to create n number of items.
How do we handle such a situation.
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-user-forum+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.