Before you start building your institution's data elements and chart(s) of accounts, you need to understand the dependencies within the Kuali Financial System, especially dependencies between modules. For example:
-
The definition of object levels has an impact on the Capital Assets Management module. So, when you start to define your objects, be sure you keep this impact in mind and identify all object types that are capitalized.
-
When you set up multiple banks, it's important that you understand how flexible cash offsets work in the Kuali Financial System.
-
If you plan to implement the Budget Construction module, keep this module in mind when you set up your organization hierarchy structure and assign fiscal officers and delegates to accounts. This is important because the Budget Construction module relies the organization hierarchy structure in the Kuali Financial System when it configures security access. If you set up your organization hierarchy structure and assign fiscal officers and delegates to accounts without regard for this fact, you may encounter security issues when you implement the Budget Construction module.
These are just a few examples, but they show the importance of understanding dependencis. If you take the time to understand the modules' dependencies up front, you'll save yourself a lot of rework later on.
Chuck Kensicki
Kuali Consultant
rSmart
Post new comment