0 evaluări0% au considerat acest document util (0 voturi)
72 vizualizări13 pagini
An ODS object is used to store consolidated and cleansed data (transaction data or master data for example) on a document level (atomic level) it describes a consolidated dataset from one or more InfoSources. Data in ODS objects is stored in flat, transparent database tables. Fact and dimension tables are not created.
An ODS object is used to store consolidated and cleansed data (transaction data or master data for example) on a document level (atomic level) it describes a consolidated dataset from one or more InfoSources. Data in ODS objects is stored in flat, transparent database tables. Fact and dimension tables are not created.
Drepturi de autor:
Attribution Non-Commercial (BY-NC)
Formate disponibile
Descărcați ca PDF, TXT sau citiți online pe Scribd
An ODS object is used to store consolidated and cleansed data (transaction data or master data for example) on a document level (atomic level) it describes a consolidated dataset from one or more InfoSources. Data in ODS objects is stored in flat, transparent database tables. Fact and dimension tables are not created.
Drepturi de autor:
Attribution Non-Commercial (BY-NC)
Formate disponibile
Descărcați ca PDF, TXT sau citiți online pe Scribd
• An Operational Data Store object (ODS object) is used to store consolidated and cleansed data (transaction data or master data for example) on a document level (atomic level). • It describes a consolidated dataset from one or more InfoSources. You can analyze this data with a BEx query. Operational Data Store: Advantages • Overwrite function characteristics of the data part keyfigures • Save data on a document level consolidated or overwritten cleansed • Reporting Drilldown from InfoCube to ODS object Integrated in the Business Explorer (BEx) • In contrast to multi-dimensional data stores for InfoCubes, data in ODS objects is stored in flat, transparent database tables. Fact and dimension tables are not created. • Hint: The number of ODS objects that must be implemented significantly depends on the complexity of the scenario that is to be implemented. Furthermore, an ODS object can also form the end of a staging process. In other words, an InfoCube does not necessarily have to be updated from the ODS object. PSA / ODS Object / InfoCube (Architecture) ODS Object Architecture • Activation Queue New data is stored in this table before it is activated. It always has a similar structure to a PSA table. In other words, the key is constructed from the request-, data package- and data record number. These requests are deleted from the activation queue once all requests waiting in the activation queue have been successfully activated. • Table with the Active Data • This is where the current status of the data is stored. This table contains a semantic key that can be defined by the modeler (order number, -item, for example). Reporting uses this table. • Change Log • During the activation run, changes are stored in the change log. Here, you can find the complete (activation-) history of the changes, since the content of the change log is not automatically deleted. The connected data targets are updated from the change log if they are supplied with data from the ODS object in the delta method. The change log is a PSA table and can also maintained in the PSA tree of the Administrator Workbench. The change log in turn has a technical key consisting of a request-, data package- and data record number. End of ODS