The first step of the development process is conceptualizing the solution. You must understand the problem that you are trying to solve. At this stage, you need to identify the where and the what – where in the standard flow you need to add your code, and what code can be reused from the standard one. Remember that Finance and Operations provides numerous application frameworks and patterns that can be reused when developing any new functionality or extending any existing functionalities. If you do not understand the existing application pattern and frameworks, you may create functionality that is necessary or one that already exists in the application.

While working with the customization requests, there are typically two kinds of scenarios presented to the developers. The first scenario is a standalone functionality, where new forms, tables, and business logic need to be developed and later integrated into the core modules. In the second scenario, the existing processes within the application need to be extended to support the requirement. In both cases, it's important for the developers to understand how the business logic for the core module and its functionalities is implemented in the application. Understanding the implementation of the core functionalities and the framework is extremely important for the developers so that they can efficiently utilize, reuse, or extend these functionalities in their custom solution. In any case, customizations need to be added on a temporary basis. The customizations should be easy to isolate and remove when they are not needed anymore, or when the required functionality is added to the product in a later release.