库存系统所需的信息
我正在为肉类市场建立一个销售点，需要特定信息，因为它涉及如何跟踪库存。我想为这个系统设计数据库，但缺乏所需的知识。我已经有了一个可以处理产品的基本数据库，但需要实现一些额外的东西来处理肉类的重量。
将会有大量库存，例如肉类和销售的产品。这里是否有人拥有一些深入的库存控制经验，可以与我分享想法，或者告诉我在哪里可以找到此信息，而不必自己成为该主题的专家？
例如：店主周一购买了 100 磅牛胸肉并将其输入库存，然后周二以不同的价格从不同的供应商处额外购买了 100 磅。两个项目在数据库中都有各自的 ID。例如，如果店主有 10 个不同的供应商销售完全相同的产品，这是否意味着我应该在数据库中存储 10 个不同的商品 ID？
I'm building a point of sale for a meat market and need specific information as it relates to how inventory should be tracked. I want to design the database for this system but lack the knowledge needed. I already have a basic database that will handle products but need to implement something additional that will handle the weight of the meats.
There will be bulk inventory such as meat plus products that are sold. Is there anyone here that has some in-depth inventory control experience that can share ideas with me or maybe tell me where I can find this info without having to become an expert on the subject myself?
For example: The store owner purchases 100 lbs of beef brisket on Monday and enters that into his inventory and then on Tuesday purchases an additional 100 lbs from a different vendor at a different price. Both items have their respective ids in the database. If the store owner has for example 10 different vendors selling the exact same product, does that mean that I should store 10 different item ids in the database?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
作为他们的顾问，您有必要了解他们的数据需求，并能够将这些需求转化为可以满足这些需求的适当模式。我同意 Oded 和 smirkingman 所说的，但为了帮助您理解您的示例：
您不应该重复该项目，而应该使用单独的表来保存
i.e. various meats
i.e. name, location
i.e. pounds of meat (identified w/ by foreign key to ITEM table)
vendor from which item were purchased (identified by foreign key to VENDOR table)
date of transaction, rate, total cost, etc.
这只是一种方法，但我们的观点是，你不仅需要精通他们的业务需求，还需要具备数据库知识，将其转化为技术设计/功能。
一如既往，客户/用户永远不知道他们需要什么，也不知道他们真正想要什么。您的工作不仅要询问他们，还要与他们一起解决问题。这包括提出场景、主要用例/故事等——基本上，他们需要跟踪哪些常见/不常见的事情？
例如，在每笔交易中，他们是否需要维护付款方式的记录？参与交易的供应商代表又如何呢？他们稍后需要这些信息来进行税务报告吗？预算/财务预测？如果一半的商品到货时有问题怎么办？了解他们的流程以及他们如何处理每种情况以及他们需要了解什么，然后尝试提出相应的技术解决方案。
As their consultant, it is necessary for you to understand their data needs and be able to translate those needs into an appropriate schema that can fulfill those needs. I agree with what Oded and smirkingman have said, but to help you along in regards to your example:
you should not duplicate the item, but rather have separate tables to hold
i.e. various meats
i.e. name, location
i.e. pounds of meat (identified w/ by foreign key to ITEM table)
vendor from which item were purchased (identified by foreign key to VENDOR table)
date of transaction, rate, total cost, etc.
This is just one way to do it, but our point is, you need to be well versed in not only their business needs, but also have the database knowledge to translate them into technical design/features.
And as always, clients/users NEVER know what they need, nor what they really want. It's also your job to not only ask them, but work with them to figure it out. This includes coming up with scenarios, primary use cases / stories, etc. - basically, what common/uncommon things do they need to track?
For example, in each transaction, do they need to maintain record of method of payment? What about the vendor representative(s) involved in the transaction? Will they need this information later for tax reporting? Budget / financial forecasting? What if the half the items are bad on arrival? Understand their process(es) and how they would handle each scenario and what they need to know, and then try to come up with technical solutions to address accordingly.
我管理一个拥有住所的维护实体。我们曾经在十二月份对仓库进行过盘点。
在从不同供应商以不同价格购买相同商品之前，数据库会计算该商品的平均价格。
但正如上面所说，了解您的客户/用户的需求很重要。他们的会计程序是什么，你可以将其翻译成技术术语和设计
i manage a maintenance entity with a wherehouse. And we used to make inventory of the wharehouse in december.
fore the same items bought from different vendors with different prices , the database compute the mean price of the items.
but as what is said above , it's important to know your client/users need. what is their procedure in accounting and you translate it in technical terms and design
库存系统中的一个关注点基本上是研究如何将管理费用、劳动力成本、增值税费用（如果有）纳入您的库存，以及如何在交货时确认其销售成本。 Bitxwise 已经提出了一些简洁的架构，artoure 表示，在开始设计表格之前，请先了解客户的会计政策和税务规定。
A point of concern in inventory system, is basically looking into how to incorporate overheads, labour cost, value-added tax charges (if any) into your inventory, and how do you recognise their cost of sales when a delivery is made. Bitxwise has come out with some neat schema, and artoure put it, understand the accounting policy and tax ruling of your client before you start designing out the tables.