We have a duplicate invoice showing up on the Aged AR report, but no where else. Similar to that below:
IN 123456 Description XYZ 6/1/2017 10.00
IN 123456 6/1/2017 10.00
We haven't modified anything in this report recently. How can I track it down to ensure no other items are duplicated and remove it from the report?
-rose
HI Rose Grennell
You should check PA refnbr of that customer, are they duplicate PA refnbr ?. If this happen when you apply duplication PA refnbr to an invoice, it will make customer's balance and age AR report incorrect.
That report does use the view vr_08610dp which joins ARDoc to AR_Balances and Customer and Terms (plus a couple of other tables/views). The standard report gets all of its information from this view. However, you stated that you joined ARDoc and this view. Did you customize this report to also bring in ARDoc? If so, you need to join based on CustID, RefNbr and DocType in order to handle the case where an assigned reference number on an invoice ends up being the same number as a payment document for the same customer (e.g., the payment check number happens to match the invoice's reference number.
Hi Rick,
See below...
Is this happening on the period sensitive aged AR or the standard aged AR? -Standard Aged AR 08.610.
In your example you seem to indicate that one document has a description and the other does not. Is that accurate? -Yes
My initial thought is that this particular document has collided with the same reference number from another document for the same customer. -Yes, actually. There is a PA from 2015 for this customer with the same reference number....
Then execute the view that report uses to look at all of the components that are joined together to make that view that has the duplicate line. -We only have two joins (ARDoc Cust ID -> vr_08610dp Cust ID) and (ARDoc RefNbr -> vr_08610dp RefNbr)).
Rose, is this happening on the period sensitive aged AR or the standard aged AR? In your example you seem to indicate that one document has a description and the other does not. Is that accurate? The aging reports use some rather complex views (the period sensitive aging in particular) joining tables and other views to provide the basis for what is reported. When something like this happens it is likely caused by one of the view having joined the document with 2 lines from one of the other joined tables/views. It is sometimes a challenge to find where the extra join is coming from but it can be found. My initial thought is that this particular document has collided with the same reference number from another document for the same customer or that, if you are seeing this with the period sensitive aging, there is an unexpected record in the aradjust table for this reference number. In order to run it down, we would need to know which aging report you see it one and then execute the view that report uses to look at all of the components that are joined together to make that view that has the duplicate line.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,532
Super User 2024 Season 2
#2
Martin Dráb
228,501
Most Valuable Professional
#3
nmaenpaa
101,148
Share
Report
All responses (
Answers (