SAP BW DataStore objects (Objects in DSO)

DataStore Objects (DSO), formerly known as operational DataStores (ODS is an old acronym) are used mainly in BA to stage data and allows for another layer of data cleansing before data is moved to the InfoCube. However, you can also use DSO to a report from (although it is not recommended as the SIDS are generated in real time) aside from the stage of the InfoCube. Is the best practice is to always include a data flow source to DSOs. Three bin data provided within the data flow should be the data source (data source)--> DSO (level of detail)--> InfoCube (data to be transmitted)

What makes DSO differs from the InfoCube? DataStore objects consist of much less tables as the data are stored on the level of detail. DSOs will not make use ' 'Extended Star schema, and therefore the best does not report this type of InfoProvider. DSOs are basically flat table (treat, spreadsheet) where the data is dumped to. Each record is unique in DSO through the technical keys which I will discuss below.

When you load data into a DSO it first gets sent to the new data table (40). The data will sit at the table until the new data, which then activates the ships over to the table of active data (00) and change log table (## ...). During the activation process, the new data table are downloaded zaprzepaszczeniu and record changes are subject to change.

Three kinds of DSOs:

Standard (most common) When to use row-level detail element capable of using secondary indexes improve read performance, set to Indicies subsidiary as part of the screen lower right modeling DSO,
Remember to delete data from the change log on regularly, and will continue to increase overtime and cause performance problems
All data are no longer used in the active table should be archived

Related tables:

New data:/BIC/Adsoname40

Live data:/BIC/Adsoname00

Change log:/BIC/#### #### #### (dynamically generated)

-Optimized write (less common) During the service, after the data you don't need to update, simply written each record is ' written ' 'zaktualizowany ', so the data is loaded quickly
Uses key technical [Requestid | DataPackage | DataRecordNumber]
Uses a key with optional semantic that you define to logically group data/ordering
If you enable the check box ' do check uniqueness "
Semantic keys will be locked
Faster loading data
reporting will be slower
Index builds on what is written most often

Related tables:

Live data:/BIC/Adsoname00

Direct update (least used) When to use-when the data is required only in one version, live data is saved using BAPIs and function modules

Related tables:

Live data:/BIC/Adsoname00

Learn more by visiting SAP BW training headquarters in http://www.sapbwtraininghq.com/

View the original article here