× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



And this won't address component serial numbers for the end item, will it?

Dale (Cork) Gindlesperger, CPIM







________________________________
From: Eric Wolf <eric_a_wolf@xxxxxxxxxxx>
To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
Sent: Fri, February 18, 2011 6:02:56 PM
Subject: Re: [MAPICS-L] MAPICS-L Digest, Vol 9, Issue 18 Serial number within a
serial no.

The only challenge that I see using Batch/Lot is if you are shipping dozens or
hundreds of units and you have to pick one batch for each serial number.


Eric


Eric Wolf
XA Business Analyst
(818) 486-5678

On Feb 18, 2011, at 11:21 AM, ARojas@xxxxxxxxxxx wrote:

same here... we use the Batch/Lot number with a quantity of 1 and rename
in reports and inquires as Serial number for the users.


Antonio Rojas
Manager Applications Development
Semtech Corp.
Cell. (805) 216-4651
Office (805) 480-2135




From: "Thibault, Roland" <Roland.Thibault@xxxxxxxxxxxxxx>
To: <mapics-l@xxxxxxxxxxxx>
Date: 02/18/2011 11:17 AM
Subject: Re: [MAPICS-L] MAPICS-L Digest, Vol 9, Issue 18 Serial
number within a serial no.
Sent by: mapics-l-bounces@xxxxxxxxxxxx



We do that using the Lot number fields and quantities of 1. Our users
always refer to the serial number, but they are actually using the lot
number field.

Roland Thibault


-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx
[mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of
mapics-l-request@xxxxxxxxxxxx
Sent: Friday, February 18, 2011 1:00 PM
To: mapics-l@xxxxxxxxxxxx
Subject: MAPICS-L Digest, Vol 9, Issue 18

Send MAPICS-L mailing list submissions to
mapics-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/mapics-l
or, via email, send a message with subject or body 'help' to
mapics-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
mapics-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MAPICS-L digest..."


Today's Topics:

1. serials within serials? (Michael Ellis)
2. Re: serials within serials? (Dale Gindlesperger)


----------------------------------------------------------------------

message: 1
date: Thu, 17 Feb 2011 14:33:54 -0800
from: Michael Ellis <michael.ellis@xxxxxxxxxxxxxxx>
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.


--
Michael G. Ellis
CEO / Enterprise Consultant
Information Systems International, Inc.
A Global ERP Consulting Firm
815-398-1670 x7882

*Be kinder than necessary-** **
Everyone you meet is fighting
Some kind of battle.** *


------------------------------

message: 2
date: Thu, 17 Feb 2011 19:13:08 -0800 (PST)
from: Dale Gindlesperger <dale_gindlesperger@xxxxxxxxx>
subject: Re: [MAPICS-L] 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.


--
Michael G. Ellis
CEO / Enterprise Consultant
Information Systems International, Inc.
A Global ERP Consulting Firm
815-398-1670 x7882

*Be kinder than necessary-** **
Everyone you meet is fighting
Some kind of battle.** *
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
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) digest list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.



End of MAPICS-L Digest, Vol 9, Issue 18
***************************************
***********************************************************************
This transmission contains information which may be confidential and
which may also be privileged. It is intended for the named addressee
only. Unless you are the named addressee, or authorized to receive it
on behalf of the addressee you may not copy or use it, or disclose it
to anyone else. If you have received this transmission in error please
contact the sender. Thank you for your cooperation.
***********************************************************************
For more information about QSA Global Inc.
please visit our website at http://www.qsa-global.com
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.