| Subject: | Improvement to POS JIWA Shift Payment List report |
| Summary: | Bula Vinaka Team After the introduction of automated payment allocation in Jiwa for all Cash Sales Transactions, XXXXX is facing difficulty in reconciling their CASH Book receipts. Below is what used to happen in previous versions: 7400 Reconciliation Steps:
- Cash book receipts created in Jiwa was based on Individual Shift i.e. One Cash Book Receipt per Shift.
- The Shift ID and POS username as set as the description of the Cash Book Receipt.
- The Remark field of the Cash Book Receipts Payment line contained the shift id and the Payment Type. This could be easily reconciled with the Cashier Reconciliation by shift report in LinkPOS. See Figure 1.1 below for details
- Once this Cash Book was activated, the remark field of the Journal Set was added to the Journal Sets. This made GL and Module comparison in Jiwa easier using GL Transaction listing report. See Figure 1.2 below for details. It also made reconciliation of Receipts between Link and Jiwa simpler for them
Figure 1.1 
Figure 1.2 
Now after the upgrade to version 8, below is what happens. - All payments for cash sales from Linksoft are directly attached to the respective Sales Orders in JIWA..
- Cash Book Receipt is only created in Jiwa after related Sales Order with payments is activated in JIWA.
- Cash Book Receipt created in Jiwa contains payment lines from multiple Sales Orders. Remark field for these lines are blank. This has created issue in reconciling Link and Jiwa payments. Refer to Figure 1.3 below for details
- When this is activated Journal is created with remark as blank. This has now created problem for their team to do monthly reconciliation. Figure 1.4 below for details
Figure 1.3 
Figure 1.4
XXXXX has requested for 2 changes: - Short term solution : Provide them with a report where they can feed in the Cash Book batch ID and systems provides them with a list of Shifts and their payment methods for each of the lines. We have provided POS JIWA Shift Payment List Report in POS Web but this report requires shift id as the parameter in order to be able to generate their report. They should be able to generate report by date, by Cash Book batch ID and by shift.
- Long Term Permanent Solution: Allow for automatic allocation without affecting their current business process. They need one Cash Book Batch per Shift ID as used to happen in version 7400 unless we can provide them a better way reconciliation.
|
| Audit Notes: | |
| 08 Sep 2017 | 11:35AM Comment 1 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-09-2017 11:35 AM |
| Required asap - Bill effort to LinkFJ |
|
| 08 Sep 2017 | 11:35AM Comment 2 by Sanjay (Link Technologies) Case 8796 added to project 8.18 |
| 12 Sep 2017 | 09:08AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 12-09-2017 09:08 AM |
| Assignment changed to development |
|
| 13 Sep 2017 | 12:24PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 13-09-2017 12:24 PM Time Taken: 2.00 |
| Completed the following: - Added Receipt Date From/To, Batch No and Shift ID parameters to "POS JIWA Shift Payment List" report
- Added columns "ReceiptDate, "BatchNo", "RemitNo", "ShiftID", "Amount" to the report data grid
|
|
| 26 Sep 2017 | 08:25AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 26-09-2017 08:25 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 | The report should be generated by date. Generated report for 8 months in the demo database | Pass | | 2 | The report should be generated by the Shift ID | Pass | | 3 | The report should be generated by Batch Number | Pass | | 4 | Data should be correct on the report. | Failed - The Shift ID is not reflected for remit numbers from POS. Hence when generating the report by shift ID only the line with the shift ID is populated. See Figure 1. |
Figure 1: POS Jiwa Shift Payment Report 
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
|
|
| 26 Sep 2017 | 12:00PM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 26-09-2017 12:00 PM Time Taken: 2.00 |
| Resolved issue with shift number not showing in some of the lines. |
|
| 28 Sep 2017 | 03:02PM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 28-09-2017 03:02 PM Time Taken: 2.00 |
| Hi Alvis, Tested case in 818 Beta in QA1 with database LINKSOFTHQ. Shift Number is still not showing for all lines. 
|
|
| 28 Sep 2017 | 04:03PM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 28-09-2017 04:03 PM Time Taken: 2.00 |
| Hi Rashna, The report was only looking at cash book receipts created from sales order payment. I have changed this so that it looks at account payments as well. regards
Alvis See screenshot below: 
|
|
| 29 Sep 2017 | 10:06AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 29-09-2017 10:06 AM Time Taken: 1.00 |
| Hi Alvis, Case has been tested in 818 Beta 2 test environment,this after you applied the updates. Shift Details are now showing for payment. Case will retested in Beta 3 to ensure the same has been added to the build. Regards
Rashna |
|
| 02 Oct 2017 | 02:47PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 02-10-2017 02:47 PM 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. Case tested with 818 Beta 3 Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | The report should be generated by date. Generated report for 8 months in the demo database | Pass | | 2 | The report should be generated by the Shift ID | Pass | | 3 | The report should be generated by Batch Number | Pass | | 4 | Data should be correct on the report. | Pass | | 5 | Shift ID should be output for cash sales, credit sales with partial payment, Account Payment and allocation,
Account Payment and multi account payment | 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
|
|
| 09 Oct 2019 | 08:14AM Comment 11 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 |