Low level codes not in sync

[Kevin Fox <kdfox@xxxxxxxxxxxxx>]

The number one reason that low level codes get out of sync is non-MAPICS 
methods of changing data in the product strucure and / or costing.

Check to make certain you do not have any non-MAPICS programs updating product 
structures. (i.e. someone with client access and MS Access Database)

You should run in dedicated mode because a reorg can effect other sub-systems 
besides product structures.  ie. IM files, MO files, MRP files, MPSP files, 
etc.)

I monitor these files at least once a month.  If they are out of sync, I try to 
determine the cause.

Also note:  just deleting componenets from bills of material can cause the low 
level codes to be out of sync.  If your running the latest code, this has been 
corrected in a PDF that the unattached job uses to keep the files in sync.

Kevin Fox

-----Original Message-----
From: mapics-l-request@xxxxxxxxxxxx
Sent: Dec 16, 2004 10:02 AM
To: mapics-l@xxxxxxxxxxxx
Subject: MAPICS-L Digest, Vol 2, Issue 356

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