Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Approvals:
Change Record
3
Reviewers
Name Position
Mayilsamy
Rajkumar Kurumala
Priti Deshmukh Technical Project Manager –Clover Infotech
Distribution
Note To Holders:
If you receive an electronic copy of this document and print it out, please write your name on
the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front cover, for
document control purposes.
Requirement
Credit hold on customer profile level should be released using custom program in
case customer is having balance amount to pay and due date is exhausted.
We can consider following scenarios to meet the requirement
1. Custom program will work for all credit customer. It should not consider any
cash customer.
2. Logic should not consider customer ‘B05_BANGALORE
MOTOR OWNERS CO_OP SOCIETY _ BNC’
3. If customer is having more than 1 transactions and any or all transactions will
be having balance amount to pay after due date, credit hold should not get
released.
4. If customer is having more than 1 transactions and all transaction will be
having balance to pay within due date, credit hold should get released.
5. For credit memo transactions, amount will be negative and program logic
should not consider such transactions for pending balance calculation.
6. Calculation of due days should be based on payment terms.
7. Credit release hold should work only for customers who have balance amount
to pay within the due date.
Technical
Existing Logic
1. Procedure developed to select customers who will be having credit hold locked
and which are eligible to release credit hold.
2. For selecting such customers, query is written where it is retrieving all customers
and minus those customers which are not eligible for credit hold, so remaining
will be considered as eligible for credit hold.
3. (part I) Select all customer having credit hold = ‘Y’ – (Part II) select customers
who are not eligible for release credit hold ‘N’ = customers who are eligible for
release hold ‘N’
4. Part II of above query was handled such that it was selected wrong customer list.
5. API is used to release such customer’s credit hold.
6. Minus query selection was having condition -
And (trunc(sysdate)-due_date) > (due_date - trx_date) which was retrieving
wrong customer list.
Case 2 25-May- 25-Jul-18 27-Apr-18 1234 -89 > 60 which is false, hence
18 customer was not selected in minus
query and was not getting minus
from all customers. And therefore
was coming as eligible for release
hold.
Whether sysdate – due_date is +ve or –ve value, logic was considering all those
customers for release hold.
Changed Logic
1. Handled condition in procedure for selecting those customers in minus query
whose due date is exhausted and balance is remaining.
2. And (trunc(sysdate)-due_date) > (due_date - trx_date) changed to And
(trunc(sysdate)-due_date) > 0
3. For above cases, logic is considering case 1 customer not eligible for release and
case 2 customer, eligible for release.
Case 1 12-Feb-18 14-apr- 27-Apr-18 1234 13>0 which is true, hence customer
18 is getting selected in minus query
and get minus from all customers,
therefore is not considered as
eligible for release hold.
Case 2 25-May- 25-Jul-18 27-Apr-18 1234 -89 > 0 which is false hence
18 customer is not getting selected in
minus query and hence it will come
as a customer who is eligible for
release hold.
Future Cases
1. Need to monitor developed logic for few days for exceptional cases if any.
Open Issues
Closed Issues
GOL Customer Payment Term Release Hold Open and Closed Issues for this Deliverable Page | 6
File Ref:
Company Confidential - For internal use only