Đang chuẩn bị liên kết để tải về tài liệu:
Mastering Data Warehouse DesignRelational and Dimensional Techniques phần 6

Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ

Trong thời hạn đó. Cho dù bạn đang phát triển kho dữ liệu của bạn cho một nhà sản xuất hay không, các khái niệm theo dõi áp dụng rộng Khi bạn ngày làm việc thực hiện phân tích cho một loạt các doanh nghiệp. Khái niệm của các nhà máy đã Been lịch mở rộng trong việc sử dụng hiện đại để | Figure 7.8 Packaged goods product hierarchy. SKU Modeling Hierarchies Figure 7.9 Packaged goods customer hierarchy. The lowest level of the customer s distribution hierarchy is the ship-to-customer location. These are grouped under sold-to customers which represent the customer s purchasing representatives. These are further grouped into planning customers which is the lowest level at which sales plans are estimated. Figure 7.9 shows the full hierarchy. Capacity planning is handled by another system which allocates to plants and distribution centers the sales plan based upon previous sales history. The planners wish to use the data warehouse to support various levels of analysis. They wish to monitor the plan against actual sales in order to adjust both the sales and capacity plans to reflect recent experience. So that the comparisons are meaningful the reports must reflect the hierarchies that were in effect at the time the plan was published. Both the product and customer are simple hierarchies. Each child has only one parent. Analysis There are a number of aspects to consider concerning how the hierarchies are to be used in this application. First and most important there is a need to compare values that are provided at different levels in the hierarchies a sale which is collected at the transaction level and is specific to a SKU sold-to customer and ship-to address and the sales plan which is specified at a higher level in both the product and customer hierarchies. Second the data warehouse will most likely be called on to provide sales history to the capacity-planning system. The feed would be required to tie the detailed history to the higher-level Modeling Hierarchies 213 hierarchy entities where the planning has taken place. It may even be necessary to calculate the allocation percentages. Third while planning is done at an intersection of the customer and product hierarchies different user groups require the numbers to be reported using one side of the .