One of the most frustrating parts of any ERP implementation is the realization that at the end of the project, there are still some functionality needs that have not been addressed.  For the successful implementations, these needs are not wide ranging and only impact a small number of users, but in other cases, they are more reflective of over promising functional abilities during the sales process, or just a plain indicator that at some point during the implementation, certain modifications make it into the application, and others don’t. 

Don’t make the mistake however to view missing functionality as an implementation failure or more importantly, an incomplete installation.  All ERP applications are designed to allow companies to add functionality via customizations or ‘add-on’ packages, as no two companies require the same functionality.  What makes an ERP application complete is the belief that is supports the business needs and objectives in a way that adds value back to the organization, with a total cost of ownership (TCO) that is acceptable, and an return on investment (ROI) that meets management’s expectations.  For these reasons, invest time to fill the missing functional parts to allow your company to ‘complete’ its ERP implementation.  Each time you complete a functional need, even a small one that leads to productivity gains, is a chance to lower your TCO and increase your ROI.  Plus you have the additional benefit of a satisified user, one who can work more efficiently and profess support for the ERP application with others in your organization.