× 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.



This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
First, a little backround before I share our idea.  We are on Rel 5.0
and have only the basic inventory modules (IM PDM PCC MRP PUR PMC).  We
have controlled warehouses with batch/lot control and FIFO dating.

We are in the process of wanting to re-label our inventory to new item
numbers.  However, there is a bunch of inventory records in various
stages of QC status (and don't for get FIFO dating).  We know what the
new item numbers are and have ITEMAS records set up for them.  We want
to know if we could just write a program to read the SLQNTY for the old
item numbers and overlay the item number field with the new item number.
We know we will also have to write a program to fix the ITEMBL records
also (for the qty on hand), but our main dilemma making sure that the
inventory records in SLQNTY are correct.  We do not discreetly allocate
inventory and we do not use the barcoding function within MAPICS, so I
don't think we need to worry about the turnaround number fields.  Our
main concerns are:
1.      How the order number is used on the SLQNTY records.
2.      Is there any tie-back to the LIFITR file?

PS.  By the way, what is the LIFITR file and what is it used for?

I would appreciate any feedback.

George Shannon
Manager of Applications
Beiersdorf Inc.,
(203) 854-8224
(203) 854-8244 (fax)
gshannon@bdfusa.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.