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.

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

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
   

--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.

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: