Re: serials within serials?

Mike,

We had to do that (government requirement) and of course, MAPICS II, DB, and XA
didn't support it (we had to have it back in the MAPICS II days). We developed
our own app to track it, with a database linked to MOMAST/MOHMST. Covered
everything we needed. I did a custom RM app at the end of the assembly line
that required the people to log all the required S/N's before being allowed to
"buy out" the unit - then I generated the "RM" transaction as a part of the
logging app.


I'd be glad to share what we did with you. There were two files MSODTLSF and
MSODTA (MSO stood for "Mfg Statement of Origin) - the MSODTLSF contained the
MO#, date produced, and VIN of the end item (trailer). MSODTA contained all the
component serial number information. We had to track all of it in the event of
a recall due to a defective component. One example that comes to mind was a
batch of defective furnaces that could catch fire - obviously that required a
recall!

Dale (Cork) Gindlesperger, CPIM







________________________________
From: Michael Ellis <michael.ellis@xxxxxxxxxxxxxxx>
To: mapics-l@xxxxxxxxxxxx
Sent: Thu, February 17, 2011 5:33:54 PM
Subject: [MAPICS-L] serials within serials?

Does anyone have general feedback for me on how to deal with serial numbers
of subassemblies and serial #'s of finished items?
How do you tie one to the other?
MO's versus usage in Rep schedules?
Interested in dialog with anyone willing about this topic.