Title: Chapter 11 ERP and the Data Warehouse
1Chapter 11ERP and the Data Warehouse
- ProfessorDon-Lin Yang
- StudentChi-Hsiang Chen
- Wei-Hsu Lin
2Outline
- ERP
- ERP Applications Outside the Data Warehouse
- Building the Data Warehouse inside the ERP
Environment - Feeding the Data Warehouse through ERP and
Non-ERP System
3Outline
- The ERP-Oriented Corporate Data Warehouse
- Summary
4ERP
- ERP is abbreviated from Enterprise Resource
Planning. - ERP is that the applications and transaction
processing build for a company.
5ERP
- Human resources
- Inventory management
- Financial management
- Supply chain management
- Logistics
- Manufacturing
- Distribution
- Customer service
6ERP
7ERP
- The primary reasons focus on the frustrations in
handling existing applications. - These include the following
- Aging
- Un-integrated
- Incomplete
8ERP
- ERP software encompasses the transaction
component of the business. - ERP applications are at the heart of running any
business. Transactions are only the start of the
information process. There is still need for a
data warehouse.
9ERP Applications Outside the Data Warehouse
- The basic architecture of the data warehouse does
not change in the face of ERP.
10ERP Applications Outside the Data Warehouse
11ERP Applications Outside the Data Warehouse
- The interface that takes data into the data
warehouse is very similar to a non-ERP interface,
with a few exceptions - The ERP interface has to deal with
- only the DBMS technologies that the
- ERP supports. The non-ERP interface
- must deal with all interfaces.
12ERP Applications Outside the Data Warehouse
- The ERP interface has a much tighter
- grip on the data and structures that
- constitute the application environment
- because the ERP vendor owns and
- controls the interface.
13ERP Applications Outside the Data Warehouse
- The interface often has to go into the
- ERP environment and find the right
- data and glue it together in order to
- make it useful for the data warehouse
- environment.
14ERP Applications Outside the Data Warehouse
- There are several advantages to pulling the data
out of the ERP environment and into a different
operating environment. - Data warehouse is free from any
- constrains that might be placed on it.
- Data warehouse designer is free to
- design the data warehouse environment
- however he or she sees fit.
15Building the Data Warehouse inside the ERP
Environment
16Building the Data Warehouse inside the ERP
Environment
- The primary advantage is that the ERP vendor
provides the infrastructure. - The infrastructure saves the designer an enormous
amount of work. - The infrastructure saves the developer from
having to deal with complexities of design an
development.
17Feeding the Data Warehouse through ERP and
Non-ERP System
18Feeding the Data Warehouse through ERP and
Non-ERP System
19Feeding the Data Warehouse through ERP and
Non-ERP System
20Feeding the Data Warehouse through ERP and
Non-ERP System
21The ERP-Oriented Corporate Data Warehouse
22The ERP-Oriented Corporate Data Warehouse
- How easy is the transition from the non-ERP
installations to the corporate data warehouse?
Not particularly. - How easy is the passage of data from a local ERP
installation into the corporate ERP? Surprisingly
difficult as well.
23The ERP-Oriented Corporate Data Warehouse
- There is a never-ending series of events that
require the corporate data to be constantly
changed. - Building the corporate infrastructure to
withstand this eternal change is a significant
challenge.
24Summary
- The ERP environment is an application-based
environment found in many places. - Even with an ERP installation there is a need for
a data warehouse.
25Summary
- The developer has several choices
- Move ERP data to a non-ERP data
- warehouse
- Move ERP data to an ERP-based data
- warehouse
- Move non-ERP data to an ERP-based
- data warehouse
- Move non-ERP data to a non-ERP data
- warehouse