[ERP software] what are the dangers of the secondary development of ERP system?

stay ERP In the practical application of the system , Because the situation of each enterprise is different , There may be some situations that cannot meet the needs of enterprises , Although the system can meet some requirements after parameter adjustment , But in many cases, the original program needs to be changed 、 Even need to modify the original database structure to meet the requirements .

The general presentation requirements are ERP The reasons for the secondary development of the system are about these ：

1. Users do not accept the operating habits of the new system

ERP Products in order to adhere to strong versatility , The function and process settings are standard and standard . But in implementation , In addition to the characteristic requirements of business processes and other aspects , There are also some that do not touch business processes 、 The need for operational habits arising from the particularity of enterprises , And put forward a large number of secondary development .

2. Special process requirements caused by the non-standard handling system of the enterprise

Most enterprises want to integrate the existing technological process 、 The craft homework is completely sealed and moved to ERP In the middle , Without analyzing the advantages and disadvantages of the standardized process and the original process of the enterprise , Stubbornly adhere to the current handling methods 、 Handling habits , It is necessary to carry out secondary development to meet its needs .

3.ERP Software really can't meet the requirements

ERP The system belongs to the general software of the industry , But every enterprise has its own characteristics , Indeed, there are some feature requirements , Secondary development is required , We should not only absorb advanced management thinking in software , We should also adhere to the characteristics of the enterprise .

4. Interface requirements

Informatization construction involves multiple systems , Such as OA、 E-commerce platform, etc , There is information sharing among the data of various systems , There are system interface requirements , Secondary development has also become inevitable .

5. New demands arise

With the deepening of the project implementation , Enterprise personnel have a deeper understanding of the information system , Application continues to deepen , More requirements will be put forward for information system products , Make the system more suitable for enterprise operation .

ERP The system will have secondary development requirements , It can solve some problems at that time , However, the secondary development has disrupted the original structure , It may also bring danger , Here's a summary of some of the dangers that can arise ：

1. Too much secondary development will increase the difficulty of system promotion

ERP Suppliers will improve and expand the new functions of the system in stages , Constantly launch new versions . The promotion of the system is only for the Standard Version , We will not consider the part of characterization and secondary development , Therefore, most of the secondary development work should be revised or developed from scratch .

2. Secondary development will reduce the stability of the system

sophisticated ERP The software has high stability . The secondary development is only for a single user , The change of a certain part often fails to consider the impact on the overall situation due to the satisfaction of special needs, which will affect the stability of the whole system , And the test and trial run time of secondary development is limited , The complexity and coupling of the system increase , Decrease the stability of the system .

3. Secondary development sometimes deviates from enterprise implementation ERP The original intention of the system

Secondary development requirements often make ERP The logic of a reasonable system succumbs to the inherent 、 Habitual working methods , It will also improve the power of the system used by employees in different departments , And affect the stability of the process . Enterprises cannot learn system optimization process , Learn advanced management mode .

4. Secondary development add ERP Cost of the project

Due to the planning effect , The price of product software is relative to its implementation cost, which is low . The secondary development is only for the only user , So all the costs of developing these programs are borne by them , That is to use the secondary development of the enterprise , Also invest manpower 、 material resources , Must add ERP Cost of the project .

Facing the dangers that may appear above , So do we have a way to control ？ Although the needs of each enterprise are different , But it is necessary to keep this rule in mind ： Execute ERP The purpose of the secondary development project is to improve the management level of the enterprise , Optimize the process of the enterprise . The stability of business processes will be affected by increasing the power of a single work , Never do ; Due to the increase of working power , There is no helpful development for business process and management level , Try to do as little as possible .

1. Plan the business of the whole enterprise , There should be trade-offs in secondary development

About manufacturing enterprises , Will touch CAD、PDM、CAPP、ERP、MES system , And there are interface integration , Therefore, according to the situation of the enterprise , Consider from the whole , Instead of considering from a function point or a business department . Enterprises should not pay too much attention to their own characteristics , Exactly? ERP The handling process in has certain progressiveness and rationality . Some particularities are caused by the irrationality of the enterprise process itself , Should go through ERP The implementation of , Optimize and reorganize the business process of the enterprise , Instead of blindly modifying the software to adapt to unreasonable processes .

2. Use the original “ Put on hold ” Field , Prevent changing the database structure

It will involve the development of new fields and affect the original database structure , Try to use the original “ Put on hold ” Field , Don't add fields or file files easily . If there is a real demand, confirm with the original developer , To prevent the secondary development from stacking or conflicting with the product development direction , To decline the trouble of promotion in future editions .

3. Don't modify the core code at will , The new function has better form its own module

Strictly abide by the rule of not modifying the core code . If necessary, develop , Try to make the functional modules of secondary development independent of the original system . So when the system version is updated , The secondary developed module can be applied to the high edition system without modification or with less modification .

4. Establish standards for secondary development

A complete set of development processes and standards should be established for secondary development . Newly expanded fields 、 Formulate unified standards for the naming of new programs , And reserve expansion space . Common components are not recommended to be modified , The method of inheritance should be used in programming .

ERP system sofastsoft.com The secondary development of enterprise has a very important meaning ,ERP The success rate and benefit of implementation have reference value , It should not only be handled according to the enterprise , We should also help enterprises develop in an all-round way .