Company: Link Technologies
Case No: L12727. Project: 14.10: LinkSOFT version 14.10 - October 2022
Logged By: Vineet (Link Business Solutions) on behalf of Sanjay (Link Technologies) on 20 May 2022 08:53AM
Priority: Low
Product: Point of Sale
Group: Enhancement
Time Taken: 56.25 (Weight: 56.25)
Assigned To: Development
Circulation: Development, Sanjay, Vineet
Resolve By: Friday, 30 September 2022 12:00 AM [699 days since logged date]
Status: Closed
Subject: Restrict data flowing into FMIS systems by Customer Category and Location
Summary:    

We have 20 Service Stations to accommodate the fuel needs of its customers. For the convenience of its Customers, the client has also made arrangements with third-party sites (Merchant Sites) where customers can fuel up at any of these Merchant Sites.

Since all transactions are processed on the same database, we need a way to prevent "Merchant Site" transactions from flowing into our FMIS system.

We use the FMISSQL integration in LinkSOFt to integrate into JIWA. Can we add a rule to prevent "Location" and "Customer Group" data from flowing into JIWA?

Section B - Below is a test plan using Mobil and OTGL as examples

Task

Business Scenario

Merchant Site|OTGL Site

Customer Category

Location

LocationMask

ReferenceNo

Record Sales in LinksoftHQ

Record Sales in Jiwa Financials

1

Energy Fiji Limited fills $100 Unleaded at Grace Road Navua

Merchant Site

MOBIL

GRNAVUA

GN

GNRC0000000298

Yes

No

2

Energy Fiji Limited fills $120 Unleaded at On The Go Sigatoka Site

OTGL Site

MOBIL

SIG01

SG

SGRC0000001021

Yes

Yes

3

Energy Fiji Limited fills $100 Unleaded at Bridge Town Service Station

Merhant Site

MOBIL

BTB01

GN

BTRC0000000401

Yes

No

4

Link Business Solutions fills $100 Diesel at OTGL Regent

OTGL Site

OTGL

SUV02

RG

RGRC0000006000

Yes

Yes

5

Link Business Solutions fills $130 Unleaded at Grace Road Navua

Merchant Site

OTGL

GRNAVUA

GN

GNRC0000001000

Yes

Yes

6

Link Business Solutions fills $90 Unleaded at Bridge Town Service Station

Mer

chant Site

OTGL

BTB01

GN

BTRC0000000401

Yes

Yes


Audit Notes:Edited by sanjay on 26/09/22 10:14. Edited by sanjay on 15/08/22 10:42. Edited by sanjay on 18/07/22 14:42. Edited by sanjay on 23/05/22 13:51. 
23 May 202201:53PM Comment 1 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 23-05-2022 05:51 PM Time Taken: 2.00

Hi Vineet, sounds like you want to limit the flow of FMIS transactions from HQ based on some criteria.
The most effective way would be to create a Plugin that allows you to define which transactions flow into FMIS.

Can you elaborate on what this criterion is? one seems to be the Customer Category, is the other the "User Organisation"?


07 Jun 202201:28PM Comment 2 by Vineet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 07-06-2022 05:19 PM Time Taken: 0.50 Notes: Edited by sanjay on 26/09/22 10:14. 

Bula Sanjay

Client has given the below Criteria:

  1. Customer Category
  2. Location

So going back to the case header,  Customers with a Customer Category: "Mobil"  buying from Merchant sites should not be recorded as a sale in OTGL Books (Financial Database). Hope this assists


08 Jun 202201:26PM Comment 3 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 08-06-2022 05:21 PM Time Taken: 2.00 Notes: Edited by sanjay on 26/09/22 10:15. 

Hi Vineet,

We can add the following "Module Configuration" in menu "Integration ~> Integration Setup" in integration name "FMISSQLAPI" under Rule code "AccountsReceivableSalesOrder"

  1. "Exclude.CustomerCategory"
  2. "Exclude.Location"

Thee will be CSV values so multiple items can be filtered.


10 Jun 202207:48AM Comment 4 by Vineet (Link Business Solutions) This comment has been removed
18 Jul 202210:11AM Comment 5 by Vineet (Link Business Solutions) This comment has been removed
18 Jul 202202:37PM Comment 6 by Sanjay (Link Technologies) Case L12727 added to project 14.01
27 Jul 202212:47PM Comment 7 by Vineet (Link Business Solutions) This comment has been removed
27 Jul 202204:58PM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 31-08-2022 08:56 PM Time Taken: 1.00 Notes: ETC extended from: 21/05/2022 to 31/08/2022
Assigned to project 14.01

22 Sep 202206:11PM Comment 9 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 28-09-2022 03:49 PM Time Taken: 32.00
PART A - Development work for this case has been completed.

1. The change will be available in version:14.10

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

  1. Added to filters to Sales Order Processing in FMISSQLAPI
    1. ExcludeCustomerCategory
    2. ExcludeShiftLocation
  2. Configuration is CSV list, users can specify multiple categories and locations using CSV format

3. Affected Areas:

  1. Sales Order Integration - Filtered by Customer Category AND/OR Shift Location

4. The issue was caused by:

  1. Change Request

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


06 Oct 202201:36PM Comment 10 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-10-2022 01:24 PM Time Taken: 18.00
The following tests were performed:

Test Setup Instructions:
  1. Setup LinkSOFT integration to Jiwa using SQL API
  2. Setup two customers, one with Category WHOLESALE, another with category RETAIL
  3. Setup Two locations, Main and Retail
  4. Enable process POS024 - FMIS Integration for POS transactions
  5. Enable FMISAR - FMISSQLAPI
Table 1 - Test Results
NoTest CaseExpected ResultPass/FailComments
1Without any Restrictions, process one transaction for each customer and each location
All transactions should flow into FMIS
Pass

2Add a Category filter for WHOLESALE in "Integration Setup ~> FMISSQLAPI ~> AccountsReceivableSalesOrder ~> ExcludeCustomerCategory". Perform two sales, one with customers in the category WHOLESALE and one with customers in the category RETAIL
Customer Category Retail should go to FMIS, Wholesale should be marked with narration "Exclusion Applied"
Pass

3Add a Location filter for location MAIN in a similar way to 2. above
Transaction performed for SHIFT created in location MAIN should not flow through
Pass

4Remove all filters and perform transactions
All transactions should flow through


5Review event log and Sales Order View
A clear indication showing which transactions have flowed through to FMIS should be visible
Pass

Environment Details

  1. OS version: Win11
  2. Application version: 14.10 BETA5
  3. Setup on:
    1. Server: LinkQA4
    2. Database: LinkSOFT
    3. LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
  4. Login Details: Standard username and password for user "admin"

Next Step: Closure


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

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