Company: Link Technologies
Case No: L12184. Project: 12.30: LinkSOFT Version 12.30
Logged By: Vineet (Link Business Solutions) on 26 Feb 2021 04:22PM
Priority: Medium
Product: Point of Sale
Group: New Feature
Time Taken: 20.50 (Weight: 20.50)
Version: 12.32
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna, Sanjay, Vineet
Resolve By: Tuesday, 23 February 2021 11:59 PM [1147 days since logged date]
Status: Closed
Subject: Change Request - Cash Sales for Loyalty Customer to Go into POSCASH Customer Account for On the Go Limited
Summary:    

Section A - Briefly explain what the change is about

When Cash Sales are done for Loyalty Customers, they should be tagged under POSCASH Customer when integrated to Financials. OTG has over 70K loyalty customers and they do not want these integrated individually to their financials.

Section B - Explain in detail what this change is about

  1. OTG has Cash Loyalty Customer and Credit Loyalty Customer.
  2. Some of these Loyalty Customers buy on Cash and Credit Both. A credit account is created for these customers with a credit limit.
  3. OTG wants all Cash Sales Processed under any loyalty customer to go into a POSCASH Customer account in the Financials Application.
  4. In some cases, the Customer gives their loyalty card after sales have been processed. OTG wants to be able to tag these invoices to the loyalty customer after-sales completion.
  5. The Loyalty Customer Number is different for the customer number so these would be maintained under Customer Additional Fields. This is the number that needs to be output in the Loyalty Export file
  6. OTG also has also requested the ability to import loyalty customers. Allow the import of loyalty customer number into additional fields.

Section C - Provide a Test plan for this change

Scenario 1

Customer ABC is a credit customer with a set limit of $2000. The customer loyalty number is LY0010. This customer buys on Cash worth $4000.

Expected Result: This sale will be integrated into Financials under POSCASH Customer. The file will be output under Customer code LY0010.

Scenario 2

Customer ABC Buys on Credit worth $1500. 

Expected Result: This sale will be integrated into Financials under Customer ABC. The file will be output under Customer code LY0010.


Scenario 3
Customer DEF is a loyalty customer (LY0011). Customer buys on Cash for $800. Gives loyalty details after the sale is processed.

Expected Result: This sale will be integrated into Financials under POSCASH Customer. The file will be output under Customer code LY0011.

Audit Notes:Edited by sanjay on 12/03/21 15:55. Edited by vineet on 10/03/21 08:32. Edited by vineet on 03/03/21 08:26. Edited by vineet on 03/03/21 08:18. 
23 Feb 202109:48AM Comment 1 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 23-02-2021 09:41 AM Time Taken: 1.00

Hi Vineet,

We can add a configuration for FMIS Integration called "Change Customer code for CASH SALES to POSCASH"

Therefore, LINKSOFT will have the ORIGINAL customer, while FMIS will get POSCASH for any CASH SALES.

This is the simplest method and will mean that transaction flow is consistent between LinkSOFT and FMIS.

If we say "Loyalty Transactions Only", this will mean that some "CASH SALES" will go to Customers and some will go to POSCASH. This will be inconsistent.

Let me know if this meets your requirements.

Development Cost: 6 hrs
Delivery: 2 weeks


23 Feb 202111:07AM Comment 2 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 23-02-2021 10:57 AM Time Taken: 1.00

Hi Vineet, here are the costs for additional items in Section B:

Section B Item 4

  1. Once a customer is allocated, changing the customer code is possible, however, "CUstomer based" discounts and other business logic cannot be applied as the transaction is processed, and in some cases, may have already flowed into FMIS.
  2. We can add a Utility on LinkWEB to allow a user to change the customer code of a processed customer
  3. Development Cost: 6 hrs

Section B Item 5

  1. Development Cost: 2 hrs

Section B Item 6

  1. Development Cost: 2 hrs

26 Feb 202104:21PM Comment 3 by Vineet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 11-03-2021 10:00 AM Time Taken: 1.00

--Discussion with Sanjay--

We have agreed on the following:

  1. Refer to comment 1. The configuration will send all the Cash Sales to the "POSCASH" Customer. We will not filter by loyalty customer as it will be difficult to reconcile as customers will be coming on and off loyalty
  2. Section B item 4, changing the customer code of processed customers will not change Linksoft Loyalty points calculation or customer balance information.
    1. We will log the customer change, against the original customer record
    2. We only allow fully settled transactions customer code to be changed.

OTGL approved the above change.



    03 Mar 202108:16AM Comment 4 by Sanjay (Link Technologies) Case L12184 added to project 12.3
    03 Mar 202108:18AM Comment 5 by Vineet (Link Business Solutions) ETC was changed from 23/02/2021 to 23/02/2021
    09 Mar 202111:58AM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 10-03-2021 11:29 AM Time Taken: 14.00

    PART A - Development work for this case has been completed.

    1. The change will be available in version:

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

    1. Added a plugin to change all integration transactions of type "cash sales' to POSCASH
    2. Added ability to change Customer Code for CASH SALES in LinkWEB
    3. Added Custom Fields to Export Output file. A standard Custom field named "Loyalty Number" is available in the Customer Maintenance
    4. Added LoyaltyNumber to Customer Import

    3. Affected Areas:

    1. Customer Maintenance
    2. Customer Import
    3. Customer Transaction Integration

    4. The issue was caused by:

    1. Customer Change Request

    5. Notes: System/UAT
    6. Next Step
    (Review and System Test (Developer) -> UAT (Quality) -> Documentation): System Test

    ----------------------

    PART B - Development Reference (Place descriptor for objects changed):

    1. Changes implemented was according to the approved design (Y/N): Y

    2. Other relevant notes:


    12 Mar 202103:55PM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 16-03-2021 03:55 PM
    For UAT

    25 Mar 202101:16PM Comment 8 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 26-03-2021 10:46 AM Time Taken: 2.50
    QA Results
    Tests carried out according to requirements specified on the case header

    Test Results Summary

    Table 1 - Summarised list of issues
    NoTest DescriptionPass/Fail
    1

    Added a plugin to change all integration transactions of type "cash sales' to POSCASH

    Verify the following:

    1. Cash sales go into POSCASH customer in AR Sales Order
    2. Returns for cash sales go into POSCASH customer in AR Sales Order
    3. Credit sales go into the respective customer accounts
    Pass
    2Added ability to change Customer Code for CASH SALES in LinkWEB
    Pass
    3Added Custom Fields to Export Output file. A standard Custom field named "Loyalty Number" is available in the Customer Maintenance
    Pass
    4Added LoyaltyNumber to Customer Import
    Pass

    Environment Details

    1. OS version: Windows Server 2012
    2. Application version: 12.32.0324BETA
    3. Setup: Demo
    4. Server : 10.0.0.16
    5. Database: LINKSOFT

    Next Step

    1. For review

      26 Mar 202102:04PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 30-03-2021 02:00 PM Time Taken: 0.50
      documentation completed

      29 Mar 202102:27PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 30-03-2021 02:26 PM Time Taken: 0.50
      QA Results
      Tests carried out according to requirements specified on the case header

      Test Results Summary

      Table 1 - Summarised list of issues
      NoTest DescriptionPass/Fail
      1Verify UAT ResultsPass

      Environment Details

      1. OS version: Windows Server 2012
      2. Application version: 12.302.0325BETA
      3. Setup: Demo
      4. Server : 10.0.0.14
      5. Database: LINKSOFT-DEMO-123

      Next Step

      1. For Closure

        06 Apr 202101:22PM Comment 11 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 07-04-2021 01:12 PM
        Thanks Rashna

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

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