We have tried to test the ADempiere for the Product with Multiple Attributes in Ordering and also in Inventory by a Single Product Information, for example, there is a situation to use One "T-Shirt" Product with Color (Red/Blue/Green) and Size (Small/Medium/Large) for processing its Ordering and Inventory with its Color and Size.
For our testing of the above example, we have defined two Attributes (Color & Size) as "Instance Attribute" with linked to a Attribute Set with "When Shipping" Mandatory Type. And then we create a New Product using this Attribute Set without Value Selected in here.
Next, we create a "Standard Order" Sales Order to order the above Product with the selected values of Attribute Set Instance (e.g. Red/Large), then we got an Error Message "Insufficient Qty on Hand" and unable to Save the Sales Order Line. Hence, we can't make a sales order of Product with Attribute Set Instance in "Instance Attribute" Type.
Hence, would anyone know how to define the Product Attribute with Color and Size as "Instance Attribute" for Ordering and Inventory Movement? Thank you.
Kindly regards,
aobahopkins
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have posted something similar. I got it to work one step further. You need to book stock in with this particular instance. I guess, you purchased stock, so you need to do a PO (select the product and complete the details in the product instance tap for the items), vendor invoice and ship/receipt. You can check the quantities on hand in the product info.
I struggle with the next step: to select the specific instance in a sales order. If you have worked this out, please let me know.
Gunda
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
re: Error Message "Insufficient Qty on Hand" and unable to Save the Sales Order Line
I haven't used attributes so perhaps we are talkng about a different message... but typically if I enter a product for which there is no stock available, I get a message "No Inventory Available" .. but this is just a warning! I click ok and can save the line and continue! I can alco complete the document, but of course it cannot be shipped as the stock is not available. This lack of stock will feed into the replenishment report! and when the stock finally does arrive the order will (assuming any other rules are met) now appear as a shipable order.
colin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your reply. For the above Error Message, it is occurred in a Sales Order if the Product is assign a "Attribute Set" which is a "Instance Attribute". And also, we have tried to create a Purchase Order and to perform Purchase Receipt of this PO, the Same Error Message is occurred for creating Sales Order of this Product with Same Attribute Set Instance Value of Purchase Order.
And also, according to the real business environment, the Purchase Order and its Receipt may not be performed before creating Sales Order of a Product with Specific Attribute Set Instance Value.
Hence, would anyone tell us how to solve this error with corresponding setting or trace it as a bug to be fixed in future release of ADempiere? Thank you.
Kindly regards,
aobahopkins
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi aobahopkins
Yes I was wrong sorry.
I had thought perhaps they they might be the same message but after translation from English to a translated version and then translated back for the purpose of posting in the forums that it was the same ... sorry about confusing you more!
I haven't implemented attributes myself so perhaps I should say nothing and leave it to others who have experience but in the absence of such people posting I can speculate; if it helps you reason out what the problem might be? So with that in mind; I think it comes down to this Instance Attribute. When we use the word instance we typically are talking about a unique existing item. So I'm working on a notebook model 4711 but the serial number on the bottom indentfies a unique instance of model 4711. So, likewise, when you select an Instance Attribue on an Order the system expects it to exist!
When you set the Instance Attribute flag on when creating a Attribute Set this is what it expects... the Attribute will indentify an instance ... the examples in GardenWorkld are Serial Number and Lot.
Again I don't know 100% but it was my understanding that the Attributes are not intended for creating sub-products. So again taking a Garden World example of T-Shirts .. they can be red, white & blue and in Sizes Small, Medium & Large are attributes. But to the system a T-Shirt is a T-Shirt .. the cost the same and are are equally exchangeable. So I would order a T-Shirts! Not 10 Large White T-Shirts! Notice how in the GardenWorld example the actually have two products TShirt-GL (Green & large) and TShirt-RL (Red-Large) so we can track & price them seperately. I think if the Attribute is important for you you need to do the same.
So what is the point of an Attribute you might ask? well my old compiere manual explains the difference as;
An Instance Attribute Set identifies a specific instance of a product while
An Non-Instance Atrribute Set is used for searching.
So you use it when someone asks "Do you have a small red t-shirt?" you go to your product search would enter in the attributes small & red and it will say we have 10xproduct number TShirt-SR in stock at such a location.
Look closely at how the TShirt & Fertiliser products in GardenWorld are defined and used!
While I guess that wasn't the answer you hoped for I hope that at least gives you some food for thought
colin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have encountered the same problem as well while I did the test on Adempiere 3.2.0. I think it's a ASI bug. It's should be fixed in the trunk. Please comment and try to reproduce as following steps:
1. Create an attribute set with instance attribute of Color and Size
2. Create a product with the attribute set created in Step 1
3. Create a Standard Order
4. Add a order line with the product created in Step 2 without ASI and Save (it'd be successful with qty warning message)
5. Add a order line with the product created in Step 2 with ASI (Color and Size) and Save (it'd be failure with qty error message "Insufficient Qty on hand")
I think it wouldn't prohibit you place an order no matter what the stock level of such product. Or is there any system parameter to control this behavior?
beta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think it's a bug beta, but a misunderstanding of what the attributes are.
There are two types of attributes & attribute sets; Instance and non-instance.
A common “instance” attribute is a serial number. It identifies, uniquely, a specific instance of a product.
Attributes such as colour & size are “non-instance” attributes... many products can & will have the same value so the attribute in itself does not identify the product, it is simply descriptive.
When an AttributeSet includes an instance attribute its “Instance Attribute” flag is set positive.
Now when you create a Sales Order, the order line allows you to specify a “Attribute Set Instance” - not an attribute set but an instance of an attribute set.
So you cannot, for example, order a blue car but a car with the instance attribute VIN number = 12345 is ok.
Not a widescreen notebook but a notebook with the serial number SN654234.
So the error message you are referring to is saying equivalent ... we don't have a product (i.e. we have zero quantity of) with instance attribute "Red" "Small" as if Red an Small were unique instance identifiers.
And you are correct in that normally it does not matter how many of a product you have in stock at the moment of Sales Order entry. But in this instance you are indicating you, by entering the Attribute Set Instance, that you are selling a unique/specific instance of a product and the application is saying ... we don't have that instance.
If you need, for example, to manage T-Shirts in sizes Small, Medium & Large you need to create product numbers for each.
So what is the purpose of the non-instance attributes then?
Well they are simply descriptive. In the T-Shirt example in gardenWorld, it allows you to search for a product. If someone asks do you have a Shirt in size Large and colour Green you can fill these values in in the Product Search and it might respond with, “yes we have a quantity of 10 of the product number “TShirt-GL”. You might also have other stocks of clothing so it might also say ... and quantity 5 of product number “Cotton-Shirt-GL” with these attributes. The product is not T-Shirt & Cotton Shirt but rather you must create a product for each combination you wish to track.
I hope I haven't confused you further.
colin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's very nice explanation. Thanks. It makes clear about the difference between instance and non-instance attribute set. Maybe it's the purpose of the attribute set and the intention of the original designer to design such feature. I just doubt that it may not be applicable to real situation unless heavy customization has made.
Our corporate is a manufacturing firm and we would face some nasty problems if I take advantage of the ASI in it's original design feature as you said:
1. high admin costs.
- Define a non-instance attribute set for style, color and size
- Define a product for each style, color and size combination, normally a style could have 10 colors and ~20 sizes
- All same style of different color and size share the same price and cost
- Normally, color or color codename are known since customers have placed an order, i.e. when issuing a standard order
- It's error-prone to admin huge amount of the same product with different AS value only
2. interface not user-friendly
- Imagine how heavy the daily workload would be in using the as-is Adempiere/Compiere version in entering the serial no during an simple inventory move, for example, only one product of qty 1000
To get around this practical problem, I think ASI needs further enhancement to cater for different industrial needs flexibly. My suggestion are:
1. Attribute supports table type, just like Reference List, besides List
2. ASI dialog support fields in Search field type besides List
3. New mixed approach in ASI, inbetween instance and non-instance AS. Let users define, e.g. color and size, non-instance nature attributes in a instance attribute way (Hope you can understand what I mean)
Could you give me advice or direct me to another threads discussing about the ASI debate or problem?
beta
-
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm in a bit of a rush today so I only have time for a quick answer.
Yes I agree with most of what you say.
There are some scenarios where the current setup works ok. In my current project for example... lucky me :) The client is a reseller of engineering consumables (i.e. cutting tools, drill bits & blades etc). They have a possible product list of 200K plus products as their suppliers sell the products in a wide variety of attributes... but the suppliers number each variation as a separate product .... hence the 200k plus numbers. But finding the right product number in a list of 200k can be an issue so being able to select a 75mm titanium bit with a 5mm diameter and diamond edges is made a lot easier with the use of attributes.
But I fully accept that it does not work in all cases.
I'm torn as to if (as an example) a large green T-shirt is the same as a red small T-shirt; I can think of arguments for and against. But regardless I agree it should be easy! ... and flexible enough to cover all our needs.
From my experience, what I think is missing in adempiere is a "sales configurator". If we take a product we all here have experience of ... computers. We choose a model but then we can add more memory, extra disks perhaps options on the CPU ... but it's still the same basic model that we order. It is possible, in this situation, to create a BOM including the different options and use the "BOM Drop" to make the selection and add to an Order. But I don't think it could, in any sense, be considered user friendly.
Thanks for kindly reply and advice. I have a more completed understanding about the design and purpose of the instance and non-instance attribute set now. It maybe fit for all general cases but it's not fit for garment industry, at least.
That make me recall the experience years ago about using the Oracle Apps 11i feature - the Flexfield, which just like ADempiere instance attribute set for non-instance attributes, e.g. define color and size as instance attribute and enter those info in an order.
Maybe I take the other way to make a separate customization module on ASI for garment industry to make user experience to ADempiere more friendly.
Could you mind to tell more about the sales configurator? Or it's included in the coming release?
beta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> It maybe fit for all general cases but it's not fit for garment industry, at least.
Actually I didn't mean that ... just that I was lucky it suited my "current" project.
And I think most peoples' initial understanding or expections (my own included) of the functionality are as you understood - but alas it is not currently so. I have zero experience of the garment industry (except as a customer :)) so I couldn't comment. The closest I came was reading the white papers & documentation on ERP5 which I understood was devevlop for precisely that industry. Not that I am suggesting you leave us for them :) but that perhaps you can help us match them!
My own experience has been "mostly" in the electronic manufacturing & services where the concept of a system configuration is common. I'm not sure how well that concept would suit the garment industry!? And the only information I have is that in the wiki... but perhaps some that are involved could enlighten you further.
colin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am facing the same problem as Beta. The explanation and work flow that Colin gave cleared the current functionality in Adempiere. However it makes things very difficult practically. We buy products for manufacturing which are defined by the international standards, material, thickness, ratings etc. For the same product there are a about 15 standards 10 types of material, 3 types of thickness, 10 type of rating ....
As per the current functionality the number of products variants that we will need to enter for each product will be 4500. There are hundred different types of products that we need to buy. Assuming only 100 products to be bought, it makes it at minimum 450,000 records for the products that we buy. To further compound the issue, for each product you need to enter the business partners again. With an average of 10 vendor for each product will mean 4,500,000 additional records. You can understand the enormity of the job and the cost involved. The standards are reviewed every few years and a change in section or code will make the whole exercise useless.
On the other hand if you define all the attributes independently and use the combinations are per the requirements the amount of data to be entered is 10(standards)+3(thickness)+10(rating)+100(products)+10(vendors) = 133.
Looking at the functionality, and reading some manuals I got the feeling that the original intent of attributes was to define a single product with different variants being defined in attributes. You can use the product and attributes to completely define the product for either a sales order, purchase order etc.
I feel that this functionality is required if Adempiere has be be successful in the production industry where a large variants are required as raw material and as finished products.
-Amit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>I feel that this functionality is required if Adempiere has be be successful in the >production industry where a large variants are required as raw material and as >finished products.
I really believe that every problem has proper solution, but it all depends how much effrot someone is ready to put in order to solve it. Before 2 years i worked for a Bulgarian company which extended Product attributes and made price depndent on Product Attributes. The same company used the system to track sales of Newspapers. So we had 200 products and each day we had new newspaper issues, which was new value of Product Attribute Set Instance. So i think that everything can be fixed and made to work as company desire.
Kind regards,
Trifon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I met now exactly the same problem Bata and Amit asked in this post 3 years ago. And just searched the forum and found this post.
After checking the codes, I feel Colin's answer for "Error Message "Insufficient Qty on Hand" is not correct. This can be solved simplely by selecting "Select existing record" Attribute Set Instance dialog (click order line's attribute set instance field button). And then just click save, then there will be no error message. Please correct me if I am wrong.
I feel that we can use instance attribute set to deal with garment industry or any kind of requests with variants needs showed by Amit, but just need to make small modification to seperate eg, color, size needs from Lot, Serial Num those kind of "real" instance attribute. Thus we don't have to create color multiply size number of products. However I want to seek for opinions that if it can be used this way? If can't, what will be the problem?
BR,
Jack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear All,
We have tried to test the ADempiere for the Product with Multiple Attributes in Ordering and also in Inventory by a Single Product Information, for example, there is a situation to use One "T-Shirt" Product with Color (Red/Blue/Green) and Size (Small/Medium/Large) for processing its Ordering and Inventory with its Color and Size.
For our testing of the above example, we have defined two Attributes (Color & Size) as "Instance Attribute" with linked to a Attribute Set with "When Shipping" Mandatory Type. And then we create a New Product using this Attribute Set without Value Selected in here.
Next, we create a "Standard Order" Sales Order to order the above Product with the selected values of Attribute Set Instance (e.g. Red/Large), then we got an Error Message "Insufficient Qty on Hand" and unable to Save the Sales Order Line. Hence, we can't make a sales order of Product with Attribute Set Instance in "Instance Attribute" Type.
Hence, would anyone know how to define the Product Attribute with Color and Size as "Instance Attribute" for Ordering and Inventory Movement? Thank you.
Kindly regards,
aobahopkins
Hi,
I have posted something similar. I got it to work one step further. You need to book stock in with this particular instance. I guess, you purchased stock, so you need to do a PO (select the product and complete the details in the product instance tap for the items), vendor invoice and ship/receipt. You can check the quantities on hand in the product info.
I struggle with the next step: to select the specific instance in a sales order. If you have worked this out, please let me know.
Gunda
re: Error Message "Insufficient Qty on Hand" and unable to Save the Sales Order Line
I haven't used attributes so perhaps we are talkng about a different message... but typically if I enter a product for which there is no stock available, I get a message "No Inventory Available" .. but this is just a warning! I click ok and can save the line and continue! I can alco complete the document, but of course it cannot be shipped as the stock is not available. This lack of stock will feed into the replenishment report! and when the stock finally does arrive the order will (assuming any other rules are met) now appear as a shipable order.
colin
Dear All,
Thank you for your reply. For the above Error Message, it is occurred in a Sales Order if the Product is assign a "Attribute Set" which is a "Instance Attribute". And also, we have tried to create a Purchase Order and to perform Purchase Receipt of this PO, the Same Error Message is occurred for creating Sales Order of this Product with Same Attribute Set Instance Value of Purchase Order.
And also, according to the real business environment, the Purchase Order and its Receipt may not be performed before creating Sales Order of a Product with Specific Attribute Set Instance Value.
Hence, would anyone tell us how to solve this error with corresponding setting or trace it as a bug to be fixed in future release of ADempiere? Thank you.
Kindly regards,
aobahopkins
hi aobahopkins
Yes I was wrong sorry.
I had thought perhaps they they might be the same message but after translation from English to a translated version and then translated back for the purpose of posting in the forums that it was the same ... sorry about confusing you more!
I haven't implemented attributes myself so perhaps I should say nothing and leave it to others who have experience but in the absence of such people posting I can speculate; if it helps you reason out what the problem might be? So with that in mind; I think it comes down to this Instance Attribute. When we use the word instance we typically are talking about a unique existing item. So I'm working on a notebook model 4711 but the serial number on the bottom indentfies a unique instance of model 4711. So, likewise, when you select an Instance Attribue on an Order the system expects it to exist!
When you set the Instance Attribute flag on when creating a Attribute Set this is what it expects... the Attribute will indentify an instance ... the examples in GardenWorkld are Serial Number and Lot.
Again I don't know 100% but it was my understanding that the Attributes are not intended for creating sub-products. So again taking a Garden World example of T-Shirts .. they can be red, white & blue and in Sizes Small, Medium & Large are attributes. But to the system a T-Shirt is a T-Shirt .. the cost the same and are are equally exchangeable. So I would order a T-Shirts! Not 10 Large White T-Shirts! Notice how in the GardenWorld example the actually have two products TShirt-GL (Green & large) and TShirt-RL (Red-Large) so we can track & price them seperately. I think if the Attribute is important for you you need to do the same.
So what is the point of an Attribute you might ask? well my old compiere manual explains the difference as;
An Instance Attribute Set identifies a specific instance of a product while
An Non-Instance Atrribute Set is used for searching.
So you use it when someone asks "Do you have a small red t-shirt?" you go to your product search would enter in the attributes small & red and it will say we have 10xproduct number TShirt-SR in stock at such a location.
Look closely at how the TShirt & Fertiliser products in GardenWorld are defined and used!
While I guess that wasn't the answer you hoped for I hope that at least gives you some food for thought
colin
Dear Colin,
Thank you for your useful replies. Based on your suggestion, we will try to test it and post that result onto here. Thank you.
Kindly regards,
aobahopkins
hi aobahopkins,colin
I have encountered the same problem as well while I did the test on Adempiere 3.2.0. I think it's a ASI bug. It's should be fixed in the trunk. Please comment and try to reproduce as following steps:
1. Create an attribute set with instance attribute of Color and Size
2. Create a product with the attribute set created in Step 1
3. Create a Standard Order
4. Add a order line with the product created in Step 2 without ASI and Save (it'd be successful with qty warning message)
5. Add a order line with the product created in Step 2 with ASI (Color and Size) and Save (it'd be failure with qty error message "Insufficient Qty on hand")
I think it wouldn't prohibit you place an order no matter what the stock level of such product. Or is there any system parameter to control this behavior?
beta
I don't think it's a bug beta, but a misunderstanding of what the attributes are.
There are two types of attributes & attribute sets; Instance and non-instance.
A common “instance” attribute is a serial number. It identifies, uniquely, a specific instance of a product.
Attributes such as colour & size are “non-instance” attributes... many products can & will have the same value so the attribute in itself does not identify the product, it is simply descriptive.
When an AttributeSet includes an instance attribute its “Instance Attribute” flag is set positive.
Now when you create a Sales Order, the order line allows you to specify a “Attribute Set Instance” - not an attribute set but an instance of an attribute set.
So you cannot, for example, order a blue car but a car with the instance attribute VIN number = 12345 is ok.
Not a widescreen notebook but a notebook with the serial number SN654234.
So the error message you are referring to is saying equivalent ... we don't have a product (i.e. we have zero quantity of) with instance attribute "Red" "Small" as if Red an Small were unique instance identifiers.
And you are correct in that normally it does not matter how many of a product you have in stock at the moment of Sales Order entry. But in this instance you are indicating you, by entering the Attribute Set Instance, that you are selling a unique/specific instance of a product and the application is saying ... we don't have that instance.
If you need, for example, to manage T-Shirts in sizes Small, Medium & Large you need to create product numbers for each.
So what is the purpose of the non-instance attributes then?
Well they are simply descriptive. In the T-Shirt example in gardenWorld, it allows you to search for a product. If someone asks do you have a Shirt in size Large and colour Green you can fill these values in in the Product Search and it might respond with, “yes we have a quantity of 10 of the product number “TShirt-GL”. You might also have other stocks of clothing so it might also say ... and quantity 5 of product number “Cotton-Shirt-GL” with these attributes. The product is not T-Shirt & Cotton Shirt but rather you must create a product for each combination you wish to track.
I hope I haven't confused you further.
colin
Hi colin,
It's very nice explanation. Thanks. It makes clear about the difference between instance and non-instance attribute set. Maybe it's the purpose of the attribute set and the intention of the original designer to design such feature. I just doubt that it may not be applicable to real situation unless heavy customization has made.
Our corporate is a manufacturing firm and we would face some nasty problems if I take advantage of the ASI in it's original design feature as you said:
1. high admin costs.
- Define a non-instance attribute set for style, color and size
- Define a product for each style, color and size combination, normally a style could have 10 colors and ~20 sizes
- All same style of different color and size share the same price and cost
- Normally, color or color codename are known since customers have placed an order, i.e. when issuing a standard order
- It's error-prone to admin huge amount of the same product with different AS value only
2. interface not user-friendly
- Imagine how heavy the daily workload would be in using the as-is Adempiere/Compiere version in entering the serial no during an simple inventory move, for example, only one product of qty 1000
To get around this practical problem, I think ASI needs further enhancement to cater for different industrial needs flexibly. My suggestion are:
1. Attribute supports table type, just like Reference List, besides List
2. ASI dialog support fields in Search field type besides List
3. New mixed approach in ASI, inbetween instance and non-instance AS. Let users define, e.g. color and size, non-instance nature attributes in a instance attribute way (Hope you can understand what I mean)
Could you give me advice or direct me to another threads discussing about the ASI debate or problem?
beta
-
Hi again beta,
I'm in a bit of a rush today so I only have time for a quick answer.
Yes I agree with most of what you say.
There are some scenarios where the current setup works ok. In my current project for example... lucky me :) The client is a reseller of engineering consumables (i.e. cutting tools, drill bits & blades etc). They have a possible product list of 200K plus products as their suppliers sell the products in a wide variety of attributes... but the suppliers number each variation as a separate product .... hence the 200k plus numbers. But finding the right product number in a list of 200k can be an issue so being able to select a 75mm titanium bit with a 5mm diameter and diamond edges is made a lot easier with the use of attributes.
But I fully accept that it does not work in all cases.
I'm torn as to if (as an example) a large green T-shirt is the same as a red small T-shirt; I can think of arguments for and against. But regardless I agree it should be easy! ... and flexible enough to cover all our needs.
From my experience, what I think is missing in adempiere is a "sales configurator". If we take a product we all here have experience of ... computers. We choose a model but then we can add more memory, extra disks perhaps options on the CPU ... but it's still the same basic model that we order. It is possible, in this situation, to create a BOM including the different options and use the "BOM Drop" to make the selection and add to an Order. But I don't think it could, in any sense, be considered user friendly.
There is some work on this and the serial number issue in the wiki
http://www.adempiere.com/wiki/index.php/ADempiere#Sponsored_Functional_Enhancements
colin
so much for my short answer :)
Hi colin,
Thanks for kindly reply and advice. I have a more completed understanding about the design and purpose of the instance and non-instance attribute set now. It maybe fit for all general cases but it's not fit for garment industry, at least.
That make me recall the experience years ago about using the Oracle Apps 11i feature - the Flexfield, which just like ADempiere instance attribute set for non-instance attributes, e.g. define color and size as instance attribute and enter those info in an order.
Maybe I take the other way to make a separate customization module on ASI for garment industry to make user experience to ADempiere more friendly.
Could you mind to tell more about the sales configurator? Or it's included in the coming release?
beta
hi beta,
>> It maybe fit for all general cases but it's not fit for garment industry, at least.
Actually I didn't mean that ... just that I was lucky it suited my "current" project.
And I think most peoples' initial understanding or expections (my own included) of the functionality are as you understood - but alas it is not currently so. I have zero experience of the garment industry (except as a customer :)) so I couldn't comment. The closest I came was reading the white papers & documentation on ERP5 which I understood was devevlop for precisely that industry. Not that I am suggesting you leave us for them :) but that perhaps you can help us match them!
My own experience has been "mostly" in the electronic manufacturing & services where the concept of a system configuration is common. I'm not sure how well that concept would suit the garment industry!? And the only information I have is that in the wiki... but perhaps some that are involved could enlighten you further.
colin
Hi,
I am facing the same problem as Beta. The explanation and work flow that Colin gave cleared the current functionality in Adempiere. However it makes things very difficult practically. We buy products for manufacturing which are defined by the international standards, material, thickness, ratings etc. For the same product there are a about 15 standards 10 types of material, 3 types of thickness, 10 type of rating ....
As per the current functionality the number of products variants that we will need to enter for each product will be 4500. There are hundred different types of products that we need to buy. Assuming only 100 products to be bought, it makes it at minimum 450,000 records for the products that we buy. To further compound the issue, for each product you need to enter the business partners again. With an average of 10 vendor for each product will mean 4,500,000 additional records. You can understand the enormity of the job and the cost involved. The standards are reviewed every few years and a change in section or code will make the whole exercise useless.
On the other hand if you define all the attributes independently and use the combinations are per the requirements the amount of data to be entered is 10(standards)+3(thickness)+10(rating)+100(products)+10(vendors) = 133.
Looking at the functionality, and reading some manuals I got the feeling that the original intent of attributes was to define a single product with different variants being defined in attributes. You can use the product and attributes to completely define the product for either a sales order, purchase order etc.
I feel that this functionality is required if Adempiere has be be successful in the production industry where a large variants are required as raw material and as finished products.
-Amit
Hi Amit,
>I feel that this functionality is required if Adempiere has be be successful in the >production industry where a large variants are required as raw material and as >finished products.
I really believe that every problem has proper solution, but it all depends how much effrot someone is ready to put in order to solve it. Before 2 years i worked for a Bulgarian company which extended Product attributes and made price depndent on Product Attributes. The same company used the system to track sales of Newspapers. So we had 200 products and each day we had new newspaper issues, which was new value of Product Attribute Set Instance. So i think that everything can be fixed and made to work as company desire.
Kind regards,
Trifon
Hi,
I met now exactly the same problem Bata and Amit asked in this post 3 years ago. And just searched the forum and found this post.
After checking the codes, I feel Colin's answer for "Error Message "Insufficient Qty on Hand" is not correct. This can be solved simplely by selecting "Select existing record" Attribute Set Instance dialog (click order line's attribute set instance field button). And then just click save, then there will be no error message. Please correct me if I am wrong.
I feel that we can use instance attribute set to deal with garment industry or any kind of requests with variants needs showed by Amit, but just need to make small modification to seperate eg, color, size needs from Lot, Serial Num those kind of "real" instance attribute. Thus we don't have to create color multiply size number of products. However I want to seek for opinions that if it can be used this way? If can't, what will be the problem?
BR,
Jack