...
NAME | Datatype | Length | Remarks | |
---|---|---|---|---|
id | BIGINT | 20 | PRIMARY KEY & AUTOINCREMENT | |
loanproduct_id | BIGINT | 20 | FOREIGN KEY | |
category_id | BIGINT | 20 | FOREIGN KEY | |
min_age | BIGINT | 20 | NOT NULL | |
max_age | BIGINT | 20 | NOT NULL | |
provision_percentage | INT | 4 | DEFAULT 0 | |
liability_account | BIGINT | 20NOT NULL | FOREIGN KEY acc_gl_account.id | |
expense_account | BIGINT | 20NOT NULL | FOREIGN KEY acc_gl_account.id | |
created_by | VARCHARBIGINT | 100 | app user name20 | FOREIGN KEY m_appuser.id |
created_on | DATE | |||
modified_by | VARCHAR | 100app user name | FOREIGN KEY m_appuser.id | |
modified_on | DATE |
For any given tenant, the provision details for a particular loan product will look like below.
id | loanproduct_id | category_id | min_age | max_age | provision_percentage | liability_account | expense_account | created_by | created_on | modified_by | modified_by |
---|---|---|---|---|---|---|---|---|---|---|---|
1 | 10345 | 1 | 0 | 0 | 5 | abcd account | dcba account | Nazeer100 | 31-Dec-2014 | Vishwas200 | 10-Jan-2015 |
2 | 10345 | 2 | 30 | 60 | 20 | abcd account | dcba account | Nazeer200 | 31-Dec-2014 | Vishwas400 | 10-Jan-2015 |
3 | 10345 | 3 | 60 | 180 | 50 | abcd account | dcba account | Nazeer400 | 31-Dec-2014 | Vishwas500 | 10-Jan-2015 |
4 | 10345 | 4 | 180 | 360 | 90 | abcd account | dcba account | Nazeer300 | 31-Dec-2014 | Vishwas600 | 10-Jan-2015 |
While editing the loan product, persisted provision details will be restored in the edit loan product screen
...
Name | Datatype | Length | Remarks |
---|---|---|---|
id | BIGINT | 20 | PRIMARY KEY and AUTOINCREMENT |
currency_code | BIGINT | 20 | FOREIGN KEY m_currency.id |
office_id | BIGINT | 20 | FOREIGN KEY m_office.id |
product_id | BIGINT | 20 | FOREIGN KEY m_product_loan.id |
category_id | BIGINT | 20 | FOREIGN KEY m_provision_category.id |
overdue_in_days | BIGINT | 20 | DEFAULT 0 |
amount_to_be_reserved | BIGINT | 20 | DEFAULT 0 |
created_by | BIGINT | 20 | FOREIGN KEY m_appuser.id |
created_on | DATE | NOT NULL | |
modified_by | BIGINT | 20 | FOREIGN KEY m_appuser.id |
modified_on | DATE |
Whenever the provision calculation is done, system is going to make an entry in the 'provision_history' table. The structure of the table is shown below
Name | Datatype | Length | Description |
---|---|---|---|
id | BIGINT | 20 | PRIMARY KEY & AUTO INCREMENT |
created_on | DATE | NOT NULL | |
journalentryjournal_entry_created | INT | 1 | DEFAULT 0 |
created_by | BIGINT | 20 | m_appuser_id or scheduler job dummy id |
created_on | DATE |
Changes required in existing Classes:
...