Sie sind auf Seite 1von 18

SYNOPSIS

The project entitled Stock Maintenance System is to maintain the entire inventory
process which is carried out in any company. Mainly the project deals with sales and
purchase of the company. First the dealer or the customer has to create an account for making
sales and purchase.

Then the registered users can make sales or purchases, product. After making sales or
purchase database is updated. First the company details and product details are added after
creating account for the customers. Then the dealers or regular customers can make sales or
purchase by choosing their desired product and company.

When it choose the product, only the available products can be transacted. For
maintaining that separate database namely stock is maintained. While entering new products
to the product database, number of quantity of the particular product available is added which
is called as stock. Stock details will then be stored in another database called stock.

When there is change in stock i.e. number of products available, stock database will
be updated. When the customer or dealer makes a sale, stock will be reduced for the
particular product. When it purchase, stock will be increased. When there is not enough
stock, product will not be transacted.

New sale and new purchase can be done by clicking new sale and new purchase
respectively. After making new sale and purchase sales and purchase database will be
updated. Administrator can view the purchase details which are done on a particular date,
total sales, total purchase, accounts details and stock details.
INTRODUCTION

Inventory management is primarily about specifying the size and placement of


stocked goods. Inventory management is required at different locations within a facility or
within multiple locations of a supply network to protect the regular and planned course of
production against the random disturbance of running out of materials or goods. The scope of
inventory management also concerns the fine lines between replenishment lead time, carrying
costs of inventory, asset management, inventory forecasting, inventory valuation, inventory
visibility, future inventory price forecasting, physical inventory, available physical space for
inventory, quality management, replenishment, returns and defective goods and demand
forecasting. The reasons for keeping stock are as follows. There are three basic reasons for
keeping an inventory:

Time - The time lags present in the supply chain, from supplier to user at every stage,
requires that you maintain certain amounts of inventory to use in the lead time. However, in
practice, inventory is to be maintained for consumption during 'variations in lead time'. Lead
time itself can be addressed by ordering that many days in advance.

1. Uncertainty - Inventories are maintained as buffers to meet uncertainties in demand,


supply and movements of goods.

2. Economies of scale - Ideal condition of "one unit at a time at a place where a user
needs it, when he needs it" principle tends to incur lots of costs in terms of logistics.
So bulk buying, movement and storing brings in economies of scale, thus inventory.
All these stock reasons can apply to any owner or product.
SYSTEM SPECIFICATION

Hardware configuration

Processor : Dual Core

RAM Capacity : 1 GB

Hard Disk : 200 GB

Mouse : 2 Button

Monitor : Color Monitor

Mother Board : Intel

Speed : 2 GHZ

Software specification

Operating System : Windows 2007

Front End : Visual Basic 6.0

Backend : Oracle 10 g
2. SYSTEM STUDY

2.1 EXISTING SYSTEM

The system which is followed at present is a manual system. The system consists of
book of accounts that has to be maintained in all aspects. Preparing export status reports
manually and reporting to the exporter becomes a touch process and becomes difficult to
satisfy the exporter printing work is difficult. In the existing system each and every time a
reference should be made.

2.1.1 Drawbacks

There are high possibilities to commit errors and mistake which lead to produce
wrong statement to the management. Report keeping is also not an easy task. Another
important drawback of existing system is time factor. It will not help the management to
solve the problem in time.

2.2 PROPOSED SYSTEM

The proposed system meant to give more easiness to the users that they can add and
retrieve information so quickly. There are mainly two types of users they are administrator
and registered members. The administrator is the master user; he gets the most number of
priorities than the other users. The different functions involve the case of an administrator are
updating, approval. The administrator can view and perform necessary actions. Registered
member can update the details, view details and get the desired result.

2.2.1 Features

The proposed system is intended to avoid all the drawbacks of existing system. It will
add some more features than the existing system. The proposed system is a cost effective way
of doing the manual processes done in the existing system. It helps the organization to win
the war in the existing competitive world.
3. SYSTEM DESIGN AND DEVELOPMENT

3.1 FILE DESIGN

The design base files are the most important of the system. The performance of the
system depends on how the system is design. It has been given at most attention to reduce the
size of files and redundancy. At the same time all the files are design to incorporate all
relevant information regarding each entity. A single database with information about all the
entities will make the system more complicated. The functions and structure of each of the
database files are given below.

1. BOOKMASTER.DBF

It contains book details of Marble Management System.

2. VENDORMASTER.DBF

It contains vendor details of Marble Management System.

3. COMPANYMASTER.DBF

It contains company details of Marble Management System.

4. BRANCHMASTER.DBF

It contains branch details of Marble Management System.

5. BILL.DBF

It contains bill details of Marble Management System.

6. STOCK.DBF

It Stores stock details

7. QUOT.DBF

It Stores quotation details


INPUT DESIGN

Input design is a part of overall system design. The main objective


during the input design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the


user.

Input Stages

The main input stages can be listed as below:

Data recording

Data transcription

Data conversion

Data verification

Data validation

Input Types

It is necessary to determine the various types of inputs. Inputs can


be categorized as follows:

External inputs, which are prime inputs for the system.

Internal inputs, which are user communications with the system.

Operational, which are computer departments communications


to the system?

Interactive, which are inputs entered during a dialogue.


Keeping in view the above description of the input types and input
media, it can be said that most of the inputs are of the form of internal
and interactive. As Input data is to be the directly keyed in by the user,
the keyboard can be considered to be the most suitable input device.

OUTPUT DESIGN

Outputs from computer systems are required primarily to


communicate the results of processing to users. They are also used to
provide a permanent copy of the results for later consultation. The various
types of outputs in general are:

External Outputs whose destination is outside the organization.

Internal Outputs whose destination is within organization and


they are the Users main interface with the computer.

Operational outputs whose use is purely within the computer


department.

Interface outputs involve the user who communicates directly


with the system.

Output Definition

The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output


Frequency of the output

Volume of the output

Sequence of the output

Output Media

In the next stage it is to be decided that which medium is the most


appropriate for the output. The main considerations when deciding about
the output media are:

The outputs were needed to be generated as a hard copy and as


well as queries to be viewed on the screen. Keeping in view these outputs,
the format for the output is taken from the outputs, which are currently
being obtained after manual processing. The standard printer is to be
used as output media for hard copies.

DATABASE DESIGN

Data base is designed to manage large bodies of information. The management of data
involves both the definitions of structures for the storage of information. In addition the data
base system must provide for the safety of the information solved, despite system crashes or
due to attempts at unauthorized access. For developing an efficient database one have to
fulfill certain conditions such as controlled redundancy.

Defining the data

Inputting the data

Locating the data

Accessing the data


Communicating the data

Revising the data

Objectives of Data base design

In the data base design several objectives are designed such as :

Ease of use

Control of data integrity

Control of redundancy

Control of security

Data independence (logical & physical)

Data storage protection

System performance

System functions

System compatibility

For achieving the abovementioned criterias one have to make use of various features
that are available with the RDBMS by enforcing integrity constrains, one can ensure data
integrity and reduce data inconsistency to a great extend.

SYSTEM DEVELOPMENT

DESCRIPTION OF MODULES

LOGIN MODULE
It is used for logging in the inventory management system.

MAIN MODULE

It is used for accessing in the inventory management system. Here the admin get
privileges to access IMS (Inventory Management System). Admin can access after logging in.
There are sub modules for this module. They are:

Vendor master module

Stock module

Branch master module

Bill module

Company master module

Book master module

Tables used: all tables

VENDOR MASTER MODULE

It is used for adding, modifying and retrieving vendor details to Inventory


Management System. Here the admin get privileges to add details in Inventory Management
System (IMS). It is the sub module of main module.

Table used: vendormaster_db

STOCK MODULE

It is used for searching items in Inventory Management System (IMS). Here the
admin get privileges to search items Inventory Management System. It is the sub module of
main module.

Table used: stock_db

COMPANY MASTER MODULE


It is used for adding, modifying and retrieving company details in the Inventory
Management System. Here the admin get privileges to update reports and create accounts for
new users or company in the Inventory Management System. It is the sub module of main
module.

Table used: companymaster_db

BILL MODULE

It is used for generating bill based on the details in the Inventory Management
System. Here the admin get privileges to generate bill Inventory Management System. It is
the sub module of main module.

Table used: bill_db

BRANCH MASTER MODULE

It is used for adding, modifying and retrieving branch details in the Inventory
Management System. Here the admin get privileges to update reports and create accounts for
new users or company in the Inventory Management System. It is the sub module of main
module.

Table used: branchmaster_db

BOOK MASTER MODULE

It is used for adding, modifying and retrieving book details in the Inventory
Management System. Here the admin get privileges to update reports and create accounts for
new users or company in the Inventory Management System. It is the sub module of main
module.

Table used: bookmaster_db

DATA FLOW DIAGRAM


Level 0 : login

Login
Admin Login

After login

Access to
inventory

Level 1

Inventory
Admin

Accounts
Account

Stock
Stock

Level 2

Inventory
After login

Admin

Accounts
Account

Purchase
Trans

Stock
Stock

Sale
Trans

B. TABLE STRUCTURE
Table name : Bookmaster

Primary key : B_id

Foreign key : B_no

Field name Data type Size Description


B_id Number 20 Book id
B_no Number 20 Book number
B_name Varchar2 30 Book name
B_gag Varchar2 30 Gadgets in book
B_unit Varchar2 30 Number of nuits
B_catid Varchar2 30 Category id
B_mftid Varchar2 30 Manufacturing id
B_desc Varchar2 30 description
B_costprice Number 20 Cost price
B_sellingprice Number 20 MRP
B_imagename Varchar2 30 Name of the image
B_openingqty Number 20 Quantity
B_selovrhead Number 20 Number of sales

Table name : Branchmaster

Primary key : r_id

Foreign key : r_name

Field name Data type Size Description


R_id number 30 Branch id
R_name Varchar2 30 Branch name
R_no Varchar2 30 Branch number
R_promotingid Varchar2 30 Promotion id
R_add1 Varchar2 30 Branch address1
R_add2 Varchar2 30 Branch address2
R_city Varchar2 30 City
R_state Varchar2 30 state
R_pin Number 30 Pin code
R_country Varchar2 30 Country
R_phone number 30 Phone
R_fax Varchar2 30 Fax
R_email Varchar2 30 Email id
R_notes Varchar2 50 Notes
R_oh Varchar2 30 Sales over head
R_balanceamt Varchar2 30 Balance amount
R_lastBRweekno Varchar2 30 Last branch week number
R_lstBRchalnno Varchar2 30 Last branch challan number
R_contactperson Varchar2 30 Contact person

Table name : Bill

Primary key : inv_no

Foreign key : ord_no

Field name Data type Size Description


Inv_no Number 20 Invoice number
Ord_no number 20 Order number
Inv_date Date 15 Invoice date
Challan_no Number 20 Challan number
Party_id Number 20 Party id
Desp_mode Varchar2 30 Dispatch mode
Party_name Varchar2 30 Name of the party
Sno number 30 Serial number
Prod_id Number 30 Product id
Prod_name Varchar2 30 Name of the product
Prod_size Number 30 Product size
Qty number 30 Quantity
rate Number 30 Rate
amount Number 30 Amount
packing Varchar2 30 Packing detail
discount number 30 Discount
Sub_total Number 30 Sub total
vat Number 20 Vendors count
sum number 20 Sum

Table name : Companymaster


Primary key : a_sno

Foreign key : a_companynme

Field name Data type Size Description


A_sno Number 20 Serial number
A_companynme Varchar2 30 Company name
A_cmpny_addr1 Varchar2 30 Address1
A_cmpny_addr2 Varchar2 30 Address2
A_cmpnycity Varchar2 30 City
A_cmpnystate Varchar2 30 State
A_cmpnypin Varchar2 30 Pin code
A_cmpnycountry Varchar2 30 Country
A_cmpnyphone number 10 Phone number
A_cmpnyfax Varchar2 30 Fax
A_cmpnyemail Varchar2 30 Email id
A_cmpnywebsite Varchar2 30 Website
A_cmpnystatus Varchar2 30 Status
A_challanno Varchar2 30 Challan number
A_receivefrom Varchar2 30 Received from
A_curyearfrom Varchar2 30 Current year from
A_curyearto Varchar2 30 Current year to
A_lastaccid Number 20 Last account id
A_lastsampleno Number 20 Last sample number

Table name : Vendormaster

Primary key : r_promotingid

Foreign key : r_id

Field name Data type Size Description


R_id number 30 vendor id
R_name Varchar2 30 vendor name
R_no Varchar2 30 vendor number
R_promotingid Varchar2 30 Promotion id
R_add1 Varchar2 30 vendor address1
R_add2 Varchar2 30 vendor address2
R_city Varchar2 30 City
R_state Varchar2 30 state
R_pin Number 30 Pin code
R_country Varchar2 30 Country
R_phone number 30 Phone
R_fax Varchar2 30 Fax
R_email Varchar2 30 Email id
R_notes Varchar2 50 Notes
R_oh Varchar2 30 Sales over head
R_balanceamt Varchar2 30 Balance amount
R_lastBRweekno Varchar2 30 Last branch week number
R_lstBRchalnno Varchar2 30 Last branch challan number