Company: Link Technologies
Case No: L08668. Project: 08.20: LinkSOFT Version 8.2
Logged By: Rashna (Edge Business Solutions) on 11 Jul 2017 07:58AM
Priority: High
Product: Point of Sale
Group: Enhancement
Time Taken: 5.00 (Weight: 5.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna
Resolve By: Wednesday, 12 July 2017 12:00 AM [2479 days since logged date]
Status: Closed
Subject: Improvement to Invalid posting account in Adjustment message
Summary:    

Hi Team, 

I have tested the case in 813.

The following was done.

  1. Created POS and JIWA Integration.
  2. Did not set posting accounts for products.
  3. Created and posted an adjustment.
  4. Enabled the "POS Health Check Process".

An email notification was sent stating, some inventory items do not have a valid posting account. The Adjustment Number was included in the alert. Refer to Figure  1 below. 

However, users do not know the products for which they have to set the posting accounts. Currently, they have to open the adjustment and verify each product. On site users have over 100 products in an adjustment.

Improvement - Modify the alert to include the part numbers which do not have posting account in an adjustment.

Figure 1: Alert 


Audit Notes:
11 Jul 201711:07AM Comment 1 by Alvis (Link Technologies) Case 8668 added to project 8.14
11 Jul 201711:08AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-07-2017 11:08 AM

Add the list of items that have invalid posting code to the log message

Rashna/Sanjeet/Alvis/Sanjay


14 Jul 201710:59AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-07-2017 10:59 AM Time Taken: 2.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): No
QA required(Yes/No.Include areas that require testing): Yes

The following changes were made(Include Database object names, Program classes and any other relevant information):|

  1. The error log has been changed to include part numbers.

14 Jul 201705:33PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 14-07-2017 05:33 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 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.


Item Number 5 has failed.

Setup is in QA1 with database LINKSOFTLOG.

  1. Items in Adjustment "LTAD000059" do not have Account Code.
  2. When posting adjustment from 521-1. System prompts message to check log.
  3. We logged into POS, message was in the Event Log. Figure 1 
  4. However, when we expand to view the detail. Record disappears from the screen.

Figure 1: Validation

Figure 2" Validation Disappears 



Table 1 - Summarised list of issues
NoIssue Description Resolved? 
1
2  
3  
4  
5  
6  
7  
8  
9  
10  
11  
12  

WORKFLOW:

  1. Original case assigned to Development
  2. When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
  3. If system test passes, assign case to Consulting Manager for UAT
  4. If UAT Passes, Assign case to MD to release patch

    14 Jul 201705:44PM Comment 5 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 14-07-2017 05:44 PM Time Taken: 1.00

    Hi Rashna, I am not able to replicate this. It shows the log when I expand the line.

    Can you verify this again?

    regards
    Alvis


    14 Jul 201706:00PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 14-07-2017 06:00 PM Time Taken: 1.00

    Hi Team, 

    I have retested the case , the log message does not disappear. 

    The log messages move to the previous page. 

    Users can filter the log message by module "LT_INV_FMS_PostAdjustment" or search by "Reference Number"


    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L08668 in the subject line of all emails regarding this issue.

    Document size: 11.1 KB
    For call complaints, please contact the Managing Director of the company using this form.