haven't come up, see some people are talking about one thing more yards, discussion is also very warm, I want to express my point views on this question, welcome to correct me,
Actually a clock face is have more than one name, in fact this name is not the name of the material itself, is the customer name, material is for a customer to use the material name, material code is also one of the problems, and not have more than one material code, this is not the real material coding, coding should be and must be unique, speaking of which, one thing more code, more than one thing actually does not exist, this problem is well done, for different systems have different solution, I listed 2,
A, oneself development system
1, to build a material only internal ID
2, add a customer table material, the main field is the
Material ID, customer ID, material code, material name
3, when the associated query to the material table above association, will need to show to the customer the material name and material code, using the material name and material in the chart above code to replace, so that different customers have different material code, material name
Second, ufida system (not advertising)
I know, ufida system itself to have the customer inventory coding, also can have multiple customer inventory coding, there is no this problem,


Everyone on the analysis of the problems, to analysis the nature of the clear problem, don't make a mistake attributes into the dead end,
Correct me if any wrong, also welcome to discuss,
The editor good harder to use,,,,,,,

CodePudding user response:

Customer material code, fill in business documents, don't need to write in basic information

CodePudding user response:

Customer code is another table, material with customer ID to retrieve the material name and material coding

CodePudding user response:

Your top one!

CodePudding user response:

To learn, also in the treatment of the ERP at present