| Subject: | Move configurations for customer statement report to Report Maintenance |
| Summary: | Move configurations for customer statement report to Report Maintenance: - Customer Statment Aging Method
- Statement Overdue message
|
| Audit Notes: | Edited by sanjay on 05/03/19 09:49. |
| 17 Sep 2018 | 02:16PM Comment 1 by Alvis (Link Technologies) Case 9578 added to project 10.0 |
| 17 Sep 2018 | 02:17PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 17-09-2018 02:17 PM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 10 beta4 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Moved Customer statement aging method and statement overdue message to report maintenance
2. The issue was caused by: - N/A
3. Next Step - UAT
|
|
| 27 Sep 2018 | 08:53AM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 27-09-2018 08:53 AM Time Taken: 1.00 |
| QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues | No | Test Description | Pass/Fail | | 1 | Customer Statment Aging Method is moved to report maintenance ~> rules | Pass | | 2 | Statement Overdue Message is moved to report maintenance ~> rules | Pass | | 3 | Customer Statement is showing aging based on the configuration. Statement overdue message is displayed. | Pass. | | 4 | Customer Balance - Age is showing aging based on the configuration. | Pass | | 5 | Customer Balance Listing is showing aging based on the configuration | Pass |
Environment Details - OS version: Windows 7
- Application version: 10 Beta 4
- Setup: Demo
- Server : 10.0.0.10
- Database: UAT-LINKSOFT-DemoData
Next Step: Update documentation with details below When statement aging method is standard, the system uses the following breakdown: - Current bracket: transactions dated between zero and 30 days. In figure 1, this equates to transactions between 29/08/2018 and 27/09/2018
- 31-60 bracket: transactions dated between 31 and 60 days. In figure 1, this equates to transactions between 30/07/2018 and 28/08/2018
- 60-90 bracket: transactions dated between 61 and 90 days. In figure 1, this equates to transactions between 30/06/2018 and 29/07/2018
- 90+ bracket: transactions dated more than 90 days. In figure 1, this equates to transactions less than or equal to 29/06/2018
Figure 1: Aging=Standard, Statement Date=27/09/2018
|
|
| 27 Sep 2018 | 01:10PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 27-09-2018 01:10 PM Time Taken: 1.00 |
| Hi Sanjay, Documentation updated on the case. Documentation updated under BI - Report Maintenance - Report Rules. Thanks
Rashna |
|
| 27 Sep 2018 | 03:09PM Comment 5 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 27-09-2018 03:09 PM |
| Thanks Rashna |
|
| 09 Oct 2019 | 08:14AM Comment 6 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |