|
Joan, can you just use the Split MO function... qty of 5 on one and 195 on the other? -----Original Message----- From: mapics-l-admin@midrange.com [mailto:mapics-l-admin@midrange.com]On Behalf Of McCready, Joan Sent: Tuesday, November 12, 2002 6:36 AM To: 'mapics-l@midrange.com' Subject: RE: Link multiple MO's to a CO LI Rel 's OK, Pete - I didn't explain very well, and I assumed that everyone does things the same way. Sample / first article - we manufacture to customer's engineering drawing/blueprint, so when we are making a new item for the very first time, say the customer's order is for 200 pieces, we make a "sample" run of one to five pieces to see if our engineering is OK or if we need to re-work the design, before we begin production of the other 195 pieces. However, to plan for capacity and to make the ship date, we issue both MO's (the sample and the rest) at the same time. If things go radically wrong with the sample, we delete the production MO (if it hasn't already been started), rework the routing and BOM, then reissue, but 99% of the time, we can just go in and manually "tweak" the existing production MO. As for MOMAST, I just finally had the time to check the logical files. Since logical MOMASTLG is by customer order number, I had to make sure it wasn't designed with a key of UNIQUE (it isn't), so I should be "good to go" to allow manual entry of the customer order information in the MOMAST fields. I'll let y'all know... Thanks again - Joan -----Original Message----- From: Pete [mailto:peteo@htol.net] Sent: Tuesday, November 12, 2002 8:17 AM To: mapics-l@midrange.com Subject: Re: Link multiple MO's to a CO LI Rel Joan, Sorry... I guess I stuck my 2 cents in something that I don't fully understand... (sample/first article ????) No idea what this is.. But one last thought...I would think that if you populated the same fields in Momast that mapics does when you create an M/O from a C/O... You should be alright..Mapics won't know how the record got there or how it got updated... Also not sure what kind of headache you will get with 2 mo's to one C/O... Should be easy enough to test.... Good Luck Pete ----- Original Message ----- From: McCready, Joan <Joan.McCready@metaltekint.com> To: <mapics-l@midrange.com> Sent: Tuesday, November 12, 2002 8:48 AM Subject: RE: Link multiple MO's to a CO LI Rel > Pete, > > The first MO is created from the CO line item; the second MO (sample / first > article) is created manually and has no "link" to the CO line item. We > do enter the CO information in the "Job Number" text field, but that > field cannot be used to link to the CO (not easily, anyway). > > Joan > > -----Original Message----- > From: Pete [mailto:peteo@htol.net] > Sent: Monday, November 11, 2002 3:11 PM > To: mapics-l@midrange.com > Subject: Re: Link multiple MO's to a CO LI Rel > > > Joan, > I created a CO with 2 line items on it... ... Then went to IM > order entry.. I said to create mo from customer order.. Press > enter.... prompted me for both line items and created 2 mo's... The > itmsq fld is the Com line item seq.. from the (mbadrep/mbcdrep) How > would you get 2 mo's for the same > Cust order/line item????? You get an error > ( E AM-3311 MFG ORDER ALREADY RELEASED FOR THIS ITEM) if you try to crreate > another MO for the same line items... > > Pete > ----- Original Message ----- > From: McCready, Joan <Joan.McCready@metaltekint.com> > To: <mapics-l@midrange.com> > Sent: Monday, November 11, 2002 3:39 PM > Subject: RE: Link multiple MO's to a CO LI Rel > > > > Pete, > > > > Yes, when you create the MO from the CO, it populates this field FOR > > THE FIRST MO. If you create a second MO, if I remember correctly (I > > need to > play > > with this in our test environ), you cannot select the CO release > > because > it > > already has an MO associated with it. > > > > Yes, you USUALLY have to cancel the MO before you can cancel the > > order > line > > item. I have successfully DFU'ed the order line item release and > > manually removed the MO number, then ditto to the MOMAST. (Needed to > > cancel the > line > > item from one order and add it to a different CO with a different > > ship-to > > address...) > > > > What happens, though, if the CO can find two (or more) MO's to which > > it is associated?.... > > > > -- Joan > > > > -----Original Message----- > > From: Pete [mailto:peteo@htol.net] > > Sent: Monday, November 11, 2002 2:20 PM > > To: mapics-l@midrange.com > > Subject: Re: Link multiple MO's to a CO LI Rel > > > > > > Joan, > > How are you creating M/O's??? If you create mfg order from a > > customer order it populates these fields.. I have done this with a > program.... Has > > not caused a problem... So Far Also I believe if you update the MBADrep > > file with the M/O you have to cancel the M/O before you can cancel > > the > order > > line item... Have not tested that lately... > > ----- Original Message ----- > > From: McCready, Joan <Joan.McCready@metaltekint.com> > > To: <mapics-l@midrange.com> > > Sent: Monday, November 11, 2002 3:01 PM > > Subject: Link multiple MO's to a CO LI Rel > > > > > > > This message is in MIME format. Since your mail reader does not > > > understand this format, some or all of this message may not be > > > legible. > > > -- > > > [ Picked text/plain from multipart/alternative ] > > > To all - > > > > > > I am becoming quite dangerous with the MAPICS Integrator! > > > > > > Has anyone put a custom data entry screen (either Integrator or > > greenscreen) > > > on MOMAST so that a Customer Order, Line Item and Release can be > > > entered > > in > > > the "untouchable" fields - ORDNC, ITMSQ and RLNB respectively (we > > > don't > > use > > > "kits", but that would be the next "linking" field if a company > > > did use them)? I know the CO LI Rel (MBADRExx) record only has > > > room for one MO, > > and > > > we create about 85-90% of our MO's from CO's, so the main MO # is > > > placed > > in > > > the CO LI Rel record, and the CO, Seq and Rel is placed in the MO > > > header. Our problem is tracking sample / first article MO's to the > > > respective CO > > as > > > well as the full MO for production (we manufacture to order, so > > > each MO usually has a corresponding CO line item release; each CO > > > line item > > release > > > can have multiple MO's, althoughly rarely more than two - the > > > sample and > > the > > > "rest" of the order). > > > > > > What I'm wondering is, if I give Production Control access to the > > > MO > > header > > > fields for hand-entering the CO information for the sample MO's, > > > what kind of chaos I'm unleashing should the CO line item release > > > need to be changed or (horrors) deleted in the meantime? Anyone > > > have any experience with > > this? > > > > > > Thanks in advance, Joan > > > > > > Joan McCready, IS Manager phone: 636-479-4499 > > > MetalTek International fax: 636-479-3399 > > > The Carondelet Division www.metaltekint.com > > > <www.metaltekint.com> > > > 8600 Commercial Blvd > > > Pevely, MO 63070 > > > > > > _______________________________________________ > > > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list > > > To post a message email: MAPICS-L@midrange.com To subscribe, > > > unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > > > or email: MAPICS-L-request@midrange.com > > > Before posting, please take a moment to review the archives at > > > http://archive.midrange.com/mapics-l. > > > > > > > > > > _______________________________________________ > > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > > post a message email: MAPICS-L@midrange.com To subscribe, > > unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > > or email: MAPICS-L-request@midrange.com > > Before posting, please take a moment to review the archives at > > http://archive.midrange.com/mapics-l. > > _______________________________________________ > > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > > post a message email: MAPICS-L@midrange.com To subscribe, > > unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > > or email: MAPICS-L-request@midrange.com > > Before posting, please take a moment to review the archives at > > http://archive.midrange.com/mapics-l. > > > > > > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, > or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives at > http://archive.midrange.com/mapics-l. > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, > or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives at > http://archive.midrange.com/mapics-l. > > _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com 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.