MES Core Dispatch: Difference between revisions
Jump to navigation
Jump to search
(explaining views) |
|||
Line 8: | Line 8: | ||
*SQL Architecture: | *SQL Architecture: | ||
**Primer - | **Primer - | ||
***SQL views - A SQL view is an aggregate of many SQL table columns that makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store the data in this usable joined together format. For instance, you will likely want a table that uses columns from products orders and traceability to show what product serial numbers are with what customer. | ***SQL views - A SQL view is an aggregate of many SQL table columns that makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store the data in this usable joined together format. For instance, you will likely want a table that uses columns from products orders and traceability to show what product serial numbers are with what customer. A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT * FROM view | ||
***Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table. | ***Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table. | ||
**Orders Master Table View | **Orders Master Table View |
Revision as of 16:03, 30 April 2019
Summary
This process kicks off other processes and decides what to do next. It is the heart of the MES and directly interacts with customer orders, returns and other data to decide how to manage all other processes.
Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS
SQL architecture
- SQL Architecture:
- Primer -
- SQL views - A SQL view is an aggregate of many SQL table columns that makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store the data in this usable joined together format. For instance, you will likely want a table that uses columns from products orders and traceability to show what product serial numbers are with what customer. A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT * FROM view
- Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.
- Orders Master Table View
- Overview: This table shows the current placed orders and links to the customer that placed it. Also has keys to
- Columns:
- PID - Foreign key to the Products table for what product is ordered
- Qty - how much was ordered
- Products Master Table View
- Columns:
- Primer -
- Traceability Master Table View
- Columns:
- Customer Data Table View
- Traceability Master Table View