Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Period Sensitive Aged ...
Finance | Project Operations, Human Resources, ...
Unanswered

Period Sensitive Aged AR Issue

(0) ShareShare
ReportReport
Posted on by JGarcia123 1,608

My client's been trying to chase down an issue with their Period Sensitive AR Aging.  They are on an old version of SL (7.0), and running the standard report.  The report has not been modified.  On February 24, they ran the TB for 12/2019.  Ran the same report for 12/2019 again today.  There were transactions from 2017 that remain outstanding that did not appear on the February 24 report, but appear in the current report.  the client insists that they ran both reports with no templates or select filters.  The client thinks something is broken and I am trying to come up with some reasonable explanations for the discrepancy.  That said:

1)  It is entirely reasonable that they ran the report with some form of template or filter and just not recall. 

2)  Looking in the tables one can confirm that other than the original entry, there have been no payments, credit memos or other adjustments against the transactions in question.  I also confirmed the existence of the same transactions in a separate historical database from 12/2018.

3)  The report is not modified - the copy of the 02/24 report has the stamp of the original report format which is the report run today.

4)  I tested the existing templates to see if any would create the condition that omitted the transactions and could not reproduce.  I have to purposely enter some odd select criteria to create the original results

5)  I checked some custom stored procedures in the SQL database to confirm if there was anything that may interfere with the transactions and could not find any.

Is there anything else I can check?  I can't seem to find anything that would cause the transactions to be omitted from the report other than a filter.  Look forward to a response.

JG

  • CFROTON Profile Picture
    CFROTON 4,710 on at
    RE: Period Sensitive Aged AR Issue

    Dear JG,

    Did they run aging? Change anything to do with statement cycles...Something could have changed on the Customer to have it suddenly appear on the report.

    Best Regards,

    Jana

  • JGarcia123 Profile Picture
    JGarcia123 1,608 on at
    RE: Period Sensitive Aged AR Issue

    Hi Jana,

    I did look at the Usr_Rpt folder.  The report in question was not there and pulling from the standard report.  I also looked at the standard report and it reflected the 2007 install date from when the system was last implemented (I know that has been an issue for some time).

    The report is the Period sensitive AR Aging and both reports were run for the 12/2019 accounting period.

    I suspect something may have changed in how the report was run, but again the customer is insisting they ran the basic report with no filters or templates.  I'm just trying to ensure that we cover any additional reasonable explanations.  

    I've checked the crtd_user, lupd-user, perpost, perent, and crtd_datetime fields and all reflect transactions and users who originally entered and released the transaction in 2017.

    I also looked at the aradjust tables and noted there were no payments, credit memos or any other adjustment that would have altered the original outstanding transaction.

    I've also tested a number of templates associated with the report to verify if they could have created the conditions to omit the transactions but did not find anything that would have reasonably created the condition.  I also purposely entered select criteria to create the condition to exclude the transactions but the options required (excluding certain transaction dates and or batch numbers) to make this happen are so unusual within the course of normal use that one not expect a user to inadvertently enter them.

    Lastly I also checked for any custom SQL jobs or custom stored procedures that would have altered the database, but did not find any.

    I did propose to the client that if they could find a backup from the night of February 24 or the 23, that we could restore it to a test database and then test the report again.  I've not yet heard back if such a backup is still available.

    Again I am open to any other suggestions or thoughts.  I just want to make sure we consider all possibilities.

    Thanks!

    JG

  • CFROTON Profile Picture
    CFROTON 4,710 on at
    RE: Period Sensitive Aged AR Issue

    Dear JG,

    Did you look in usr_reports for the report or something recently renamed to force it to use standard report

    Are you using the same aging date? Was aging ran after the Feb report?

    Perhaps something in the data changed rather than the report...doc date, due date something like that ...I assume the records are correct in that they have not been paid?

    You can check the lupd_xxx fields to see if the records were updated recently on the customer or the doc and tran records for the transactions.

    Best Regards

    Jana M

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans