Hello Gayl and all! First of all, assuming that you have successfully inserted the GL Accounts and run Mifos, the "blank screen" error/problem doesn't output any errors associated with it. I tested it myself. That is why such a problem is kind of frustrating. Probably the Mifos team are yet to put a solution to this problem such that an appropriate error message will be prompted on the screen.
Gayl, I examined your chart of accounts and I think it is just fine. But in your financial action mappings, I noticed that you changed the key names such as the <entry key="PRINCIPALPOSTING" value="11200-1000"/> into <entry key="PrincipalPosting" value="11200-1000" />. I believe that you should retain the key names since they are looked for by the FinancialActionConstants java class during runtime. Here's a copy of the financial action mappings that you should follow: http://www.mifos.org/knowledge/support/deploying-mifos/configuration/guide#creating-your-own-financial-action-mappings . Also, you have an entry in the financial action mappings with GL code " 31101-1000" that does not exist in your chart of accounts: <entry key="INTERESTPOSTING" value="31101-1000" /> This might cause a problem. :D I've written what I have found out during the time I encountered this case particularly in the 1.4 and 1.5 versions. Someone might call these "newbie's findings" but at least these might help. :D 1.) The file mifosChartOfAccounts.custom.xml (customized chart of accounts file) overwrites mifosChartOfAccounts.xml (default chart of accounts file shipped with Mifos) on the database. Meaning to say, the moment Mifos is started for the first time, it first looks for a file named mifosChartOfAccounts.custom.xml to see whether or not there is an existing customized chart of accounts defined. If it saw errors from that file, it will immediately crash by itself and won't proceed anymore looking for mifosChartOfAccounts.xml. If it doesn't see such a file, it will just proceed reading the default chart of accounts. Therefore, it doesn't really matter if we used some of the GL codes from the default chart of accounts and use it on our customized one. We can also conlcude from here that we can fully customize a chart of accounts as long as we abide by the parent accounts (Assets, Liabilities, Income, Expenditure). 2.) As a corollary to 1) I successfully added a second level GL account with ease, including child accounts (leaf) under that new account I added, particularly directly below the Assets account, which was already reflected in the Mifos application. 3.) Alphanumeric GL codes are possible. Although not just alphanumeric but also it can include special characters such as the '-'. We can have GL codes such as "101002", "AB1829", "1020-AB7128", "xx234", "^...@*#()" and so on since in the database their datatypes are varchar. 4.) The assignment of GL codes is fully arbitrary. For instance I have "10000" as the GL code for Assets which is a parent account (root). The GL codes of its immediate children doesn't have to follow its GL code in such a way that you should have their GL codes, say for example, as "10020" or "101010." In fact, we can define any GL codes we desire. Say, for instance, I want the account "Loans Receivable-Group Loan-Admin" which I will place under "Assets" to have a GL code of "2000310-010" or "500932840892-203984-9123487009238" and etc. 5.) All financial action mappings must be mapped to one account in the chart of accounts. If there is a mismapping, the application would immediately crash since the mappings are mapped in the FinancialActionConstants java class. -------------------------------- (1) Be warned that you need to update the class attribute in your mifosBeanConfig.custom.xml. You should change the tag <bean id = "financialRules" class="org.mifos.application.accounts.financial.util.helpers.FinancialRules" abstract="false" factory-method="getInstance"> into <bean id = "financialRules" class="org.mifos.accounts.financial.util.helpers.FinancialRules" abstract="false" factory-method="getInstance"> The change must be a result of refactoring the Gazelle repository of Mifos. Mifos haven't included this upgrade yet. And also I copied the default financial action mappings from http://www.mifos.org/knowledge/support/deploying-mifos/configuration/guide#creating-your-own-financial-action-mappings in which they haven't updated yet in the section "Creating Your Own Financial Action Mappings" section hence the problem. (2) As defined in the FinancialActionsConstants class (F inancialActionConstants.java) these are the only financial actions that can be used. But be warned that the word "voluntary" as in voluntarydeposit is spelled as "voluntory" as in VOLUNTORYDEPOSIT. Tricky eh. Been a victim of this. 01. PRINCIPALPOSTING 02. INTERESTPOSTING 03. FEEPOSTING 04. MISCFEEPOSTING 05. PENALTYPOSTING 06. MISCPENALTYPOSTING 07. DISBURSAL 08. ROUNDING 09. MANDATORYDEPOSIT 10. VOLUNTORYDEPOSIT 11. MANDATORYWITHDRAWAL 12. VOLUNTORYWITHDRAWAL 13. SAVINGS_INTERESTPOSTING 14. CUSTOMERACCOUNTMISCFEESPOSTING 15. MANDATORYDEPOSIT_ADJUSTMENT 16. VOLUNTORYDEPOSIT_ADJUSTMENT 17. MANDATORYWITHDRAWAL_ADJUSTMENT 18. VOLUNTORYWITHDRAWAL_ADJUSTMENT 19. WRITEOFF 20. RESCHEDULE But according to http://www.mifos.org/knowledge/support/deploying-mifos/configuration/guide#creating-your-own-financial-action-mappings there are other mappings that can be used which were not included in the default Mifos package. On Tue, Aug 17, 2010 at 6:37 PM, Gayl Kennedy <[email protected]> wrote: > We successfully tested mifos on our own server last week and all was > looking good until we tried to load our final chart of accounts and > financial mapping table to replace the default version. > I have attached chart of accounts and mapping. The Financial Mapping I > have has refuses to load. Not quite sure why, I have attached both > files (chart of accounts and mapping) with the log file . > > When we try to create a loan, savings product or fee it does not work > - the error messages are: > Loan product: Page expired since the action is not permissible. Click > on the tabs above to proceed. > Savings product: Fatal chart of accounts error: account with general > ledger code 24000 not found. > Fees: - gives a blank page, no error message > > When we reverted back to the default chart of accounts we no longer > get the above errors. > Regards > Gayl > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Mifos-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mifos-users > > -- *NEIL*
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Mifos-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-users
