| Subject: | Journal Not created in Jiwa at Full Cost when Stock Take and Adjustments are Posted from Branch |
| Summary: | A stock take was made at one of the branches on 05/07/2017. When this was posted from Branch, all data had settled in HQ DB, however, journals were created worth $5157.61. The Total value of the adjustments was $723,152.18. This has been reproduced in our Demo Setup as well. These are the kinds of Systems related issues that will cause a mismatch between GL and Link Module. Please add to 8.13 for release.
Figure: 1
Stock Take Adjustment from Link
.png)
Figure 1.2 Journal from Jiwa for the posted stock take
.png)
|
| Audit Notes: | |
| 06 Jul 2017 | 03:48PM Comment 1 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 06-07-2017 03:48 PM Time Taken: 2.00 |
| Hi Team, The issue is when the stock tale or adjustment is posted from branch , then the header record comes first. As soon the first header information comes through, JIWA integrations picks that and journal is created. All details coming after the first header record is is not integrated. We need to disable Stock take posting from Branch. Current Workaround Users to only post adjustment and stock take from HQ.
|
|
| 07 Jul 2017 | 03:33PM Comment 2 by Alvis (Link Technologies) Case 8654 added to project 8.14 |
| 07 Jul 2017 | 03:36PM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 07-07-2017 03:36 PM Time Taken: 1.00 |
| The following design needs to be changed in order for this bug to be resolved: - Add a new menu in BackOffice to post adjustments to FMIS (similar to posting purchase order to FMIS)
- Remove adjustments integration to JIWA from JIWA integration background process
regards
Alvis |
|
| 10 Jul 2017 | 10:06AM Comment 4 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 10-07-2017 10:06 AM Time Taken: 1.00 |
| I have investigated this issue in version 7400 as well. Below are the results: - Created stock take in a branch
- Posted stock take in the branch. Variance of $69,142.50. See figure 1 below
- Journal created in JIWA. Journal Amount: $8,547. See figure 2 below
- Re-sent the stocktake journal to JIWA (after the replication queue was settled). Journal amount: $69,142.50 See figure 3 below.
Figure 1: Variance report
.jpg)
Figure 2: Journal 1
Figure 3: Journal 2
|
|
| 14 Jul 2017 | 10:33AM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-07-2017 10:33 AM Time Taken: 12.00 |
| Development work for this case has been completed. The change will be available in version: 8.14 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):| - Removed "adjustments posting" to JIWA from "Jiwa Integration" process
- Removed automatic posting to JIWA when "adjustment" and "stock take" is posted
- Added a new menu "Post Inventory Adjustments to FMIS" under "inventory adjustment" menu.
- Adjustments can be posted from the adjustment screen, however, this will not send adjustments data to JIWA.
- To send adjustment data to JIWA, the user must use item 3 above.
- For branch locations, item 3 above is not applicable.
- When a stock take is closed in the branch, the adjustment will flow to head office and can be posted to JIWA from item 3 above.
- When a stock take is closed in the head office, the user needs to use item 3 above to post it to JIWA.
2. Perform the following test: - Perform adjustment at a branch. Post and verify in head office (LINKSOFT and JIWA)
- Perform stock take at branch and verify data
- Perform stock take at head office and verify data
3. Important notes: - Adjustment data is only transferred to JIWA when open 1.3 above is used.
- Item 1.3 cannot be used at the branch level.
- All other functionality remains the same.
|
|
| 15 Jul 2017 | 12:12PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 15-07-2017 12:12 PM Time Taken: 2.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 3 - Sanjay to release patch only after steps 1 and 2 are completed successfully. STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Test Case 
Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | | | | 2 | | | | 3 | | | | 4 | | | | 5 | | | | 6 | | | | 7 | | | | 8 | | | | 9 | | | | 10 | | | | 11 | | | | 12 | | |
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 to MD to release patch
|
|
| 15 Jul 2017 | 01:18PM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 15-07-2017 01:18 PM |
| Case reopened for Documentation |
|
| 19 Jul 2017 | 08:52AM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 19-07-2017 08:52 AM Time Taken: 1.00 |
| Documentation completed the case. Documentation updated at Backoffice -- Processing -- Post Adjustments to FMIS |
|