Has anyone experienced a problem with releasing a SO with a Kit item on it??
 
I don't know when this broke, because we have been using kit
items for some time now.
 
When I try and release the kit item, the end result is that the kit item number
Ship and back-order qty's get set to zero.
 
If I go in and modify the order to put the numbers back, it asks if I want to
change the original order qty (1.00)?.  If I say yes, it sets the
Original qty to 2!!!  It ADDS the qty 1 that I just put back in to the
previous  1 and puts 2.00 in the Original Order Qty!!
 
I am now on ISTECH release 10/31/06.
 
This is a real problem now that we are trying to use Kits to minimize the
number of item numbers and BOM's we have to maintain.

If we always release all qty's ordered, then it works great.
 
If we only want to ship a partial, we have the problem
outlined above.

I currently have it set to 1.
 
I cannot change it while people are logged in,
(see: http://www.istechforum.com/cgi-bin/YaBB.pl?board=UPdateSuggestions;action=displa y;num=1169050396;start=3#3 )
 
If you can tell me which field in which file this setting is, than I will change it and check it out.

Kevin -  
 
Did you ever get the default changed and did that solve it?

And you all wonder why we can't just "Fix It"....
 
No slam to Kevin, he has been a great resource in fixing other issues.  But he has a job to do too (as we all do).
 
We are all trying.....
 
I will also post this on the main Problem Reports screen:
 
When you have a bug to report -  
 
Screen prints are great.  Google screenprint programs.  screenprint32 is great.  Please try not to send 5 Meg+ files of a screenprint - use the tools available
 
Identify the program with the problem
 
list as many specifics as you can determine.
 
Case in point...
 
I had a customer call and say that WO-G material issues were (seemingly) randomly changing quantity.  Issue 4 and the program issued 2.75.  But not all the time.  About 20% of issues, no obvious pattern.
 
After a number of attempts and special programs with messages, we discovered that the items that were issuing the wrong quantity were on the BOM multiple times.  The problem was that WO-G would attempt to split the issue to multiple occurrences of the cmponent on the BOM but after the first split, it was exiting and not completing the transaction.  
 
Easy enough to fix one the details are identified but of all the users out there, only ONE (that has contacted us) is using multiple occurrences of the same item on the BOM AND manually issuing components (as opposed to Kit Issues, Backflushing or WO-G List Issues) AND paying enough attention to inventory to identify there is a problem.  
 
We can't possibly test all permutations and combinations.