|
-- [ Picked text/plain from multipart/alternative ] Bud, Do you use Quotes? You might want to really consider using Quotes for Hold for Release orders. We did that when I was a customer of MAPICS and it worked great! Once the orders were approved and were to be planned, we used the copy function to copy it into an valid order with a "true ship date". That way you wouldn't have to do any coding at all, just a little retraining. If you can't get your user's to buy into this idea, you might want to ask MAPICS support if you can write a program in the shell User Exit to total the value of the orders with your special date and return it to the MAPICS program as a negative to Current order value and Total Open Order Value so it is deducted? Not sure you can do this, but I think you can. Hope this helps, but you really need to consider using Quotes to seperate your orders - it's a great feature of COM that many customers to not utilize to their advantage. Paola Groeber MAPICS Consultant 770-591-1497 Bud Roble wrote: > Dale, > > Thanks for the input. You first example wouldn't work in our case as we > don't want to deal with multiple customer numbers. Here is the exact > situation..... We have certain orders we key into the system that have an > "undefined" due date. We really have no idea when they will be shipped and > in some cases, they never do. We call these orders "Hold for release" > orders (HFR's). These orders have been keyed into the system with a > special due date 01/01/39. I know you're going to ask "what happens when > you get to the year 2039" ;-) What can I say.... I inherited this, but I > have to deal with it now. We want the credit checking procedure to ignore > any open orders having this special due date. In an ideal world, the > credit checking would occur in a single program somewhere and I would go in > and modify the code to ignore the 01/01/39 dates when it's figuring out the > value of the open orders in the system. I've found an API (UMBCLC1R) that > is for Customer Credit Checking but the Mapics support line told me this is > a shell program and I would need to write a whole credit checking routine > from scratch myself. In addition, if I was to put my own routine in this > API, they say I would need to turn off the Mapics credit checking. I don't > really want to do that. The mod I need to make seems pretty simple on the > surface; I just need to figure out where to make it and hopefully only in > one place. > > Bud > > -----Original Message----- > From: DaleGindlesperger@fft-inc.com [mailto:DaleGindlesperger@fft-inc.com] > Sent: Tuesday, November 05, 2002 1:37 PM > To: mapics-l@midrange.com > Subject: Re: Maintaining Open Order Total for Customers > > This is a multipart message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > We have what may be a similar situation. Our dealers have multiple credit > limits, depending on the product they purchase. We gave each dealer a > unique customer number for each product line. To make it easier, we broke > the customer number in to a 6 and 2 format. For example: > > Campers: 12332110 > Parts: 12332111 > Trailers: 12332130 > > The common customer number in this instance would be 123321. You can set > a different credit limit on each of the 8 digit customer numbers. > > You can also do it in user exits. We do some terms code overrides and > automatic credit approvals in the end-of-order user exits for certain > orders (promotional items and so on). That's especially useful if you use > COM_Net, which doesn't allow for terms code entry and other special stuff. > > Dale Gindlesperger > Fleetwood Folding Trailers, Inc. > > Bud Roble <BRoble@CharlesRobleConsulting.com> > Sent by: mapics-l-admin@midrange.com > 11/05/02 03:06 PM > Please respond to mapics-l > > To: "'Mapics Mailing List (mapics-l@midrange.com)'" > <mapics-l@midrange.com> > cc: > Subject: Maintaining Open Order Total for Customers > > 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 ] > I have a need to filter out certain orders from being included in the Open > Order Totals for Customers. Basically, I don't want certain orders to > be > counted against the customer's credit limit. Can anyone tell me where > I > would look to make this modification? I'm hoping Mapics had the > foresight > to place the logic in a single program somewhere. I would love to be > able > to use a user exit, but that's probably pushing the envelope. :-) Any > assistance would be greatly appreciated. > > Bud Roble > (805)794-3027 > > _______________________________________________ > 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.