RMG 300 Lecture Notes - Lecture 3: Audit Trail, Cash Register, Granularity
2 Feb 2018
School
Department
Course
Professor
WEEK 3
LECTURE 3
Chapter 10 ERP
Decisions – What’s Needed to Make a Decision?
• Every business activity is involved in making a decision
• Time is needed to make a decision
• Choices are needed to make a decision
o In order to have choices we need data
o Data raw facts
▪ You need something to compare it to (context) – context turns data into information
▪ No ou’e got our information, so you need to turn it into wisdom which turns
information into knowledge
• Example
o Data: we just sold a white blouse, style 130 size 10
o Context: we have been selling a lot of this style in the past week and our inventory is low
o Wisdo/Eperiee: its the ed of the seaso so e do’t order aore ut o e ko for
next season
Data is the Basic Building Block
• Fine details
• Needed for the big picture
• Where does data come from? And How do we Collect it?
o Transactions – some exchange between 2 people (ex: a business and a person). Something
happens, and something comes back
▪ Example of a transaction: a sale
TPS: Transaction Processing System
Bus Event/Transaction TPS (Detailed Reports) Org Database
• In any data there is the first part which is the TPS
• TPS first looks at that transaction
o Ex: cash register deals w/ a transaction when you buy item of clothing
▪ Deals w/ price, employee ID
▪ Once all that info is satisfied then it moves on to the larger system
• TPS looks at the validity of the data
• Org. Database
o Want to make sure info is stored securely
o No overlapping updates
o Protection from failures – want to make sure system can recover
• TPS processes for:
o Accuracy of data
o Ability to cancel
o Audit trail
• It’s like a gatea, esures eerthig is good/solid/aurate as the data flos to
the rest of these systems
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Decisions what"s needed to make a decision: every business activity is involved in making a decision, time is needed to make a decision, choices are needed to make a decision. And how do we collect it: transactions some exchange between 2 people (ex: a business and a person). Something happens, and something comes back: example of a transaction: a sale. Bus event/transaction tps (detailed reports) org database. Database: want to make sure info is stored securely, no overlapping updates, protection from failures want to make sure system can recover, tps processes for, accuracy of data, ability to cancel, audit trail. It"s like a gate(cid:449)a(cid:455), e(cid:374)sures e(cid:448)er(cid:455)thi(cid:374)g is good/solid/a(cid:272)(cid:272)urate as the data flo(cid:449)s to the rest of these systems. Fais: functional area info systems: accounting, finance, hr, production/ops, marketing, all consist of, strategic, tactical and operational areas, re(cid:373)e(cid:373)(cid:271)er (cid:449)e (cid:272)a(cid:374)"t (cid:373)ake a(cid:374)(cid:455) i(cid:374)for(cid:373)atio(cid:374) (cid:449)ithout data. Granularity of data: transactions, collections of very detailed (fine) data, cannot see the big picture.
