Professional Documents
Culture Documents
Logical Database Structure For Accounting Information System
Logical Database Structure For Accounting Information System
Introduction
A big advantage of computer-based accounting information systems is that they automate and
streamline reporting. Reporting is major tool for organizations to accurately see summarized,
timely information used for decision-making and financial reporting.
The accounting information system pulls data from the centralized database, processes and
transforms it and ultimately generates a summary of that data as information that can now be
easily consumed and analyzed by business analysts, managers or other decision makers. These
systems must ensure that the reports are timely so that decision-makers are not acting on old,
irrelevant information and, rather, able to act quickly and effectively based on report results.
Consolidation is one of the hallmarks of reporting as people do not have to look through an
enormous number of transactions. For instance, at the end of the month, a financial accountant
consolidates all the paid vouchers by running a report on the system.
The systems application layer provides a report with the total amount paid to its vendors for that
particular month. With large corporations that generate large volumes of transactional data,
running reports with even an AIS can take days or even weeks.
In this we assume that mike is opening the business for goods of which he needs the logical
database design of accounting information system
The requirements analysis for this database led to the following six entities and their unique
identifiers are as follows
7
Entity Entity Key
Customer Customer_id
Inventory Item_Number
Order Order_Number
Sales Shipment_Number
Employee Employee_Id
Payroll Payroll_id
Here the relation between customer and Item can be multiple as multiple customers can purchase
multiple items and the same time multiple items can be purchased by single customer
Customer
7
1
Plac N Inventory
es
Order N Item
1. Each customer may place many orders, but only one customer may place a particular
order.
4. In a payroll table multiple employees will be there and the data of the single employee
can be multiple times.
The relationship between Order table and Item table can also multiple relationships as in one
order there can be multiple items.
7
[Item_Name] [varchar](100) NULL,
[Qty] [int] NULL,
[Cost_Per_Unit] [decimal](18, 0) NULL,
[Cost_Price_Per_Unit] [decimal](18, 0) NULL,
CONSTRAINT [PK_Inventory] PRIMARY KEY CLUSTERED
(
[Item_Number] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
GO
7
ALTER TABLE [dbo].[Sales] WITH CHECK ADD CONSTRAINT [FK_Sales_Customer]
FOREIGN KEY([Cust_No])
REFERENCES [dbo].[Customer] ([Customer_Id])
GO
GO
7
) ON [PRIMARY]
GO
GO
7
SET ANSI_PADDING OFF
GO
References
Database design basics. (n.d.). Database design basics. Retrieved May 1, 2010, from
http://office.microsoft.com/en-us/access/HA012242471033.aspx
Gehani, N. (2006). The Database Book: Principles and practice using MySQL. 1st ed., Summit,
NJ.: Silicon Press
Teorey, T.; Lightstone, S. and Nadeau, T.(2005) Database Modeling & Design: Logical Design,
4th edition, Morgan Kaufmann Press. ISBN 0-12-685352-5