CampusLearn
← BIT 303 Enterprise Resource Planning

Configuration, Customisation and Case Studies

Notes

Choosing how to adapt ERP Configuration adjusts supported settings without changing core application code, such as approval limits, tax codes, warehouses or account mappings. Customisation changes or extends software behaviour through code when standard functionality cannot satisfy an important requirement. Configuration is usually easier to maintain, but it still requires documentation and testing. Excessive customisation can increase upgrade costs, create dependence on specialist developers and undermine vendor support. Before extending a system, assess whether a process can reasonably adopt standard functionality. A genuine legal or strategic requirement deserves stronger justification than a preference for familiar screen layouts. Extensions and evaluation An application programming interface (API) defines how systems exchange requests and responses. Supported APIs and separate extensions can reduce direct interference with ERP internals, but integrations still need authentication, error handling and reconciliation. Change control records the purpose, approval, testing and release plan for each modification. A useful case study compares the original problem, chosen intervention and measured outcomes while acknowledging other possible causes of change. Evaluate processing time, error rates and ownership cost rather than declaring success because the new screens look modern or because installation finished on schedule. Practical example A Machakos SACCO configures loan approvals so requests above KES 100,000 require a second authorised officer. This is a settings change, not necessarily custom code. A separate mobile repayment connector needs an API integration costing KES 180,000 initially and KES 30,000 annually in support. If it saves 25 staff hours monthly at KES 500 per hour, monthly labour capacity released is KES 12,500, or KES 150,000 annually. First-year net benefit is 150,000 minus 210,000, or negative KES 60,000. Later annual benefit is KES 120,000 before other costs, and released staff time is not automatically a cash saving.

Quiz

1. Changing a supported approval threshold is normally what kind of change?

2. Why favour supported APIs over direct changes to ERP internals?

3. With KES 150,000 annual benefit and KES 210,000 first-year cost, what is first-year net benefit?

Sign in to submit and securely grade your quiz.