| Subject: | Customer Statement to Output Customer Balances by Period. |
| Summary: | Hi Team, We discussed in the morning meeting(10/01/2017) to output customer balances by Period. Period meaning balances for a month. This feature is evident in the JIWA reports. We will remove the feature to populate balances with 30, 60 or 90 days transactions. If a user generates the report with "Date From" as 01/04/2016 and "Date To" as 31/04/2016. All Transactions made in April should be populated in the "Current" balance portion. Taking the above dates, all transaction from March to be output in Period 1. Transactions from February to be output in Period 2. Period 3 to show all balance Prior to February.Refer to the image below. The above change is necessary because clients mostly send statements by month. 
|
| Audit Notes: | |
| 16 Jan 2017 | 09:02AM Comment 1 by Alvis (Link Technologies) Case 8293 added to project 8.10 |
| 06 Jun 2017 | 11:06AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 06-06-2017 11:06 AM Time Taken: 2.00 |
| Development Meeting - 06/06/2017 - Alvis, Sanjeet, Rashna, Sanjay Add a report parameter name: Ageing Method. Options are: Standard, Month Allocate to release 900 Regards
Sanjay |
|
| 06 Jun 2017 | 12:07PM Comment 3 by Alvis (Link Technologies) Case 8293 removed from project 8.14 |
| 06 Jun 2017 | 12:07PM Comment 4 by Alvis (Link Technologies) Case 8293 added to project 9.00 |
| 01 Sep 2017 | 10:53AM Comment 5 by Alvis (Link Technologies) Case 8293 removed from project 999 |
| 01 Sep 2017 | 10:54AM Comment 6 by Alvis (Link Technologies) Case 8293 added to project 8.18 |
| 06 Sep 2017 | 04:47PM Comment 7 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 06-09-2017 04:47 PM Time Taken: 4.00 |
| Development work for this case has been completed. The change will be available in version: 8.18 Documentation update required(Yes/No. Add change details below): Yes QA required(Yes/No.Include areas that require testing): Yes
1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Added a configuration on POS-WEB for "Customer Statement Aging Method (Standard/Month)". By default, the value is "Standard"
- Changed all customer statement reports to display aging based on the configuration above.
|
|
| 21 Sep 2017 | 12:33PM Comment 8 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 21-09-2017 12:00 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | Statement balances to appear by Month | Pass | | 2 | Unallocated payment reduces the very first months balance | Pass | | 3 | Allocated payment reduces the same month's balance the payment is applied to | Pass |
WORKFLOW: - Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 02 Oct 2017 | 03:13PM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 02-10-2017 03:13 PM Time Taken: 1.00 |
| Documentation Completed Documentation updated under Point of Sale - Web -- Administration - Configuration |
|
| 09 Oct 2019 | 08:14AM Comment 10 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 |