© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 96 C HAPTER 17 Special Topics in REA Modeling for the.

Slides:



Advertisements
Similar presentations
Chapter 14 Audit of the Sales and Collection Cycle
Advertisements

The Sales/Collection Business Process
Database Design Using the REA Data Model
6 Accounting for Merchandising Businesses Accounting 26e C H A P T E R
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Implementing an REA Model in a Relational Database
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 5-1 Accounting Information Systems 9 th Edition Marshall.
FIS 431/631 Financial Information Systems: Analysis and Design REA Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 121 C HAPTER 16 Implementing an REA Model in a Relational.
M ERP (Enterprise Resources Planning) M ERP (Enterprise Resources Planning) Session 5 Sales and Marketing Information System Ir. Ekananta Manalif,
Technology Review-II Professor Martin Professor Xiong CSUS
Database Design Using the REA Data Model
Collecting and Reporting Accounting Information Design of an effective AIS begins by considering outputs from the system. Outputs of an AIS include: 1.
Implementing an REA Model in a Relational Database
Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 18-1.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 11-1 Accounting Information Systems 9 th Edition Marshall.
Accounting Information Systems 9th Edition
Lecture Note 8 Using Data Flow Diagrams
Database Design Using the REA Data Model
Hall, Accounting Information Systems, 7e ©2011 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
Chapter 19 Special Topics in REA Modeling Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 19-1.
© 2014 Cengage Learning. All Rights Reserved. Do Now: ●Where do you get new shoes? ●Have you ever had to wait for a size you need to be brought out to.
Database Design Using the REA Data Model
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 43 The revenue cycle involves interactions with your.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 92 C HAPTER 17 Special Topics in REA Modeling.
The REA Model. The REA model provides structure for developing an accounting database It helps to identify It helps to The REA Model.
Accounting Information Systems 9th Edition
2-1 ©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart Overview of Business Processes Chapter 2.
Clients (and the interface level) Application Server (and the application level) Database Server (and the Database level)
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 131 C HAPTER 16 Implementing an REA Model In a Relational.
Acct 316 Acct 316 Acct 316 Data Modeling and Database Design 5 UAA – ACCT 316 Accounting Information Systems Dr. Fred Barbee Chapter.
Implementing an REA Model in a Relational Database
The Revenue Cycle Yan Xiong Merle P. Martin College of Business CSU Sacramento 3/11/03.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
Implementing an REA Model in a Relational Database
Advanced Accounting Information Systems Day 7 Database Modeling.
Reports. Report Summary Warehouse Reports Returned Material Serial Numbers Not Found This report list the serial numbers of material returned which were.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
Chapter 2 Starting a Proprietorship: Changes That Affect Owner’s Equity.
McGraw-Hill/Irwin © 2013 The McGraw-Hill Companies, Inc., All Rights Reserved. Chapter 12 Sales/Collection Process.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
Accounting Information Systems: A Business Process Approach Chapter Three: Documenting Accounting Systems.
12-1 Anup Kumar Saha The Expenditure Cycle: Purchasing and Cash Disbursements.
Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 18-1.
Chapter 19 Special Topics in REA Modeling Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 19-1.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 131 C HAPTER 16 Implementing an REA Model In a Relational.
© 2014 Cengage Learning. All Rights Reserved. Learning Objectives © 2014 Cengage Learning. All Rights Reserved. LO4 Describe accounting procedures used.
0 Glencoe Accounting Unit 4 Chapter 14 Copyright © by The McGraw-Hill Companies, Inc. All rights reserved. Unit 4 The Accounting Cycle for a Merchandising.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
Special Topics in REA Modeling
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 96 C HAPTER 17 Special Topics in REA Modeling.
Database Design Chapters 17 and 18.
Implementing an REA Model in a Relational Database
ACCOUNTING FOR MERCHANDISE OPERATIONS
Implementing an REA Model in a Relational Database
Chapter 4 The Revenue Cycle 1.
Implementing an REA Model in a Relational Database
Accounting Information Systems 9th Edition
Database Design Using the REA Data Model
The Fulfillment Process
Sales Order Process.
Database Design Chapters 17 and 18.
Database Design Using the REA Data Model
Accounting Information Systems and Business Processes - Part I
Presentation transcript:

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 96 C HAPTER 17 Special Topics in REA Modeling for the Revenue Cycle

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart2 of 96 INTRODUCTION Questions to be addressed in this chapter: –How are REA data models developed for organizations other than retail stores? –How are REA data models developed for the HR/payroll, manufacturing, and capital asset transaction cycles?

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart3 of 96 INTRODUCTION Chapters 15 and 16 introduced the topic of REA data modeling and explained how to implement an REA model in a relational database. We focused on revenue cycle activities for a typical retail organization. This chapter extends those basic concepts to other types of businesses.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart4 of 96 ADDITIONAL REVENUE CYCLE MODELING TOPICS The revenue cycle REA models we’ve already developed focused on activities performed by a typical retail store. Events included: –Taking customer orders –Filling those orders –Collecting payment

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart5 of 96 MANUFACTURERS AND DISTRIBUTORS Manufacturers, distributors, and other types of businesses often engage in additional activities that management wants to monitor, such as: –Sales calls on customers –Picking and packing orders

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart6 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash Many of the entities and relationships depicted in in this diagram have already been discussed, so we’ll focus on the new ones or ones we’ve not discussed in depth. The call on customer event collects information about activities of the sales staff. Each customer call represents a visit by a salesperson to a specific customer.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart7 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash Sales calls do not always result in orders, so the minimum cardinality from the call on customer event to the take order event is 0. Though a single call may be followed by many orders, it is easier to evaluate sales force productivity by linking each call only to orders placed at the time the call is made, so the maximum cardinality here is 1.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart8 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash Orders are often received by phone, fax, or via the company’s website, rather than as a result of a sales call. So the minimum between take order and call on customer is 0. It may take many sales calls to obtain the first order, but it’s customary to associate the order only with the particular sales call that generated it. So the maximum is 1.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart9 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash The relationship between take order and fill order is one-to-many. –The two events occur sequentially, so for every order taken, the order can be filled a minimum of zero times. –The maximum cardinality is N, because some items may not be in stock and will have to be filled later.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart10 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash For every time an order is filled, there must be at least one order (minimum of 1), and because best practice is to fill each order immediately, there should be a maximum of one take order for every fill order event.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart11 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash The warehouse activity of filling an order is separate from the activity of actually shipping (or delivering) the order. The fill order event represents the picking and packing activity.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart12 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash The relationship between fill order and ship order is one-to-one. The fill order event occurs first, so for every order filled, there is a minimum of zero shipping events. Each order is typically sent as one shipment, so for every order filled, there is a maximum of one shipment.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart13 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash Each shipment is typically linked to one and only one fill order event.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart14 of 96 MANUFACTURERS AND DISTRIBUTORS Attribute Placement –The primary key of the shipping event is the shipment number. –The bill of lading number is another attribute in the shipping event. The bill of lading number is not the primary key because it can be null for deliveries made with the company’s own vehicles. –The sales invoice number is another attribute of the shipping event. The invoice number is not the primary key because some companies use electronic invoices or eliminate invoices altogether. Also, if the invoice number were used as the primary key, it would be null until such time as an invoice were actually issued, which may often occur after shipment.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart15 of 96 MANUFACTURERS AND DISTRIBUTORS For companies which still use invoices, the invoice number serves an important internal control function. –This attribute can be examined to determine whether all goods that have been shipped have been billed. –If it’s null, the billing hasn’t occurred.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart16 of 96 MANUFACTURERS AND DISTRIBUTORS Information about prices and costs is stored in several places. –The inventory table contains information about the standard (list) price and standard cost of each item because those values are typically constant for the fiscal year. –The take order-inventory table contains the quantities ordered for each item, as well as the actual price and accounting cost assigned to each, because these change during the year.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart17 of 96 Customer Employee (Salesperson) Customer Employee (Warehouse) Employee (Shipping) Carrier Employee (Cashier) Customer Call on Customer Take Customer Order Fill Customer Order Ship Order Receive Cash Inventory Cash The REA diagram identifies different employees who participate in each event by their job functions. Makes it easier to use the diagram as a guide to verify whether duties are properly segregated. However, only one employee table is required, which includes the attribute “job title” to identify each employee’s primary function.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart18 of 96

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart19 of 96 SALE OF SERVICES We’ve focused so far on businesses that sell tangible inventory. Many businesses sell services, such as auto repair or veterinary services. A partial REA model for the revenue cycle of a service company is shown on the following slide.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart20 of 96 Employee Customer Employee Cash Inventory Services Receive Cash Sales SALE OF SERVICES

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart21 of 96 Employee Customer Employee Cash Inventory Services Receive Cash Sales SALE OF SERVICES The relationship between the sale event and the services resource is likely to be M:N. –For each sale, many services can be provided. –For each service the company offers, they are likely to have sold it many times.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart22 of 96 Employee Customer Employee Cash Inventory Services Receive Cash Sales SALE OF SERVICES The minimum cardinality between the service resource and the sale event is typically 0, because some services may never be sold.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart23 of 96 Employee Customer Employee Cash Inventory Services Receive Cash Sales SALE OF SERVICES The minimum cardinality between the sales event and the services inventory will probably be 0 if the entity offers any tangible product. For example: –A veterinarian could provide a service to a customer’s pet without selling any tangible product. –A veterinarian could sell flea-and-tick medicine (inventory) to a customer without providing any services. –A veterinarian could provide both a service and a tangible product. –But for each sale, the minimum amount of service or tangible product provided is zero.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart24 of 96 DIGITAL ASSETS Companies that sell software, music, or digital photographs over the Internet give up a digital copy of these resources, but not the actual resource. They still need to collect information about orders for delivery of those digital assets, along with receipt of customer payments. They need an inventory table so customers can see what products are available. The structure of the table is very similar to tables for tangible products, except there is no need for quantity- on-hand fields or any data on re-order points. The inventory table will still include information about standard list prices of each item.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart25 of 96 RENTAL TRANSACTIONS Some businesses generate revenue through rental transactions rather than sales. The give-to-get exchange involves the temporary use of a resource in return for: –The receipt of cash; and –The subsequent return of the resource being rented.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart26 of 96 Employee Customer Employee Cash Rental Inventory Receive Cash Rent Item Customer Return Item Each row in the rent item event entity records information about the rental of one specific item, such as date and time of rental, rental price, and terms. If a customer rents multiple items, each item is treated as a separate rental event, since the items must be tracked individually.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart27 of 96 Employee Customer Employee Cash Rental Inventory Receive Cash Rent Item Customer Return Item  The rent item event is linked to both the receive cash and return item events.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart28 of 96 Employee Customer Employee Cash Rental Inventory Receive Cash Rent Item Customer Return Item In the cardinality between rent item and receive cash: –The minimum cardinality of 1 reflects that the customers typically pay first before taking possession. –The maximum of N reflects that there may be additional charges when the rental item is returned.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart29 of 96 Inventory Control Employee (Supervisor) Employee (Purch. Clerk) Supplier Employee (Receiving) Employee (Warehouse) Employee (Cashier) Supplier Request Goods Order Goods Receive Goods Pay for Goods Inventory Cash Supplier Warehouse Financial Institution The relationship between receive goods and receiving employees is M:N because: –When a shipment is received, several employees may work to unload the shipment. –An individual employee may unload several shipments. –Allows for individual monitoring of performance