| Subject: | Disallow Multi Account Payment for POSCASH customer. |
| Summary: | Hi Team This has been tested with version 949 Users can allocate payments for POSCASH customer via Multi - Account Payment Justification - The system should not allow any payment for a POSCASH customer.
- POSCASH is a system generated customer, no user should be able to be load it or the search screen to allow payments.
- When a users processes multi-account payment for POSCASH, the "Customer Balance" for POSCASH is updated
Steps to Replicate - Navigate to Multi - Account Payment in POS.Enter cash as 100.
- Complete the payment
- Customer screen opens
- Search for POSCASH or scroll to POSCASH
- Enter the 100 as the Payment Amount and save
Suggestion Do not load POSCASH in the customer search for payment allocation under Multi - Account Payment Figure 1: POS Cash Payments 
Test Plan - Navigate to Multi - Account Payment in POS.Enter cash as 100.
- Complete the payment
- Customer screen opens
- POS Cash Customer should not be in the customer list.
- Users should not be able to search for POSCASH or scroll to select POSCASH
- No Payment should be allowed for POSCASH
|
| Audit Notes: | Edited by sanjay on 05/03/19 10:22. Edited by rashna on 26/07/18 13:26. |
| 10 Jan 2018 | 01:54PM Comment 1 by Alvis (Link Technologies) Case 8677 added to project 900 |
| 10 Jan 2018 | 02:00PM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Development Followup Date: 10-01-2018 02:00 PM Time Taken: 1.00 |
| Development meeting January 2018 Sanjeet, Vineet, Alvis, Rashna and Sanjay Approved for development |
|
| 26 Jul 2018 | 08:35AM Comment 3 by Rashna (Edge Business Solutions) Case 8677 removed from project 999 |
| 26 Jul 2018 | 01:27PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 06-08-2018 12:00 AM Time Taken: 1.00 |
| Hi Team, The case header has been updated, the issue on the case exist. Case added to 999 for development approval. Thanks
Rashna |
|
| 26 Jul 2018 | 01:28PM Comment 5 by Rashna (Edge Business Solutions) Case 8677 added to project 999 |
| 23 Aug 2018 | 10:28AM Comment 6 by Sanjay (Link Technologies) Case 8677 removed from project 999 |
| 23 Aug 2018 | 10:28AM Comment 7 by Sanjay (Link Technologies) Case 8677 added to project 09.5 |
| 30 Aug 2018 | 06:00PM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 30-08-2018 06:00 PM Time Taken: 1.00 |
| Development work for this case has been completed. The change will be available in version: 95 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Changed the "Customer Search" method to "Account Payment List"
2. The issue was caused by: - Search method was listing all customers
3. Next Step - UAT - Customer list should display all customers with outstanding balance
|
|
| 07 Sep 2018 | 03:54PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 07-09-2018 03:54 PM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 9.5 beta 3 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Renamed "Account Payment and Allocation" to "Payment for Credit Sale" - This list will load customer that have an unpaid credit sale invoice. This excludes layby sales.
- Renamed "Account Payment and Credit Note" to "On Account Payment/Credit Note" - This list loads all customers except POSCASH
- Renamed "Multi Account Payment" to "Multi On Account Payment" - This list loads all customers except POSCASH
- "Payment Adjustment / Refund" loads all customers.
2. The issue was caused by: - Redesign from comment 8 to clarify menu names.
3. Next Step - UAT
|
|
| 18 Sep 2018 | 02:14PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 18-09-2018 02:14 PM Time Taken: 1.00 |
| Hi Sanjay
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 | Renamed "Account Payment and Allocation" to "Payment for Credit Sale" - This list will load customer that have an unpaid credit sale invoice. This excludes layby sales. | Pass | 2 | Renamed "Account Payment and Credit Note" to "On Account Payment/Credit Note" - This list loads all customers except POSCASH | Pass | 3 | Renamed "Multi Account Payment" to "Multi On Account Payment" - This list loads all customers except POSCASH | Pass | 4 | "Payment Adjustment / Refund" loads all customers.
| Pass
|
Environment Details - OS version:Windows Server
- Application version: 10.0.0 Beta 3
- Setup: Demo
- Server : 10.0.0.10
- Database: LINKSOFT-DEMO-10-RASHNA
Steps to reproduce failed scenarios: N/A Next Step: Case added to the documentation que.
|
|
| 24 Sep 2018 | 04:58PM Comment 11 by Alvis (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 24-09-2018 04:58 PM Time Taken: 1.00 |
| Documentation completed |
|
| 09 Oct 2019 | 08:14AM Comment 12 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 |