SAP BW DataStore Objects (DSO)

DataStore Objects (DSO) formerly called Operational DataStores (ODS is the old acronym) are mostly found in the BW setting to phase data and allow for another level of data cleaning before data is moved to the InfoCube. But, you might also use a DSO to record from (but not recommended as SIDs are generated in real-time) bypassing the necessity for an InfoCube. It is a most readily useful practice to always include DSOs in your source to a target information movement. The three containers of data within your data stream should really be DataSource (source of data) --> DSO (depth level data) --> InfoCube (data to be described )What makes a DSO different from an InfoCube? DataStore Objects include much less platforms as data is stored at the detail level. DSOs do not utilize the 'Extended Star Schema' and therefore it is far better not record from this kind of InfoProvider. DSOs are basically a set dining table (consider a spreadsheet) where data is left into. Every report is unique in a DSO thanks to specialized keys that we will examine below.When data is loaded into a DSO, it first gets sent to the Brand New Data (40) stand. The information will sit in the Newest Data table until it is activated, which thenhich in turn ships it over to the Change Log table (##.. Johns Creek Lawn Care.) and the Active Data (00) table. During the activation process, the New Data desk gets wiped out, and a change record is filled to the Change Log.Three Kinds of DSOs:Standard (most frequently used) When to use- Line merchandise aspect degree Capable of using extra indexes to enhance examine efficiency Extra indices are arranged within the DSO modeling monitor, reduce rightRemember to remove data from change signood frequently since it may continue to grow overtime and trigger performance issuesAny data no further being used in the active stand should be archivedAssociated tables:New Data: /BIC/Adsoname40Active Data: /BIC/Adsoname00Change Log: /BIC/########## (dynamically made )Write-Optimized (less common) When to use- When data does not must be updated, only written Every record is 'prepared' perhaps not 'updated' therefore knowledge loads quicklyUses a complex essential [RequestID