So every night, Wal-Mart will then pull from the OLTP system, push that data into the OLAP environment, which is the BW data warehouse, and during that pull process, BW will cleanse that data, removing any invalid values that would've caused issues in reporting, and it's essentially staging the data and aligning it exactly how the reports are architected for the end user. The OLAP system can't actually see this transactional information until it's loaded into the data warehouse on the BW side of things. When a customer comes in and buys a product, a transaction is written to the database of the transactional environment. A good example of a transactional system would be pretend you're a large retailer like Wal-Mart. It's not real-time unless you configure it to be, and it's optimized for reporting. BW is our OLAP system which provides analytics, and ECC is an example of a transactional system where things happen in real-time, data's entered manually by users, and the BW system, which is the OLAP system, which you can see at the bottom half of the screen here in this image, is showing you that it's made for data mining, cleaning data, setting up all of your data in a reportable fashion, whereas the OLTP side, the top part, is just taking all sorts of data, it's not cleansed, and it's in real-time, transactional, and the OLAP, the bottom half, is historical.
It's important to understand the difference between the OLTP system and the OLAP system. Okay, so in this presentation we're going to briefly walk you through what makes up the SAP BW system, the objects that are used within SAP BW, and how everything sort of works together to form a cohesive solution that makes this SAP BW Warehouse such a great tool.
0 kommentar(er)
