Validationr equired for Colending Child Contract in Dev Plugin:

Business Requirements Document

Request From:

Request Date: 05-APR-2020

Process Owner:

BPM Validator: Madhumita Kundu / Kaushik Bhattacharya /Sujit Datta

Technical Lead Arijit Chatterjee / Kuntal Mitra

BPM Approver Purnendu Mukherjee

VERSION AND APPROVALS

Versio Effective Change details in brief FRD Reviewed Approve By

n No. Date change By
suggested
By

1.0 07-Apr- BRD Creation NA

2020

Creation new validation for co-lending child contract:

There will be a new validation at Contract Complete Activation State Change work flow for the co-
lending child contract (program_id – 1403, 1303, 1203, 1103, 1002). From the child contract the Parent
contract id need to picked from the contract custom field “Co-Lending Parent Contract”
(Contract_CFD_ID = 5782). Now for the following fields need to check, that all the values are same for
both child contract and the parent contract.

If anything is not match, there will be a validation message and the system will not allow to activate the
child contract.

Fields Level Actual Fields Name Custom Comment

fuild or
not
Collection Officer name/id Contract Collection Officer
RM name/id Contract Current Relationship
Manager
Dealing Officer name/id Contract CSQA Dealing Offficer
 Agent Type Contract Agent Type
Agent Name/ID Contract Agent Name
Drawdown Party Name/id Contract Drawdown Recipient
Alliance Contract Alliance Type
Branch Contract BRANCH_ID If branch Id is same
no need to check the
region and zone.
Region Not exist Link with branch Id
contract/asset
level
Zone Not exist Link with branch Id
contract/asset
level
CIBIL Contract Cibil Scrore
RBI Risk Category Contract RBI Risk Category
Contract Start Date Contract Contract Start Date
Instalment start date Contract Instalment start date
Tenure Contract Tenure
Customer Contract Customer
Business Unit Contract Business Unit
Vendor Contract VENDOR_ID
CIBIL Score Contract CIBIL Score
PSL Contract PSL Category
Colender Contract Co-lender
Credit Manager Name/id Contract Credit Manager
New Client Grading Contract New Client Grading
Name of Firm Contract Name of Firm
Approving Committee Contract Approving Committee
Risk Mitigates Asset Risk Mitigates
Insured By Asset Insurance By
Asset name/ID Asset Asset name
Asset Type Asset Asset Type
Asset Manufacturer Asset Manufacturer
Asset Scheme Name Asset Scheme Name 2
Customer Segmment Party Customer Segmment
Customer Sub segment Party Customer Sub segment

Validation logic and Message building rules:

1. Each value of a particular property of a child contract will be checked with the same property of the
parent contract. Both the value needed to be trimmed.
2. List of the properties should be arranged according to the priority (Please ordered list has to be
shared)
3. Validation message can be formed in three ways
a. Generic message for any mismatch.
b. Validate properties one by one and stop whenever there is an error and show the message
for that particular property.
 c. Validate all the properties at a time and at last list all the properties where there are
mismatches in the validation message.

Best way need to be chosen according to the performance and practice.

4. For contract with single asset there is no problem for the Asset level properties to be checked. But
for contract with multiple assets there is no way to match the assets from the parent contract with
child assets from child contract. We have to go by the Descending order of the Asset_ids of the
parent contract and the child contract.
5. Validation message pattern will

“Please review the property where Parent level and the child level are not matched –

1. Property name : Property_name ”