Re: Planning for scrap due to machine setup

Hi Vic, 

I had the same thing in my wood department - we always had to toss the 1st 
part.  I couldn't find an acceptable way to handle it at the time (this started 
in the DB days), so I just programagically did it as a part of order release (I 
had created a user exit in the middle of the order release process) - you could 
also add it to the shop packet print process.  Easy to do, if the value is 
already a 1 for that work center, skip the record, otherwise Z-ADD a 1 into it.  
VERY minor change in a almost totally static program.  I don't like modifying 
code (you know that), but if you have to, a program that hasn't changed in a 
long time is the safest place to do it.

 Dale (Cork) Gindlesperger, CPIM 

Knowledge is knowing a tomato is a fruit. 
Wisdom is not putting it in a fruit salad.





________________________________
From: Vic Belebczuk <vbelebczuk-z6Jt9gKu7/O/t4LUGa9KWQC/[email protected]>
To: MAPICS ERP System Discussion <mapics-l-Zwy7GipZuJhWk0Htik3J/[email protected]>
Sent: Fri, November 12, 2010 2:17:59 PM
Subject: Re: [MAPICS-L] Planning for scrap due to machine setup

Certain work centers always create scrap during setup of the machining 
operation. Expected scrap quantity will be "1" regardless of operation quantity. 
Is there a way to have MRP and order release automatically adjust component qtys 
to allow for this?  Both the Qty per in the product structure and the Yield in 
the routing operation are ratio based, so they are not a good fit because we do 
not have standard run qtys. From one mfg order to the next there could be a big 
difference in qty, so (for instance) using .9 in the Yield would work OK for a 
small qty but would greatly exaggerate scrap for a large M.O.   Has anyone 
developed a solution for this?
Thanks,
Vic
This electronic message transmission is intended only for the use of the party 
to which it is addressed, including any attachments and contains information 
from AeroControlex Group Inc., which may be privileged, confidential, or 
protected by law. If you are not the intended recipient you are hereby notified 
that any dissemination, copying or distribution of this e-mail or its contents 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Thank you. ITAR Notice: This email may contain technical data which 
may be controlled by the US International Traffic in Arms Regulation (ITAR) 22 
CFR part 120-130. If this data is determined to be ITAR controlled, such data 
may not be transmitted, shared or provided to any foreign party or entity either 
verbally or visually without proper licenses from the State Department. It is 
your responsibility to assure this item can be legally sh!
ared with another party.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.


      
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.