Difference between an ODS and DSO

What is the difference between an ODS (operational data store) and a DSO?

Hi
There is no difference in ODS and DSO. In BW 3.5 object is called ODS which is now known as DSO in 7.0 version.
To enhance the functionality, we have three types of DSO.
1. Standard DSO
2. Write Optimized DSO
3. Direct Update
Where as there was only type of ODS. this is the only difference.
- Jaimin

Similar Messages

Difference between standard ods and transaction ods

hi experts make this answer

Transactional ODS Object
Definition
A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions (active, delta, modified), whereas a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application. In BW, you can use a transaction ODS object as a data target for an analysis process. You can find more information under Analysis Process Designer.
The transactional ODS object is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
Use
Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object is accessed transactionally, that is, data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible.
It offers no replacement for the standard ODS object. Instead, an additional function displays those that can be used for special applications.
Structure
The transactional ODS object simply consists of a table for active data. It retrieves its data from external systems via fill- or delete- APIs. Refer to ODS Data and External Applications.
The loading process is not supported by the BW system. The advantage to the way it is structured is that data is easy to access. They are made available for reporting immediately after being loaded.
http://help.sap.com/saphelp_nw04/helpdata/en/c0/99663b3e916a78e10000000a11402f/frameset.htm
Regards
Anujit Ghosh

Difference bet cube indexes and dso indexes

hi,
1.can any tell me the difference between cube indexes and dso indexes?
if we have aggregates on the cube it improves the performce of the query created on it
2.so why to create indexes on the cube?
for creating indexes on the dso i right click on dso and click create indexes
it is asking two options
1.unique key 2.non unique
4.what is the functionality of these two?
i will assign points if ur answers clear my questions

The BW automatically defines multiple indexes on your cubes, based on the dimensions you have defined. You do not need to create any additional indexes on your Fact tables. It can somtimes be helpful to create a secondary index on dimension tables or master data tables depending on their size and the queries. There is not BW wkbench tool to do this, it usually requires a DBA in most shops.
Secondary indexes on DSO/ODS can help some queries substantially, again, depending on the data and the queries. You can define secondary indexes on DSO/ODS from the BW workbench.
Aggregates are another tool for query performance, by summarizing the data, it can reduce the number of rows that must be read by a query. Again, it dpends on the query and the data as to how much an aggregate helps.

Please write the difference between ODS and DSO...

Hi all,
Please write me the differences between ODS and DSO.. I think both are same in structure and have same update types (Over write, Addition) and also with the tables (changelog, Activation queue, Active table).. Is there still a difference between ODs and DSO...I can assign the points..
thanks
arya

Hi,
You can check the below document for new Features in BI:
http://help.sap.com/saphelp_nw04s/helpdata/en/a4/1be541f321c717e10000000a155106/frameset.htm
/people/martin.mouilpadeti/blog/2007/08/24/sap-netweaver-70-bi-new-datastore-write-optimized-dso
Reg
Pra

Difference between US eliminations and "normal" intercompany eliminations?

Hi,
Can a kind soul please explain the differences between intercompany eliminations and US eliminations please?
Thanks

Hi Varda ,
RDA is Real Time Data Acquisition . In this We can retrieve Live data . While using Normal DTP We can t pull live data
For example :- Today We have Create a 50 orders . This 50 order information pulled after completion of sales order creation . we can t see live . But RDA process pulled the data at the point of sales order creation it self ,It support only Stranded DSO .It will use Some industries like FMCG.Retail,banking sector they want to know current data information from BI Side then RDA.
Please Find below link for Demonstration of Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00db64ee-82f0-2b10-01b0-fe9543dc227e?quicklink=index&overridelayout=true.
Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f704bd-b6e8-2c10-569e-d726784388ce?quicklink=index&overridelayout=true
Thanks & Regards,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://www.bluemarlinsys.com/
http://bluemarlinsys.com/bi

Difference between Snapshot scenario and non cumulative scenario

Hi,
Can any one please tell me the difference between snapshot scenario and non cumulative scenario in
inventory management.
Also please give example. I read the pdf " how to handle inventroy management scenarios", but can any one please give some easy to understand examples.
full points guaranteed-

hi,
In Non-cummulative method your stock movements are stored in the cube (inflow and outflow of NC KF) and the Total stock is calculated during query execution. Hence if there are lot of movements in the stock for the period you want to report on, query will take long time to execute.
In case of Snap shot scenario Stock movements are not loaded to cube. you use ODS to load the status of the stock and then from ODS you can load to Cube once in a month. So only summarized data will be availabe in Cube. Reporting will be fast.
Check the below threads
Inventory Management - SnapShot model
snapshot scenario?
SNAP SHOT Scenario in IM

Difference between 4.6 and 4.7 vesion in MM point of view

Hai,
can any body tell me the difference between 4.6 and 4.7 version. Please treat it as Urgent

SAP BW 7.0 is called SAP BI and is one of the components of SAP NetWeaver 2004s. There are many differences between them in areas like extraction, EDW, reporting, analysis administration and so forth. For a detailed description, please refer to the documentation given on help.sap.com.
1. No Update rules or Transfer rules (Not mandatory in data flow)
2.Instead of update rules and Transfer rules new concept introduced called transformations.
3. New ODS introduced in additional to the Standard and transactional.
4. ODS is renamed as DataStore to meet with the global data warehousing standards.
And lot more changes in the functionalities of BEX query designer and WAD etc.
5. In Infosets now you can include Infocubes as well.
6. The Re-Modeling transaction helps you adding new key figures and characteristics and handles historical data as well without much hassle. This facility is available only for info cube.
7. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
8. The monitoring has been improved with a new portal based cockpit. Which means you would need to have an EP guy in your project for implementing the portal !
9. Search functionality has improved!! You can search any object. Not like 3.5
10. Transformations are in and routines are passe! Yes, you can always revert to the old transactions too.

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Differences between Classic BW and HANA on BW?

Dear Friends,
can we discuss here what are main difference between classic BW and HANA on BW?
Please share your thoughts who was involved in RAMPup.
already know some differences IMDB DSO, Cube, still some gaps are not clarify till i install BW on HAN
thanks
rao

First of all , HANA Enterprise Extend edition DOES NOT Meets all BW features.
There are no best scenario, it is dependent on scenarios.HANA SPS3 scenarios would be great fit for Agile Data mart however BW on HANA would be great fit for EDW scenarios.
For users who already have BW with BWA, BW on HANA bring performance improvement on the other side of equation (ETL side) along with query improvement.
At high level, following are some of techinal issues with using HANA SPS 3 as "One fit for all" :
1. Currently, there is no reporting tool available which can recogonize variable functionality of HANA. One may use universe variable functionality however the functionality will not provide all exhaustive options.
2. Currently Hierarchies cannot be recogonized by any of reporting tools.
3. Currently Data Level security options in HANA is limited.
Another dimension to consider is if you have planning application,Integrated Planning is currently supported and BPC will be supported soon (the scenario is only possible BW on HANA).
Hope this is helpful.
PS:
Regarding HANA 1.0 SPS3, for your below scenario:
SAP & non SAP - BODS 4.0 -- HANA 1.0 SPS3 -- BI 4.0( Any front end ODBC support )
you will need BODS 4.1 version.

Difference Between data target and infoprovider

Hi Experts,
I am new to BW
What is the difference between data target and infoprovider
Thanks and Regards,
saveen

Hi Saveen,
InfoProvider is an object on which BEx queries are created. It provides information (data) to the queries when they are executed. InfoProviders may contain data (like cube) or may not contain data (like multiproivder and InfoSet).
Data Target is an object to which you will load the data, like cube, ODS or InfoObject. But it is not necessary that each data target is an InfoProvider...like you may have ODS objects that are not enabled for reporting, but you are loading data to them for staging purpose.
Hope this helps...

Difference between Transaction database and relational database

Whats the Difference between Transaction database and relational database ??

'Transaction' refers to the usage of a database. 'Relational' refers to the way in which a given database stores data.
A 'transaction database' (or operational database) could be relational, hierarchical, et al. A transaction database supports business process flows and is typically an online, real-time system. The way in which that data is stored is typically
based on the application(s). Companies often have multiple 'transaction databases'.
An 'operational data store' (ODS) is an integrated view or compilation of transaction data.
The you get into data warehouse databases, where the transaction data is optimized for querying, reporting, and analysis activities.

Difference between BI content and HANA optimized BI content ?

Hi to all,
Is BW is already have HANA database, what is difference between BI content and HANA optimized BI content.
Can any one explain in general term, I have already gone with SAP HELP but, cant grab more of it.
Does we have HANA optimized BI Content only for DS and FI only.
Regards
Pavneet Rana

Hi Pavanet,
you can find more info on the SAP HANA-optimized BI Content and the supported areas following this link:
http://help.sap.com/saphelp_nw74/helpdata/en/28/a1065182d3c557e10000000a44176d/frameset.htm
The SAP HANA-optimized content does contain physical InfoProviders and adheres to the LSA++ architecture paradigm as to reduce persistencies where possible and if it makes sense. One purpose is to provide a guidance of data modelling in the SAP BW on HANA case making use of recent SAP BW features.
For the near future a switch to the recent BW Infoproviders (advanced) DSO and CompositeProvider is planned.
best regards,
Simon

Difference between BW3.5 and BI 7.0 version

difference between BW3.5 and BI 7.0 version

Hi ,
Differences between BW 3.5 and BI 7.0
Major Differences between Sap Bw 3.5 & sapBI 7.0 version:
1. In Infosets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal !
5. Search functionality hass improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
7. The Data Warehousing Workbench replaces the Administrator Workbench.
8. Functional enhancements have been made for the DataStore object:
New type of DataStore object
Enhanced settings for performance optimization of DataStore objects.
9. The transformation replaces the transfer and update rules.
10. New authorization objects have been added
11. Remodeling of InfoProviders supports you in Information
Lifecycle Management.
12 The Data Source:
There is a new object concept for the Data Source.
Options for direct access to data have been enhanced.
From BI, remote activation of Data Sources is possible in SAP source systems.
13.There are functional changes to the Persistent Staging Area (PSA).
14.BI supports real-time data acquisition.
15 SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
a) Renamed ODS as DataStore.
b) Inclusion of Write-optmized DataStore which does not have any change log and the requests do need any activation
c) Unification of Transfer and Update rules
d) Introduction of "end routine" and "Expert Routine"
e) Push of XML data into BI system (into PSA) without Service API or Delta Queue
f) Intoduction of BI accelerator that significantly improves the performance.
g) Load through PSA has become a must. I am not too sure about this. It looks like we would not have the option to bypass the PSA Yes,
16. Load through PSA has become a mandatory. You can't skip this, and also there is no IDoc transfer method in BI 7.0. DTP (Data Transfer Process) replaced the Transfer and Update rules. Also in the Transformation now we can do "Start Routine, Expert Routine and End Routine". during data load.
New features in BI 7 compared to earlier versions:
i. New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition (RDA).
ii. Enhanced and Graphical transformation capabilities such as Drag and Relate options.
iii. One level of Transformation. This replaces the Transfer Rules and Update Rules
iv. Performance optimization includes new BI Accelerator feature.
v. User management (includes new concept for analysis authorizations) for more flexible BI end user authorizations.
Regards
KP

Differences between BW3.5 and BW7.0 Realtime Data Acquisition

Hi,
Could any one explain me clearly the differences between BW3.5 and BW7.0 for Realtime Data Acquisition and also steps for creating it in BW7.0.
Eagerly waiting for your reply. Thanks in advance
Anan

You have to create tranformation in between your DSO and datasource.
If u have not done init of delta earlier, create Standard DTP and schedule init load.
If you did already, create or convert(if standard DTP already exists) Real time DTP. Now create infopckage with realtime field enable, and follow the steps of my blog on demanon from here onwards.
check the below link to know more abt BI 2004s modeling steps:
BI 7

What is difference between sy-tabix and sy-index.

SAP Seniors,
Can you please let me know what is difference between sy-index and sy-tabix.
I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
Thank you
Anitha.

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

Difference between an ODS and DSO

Similar Messages

Maybe you are looking for