• Subject: RE: AR Aging
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Fri, 3 Nov 2000 08:28:27 -0500

That sounds right - we don't use MAPICS here, so I'm relying on memory - if
MBEKREP is the file that the CUSMAS01 logical is over, it's the right one.
Note the posting about the enhancements that are in R6, and that AM Plus
apparently has real-time aging for R4 and R5.  I think it's great that,
after all these years, MAPICS is finally making a solid effort to resolve
these little annoyances that we've been complaining about for all these
years (I worked with MAPICS as a user and programmer from 1980 to 1999).

-----Original Message-----
From: Shrader, Patrick [mailto:pshrader@wkep.com]

Thanks for the information. Too bad we all have to do this, when it seems
like a simple bug fix in MAPICS -- perhaps as a tailoring question to
protect systems with this modification.

Am I correct that the files to be affected are OPENAR and MBEKREP? Simply
examine the aging date for an invoice and insure that the age code is what
you expect and, if you have to make a change, adjust the totals in MBEKREP?


> -----Original Message-----
> From: Shaw, David [SMTP:dshaw@spartan.com]
> Sent: Thursday, November 02, 2000 2:55 PM
> To:   'MAPICS-L@midrange.com'
> Subject:      RE: AR Aging
> Patrick,
> I was told once that real-time aging in AR is the most common modification
> made to MAPICS.  Basically all that's required is a program to be run
> regularly (we ran ours several times a day) which corrects the age code in
> the OPENAR records and corrects the AR balances in the Customer AR Balance
> records.  You can write it yourself or buy it, I imagine just about every
> MAPICS BP knows where you can get it, if they don't have one to sell you
> themselves.
> Dave Shaw
> MAPICS-L Moderator
> Spartan International, Inc.
> Spartanburg, SC
> -----Original Message-----
> From: Shrader, Patrick [mailto:pshrader@wkep.com]
> We are running XA 5.
> We have several customers that have extended terms (60 days). However,
> when
> MAPICS ages the open AR, it ignores the terms code (verified by support
> line
> this morning). So, when a customer does not pay within 90 days of the
> aging/invoice date, but has credit terms to 60 days, MAPICS puts that
> invoice in the past 90 column on the aging report. However, the customer
> is
> only 30 days past due because of the extended aging.
> MAPICS says that they will look at terms in XA 6. However, that does not
> help me now.
> I have to think that someone out there is aging invoices greater than 30
> days. How have you solved the aging problem I have described above?
> Patrick Shrader
> White Knight Engineered Products
| This is the MAPICS Mailing List!
| To submit a new message, send your mail to MAPICS-L@midrange.com.
| To subscribe to this list send email to MAPICS-L-SUB@midrange.com.
| To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dshaw@spartan.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.