Offices and Branches. Hierarchical structure. There is a 'hierarchy' field which has a dot notation e.g. '.3.2.' is the value for office_id 2 which has a parent office_id of 3 and the parent of 3 is the default top office with a hierarchy of '.' - if you order office records by hierarchy field they are returned in the tree structure of the hierarchy.
Allow recording of office transactions into and out of an m_office. It can be used to set opening balances e.g. someone funded the Head Office with $25,000 US. It can be used to show the Head Office giving and receiving funds from branches. It can be used to declare incidental costs within a branch e.g. $100 US for furniture.
Note: This table is used for Heaven Family MFI, and in general need not be applicable to others.
All the MFI's staff. Some (or all) of these will have logins for Mifos X (m_app_user). Currently, very lonely as development recently started.
All formation of a group by adding clients. A Client can be in more than one group at one time. (development recently started)
Fees, Penalties and Charges - still under development - may need to have separate tables for fees, penalties and charges - may not. Currently scope to all flat and % fees for loans.
Defines a loan product.
Defines the list of m_charges associated with loan product.
Identifies a fund. And so can be used for seeing how funds have been 'disbursed'. Can be associated with loan products and loans.
List of charges associated with a loan.
Loan Disbursals, Repayments, Waivers and Adjustments.
Loan schedules (installments for loans).
Defines a savings product (very lonely at the moment, doesn't even have its m_savings table set up - still under development)
Defines a deposit account. The current scope is Fixed Term Deposit Accounts and Certificate of Deposit Accounts.
Deposit account - relates to m_product_deposit
Deposit account transactions - deposits, withdrawals and interest postings
Identifiers associated with a customer
Metadata of documents associated with various entities (clients, loans, client Identifiers, staff)
Application Users, Roles & Permissions Tables
Mifos X application users (logins)
Roles associated with an application user
Permissions associated with a role.
Codes, Enums, Notes & Currency Tables
User definable codes. Right now there are no user defined codes in the mifos X database. But there will be e.g. gender, title. Some 'user-defined' code values may be shipped with the database but these values can be changed and added to.
User defined values for m_code. The code field will typically save the m_code_value.id. Example SQL
select cv.code_value as Occupation from m_client c left join m_code_value cv on cv.id = c.occupation_id
Database version of Java enums. Not linked to Java code. For reporting only. e.g. If I want to report on loan statuses, I see what enums are used and put values on this table. Example SQL
select l.id, st.enum_message_property as Status from m_loan l left join r_enum_value st on st.enum_name = "loan_status_id" and st.enum_id = l.id
List of currencies and currency data.
List of currencies that can be used within the MFI (organisation). Probably will be put in the "On the way out Tables" list at some point as the same functionality can be achieved by adding a "can_use" flag onto m_currency.
General note table. Other tables such as m_client, m_loan, m_loan_transactions can have notes associated with them.
The 'strategy' to be applied when receiving loan repayments e.g. What order to pay fees, penalties, interest and principal.
Reporting MetaData Tables
Functionality related to these tables runs Pentaho reports and returns Pentaho output (html, pdf, excel, csv formats). Also runs "screen-based" reports/charts where the Java API returns a generic resultset output which is processed by a reporting JQuery plugin based on JQuery Data Tables
Data for Pentaho reports, screen-based reports and charts (includes SQL if not Pentaho)
Parameter definition data (may include SQL)
Parameters for Reports
Utility table (just has an id value) used to create certain reports... not important. Might be put in the "On the Way Out" list at some point.
Registered External Data Tables
Contains a list of registered external tables (currently MySql in same database as Mifos X schema) and the Mifos X core table to which they are associated. Allows the external table's data to be restricted to the user hierarchy and CRUD permissions to be managed.