Technical logic analysis of ERP creating productio

  • Detail

Technical logic analysis of manufacturing ERP to create production orders

production planning is an insurmountable gap in the manufacturing industry. Therefore, in the process of purchasing and developing various information management software, such as ERP or inventory management software, how to generate production plans in an appropriate way and at an acceptable cost is also a more important indicator. The author will discuss this content with readers today

I. business overview

there are many ways to generate production plans, among which "generate production plans according to sales orders" is the most typical. As shown in the figure below, this positioning is not standard, that is, the interface for generating production plans in an ERP system. For different industries, the specific operation methods may be different, but the principle is still the same

II. Correlation analysis with sales order business

from the business of "generating production plan from sales order", it is mainly related to three businesses of ERP system. These three businesses are sales order management, product management and capacity planning. Due to the complexity of capacity planning, it has a certain degree of independence, so the author will not describe it here. The key point I want to emphasize here is the correlation analysis between the two modules of sales order and product and this business

first, the status of the sales order determines the generation time of the production plan. In practice, when to generate a production plan is a more delicate question. It's not good to be too late or too early. In ERP system, this opportunity needs to be controlled in the sales order. The simplest principle is that only confirmed sales orders can generate production plans. From a technical point of view, only the sales order with the status of "approved" is the basis of the production plan. For those orders that are voided or in the process of confirmation, planners cannot generate production plans based on them

the second is the impact of product management on generating plans. For production planning, the BOM of products is very important. If the BOM is uncertain, the MRP cannot be expanded in the production plan. From a technical point of view, it is necessary to judge the status of the BOM of the involved products before generating a production plan. Only the verified BOM can generate a production plan. If there is no verification, the alarm information needs to be provided to the user

III. logic operation and control points behind

people have been using micro silicone tubes in the anastomosis surgery of lacrimal canaliculus fracture, and the curative effect is satisfactory

so what should we pay attention to when developing this business? The following points are for your reference

point 1: de control of manufacturing order over sales order. The main purpose of this anti control is to solve the problem of generating plans repeatedly. For example, a production plan has been generated for a sales order. When generating a production plan for the second time, what about filtering orders that have already generated a production plan? This is the first key point to control 109 ceramic bricks. Technically, the difficulty of implementation is not very great. You only need to add a "production plan" field in the sales order. When generating a production plan from a sales order, let this job automatically write the generated production plan back to this field. In this way, it can also realize the correlation between the two windows, killing two birds with one stone

second point: the change of sales order leads to the adjustment of production plan. What should I do if the sales order changes? In practice, this often happens. There are generally two treatment schemes. First, after the sales order changes, the production plan is adjusted manually. Second, after the sales order changes, the original production plan becomes invalid and needs to be rearranged. In terms of technology, similar control is also required. For example, you can set these two options in the basic settings of the production module. When the user selects which option, it is processed according to which option. For example, when users choose the second, from a technical point of view, if they want to modify the sales order, they must first delete the original production plan. For this reason, a simple control rule is that when the "production plan" field in the sales order is not empty, the sales order cannot be changed or voided through the "order change order". This can be done by triggers. However, it should be noted that when deleting this production plan, you need to clear the content in the "production plan" field of the corresponding sales order at the same time

third point: it is necessary to check the legitimacy of products and sales orders. If the product is illegal, such as a product without BOM or BOM approval, then the product cannot generate a production plan. Because this product has not been finally confirmed. Similarly, if the sales order is not approved, the production plan that can meet the basic needs of the domestic market cannot be generated. Technically, these can be achieved. Because in the corresponding table of the database, it is controlled by fields. When generating a production plan, you only need to judge the contents of these fields

IV. common problems and Countermeasures in business application

in the specific application and development process, this business will have different ways of expression in different industries, and will also encounter different problems. The author has implemented this business for many industries. Here will be encountered some common problems, I hope you readers take warning

first question: the name of the production plan. In the final analysis, a production plan is also a document. So how to name this production plan? A simple principle is that the name of the production plan should be easy to understand and recognizable. So how to name it? The author's simple point is that if the sales order corresponds to the production plan one by one, the name of the sales order can be added to the production plan. In this way, users can understand the relationship between the production plan and the sales order as soon as they see the production plan. From the technical level, the design is a little responsible. In order to meet the different needs of different enterprises, you may need to set a switch in this document rule. For example, the user can select the coding rule to be used, including the content of the sales order in the name of the production plan. Even take the name of the sales order as the name of the production plan, and so on

the second problem: the control of the estimated completion time. Some systems are not well designed in this regard. The estimated completion time or estimated start time finally calculated by the system through a series of rules is actually later than the delivery date of the sales order. This result is obviously unacceptable to users. Therefore, in the process of production plan review, it is necessary to add this control. If the estimated start time set by the user is later than the estimated delivery date of the sales order, a warning can be given to the user, and in serious cases, the user's modification can be rejected. This can be done by triggers in the database or by code. (end)

Copyright © 2011 JIN SHI