Here we shared Enterprise management system Database Schema Diagram. This image represents a relational database schema for a system (likely an order management or business application) under the database leenaenterprises. It consists of six tables: orders, products, contact, employees, pages, and admin. This database is designed to streamline and centralize key business functions such as order management, product tracking, customer communication, staff administration, and content/page management.
Here’s an explanation of each table and their relationships:
🔷 orders Table
- Use: Tracks every customer order including the products ordered, quantity, pricing, delivery, and order status.
- Value: Helps manage logistics, track sales, monitor delivery timelines, and analyze order trends.
- Example: A manager can query which orders are pending or delivered, and calculate total revenue from orders.
Purpose: Stores customer orders.
Columns:
orderid: Primary key.productid: Foreign key referencingproducts.productid.enquiryid: Foreign key referencingcontact.enquiryid.orderdate,deliverydate: Dates related to the order.protype,qtytype: Type of product and quantity type.quantity: Number of items ordered.cost,totalcost: Unit cost and total cost of the order.orderstatus: Status of the order (e.g., pending, completed).
Relationships:
- ✅ Linked to
productstable viaproductid. - ✅ Linked to
contacttable viaenquiryid.
🔷 products Table
- Purpose: Stores details about products offered.
- Use: Maintains the list of products the enterprise sells, including type and cost.
- Value: Acts as a master table for product reference in orders, enabling consistent pricing and product info.
- Example: Useful for generating price lists or for checking stock availability if integrated with inventory.
Columns:
productid: Primary key.productname,productinfo,producttype: Basic details.cost: Unit cost of the product.
🔷 contact Table
- Purpose: Stores customer contact/enquiry information.
- Use: Stores enquiry details from potential or existing customers.
- Value: Enables tracking of customer queries and follow-ups. It helps build customer history and support.
- Example: Employees can see all enquiries and convert them into orders through the
orderstable.
Columns:
enquiryid: Primary key.name,staddress,city,pincode,mobile,email,message: Customer contact details.
🔷 employees Table
- Purpose: Stores employee login and identity details.
- Use: Stores login credentials and identity of employees using the system.
- Value: Enables secure access control and tracks employee activity like login sessions.
- Example: Admin can monitor which employee accessed the system and when.
Columns:
empid: Primary key.empname,emploginid,password: Login credentials.lastlogin: Last login timestamp.
🔷 pages Table
- Purpose: Likely for content management on a website.
- Use: Manages dynamic web content such as page titles, images, and descriptions.
- Value: Useful for enterprises maintaining a website, allowing non-technical users to manage pages.
- Example: Pages like “About Us,” “Services,” or “Contact” can be managed from this table.
Columns:
pageid: Primary key.pagename,pagetitle: Display info.imagepath: Image associated with the page.description: Page content or summary.
🔷 admin Table
- Purpose: Admin login and management info.
- Use: Manages administrator access with login and password, similar to employees but with higher privileges.
- Value: Secures high-level access to the system and manages overall database control.
- Example: Admins can add/edit products, view all orders, manage employees, and content pages.
Columns:
admin_id: Primary key.admin_name,login_id,password: Admin credentials.last_login: Admin last login timestamp.
🔁 Relationships Summary:
orders.productid→products.productid(many-to-one)orders.enquiryid→contact.enquiryid(many-to-one)
The other tables (employees, pages, admin) are standalone and do not have explicit foreign key relationships in this schema.
Leave a reply