SIFL Plugin

Release Notes
[SIFL Plugin – Custom Validation for Ambit Asset Finance- SIFL ]

1
 SIFL Plugin

Document History

Author Version Date

Arijit Chatterjee 5.30.6018.4019 16th May 2016
Arijit Chatterjee 5.30.6773.5068 6th Nov 2019

Table of Content
1. Features -
1.1 Party Validation ………………………………………………………………………………………………… 3
1.2 Contract Validation ………………………………………………………………………………………………… 5
1.3 Contract Termination Validation ………………………………………………………………………………………………… 6
1.4 Bank Flow Validation ………………………………………………………………………………………………… 7
1.5 Credit Line Validation ………………………………………………………………………………………………. 8
1.6 Purchase Invoice Validation ………………………………………………………………………………………………. 9
1.7 Work Flow Validation ………………………………………………………………………………………………. 10
2. Configuration – ………………………………………………………………………………………………. 13
3. Known Issue …………………………………………………………………………………………….... 14
4. Installation ………………………………………………………………………………………………. 14

2
 SIFL Plugin

1. Features
1.1 Party Validation -

Party Validation implements ‘I42PartyValidation’ interface to enforce the following rules

1. In case of Business ‘Name’ should not be greater than 50 char, and in case of Individual total length of ‘First
Name’, ‘Middle name’ and ‘Name’ should not greater than 50 char (along with 2 spaces).
Validation message – “Party Name can not be more than 50 characters”

2. ‘Entity Type’ for Business party is mandatory.

Validation message – “Please select Entity Type.”

3. If Party Type is “None” then in the custom field value for “ Oracle Supplier Number” cannot be supplied.
Validation message – “No value is allowed in "Oracle Supplier Number".”

If party type is “Direct Customer/End Customer/Bank/Tax” then in the custom field value for “ Oracle
Supplier Number” cannot be supplied. Validation message – “No value is allowed in "Oracle Supplier
Number".” And custom field value for “Oracle Supplier Site Code” cannot be supplied. Validation
message – “No value is allowed in "Oracle Supplier Site Code"”

Note:- Config entry for the custom field names –

<add key="Party_Oracle_Supplier_Number" value ="Oracle Supplier Number"/>.
<add key="Party_Oracle_Supplier_Site_Code" value ="Oracle Supplier Site Code"/>

4. If party type is “TaxAuthority” then the “Operating Unit” have to selected – Validation message – “Please
select Operating Unit” and also that selected value have to be “SEFPL”, Validation message – “Please select
Operating Unit only "SEFPL"”.

Config entry for the Id of “SEFPL” –

<add key="Party_BranchId_For_SEFPL" value ="17"/>

If party type is “TaxAuthority” then the “Business Unit” have to selected – Validation message – “Please
select Business Unit” and also that selected value have to be “Srei Equipment Finance Private Limited”,
Validation message – “Please select Business Unit only "Srei Equipment Finance Private Limited"”.

Config entry for the Id of “Srei Equipment Finance Private Limited” –

<add key="Party_OperatingUnitId_For_SEFPL" value ="3"/>

5. At least one receipt type "Oracle Receivables Standard" method have to be added in party payments tab
which is not marked as default

3
 SIFL Plugin

Validation message – “Atleast one receipt type "Oracle Receivables Standard" method have to be added in
party payments tab which is not marked as default”.

At least one payment type "Oracle Payables" method marked as default have to be added in party payments
tab
Validation message – “Atleast one payment type "Oracle Payables" method marked as default have to be
added in party payments tab”.

At least one receipt type "Post Dated Cheque" method marked as default have to be added in party
payments tab
Validation message – “Atleast one receipt type "Post Dated Cheque" method marked as default have to be
added in party payments tab”.

"Day of Month" entry for all Payment methods should be "None"

Validation message – “"Day of Month" should be "None" for all Payment methods”.

6. In case party is of type Direct Customer/End Customer

Any phone number field for Business Phone/Home Phone/Mobile cannot contain alpha-numeric value.
Validation message – “Please enter numeric in all the phone numbers for the Contacts”.

Any STD code provided must be of format (+91)

Validation message – “Please enter only '91' in all the country code for Home phone/ Business Phone of
the Contacts”.

No area code is allowed for Mobile –

Validation message – “No area code is allowed for Mobile -{0}”.

Wrong inputs (length greater than 10) is not allowed for any mobile entered.
Validation message – “Mobile Nos -({0}) entered for the Contacts are not all Valid”.

7. All the party validation will be applicable for those parties whose create date is later than a date specified in
the config.

Config entry for the Cut-off date - <add key="Party_InputDate" value ="2013-02-28"/>

4
 SIFL Plugin

1.2 Contract Validation -

Contract Validation implements ‘I42ContractValidation’ interface to enforce the following rules. All validation is
done for the Contract Id greater then 237.

1. Operating Unit cannot be blank and has to be the last child item of the list.
Validation message – “Please select proper Operating Unit.”

2. Business Unit cannot be blank and has to be the last child item of the list.
Validation message – “Please select proper Business Unit.”

3. BusinessModelId has to be selected 100/102.

Validation message – “Please select proper Business Model ”

4. In case of Contracts are of “Product Type” – “Adhoc Payment”/ “dhoc Receipt” all the flows created under
that contract should be of type “Post Dated Cheques”/ “Oracle Payables”.
Validation message – “Please select proper Payment Method”
Product Ids are not configurable. Ids are 16/17. Also FlowMethodIds are not configurable. Ids are 5140
and 5137.

5
 SIFL Plugin

1.3 Contract Termination Validation -

Contract Termination Validation implements ‘I42ContractTerminationValidation’ interface to enforce the

following rules

1. No quote for termination can be created without selecting a reason for termination.
Validation message – “Please select a reason for Termination.”

6
 SIFL Plugin

1.4 Bank Flow Validation -

Bank Flow Validation implements ‘I42PluginBase’ and ‘I42BankFlowValidation’ interface to enforce the following
rules

All the validation is for Bank flow of type “Receipt”

1. If Bank Flow Item Type is ChequePayable

Validation message – “Please select Bank Flow Type other than Cheque Payable .”

2. If Bank Flow is not IsManualDd.

Validation message – “Please select Manual Request”

3. If Bank Flow method ID is not 5140 then

Validation message – “Please select Flow Method other than Oracle Payables.”

4. If Bank Flow created for Direct Customer or End Customer Party then party should be in Customer State”.
Validation message – “No Financial Transaction could be done until the respective Party is a
Customer.”

7
 SIFL Plugin

1.5 Credit Line Validation -

Credit Line Validation implements ‘I42CreditLineValidation’ interface to enforce the following rules

1. Branch cannot be blank for Credit Line.

Validation message – “Please select Operating Unit”

2. Branch has to be last child element from the list for Credit Line.
Validation message – “Please select Proper Operating Unit”

3. Business Unit cannot be blank for Credit Line.

Validation message – “Please select Business Unit”

4. Business Unit has to be last child element from the list for Credit Line.
Validation message – “Please select Proper Business Unit”

5. Maximum External IRR for the Credit Line is restricted. Any value cannot be entered into that field.
Validation message – “Please do not Enter anything in 'Maximum External IRR' field.”

6. Minimum External IRR for the Credit Line is restricted. Any value cannot be entered into that field.
Validation message – “Please do not Enter anything in 'Minimum External IRR' field.”

8
 SIFL Plugin

1.6 Purchase Invoice Validation -

Purchase Invoice Validation implements ‘ I42ContractPurchaseInvoicesValidation’ interface to enforce the

following rules

All the validation is for Purchase Invoice whose invoice date is greater than a configurable date.

1. For Purchase Invoice Contract/Asset have to be selected.

Validation message – “No contracts/asset associated with this PI or No line item to save.”

2. Total PI cannot be more than the Asset Cost for the selected Asset.
Validation message – “Total PI can not be more than the Asset Cost for the asset id - {0}”

3. If Invoice Date is prior to the Creation date of the Contract.

Validation message – “Invoice Date of PI can not be prior to Contract Start Date ”

4. If the Contract is not in Complete Activated state.

Validation message – “No PI can be created - Contract is not in Complete Activated state ”

5. In case of editing the existing PI If Bank Flow is created against the PI already no editing is allowed.
Validation message – “The PI is already allocated. No updation is allowed.”

6. In case of editing the existing PI If the contract associated with the PI is in in Terminated / Matured /
Suspended state then no editing is allowed.
Validation message – “The Contract associated with this PI is already in Terminated/Matured/Suspended
state. No updation is allowed.”

9
 SIFL Plugin

1.7 Work Flow Validation -

Work Flow Validation implements ‘I42WorkflowStateChangeValidation’ interface to enforce the following rules.

Each Validation is for certain states. There is a “From State” – from which state the work flow is achieving the current
state and “To State” – to which state the work flow is currently reaching.

Validation for the System Work Flow State Chain.

1. If the Work Flow To State is “Completely Activated” then if the applicant of the contract is not in
“Customer” state the action cannot be completed.

Validation message – “Applicant for the contract is not in customer state”

2. If the Work Flow To State is “Completely Activated” then for the contract where product Id In
2,3,5,6,8,9,13 the purchase location and sales location need to be selected properly.
Validation message – “Please select proper Purchase Location/Sales Location with respect to
GST”

Validation for the Custom Work Flow State Chain.

Validation for “Party” Work Flow. – All the validation is for the party type “Direct Customer”/ “End
Customer” and for the state (To State) “ Qualified Prospect”

1. If the Party is “Individual” then if the Pan Number (Field Name – Reference in the Party Tab) is provided
but the format is wrong the action cannot be completed.

Validation message – “Please input valid Pan No.”

2. If the Party is “Individual” then if the Pan Number (Field Name – Reference in the Party Tab) is provided
and the format is correct but “Form 60” Custom field is checked the action cannot be completed.

Validation message – “There is a valid Pan No. - 'Form 60' can not be checked'”

3. If the Party is “Individual” then if the Pan Number (Field Name – Reference in the Party Tab) is not
provided and “Form 60” Custom field is checked then “Document Id” has to be provided otherwise the
action cannot be completed.

Validation message – “'Form 60' is checked, please enter at least one item in Driving Licence
No./Passport”

4. If the Party is “Individual” then if the Pan Number (Field Name – Reference in the Party Tab) is not
provided and “Form 60” Custom field is not checked the action cannot be completed.

10
 SIFL Plugin

Validation message – “Please enter Pan No. or check 'Form 60' and atleast one of the Driving License
No./Passport”

5. If the Party is “Individual”/“Business” then at least one Phone among Home Phone/Business Phone/
Mobile has to be provided for one of the office type contact otherwise the action cannot be completed.

Validation message – “Atleast one Phone among Home Phone/Business Phone/ Mobile has to be
provided for one of the office type contact”

6. If the Party is “Individual”/“Business” then at least one Street Address/Mailing Address has to be
provided for one of the office type contact where Home Phone/Business Phone/ Mobile has been
provided otherwise the action cannot be completed.

Validation message – “Street Address/Mailing Address has to be provided for one of the office type
contact where Home Phone/Business Phone/ Mobile has been provided”

7. If the Party is “Individual” then “Date of birth” is mandatory otherwise the action cannot be completed.

Validation message – “Please enter date of birth.”

8. If the Party is “Individual” then “Date of birth” has to be valid otherwise the action cannot be completed.

Validation message – “Please enter valid date of birth. Applicant must be above 18 yrs.”

9. If the Party is “Business” then “TAN” has to be provided otherwise the action cannot be completed.

Validation message – “Please input Tax Registration No.”

10. If the Party is “Business” then Pan Number (Field Name – Reference in the Party Tab) is mandatory
otherwise the action cannot be completed.

Validation message – “Please input Pan No.”

11. If the Party is “Business” then Pan Number (Field Name – Reference in the Party Tab) is provided but the
format is wrong the action cannot be completed.

Validation message – “Please input valid Pan No.”

12. If the Party is “Business” then and a valid Pan Number (Field Name – Reference in the Party Tab) is
provided but “Form 60” is also selected then the action cannot be completed.

Validation message – “There is a valid Pan No. - 'Form 60' can not be checked”

11
 SIFL Plugin

13. If the Party is “Business” then “Date of Incorporation” is mandatory otherwise action cannot be
completed.

Validation message – “Please enter date of Incorporation”

14. If the Party is “Business” then “Date of Incorporation” can not be after today.

Validation message – “Established Date cannot be greater than today. ”

Validation for “Contract” Work Flow. –

1. If the Work Flow State Name is “Credit Line Takedown” if there is no Credit Line Takedown
Validation message – “No Credit Line Takedown for this contract ”

2. If the Work Flow State Name is “Contract Activated” then contract where product Id In 2,3,5,6,8,9,13
the purchase location and sales location need to be selected properly.
Validation message – “Please select proper Purchase Location/Sales Location with respect to
GST”

Validation for “Credit Line” Work Flow. –

1. If the Work Flow State Name is “Lead Recommendation” and Effective date of the credit line is not
selected -
Validation message – “Please enter Effective Date”

2. If the Work Flow State Name is “Lead Recommendation” and Effective date of the credit line is same with
Expiry Date-
Validation message – “Please enter Term (months)”

12
 SIFL Plugin

2. Configuration
For all required configuration entries the will be .config file – “SREIValidation.config”. this file has to be placed in the
“plugin” folder of the installed directory path of the AAF application.

<?xml version="1.0" encoding="utf-8" ?>

<configuration>
<appSettings>
<!-- yyyy-MM-dd-->
<add key="Party_InputDate" value ="2013-02-28"/>
<add key="Contract_CalcDate" value ="2013-03-31"/>
<add key="BankFlow_ActualDate" value ="2013-02-28"/>
<add key="PurchaseInvoice_InvoiceDate" value ="2013-02-28"/>

<add key="Party_Oracle_Supplier_Site_Code" value ="Oracle Supplier Site Code"/>

<add key="Party_Oracle_Supplier_Number" value ="Oracle Supplier Number"/>
<add key="Party_BranchId_For_SEFPL" value ="17"/>
<add key="Party_OperatingUnitId_For_SEFPL" value ="3"/>
<add key="Party_CFD_Form_60" value ="Form 60"/>
<add key="Party_CFD_CIN" value ="Customer Identification Number"/>

<add key="CreditLine_Client_Grading" value ="Client Grading"/>

<add key="CreditLine_Customer_Type" value ="Customer Type"/>

<add key="Contract_Exclude_Business_Ids" value ="104,105,106,107,108,109"/>

<add key="Purchase_Invoice_allowed_Ids" value ="21,22,23"/>

<add key="Contract_Cfv_Upfront_collected" value ="51"/>

<add key="Wf_Party_Qualified_Prospect" value ="Qualified Prospect"/>
<add key="Wf_Contract_Disbursement_Request" value ="Disbursement Request"/>
<add key="Wf_Contract_DOAApproval_Initiated" value ="DOA Approval Initiated"/>
<add key="Wf_Contract_Deviation_Level_3" value ="Deviation Level 3 : RH"/>
<add key="Wf_Contract_Deviation_Level_4" value ="Deviation Level 4 : BH"/>
<add key="Wf_Contract_Deviation_Level_5" value ="Deviation Level 5 :CH / CEO"/>

<add key="Wf_CrefitLine_Lead_Generation" value ="Lead Generation"/>

<add key="Wf_CrefitLine_CAM_Reviewed" value ="CAM Reviewed"/>

<add key="Party_Related_Party_CFD_ID" value ="128"/></appSettings>

</configuration>

13
 SIFL Plugin

3. Known Issue
There no known issue.

4. Installation
According to the Documentation of the AAF application and setting.

14