|
Jingker, I think you already have the suggested solutions using BOM and the related impact on cost. Although, if the BOM has to be adjusted you may also consider Method codes as a way to retain multiple BOM/Routings. If you are not concerned with cost at this point, there are a couple of simple solutions that may be available. They involve using the order policy code or the planner code. If C & D are used exclusively in B you can set the order policy to Blank on C & D. From then on, MRP, MPS & DRP will ignore these two items. When the experiment is over, reset the policy code. The other alternative is to assign these components to a different planner code, perhaps the same planner code you use for obsolete items. Assuming you release by planner code, you could look at the planned requirements and release or ignore as you please. Larry In a message dated 7/16/2003 12:16:09 PM Eastern Daylight Time, macwheel99@xxxxxxxxxxx writes: > Subj:Re: Reply: MRP and BOM (Item type) setting > Date:7/16/2003 12:16:09 PM Eastern Daylight Time > From:<A HREF="mailto:macwheel99@xxxxxxxxxxx">macwheel99@xxxxxxxxxxx</A> > Reply-to:<A HREF="mailto:bpcs-l@xxxxxxxxxxxx">bpcs-l@xxxxxxxxxxxx</A> > To:<A HREF="mailto:bpcs-l@xxxxxxxxxxxx">bpcs-l@xxxxxxxxxxxx</A> > Sent from the Internet > > > > You have several potential problems. > First is to get the planning working correctly. > Second is the impact on other things like Cost Roll-up if you have > inappropriate Engineering data to the type of item. > We also have parts that fluctuate between being purchased and being > manufactured, based on a number of factors, such as cost and speed with > which we need something when we have a capacity problem. If you want to > keep the BOM on the purchased item, I suggest you change the effectivity so > that it is not to be currently paid attention to, then if you want to > change it back to manufactured, then change the effectivity on BOM and > Routings so that once again that data is to be included. > We also have an outsourcing scenario in which we changed the item # > structure, so that the components sent to the outsourcer are tracked as > discrete items, separate from the item made by the outsourcer. > We are 405 CD Mix Mode > - > Al Macintyre http://www.ryze.com/go/Al9Mac > Find BPCS Documentation Suppliers > http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html > BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/ > > >The components CCC and DDD will still be planned even I change the item > >type of assembly BBB to Purchased (N). Do I have to delete the structure > >finally if we would like > >to get the BBB be planned ? > > > >Thanks. > > > >Jingker Cheng > > > > >Only change the item's Item type to purchase property. need not delete > the > >BOM. > > >as a client requirement, the BOM may be a reference.> > > >Ren > >----- Original Message ----- > > > > > The problem is that you are oursourcing the item and making it a > >component for the item type, but it still plans the sub components. > > >Delete the BOM and > > > make sure that the item type has the flag set to mfg = No, so that it > >will plan this as a purchased item. > > > > > > Have a great day. > > > > > > John Kasper > > > J.D. Kasper & Associates, Inc. > > > KASP6281@xxxxxxx > > > (847) 644-1042 Cell Phone > >Dear All: > > > >Using BPCS C/S v6.1.01 on HP-UX. Have a question about the MRP calculating > >result. > > > >Product "AAA" with assembly "BBB" and the BBB with two components "CCC" and > >"DDD". > >Normally, the item type of BBB is assembly. After the MRP execution, > >requirement > >CCC and DDD will be calculated. > > > >Question is: > > > >If we oursourcing the BBB and change the item type to component, the > >requirement CCC and > >DDD will be still calculated in the same BOM structure. But we just needs > >to calculate the > >BBB only. > > > >Can anyone know how to solve it ? Thanks. > > > >Jingker Cheng >
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.