InfoCube
This is an excerpt from the paper...
1. What is the difference between a basic and transactional InfoCube? Why does planning in BPS require transactional InfoCubes?A Basic InfoCube is one that physically stores data. Data is placed into a Basic InfoCube through the process of BW (Business Warehouse) Staging. Once date is placed in a Basic InfoCube, the Basic InfoCube can act as an InfoProvider for BEx (Business Explorer) reports. The structure of a Basic InfoCube follows the patterns of a Star Schema. The Star Schema requires dimension tables for each data source. In the Star Schema, the fact table is at the center of the schema, as the fact table contains the data that is the primary focus of the business intelligence objective. The dimension tables store the information needed to develop the required business intelligence. One difference between Basic InfoCubes and Transactional InfoCubes is that Transactional InfoCubes have the capability to support parallel write access. In contrast, Basic InfoCubes are optimized for read access. Planning in BPS (Business Planning and Simulation) frequently requires the simultaneous entry of multiple sets of data (planning data and data for fact tables) into an InfoCube. The BW Staging process for data entry used in the Basic InfoCube does not support simultaneous data entry. The Transactional InfoCube, however, is designed to allow data filling through the use of BW-BPS (Business Planning Simulation), which support simultaneous data entry.
. . .
ey figures in a BW, where data are always disaggregated to the lowest level
A fixed Planning Level (Location / Product) can be setup
Planning package: A planning package represents the quantity of transaction data on which the planning functions; a planning package distinguishes between plans; planning packages are created automatically at every planning level
3. Take each of the characteristics of groups (membership, interaction, hierarchy, location and time) and rate it to your Andina team (including Bentley and HES).
Membership refers to the inclusion of related data elements in specific InfoCubes (in relation to the Andina team, workgroup affiliation of individuals working on BPS planning projects is an example of such group data membership)
Interaction refers to relationships among various data elements (in the Andina team, identities and skills are examples of interaction)
Hierarchy refers to the differentiation between key figure and characteristics (for the Andina team, names are key figures entered into fact tables at different levels)
Location and time are among the dimensions of data entered into fact tables (for the Andina team, such data are included in dimension tables)
4. Explain what a query is in BW (relat
. . .
Some common words found in the essay are:
Data Packet, Star Schema, InfoCube Multi-planning, HES Membership, Level Location, Planning Level, Basic InfoCube, Planning Simulation, InfoCube Standard, InfoCubes Characteristics, planning level, key figures, standard planning, dimension tables, basic infocube, andina team, characteristics key figures, planning package, characteristics key, star schema, planning data, data planning data, dimension tables infocube, placed basic infocube, own planning data,
Approximate Word count = 1209
Approximate Pages = 5 (250 words per page)
|