Database and the implementation of dssdw user support

This preview shows page 16 - 18 out of 47 pages.

database and the implementation of DSS/DW user support product companies candesign a decision support/data warehouse database that allows cross-functionalarea analysis and comparisons for better decision-making.Since companies usually implement an ERP in addition to their current applications,the problem of data integration from the various sources of data to the datawarehouse becomes an issue.Actually, the existence of multiple data sources is a problem with ERPimplementation regardless of whether a company plans to develop a datawarehouse; this issue must be addressed and resolved at the ERP project initiationphase to avoid serious complications from multiple sources of data for analysis andtransaction activity. In data warehouse development, data is usually targeted fromthe most reliable or stable source system and moved into the data warehousedatabase as needed. Identification of the correct source system is essential for anydata warehouse development, and is even more critical in a data warehouse thatincludes an ERP along with more traditional transaction systems. Integration of datafrom multiple sources (ERP database and others) requires rigorous attention to thepg. 16
metadata and business logic that populated the source data elements, so that the“right” source is chosen.Another troubling issue with ERP data is the need for historical data within theenterprise’s data warehouse. Traditionally, the enterprise data warehouse needshistorical data (see Inmon’s definition). And traditionally ERP technology does notstore historical data, at least not to the extent that is needed in the enterprise datawarehouse. When a large amount of historical data starts to stack up in the ERPenvironment, the ERP environment is usually purged, or the data is archived to aremote storage facility. For example, suppose an enterprise data warehouse needsto be loaded with five years of historical data while the ERP holds at the most, sixmonths’ worth of detail data. As long as the corporation is satisfied with collecting ahistorical set of data as time passes, then there is no problem with ERP as a sourcefor data warehouse data. But when the enterprise data warehouse needs to go backin time and bring in historical data that has not been previously collected and savedby the ERP, then using the ERP environment as a primary source for the datawarehouse is not a viable option.Metadata in the ERP is another consideration when building a data warehouse is inthe ERP environment. As the metadata passes from the ERP to the data warehouseenvironment, the metadata must be moved and transformed into the format andstructure required by the data warehouse infrastructure. There is a significantdifference between operational metadata and DSS/DW metadata. Operationalmetadata is primarily for the developer and programmer. DSS metadata is primarilyfor the end user. The metadata that exists in the ERP application’s database must be

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 47 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Fall
Professor
N/A
Tags
Computer program

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture