Hello:
I spent at least five months of business and personal time trying to create a "point in time" receivables historical aged trial balance in T-SQL where, for whatever aging date I would choose, I could show the open accounts receivable balance of each customer in a GP company.
I failed to deliver this. It behooves me to reflect on why.
For future reference, especially if I'm fired over this, I really would like to know from you (the experts) what I could have done differently.
I ran into a quagmire of questions and, to be frank, even the blogs that are written about items such as A/R apply tables were of absolutely no value to me. Now, that's no criticism of those who wrote those blogs. I simply could not absorb what I was being "told" by those blogs, in my ignorance.
Again, for my future reference, the following are my questions:
(1) When trying to garner the open balance for a customer based on the potentially hundreds of documents the customer may have in the RM20101 and RM20201 tables, which figure is used--the RM20101.ORTRXAMT or the RM20201.CURTRXAM?
(2) In GP, our Receivables Management Setup window is set to age documents based on Due Date. So, let's say that the arbitrary aging date that I have is 09/30/2015, while the RM20101.DUEDATE of a document with an RM20101.RMDTYPAL of 1 is 08/31/2015. Does that mean that this invoice is past due, then? What about Due Dates after 09/30/2015?
(3) For documents where the RM20101.RMDTYPAL is 7 or greater, is RM20101.DOCDATE the date that is used to compare with the arbitrary aging date instead of due date?
(4) Without paying a fortune teller or Dr. Strange from Marvel Comics, how in the world do you take into account all of the combinations of credit memos, debit memos, returns, and payments--especially, when some of those amounts are only partial amounts?
(5) I tried using CTEs to capture a lot of the reports data, joined by UNION statements. If stored procedures and tables are better, are there any books that you all can recommend for reading or online T-SQL classes, so that I can hopefully someday--before Social Security day--be able to do this programming in my sleep?
Incidentally, we do not conduct Paid Transaction History removal. So, there were no historical tables at play, here.
Thank you!
John