Company recently need to do an ERP, because of little experience, so the design table this don't know the design scheme is correct
I design, the detailed information of the material table has material about 30 to 40 or so material information fields,
But when I was doing the purchase order and sales orders, there is the material information to purchase the details of the database table and sales details table,
But I make storage and delivery of these, I just link the primary key of the in and out of storage and material details of the consignee or consignor table inside, do not put all of the fields are written in,
Read out, is to use a primary key to manage information, display
I want to ask next, so that the design is reasonable? The traditional way is such a design?
In directly and accept the delivery schedule of these, whether to need to write the material information is in? Or just associated primary key is ok?
Ask ace to guide, thank you

CodePudding user response:

Purchase order and sales orders, it is the material information to purchase the details of the database table and sales details table,
-- -- -- -- --
This is a material of the snapshot model,
Instead, don't write the material information for the primary key, that is the real time mode,

CodePudding user response:

Loading and unloading materials, procurement and sales details, and itself is their a log, only when you are really exist on the management and the relationship between each other, have a role,

At the time of purchasing books, for example, assume that you do need accounting to the subsidiary materials, then accounting to the subsidiary materials; If you don't need that is not accounting - just a log laundry list on,

Actually what do you want to business accounting, the managers should ask himself, rather than ask programmer,

CodePudding user response:

Between the surface form and internal accounting, never has a hierarchical relationship,

For example, I only fill in a certain goods sold on the sales documents given to consumers, then its packing should immediately be recorded? Is out of the storehouse goods has already been recorded before packing, or sales to record? This is to test your leadership understand don't understand the business management process,

CodePudding user response:

In ERP system, management reform, first management to first, otherwise system do again good also curb,

CodePudding user response:

refer to the original poster hello_meimei response:

company recently need to do an ERP, because of little experience, so the design table this don't know the design scheme is correct
I design, the detailed information of the material table has material about 30 to 40 or so material information fields,
But when I was doing the purchase order and sales orders, there is the material information to purchase the details of the database table and sales details table,
But I make storage and delivery of these, I just link the primary key of the in and out of storage and material details of the consignee or consignor table inside, do not put all of the fields are written in,
Read out, is to use a primary key to manage information, display
I want to ask next, so that the design is reasonable? The traditional way is such a design?
In directly and accept the delivery schedule of these, whether to need to write the material information is in? Or just associated primary key is ok?
Seek expert guidance, thank

Associated with the primary key can, but must follow the principle of a yard,

CodePudding user response:

refer to the original poster hello_meimei response:

in directly and accept the delivery schedule of these, if you need the material information is written in? Or just associated primary key is ok?

This is not a pure technical (empty) on ERP explanation,

This is called "pig and pig's feet" problem, suppose a company has entered the 100 pigs, sold 257 feet, how much is left pig, please?

The problem is to test your manager, he knows that need to put the items in the middle of the machining process is defined as the information system of operation process, rather than merely playing with Numbers! At this point if you just said should be in the face of material information on the receipt, so this is grappling with fur (digital), and don't ask questions of management process,

CodePudding user response:

Can take a look at this little system, use the ACCESS library: https://blog.csdn.net/TOP_SC/article/details/52823758

CodePudding user response:

Ask for such a big problem in this BBS, as if there will be no simple answer, a more practical way is to install an open source ERP, then anatomy, then have everything, Odoo is a open source software, after many years development has been very mature, can on the basis of this data structure to build what they want, and is more effective than oneself there,

CodePudding user response:

Custom system less complex for the company, after all requirements can be customized in at any time, the database structure can change
Gm's finished ERP this it will be difficult to handle,
Can refer to this little system, universal inventory management system

CodePudding user response:

The building Lord, is only associated with material master key is likely to have problems, such as product after some years, some parameters have changed, you open the previous document you will find the documents on the material information does not accord with the information, this problem is likely personnel information, such as personnel, change the department such as
There is a snapshot of the problem, is to save material information when opening sheet to the documents, so no matter when to open the documents you can see the content is not affected by changes,

CodePudding user response:

ERP is the most critical business, business units to develop together,

CodePudding user response:

Table named principle to build
AB_PP01

A 1 yards the ERP project code
2 yards B module code, example:
Base B
The system S
Business O
3 yards of the line
4, 5 yards of the Table name
6 yards available serial number or meaningful symbol

CodePudding user response:

Normally associated with a primary key, basic data in other fields into the other table, not
But also depends on you what type of ERP, such as furniture, clothing, such as steel, figuring out the best which apply best industry standardization,

CodePudding user response: