|
midrange.com
I don't think things will be planned wrong. All that happens is that the LLC
will be artificially inflated in some items then all components of these items
will have a larger LLC. You should never have a component of an item with a
lower value in the LLC. As long as that is true (regardless of "gaps") MRP and
Costing should perform fine. MRP starting at the lowest value and Costing
starting at the highest. The only time gaps should become a problem is when
the LLC gets pushed past 99 (very unlikely).
Robert Russell
Paragon SI
-----Original Message-----
From: Kevin Fox [mailto:kdfox@xxxxxxxxxxxxx]
Sent: Mon 12/20/2004 2:37 PM
To: mapics-l@xxxxxxxxxxxx
Cc:
Subject: Subject: RE: Low level codes not in sync
Terry,
You are correct.
The theory goes like this.
Let's say that an item has a LLC of 4. MRP will use this LLC to plan
the item in the proper order. So for example, if the LLC for all items is 0 -
7, then MRP will start planning on LLC 7. So LLC 4 will be planned after 7,6,
and 5.
Now, let's suppose that a bill change causes the item's LLC to change
from LLC of 4 to an LLC of 7. This will result in the item being planned near
the beginning of the MRP run so as to ensure the higher level items (lower
LLC's) will see the demand correctly.
One more change, suppose we now delete the item from the LLC 7 level
leaving only the LLC 4 level. MAPICS does not change the LLC from 7 to 4. So
again, the MRP plan will plan the item near the beginning of the planning run.
Normally, this does not cause an issue. However, let's suppose that
over the course of a few months (or years!) we don't reorganize the file. What
happens then? Well we would end up with many items at level 7 that should not
be. And depending upon the higher level relationships (i.e. does the item
appear in multiple bills at multiple LLC's?) MRP may not calculate all of the
demand accurately which can lead to some problems.
Most of the time this problem will have a symptom... the dreaded "33".
For those of you who do not know what the dreaded "33" is, let's just say that
as a planner it is your worse nightmare. (BTW what you don't know can hurt you
and your career!)
Hope that helps.
Kevin Fox
'kdfox@xxxxxxxxxxxxx'
- - - - - -
Kevin
Correct me if I'm wrong, but doesn't MRP use the low level code to
determine the
item planning order so that it will not miss a demand. So if an item
is at the
wrong low level code, isn't possible the system could not plan an order
for an item.
Terry Moffitt
Mfg. Engineer
Altek Inc.
-----Original Message-----
From: Kevin Fox [mailto:kdfox@xxxxxxxxxxxxx]
Sent: Friday, December 17, 2004 10:19 AM
To: mapics-l@xxxxxxxxxxxx
Subject: RE: Low level codes not in sync
Robert,
As usual you are correct. Everyone should take note of this as it has
caused much
confusion over the past few years.
The LLC is updated during BOM maitenance ONLY if the LLC is at a higher
level as
a result of the maintenance that is processed.
There was a problem with the Green Screen program having the incorrect
LLC which
was fixed on SH71748 (R6 PTF 6365, R7 PTF2919
Kevin Fox
"kdfox@xxxxxxxxxxxxx"
I don't know what you mean about deleting components. If you are
refering to using
a component at level 4 in one bill and level 7 in another bill and then
later deleting
the level 7 component. If my memory serves me right, BoM maintenance
never reduced
the low level code only increased it.
Robert Russell
Paragon SI
-----Original Message-----
From: Chris Neely [mailto:Chris.Neely@xxxxxxxxxx]
Sent: Thu 12/16/2004 4:10 PM
To: MAPICS ERP System Discussion
Cc:
Subject: Re: Low level codes not in sync
I am running EPDM however.
Kevin Fox <kdfox@xxxxxxxxxxxxx>
Sent by: mapics-l-bounces@xxxxxxxxxxxx
12/16/2004 01:36 PM
Please respond to MAPICS ERP System Discussion
To: mapics-l@xxxxxxxxxxxx
cc:
Subject: Low level codes not in sync
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
_______________________________________________
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 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.
