INVENTORY

MANAGEMENT
SYSTEM OF SMU
FEA COOP

SUBMITTED BY:
JAN MARLO QUEROL

SUBMITTED TO:
MR. ROGIE B. TABORDA
 OVERVIEW OF THE SYSTEM

The main function of the system is that it implies store, manage, and retrieve

of data. And by the help of the system and the database, it will be easy to

manage and monitor the products that are purchased and ordered by the

customer and the manager. The system’s diagram is the main method of the

system. Now what are the main idea why it is designed and the main purpose of

the system?

The main idea why it is created is because the system will help the owner and

the company/enterprise to establish more success and by using this system it will

make a lot of money. Save money, manage the ordered products, stock

products, and purchased products by the customers.

What if the system suddenly bug down, what will happen to the data that are

stored in the database will it still be in the database or will it disappear or be

deleted?
 If the database suddenly bug down then it is the main objective of the data

admin and the programmer to back-up all of the files and data’s that are stored in

to the database.

This system is designed to monitor sales and inventory on cash basis and

salary deduction.
IMS is design to allow the manager to monitor and record products that are

sold, unsold, ordered and delivered and the products that are stock and not yet

use.

In recording in the IMS, database is needed that’s why I created the database of

it and using the database created, it will help them to know whether products are

recorded on the database or not. Transaction counting

Each system of control must contain the information about the motion of the

goods for the goals of control. Accuracy of the goods calculation is difficult to

overestimate. Many systems do not ensure the adoption of correct solutions,

because does not have precise data about the stock in way and on hand.
 Suppliers

The owner should know how to monitor all the products that is present

on the inventory and on his/her market. When to order a product how

much he/she will spend in ordering.

Product and Services

In product and services, a customer should know how to budget and

what are the things that are needed to buy. The manager will assist the

customer to the following:

Product Purchasing

The customer should know the requirements needed in becoming a

member of the company.

 INVENTORY
MANAGEMENT SYSTEM
FEA COOPERATIVE
CONCEPTUAL
ENTITY-
RELATIONSHIP
DIAGRAM
 PURCHASE DIAGRAM FIGURE 1.1

DIAGRAM INTERPRETATION

The customer went to the company to buy products purchased by SMU-FEA COOP,

and the supplier supplies products sold by the enterpriser. And SMU-FEA COOP paid

the supplier for the products supplied by the supplier.

 CONSTRAINTS APPLIED

Mapping Constrains applied in the diagram

1. MANY TO MANY – purchased by from set A to set B

2. MANY TO ONE -paid by, sold to set B to set A

3. ONE IS TO ONE – went to paid by set A to set A

4. ONE TO MANY – supplies set C to set B

 ORDER DIAGRAM FIGURE 1.2

DIAGRAM INTERPRETATION

The customer ordered some products since the start of product purchasing

CONSTRAINT APPLIED

MAPPING CONSTRAINTS APPLIED IN THE DIAGRAM

ONE TO ONE -ordered, ordered to, paid to set A to set B

ONE TO MANY – delivered to, set A to set C

 INVENTORY
MANAGEMENT SYSTEM
OF SMU FEA
COOPERATIVE
LOGICAL DATABASE
DESIGN
 Database FEA Cooperative

CODES

CREATE DATABASE DB_FEACOOP

SHOW DATABASES

USE DB_FEACOOP
 TABLE CUSTOMERS

SHOW DATABASES

USE DB_FEACOOP

SHOW TABLES

CREATE TABLE TBL_CUSTOMERS(

CUSTOMERID INT(11),

CUSTOMERNAME VARCHAR(20),

CUSTOMERADDRESS VARCHAR(20),

CUSTOMERPHONE INT(11),

PRIMARY KEY(CUSTOMERID))
 SELECT *
FROM TBL_CUSTOMERS

INSERT INTO TBL_CUSTOMERS(CUSTOMERID, CUSTOMERNAME,

CUSTOMERADDRESS, CUSTOMERPHONE)
VALUES(‘101’, ‘MEYNARD KEYNES DELA CRUZ’, ‘BAGABAG’, ‘21483647’)

INSERT INTO TBL_CUSTOMERS(CUSTOMERID, CUSTOMERNAME,

CUSTOMERADDRESS, CUSTOMERPHONE)
VALUES(‘102’, ‘ARLENE R. QUEROL’, ‘BONFAL PROPER’, ‘21483647’)

INSERT INTO TBL_CUSTOMERS(CUSTOMERID, CUSTOMERNAME,

CUSTOMERADDRESS, CUSTOMERPHONE)
VALUES(‘103’, ‘GERTRUDE G. DANAO’, ‘STA. ROSA BAYOMBONG’,
‘21483647’)
 TABLE ORDERS

SHOW DATABASES
USE DB_FEACOOP
SHOW TABLES
CREATE TABLE ORDERS(
ORDERID INT,
CUSTOMERFIRSTNAME VARCHAR(20),
CUSTOMERLASTNAME VARCHAR(20),
ADDRESS VARCHAR(20),
PRODUCTNAME VARCHAR(20),
ORDERDATE DATETIME,
REQUIREDDATE DATETIME,
UNITPRICE DECIMAL(10, 2),
QUANTITYPERSTOCK CHAR(30),
PRIMARY KEY(ORDERID, CUSTOMERID))

TABLE PRODUCTS

SHOW DATABASES
USE DB_FEACOOP
SHOW TABLES
CREATE TABLE TBL_PRODUCTS(
PRODUCTID INT(11),
PRODUCTNAME VARCHAR(20),
QUANTITY VARCHAR(10),
UNITPRICE DECIMAL(10, 2),
PRIMARY KEY(PRODUCTID))
 ORDER_DETAILS

SHOW DATABASES
USE DB_FEACOOP
SHOW TABLES
CREATE TABLE TBL_ORDER_DETAILS(
ORDERID INT(11),
PRODUCTID INT(11),
SINCE DATETIME,
PRIMARY KEY(ORDERID, PRODUCTID),
FOREIGN KEY(ORDERID) REFERENCES TBL_ORDER(ORDERID),
FOREIGN KEY (PRODUCTID) REFERENCES TBL_PRODUCT
(PRODUCTID))
 INVENTORY
MANAGEMENT SYSTEM
FEA COOP FUNCTIONS
AND SEQUENCE
 WHY DID I CREATE A TABLE NAME ORDER DETAILS?

An order detail is the relationship of product table, customer table and

order table. The customer will order some products of the company.

And the customer paid for the delivery

Order detail table is the one responsible for monitoring records and it is

used as a foreign key and a relationship table for the 3 table

MAIN PURPOSE OF THE ORDER DIAGRAM

The main purpose of the diagram is that to show the sequence on how

smu fea coop order some products to the suppliers and how it is delivered.

The idea of it is that to know the fields needed in creating a record for the

products and delivery for your business.

And that’s why I created the order diagram to create a method that will be

used for the creation of the inventory management system for smu fea

coop enterprise.

Customer’s location, ordered products, these are the field column that are

needed to use in creating a records.

MAIN PURPOSE OF THE PURCHASE DIAGRAM

The entity used: customer products smu-fea coop supplies

The attributes used: customer id, customer name, customer address,

customer location, product id, product name, unit price, coop id, coop

location, coop address, supplier id, supplier name, supplier address.

The constraint used: many to many, many to one, one to one, one to

many.

The purpose of the purchase diagram is to create a plan or method that is

needed to for the manager to understand the flow of the system design for
their business. It is a method for them to easily have an idea on what to do

in case they needed to purchase something or incase a customer will buy

some of their product then the owner won’t have any more problem with

their products and business.