Could a scrap qty and code field be added to the WO-I routine so that finished parts can be scrapped at the time the WO is backflushed? Currently we enter finished production and then scrap through an inventory adjustment - using this method I lose the ability to use scrap codes.
 
Thanks
 
Keith

We do more assembly than manufacturing, and we have very little scrap, so this might not work for you.  
 
We have set up an indirect work order for scrap. This allows us to issue raw, subs or finished goods to it and to use scrap codes.

There are so many facets to consider.  We look at scrap as scrap; it is not reworkable or salvageable in any way shape or form.  If it's reworkable, it's not scrap.
 
Our philosophy for costing is on a job by job basis.  Did this job have a profit, loss, or breakeven.  Therefore, all costs go to the job-rework & all.  The quantity complete bears the bottom line cost.  But it is our responsibility to control the jobs-if there's a lot of scrap or rework, the "good" parts are charged for it.  If it's really out of whack (good or bad) an adjustment can be made.  
 
REWORKS:
I add a 999 sequence to all my routings for rework.  All rework for that job/item would be posted here.  If it's major rework and we need to identify it better, we add a new routing line with the operation.  
 
SALVAGE as another part
I would either post it to Finished Goods, then immediately issue it to the other part or do a manual reduction in "Quantity to Make" on the work order, manually deduct costs through the Misc/Extra entry and add them to the new Work Order/part.
 
PENDING determination
Possibly a third category:  Good, scrap, pending.
Pending would not be available to allocate, but might show up with its quantity with an "H" for hold or something like that.
 
SCRAP
Quantity scrapped should not be available to MRP, Schelduling, ITems etc.
I would like to see operation by operation.  However, need to be able to enter without an operation code also as sometimes it is not always feasible to determine what operation caused the scrap-Might be scrapped at operation 50, yet it was because of something done at operation 10 but never caught.
Be nice to have an employee slot also, however, same applies as above-not always able to determine who.  But if there is someone consistently contributing to the scrap, need to be able to zero in on it.
Scrap % by operation, Scrap % from job to job.  (needs to be in JC-A)
Would like to produce a monthly scrap report so that trends can be charted.  Would show scrap as a % of overall parts, and scrap as a % of overall dollars.
Then an annual report could be generated with monthly totals. This is something we do with linked spreadsheets.