Quantity difference by .001 between toplevel qty and child level qty -- MAPICS-L

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

Subject: Quantity difference by .001 between toplevel qty and child level qty
From: "Aiyanathan, Devendran \(GE Consumer & Industrial\)" <Devendran.Aiyanathan@xxxxxx>
Date: Thu, 3 Jun 2004 19:54:46 +0530
List-archive: <http://archive.midrange.com/mapics-l>
List-help: <mailto:mapics-l-request@midrange.com?subject=help>
List-id: MAPICS ERP System Discussion <mapics-l.midrange.com>
List-post: <mailto:mapics-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/mapics-l>, <mailto:mapics-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/mapics-l>, <mailto:mapics-l-request@midrange.com?subject=unsubscribe>

Hi List,

We have a peculiar problem in the plant, where if the Quantity required is 1000 
for a top level item, its child item Quantity required is 999.999. The QTYPER 
is 1,  QTYDEV = 0 for the child level item. This gets reflected both in MOMAST 
and MODATA records for the child level item.

Please let me know your thoughts.

Thankyou,
Devendran.

As an Amazon Associate we earn from qualifying purchases.

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.