- SAP BW Tutorial
- SAP BW - Home
- SAP BW - Overview of SAP BI
- SAP BW - Data Warehousing
- SAP BW - Data Flow
- SAP BW - Transformation
- SAP BW - InfoArea, Object & Catalog
- SAP BW - DataStore Objects & Types
- SAP BW - Write Optimized DSO
- SAP BW - Infoset
- SAP BW - InfoCube
- SAP BW - Virtual InfoProvider
- SAP BW - MultiProvider
- SAP BW - Flat File Data Transfer
- SAP BW - DB Connect
- SAP BW - Universal Data Connect
- SAP BW - Process Chain
- SAP BW - Reporting
- SAP BW Useful Resources
- SAP BW - Questions Answers
- SAP BW - Quick Guide
- SAP BW - Useful Resources
- SAP BW - Discussion
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
SAP BW - Write Optimized DSO
In the Write Optimized DSO, data that is loaded is available immediately for further processing.
Write Optimized DSO provides a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written on to the DataStore object. The data can then be updated to further InfoProviders. You only have to create the complex transformations once for all data.
Write Optimized DSOs are used as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
In Write Optimized DSO, the system does not generate SIDs and you do not need to activate them. This means that you can save time and further process the data quickly. Reporting is possible on the basis of these DataStore objects.
Structure of Write Optimized DSO
It only contains the table of active data and there is no need to activate the data as required with the standard DSO. This allows you to process the data more quickly.
In Write optimized DSO, loaded data is not aggregated. If two data records with the same logical key are extracted from the source, both records are saved in the DataStore object. The record made responsible for aggregation remains, however, so that the aggregation of data can take place later in standard DataStore objects.
The system generates a unique technical key for the write-optimized DataStore object. The standard key fields are not necessary with this type of a DataStore object. If there are standard key fields anyway, they are called semantic keys, so that they can be distinguished from the other technical keys.
The technical keys consist of −
- Request GUID field (0REQUEST)
- Data Package field (0DATAPAKID)
- Data Record Number field (0RECORD) and you load only new data records.
Use T-Code: RSA1
Go to Modeling tab → InfoProvider → Select InfoArea → Right click and click on create DataStore Object.
Enter the technical name and description of the DataStore object.
Type of DataStore Object − This is used to select the DSO type. It takes a standard DSO by default.
Click on Create (F5) button as shown in the following screenshot.
To change the DSO type, go to the settings tab as shown in the following screenshot. Click on the Edit icon and when a new window opens, you can change the DataStore Object and also select the type which is required.