Three types of DSO in BI 7.0

Hi,
I went through the sap help documents related to the three types of DSO.
1. Standard
2. Direct Update
3. Write Optimized
Still not clearly understood in which case we use what kind of DSO's.  Could any one explain me that in your own words.
I am new to BI, your explanation is appreciated.
What is this ADP process that is used using the Direct Update DSO.........Any docuements or links or info on it?
Thanks,

DataStore Objects for Direct Update
DataStore objects for direct update ensure that the data is available quickly. The data from this kind of DataStore object is accessed transactionally. The data is written to the DataStore object (possibly by several users at the same time) and reread as soon as possible.
It is not a replacement for the standard DataStore object. It is an additional function that can be used in special application contexts.
<b>APD -</b>
In the BI system, you can use a DataStore object for direct update as a data target for an analysis process
In the BI system data is collected from the heterogeneous databases in the various systems that the enterprise is using and is consolidated, managed, and staged for evaluation purposes. There is often further, valuable potential in this data.
This is completely new information that is displayed in the form of meaningful correlations between data but that is too well hidden or complex to be discovered by simple observation or intuition.
The Analysis Process Designer (APD) allows you to find and identify these hidden or complex relationships between data in a simple way. Various data transformations are provided for this purpose, such as statistical and mathematical calculations, data cleansing and structuring processes.
The results of the analysis are saved in BI InfoProviders or in CRM systems. They are available for all decision and application processes and thus can be decisive (strategically, tactically, and operatively).
Examples of analysis processes include the calculation of ABC classes, determination of frequency distribution or of scoring information.
http://help.sap.com/saphelp_nw04s/helpdata/en/49/7e960481916448b20134d471d36a6b/content.htm
<b>Standard DataStore Object</b> The standard DataStore object is filled with data during the extraction and load process in the BI system.
It has 3 tables - New , Active , Change log table
<b>Write-Optimized DataStore Objects</b>
Data that is loaded into write-optimized DataStore objects is available immediately for further processing.
You use write-optimized DataStore objects in the following scenarios:
&#9679;     You use a write-optimized DataStore object as a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written to the DataStore object. Subsequently, the data can be updated to further (smaller) InfoProviders. You only have to create the complex transformations once for all data.
&#9679;     You use write-optimized DataStore objects as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
The system does not generate SIDs for write-optimized DataStore objects and you do not need to activate them. This means that you can save and further process data quickly. Reporting is possible on the basis of these DataStore objects. However, we recommend that you use them as a consolidation layer, and update the data to additional InfoProviders, standard DataStore objects, or InfoCubes.
http://help.sap.com/saphelp_nw04s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
Hope it Helps
Chetan
@CP..

Similar Messages

  • Differences between the types of DSO's and DTP's

    Hi Friends,
    1. pls help me in telling different types of DSO's and their differences?
    2. pls help me in telling different types of DTP's and their differences?
    Thanks in Advance.
    Jose Reddy

    Hi,
    Please check :
    1. pls help me in telling different types of DSO's and their differences?
    There are three types of DSO in BI 7.0........
    Standard DSO
    It consists of three tables.......activation queue,active table,and change log table.....It is completly integrated in the staging process.....Using change log table means that all changes are also written and are available as delta uploads for connected data targets.......
    Write optimized DSO
    It is integrated for warehouse level of architecture..........and has the advantage of quicker loads.has only active data table .(with delta capture capability) ...... SIDs are not generated
    Check this :
    http://www.biportal.org/Default.aspx?pageId=90410&mode=PostView&bmi=17541
    Direct update DSO
    It consists of active data table only. This means it is not easily integrated in the staging process...SIDs are not generated ......This DSO type is filled using API and can be read via BAPI......It is generally use for external application and APD...
    Also check this :
    http://help.sap.com/saphelp_nw04s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
    2. pls help me in telling different types of DTP's and their differences?
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10339304-7ce5-2c10-f692-fbcd25915c36
    -Vikram

  • Types of DSO

    Hi,
    I am new , and want some information on this site. Can someone give me some information on types of DSO?
    regards,
    Cheers...

    Hi,
    A DataStore object serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level.
    This data can be evaluated using a BEx query.
    A DataStore object contains key fields (such as document number, document item) and data fields that, in addition to key figures, can also contain character fields (such as order status, customer). The data from a DataStore object can be updated with a delta update into InfoCubes (standard) and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
    Unlike multidimensional data storage using InfoCubes, the data in DataStore objects is stored in transparent, flat database tables. The system does not create fact tables or dimension tables.
    Click the below links and you will find the detailed information on three types of DSO's.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90d9ab26-7a66-2e10-36bb-deea308c7020
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/101ba999-7a66-2e10-5899-8b5bec800d67
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e09289b7-7a66-2e10-1c83-bed127c635f0
    thanks
    cheers!!!

  • What is dsp.how many types of dso's

    hi
    guys
              what is dsp.how many types of dso's  plz post answer

    Hi,
    Types of DSO are
    1. Standard DSO
    2. Direct Update DSO
    3. Write Optimized DSO
    Standard DataStore object
    Data provided using a data transfer process
    SID values can be generated
    oData records with the same key are aggregated during activation
    Data is available for reporting after activation
    *Write-optimized DataStore object
    Data provided using a data transfer process
    SID values cannot be generated
    Records with the same key are not aggregated
    Data is available for reporting immediately after it is loaded
    *DataStore object for direct update
    Data provided using APIs
    SIDs cannot be generated
    Records with the same key are not aggregated
    Standard DSO:
    zRThe standard DataStore object is filled with data during the extraction and load process in the BI system.
    A standard DataStore object is represented on the database by three transparent tables:
    Activation queue: Serves to save DataStore object data records that are to be updated, but that have not yet been activated. The data is deleted after the records have been activated.
    Active data: A table containing the active data (A table).
    Change log: Contains the change history for the delta update from the DataStore object into other data targets, such as DataStore objects or InfoCubes.
    Direct Update DSO:
    The DataStore object for direct update differs from the standard DataStore object in terms of how the data is processed. In a standard DataStore object, data is stored in different versions (active, delta, modified), whereas a DataStore object for direct update contains data in a single version. Therefore, data is stored in precisely the same form in which it was written to the DataStore object for direct update by the application. In the BI system, you can use a DataStore object for direct update as a data target for an analysis process.
    DataStore objects for direct update ensure that the data is available quickly. The data from this kind of DataStore object is accessed transactionally. The data is written to the DataStore object (possibly by several users at the same time) and reread as soon as possible
    Write Optimized DSO:
    DataStore object that only consists of one table of active data. Data is loaded using the data transfer process.
    Data that is loaded into write-optimized DataStore objects is available immediately for further processing.
    You use write-optimized DataStore objects in the following scenarios:
    ● You use a write-optimized DataStore object as a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written to the DataStore object. Subsequently, the data can be updated to further (smaller) InfoProviders. You only have to create the complex transformations once for all data.
    ● You use write-optimized DataStore objects as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
    The system does not generate SIDs for write-optimized DataStore objects and you do not need to activate them. This means that you can save and further process data quickly. Reporting is possible on the basis of these DataStore objects. However, we recommend that you use them as a consolidation layer, and update the data to additional InfoProviders, standard DataStore objects, or InfoCubes

  • Three types of restaurant menus with same dishes but different prices.

    Hi,
    I have to artwork three types of menus for a small restaurant chain. These menus have the same dishes and same background but different prices per restaurant. I will be sending three high res PDFs to print and would like to know if there is a way of doing this without creating three versions of the menues. I know I could create layers and have a layer per restaurant with the text boxes on, turning off and on as I create my PDFs for print but can I have text within the text block that I can turn on and off? Two text blocks, one with prices and one without, is not an option becaues the text all needs to run round together. The reason for this is if a dish needs to be amended it only has to be done once to the master dish. I hope this makes sense.
    Many thanks!

    Hi Guys,
    Thanks very much for your speedy responces!
    With regard to the data merge method I am not sure this would work for me because there is a lot of text and I need them to flow from page to page so would need all the text and prices in one text block (I hope I have understood your method correctly MW Design!). I have just had a look at the Conditional Text method and that seems as though it might work for me but one issue I might have is if one dish is removed form a menu all together then the text will run up from another block. I am sure there is a way once I have the master menu done to force the text to the next text block after the last dish I want on that page and then enlarge the text block a little to accommodate any movement of the dishes on that page, I will look into that!
    Thanks very much for your help.
    PS InDesign never ceases to amaze me!!

  • Differentiate the types of DSo Objects

    Hi Friends,
    can u pls differentiate the standard,wtrite optimised and direct dso objects. in wat scenarios we should use the different types of dso objects.
    thanks
    kumar

      please check in SDN before posting

  • Different Types of DSO

    Hi,
    What are the advantages of Write-Optimized DSO and Direct Update DSO ?
    When is it advisable to use these instead of a Standard DSO?
    The explanation that I have read so far is not very clear, so I am posting in the forum.
    TIA
    Amrita

    Hi,
    check this link:
    http://help.sap.com/saphelp_nw70/helpdata/en/80/1a60cae07211d2acb80000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    There are
    3 types of DataStore Objects
    1.standard DataStore object
    The standard DataStore object is filled with data during the extraction and load process in the BI system.
    Structure
    A standard DataStore object is represented on the database by three transparent tables:
    Activation queue: Serves to save DataStore object data records that are to be updated, but that have not yet been activated. The data is deleted after the records have been activated.
    Active data: A table containing the active data (A table).
    Change log: Contains the change history for the delta update from the DataStore object into other data targets, such as DataStore objects or InfoCubes.
    2.DataStore Objects for Direct Update
    The DataStore object for direct update differs from the standard DataStore object in terms of how the data is processed. In a standard DataStore object, data is stored in different versions (active, delta, modified), whereas a DataStore object for direct update contains data in a single version. Therefore, data is stored in precisely the same form in which it was written to the DataStore object for direct update by the application. In the BI system, you can use a DataStore object for direct update as a data target for an analysis process..
    The DataStore object for direct update is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
    Use
    DataStore objects for direct update ensure that the data is available quickly. The data from this kind of DataStore object is accessed transactionally. The data is written to the DataStore object (possibly by several users at the same time) and reread as soon as possible.
    It is not a replacement for the standard DataStore object. It is an additional function that can be used in special application contexts.
    Structure.
    The DataStore object for direct update consists of a table for active data only. It retrieves its data from external systems via fill or delete APIs.
    The load process is not supported by the BI system. The advantage to the way it is structured is that it is easy to access data. Data is made available for analysis and reporting immediately after it is loaded
    3.Write-optimized datastore object
    DataStore object that only consists of one table of active data. Data is loaded using the data transfer process.
    Use
    Data that is loaded into write-optimized DataStore objects is available immediately for further processing.
    You use write-optimized DataStore objects in the following scenarios:
    ● You use a write-optimized DataStore object as a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written to the DataStore object. Subsequently, the data can be updated to further (smaller) InfoProviders. You only have to create the complex transformations once for all data.
    ● You use write-optimized DataStore objects as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
    The system does not generate SIDs for write-optimized DataStore objects and you do not need to activate them. This means that you can save and further process data quickly. Reporting is possible on the basis of these DataStore objects. However, we recommend that you use them as a consolidation layer, and update the data to additional InfoProviders, standard DataStore objects, or InfoCubes.
    Structure
    Since the write-optimized DataStore object only consists of the table of active data, you do not have to activate the data, as is necessary with the standard DataStore object. This means that you can process data more quickly.
    assign points if useful.
    Regards,
    Narendra

  • How to delete data older than three years from DSO

    Hi  all,
    We needs to keep historical data in the DSO only for three years. One way of doing this is by selective deletion we can delete data older than three years but we want to make it authomated. Is it possible to add a process or ABAP program to delete data older than three years.
    If it is p[ossible by ABAP code then can you please give me sample code.
    Many Thanks in advance.
    Harman

    Some time for in case of huge volume of data selective deletion is not works, Try for "prunning" option.
    It's work as follows
    1)     Create DSO which is same replica of your Source DSO.
    2)     Create two transformation
         a) from Source DSO to Copy DSO
         b) Another is from Copy DSO to Source DSO
    3)     Transprort Last 3 years records to Copy of Source DSO using DTP Filter range for time.
    4)     Once data loading from Source DSO to Copy DSO get completed delete all data from Source DSO.
    5)     Now load data from Copy DSO to Source DSO.
    6)     After complete loading delete entire data from Source DSO.
    I use prunning process to one of my client and it's work perfectly.
    Regards,
    Sushant
    +919820849482

  • Difference between three types of product costs

    Hi,
    SAP Masters
    can any bode explain the what is the difference between product cost by period, product cost by sale order and the third one is there and also please esplain the master recipe

    Dear Kavya,
    __1.Product Cost by Period:__
    Product cost Collector:
    1.Product Cost collector is one of the master data in REM scenario.
    2.Product Cost collector is used as a cost object in REM scenario,which means all the cost will be booked under this product
    cost collector for that material which is nothing but period based costing.
    3.Whatever the confirmations that are done in MFBF or MF41 or MF42N,the cost will get debited or credited accordingly for that
    material and the impact will be seen in the product cost collector.
    4.This product cost collector will be having an order number which will be used for order settlement and variance calculation.
    5.For creating a product cost collector you will require a production version.
    6.so whenever you do an assembly or activity or component backflush,the cost will be booked under this product cost collector.
    2.Master Recipe:
    This comes under PP-PI,where Process order's are used for production.
    The master recipe is used for the manufacture of products or for rendering services.
    Structure
    A master recipe consists of a header and several operations, each of which is carried out at a primary resource. An operation
    is subdivided into phases.
    A master recipe contains process control data that can be stored in the following way:
    ·        in the form of characteristic-based process instructions, which you define in the operation overview for the phases.
    ·        in the form of XSteps, that you maintain in the XStep editor ( XSteps).
    http://help.sap.com/saphelperp60_sp/helpdata/en/05/603bc6462311d182b50000e829fbfe/frameset.htm_
    Revert back with your further queries.
    Regards
    Mangalraj.S

  • How can display three type of service taxes in a single PLD

    Dear All,
    If we want a  *PLD* in following pattern how is it possible
    *Itemid*           *Item Name*          *Unit Price*            *Discount*        *Quantity*      *Tax*       *Total*
      Item01                       TEST1                          10                                  0                             1                    Service             11.2   
      Item01                       TEST1                          10                                  0                             1                  Cess_ST            10.2   
      Iitem01                      TEST1                          10                                  0                             1                HS Cess_ST          10.1         
    Please anybody help me

    Hi Follow These Steps in PLD And Automatically tax will split and show in ur layout .i think this vill solve ur problem Let take Tax Like 1).VAT -
    1
    2).CST----
    4
    3).SERVICE----
    5
    4).CESS_ST----
    6
    5).HSCESS_ST----
    -100
    Etcu2026.
    Now open Any Pld (For Ex: A/R Invoice)
    Add New Repititive Field Take all these fields in Repititive Area 1
    (I) Now take For VaT Let Text Field F_101 = 1
    (ii) Let Database Field F_102 = Database Table = SalesTaxAuthorities Column name = Numerator
    (iii) Let Database Field F_103 = Database Table = A/R Invoice Rows_TaxAmount Per Document Column name = TaxSum
    (iv) Let Formula Field F_104 = F_101 == F_102
    (v) Let Text Field F_105 = F_103*F_104
    (II)Now take For CST
    Let Text Field F_106 = 4
    (ii) Let Database Field F_107 = Database Table = SalesTaxAuthorities Column name = Numerator
    (iii) Let Database Field F_108 = Database Table = A/R Invoice Rows_TaxAmount Per Document Column name = TaxSum
    (iv) Let Formula Field F_109 = F_106 == F_107
    (v) Let Formula Field F_110 = F_108*F_109
    (I) Now take For Service
    Let Text Field F_111 = 5
    (ii) Let Database Field F_112 = Database Table = SalesTaxAuthorities Column name = Numerator
    (iii) Let Database Field F_113 = Database Table = A/R Invoice Rows_TaxAmount Per Document Column name = TaxSum
    (iv) Let Formula Field F_114 = F_111 == F_112
    (v) Let Text Field F_115 = F_113*F_114
    (II)Now take For Cess_ST
    Let Text Field F_116 = 6
    (ii) Let Database Field F_117 = Database Table = SalesTaxAuthorities Column name = Numerator
    (iii) Let Database Field F_118 = Database Table = A/R Invoice Rows_TaxAmount Per Document Column name = TaxSum
    (iv) Let Formula Field F_119 = F_116 == F_117
    (v) Let Formula Field F_120 = F_118*F_119
    (I) Now take For HSCess_ST
    Let Text Field F_121 = 1
    (ii) Let Database Field F_122 = Database Table = SalesTaxAuthorities Column name = Numerator
    (iii) Let Database Field F_123 = Database Table = A/R Invoice Rows_TaxAmount Per Document Column name = TaxSum
    (iv) Let Formula Field F_124 = F_121 == F_122
    (v) Let Text Field F_125 = F_123*F_124
    Similarly follow for the rest of taxes
    and in the End of the report
    Take one Let Text Field F_126 = VAT & link to F_127 Let Formula Field F_127 = ColSum("F_105")
    Let Text Field F_128 = CST & link to F_129 Let Formula Field F_129 = ColSum("F_110")
    Let Text Field F_130 = Service & link to F_131 Let Formula Field F_131 = ColSum("F_115")
    Let Text Field F_132 = Cess_ST & link to F_133 Let Formula Field F_133 = ColSum("F_120")
    Let Text Field F_134 = HSCess_ST & link to F_135 Let Formula Field F_135 = ColSum("F_125")
    And similarly follow for the other taxes
    Reagrds Jenny

  • How to make standard DSO available for reporting?

    In previous version I have Bex setting to make ODS for reporting but in new DSO I don't see this kind of seeting. Any Idea?
    Actually I want the DSO in the query designer to create an adhoc report.
    Thanks in advance.
    York

    hi,
    that option(bex reporting) is taken out from this version in the settings of dso object.
    by default all the three types of DSO object provide reporting on it.
    sap help document. check the following link
    http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    hope this help you
    regards
    harikrishna N

  • 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

  • What are the major changes in BI -7

    Hi experts,
    can any one send me document for major changes in BI -7

    Hi,
    Changed Terminology for SAP NetWeaver 2004s BI
    Old terminology New terminology
    ODS object DataStore object
    Transfer/update rules Transformation
    Reporting Agent Information Broadcasting
    Transactional ODS object DataStore object for direct update
    Transactional InfoCube Real-time InfoCube
    RemoteCube,
    SAP RemoteCube, VirtualProvider
    virtual InfoCube with services
    Administrator Workbench Data Warehousing Workbench
    Monitor Extraction monitor
    Reporting authorizations Analysis authorizations
    OLAP Engine Analytic Engine
    OLAP statistics BI query runtime statistics
    Three type of DSO
    •Standard
    •Direct update
    •Write optimized
    &#1048766;only consists of the table of active data
    &#1048766;not need to activate them
    &#1048766;you can save and further process data quickly
    &#1048766;slightly worse performance during reporting as SIDs are generated during reporting
    See this very nice presentation prepared by Dr Berg on new features of BI 7.0 (these are the differences between BI 7.0 and BW 3.5):
    http://csc-studentweb.lrc.edu/swp/Berg/Articles/NW2004s_what_is_new.ppt
    Check the release notes:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
    This presentation:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
    Web Blog:
    /people/michael.eacrett/blog/2006/06/07/whats-new-in-sap-netweaver-702004s--an-introduction-to-the-functionality-deltas-and-major-changes
    You can also refer below posts:
    Re: BW 7.0 Release
    /message/1383908#1383908 [original link is broken]
    Upgrade from BW 3.5 to BW 7.0 (BI 7.0)
    Some of the other features of BI 7 are
    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.
    this is a good PDF on Upgrade from BW 3.5 to BW 7.0
    latest on upgrade tp BI7.0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Planning/Master_Guide_NW2004s.pdf
    You can seek more information on BI 7.0 in the SAP NetWeaver2004s Ramp-Up.
    /community [original link is broken]
    Re: BW 7.0 Release
    Re: BW 7.0 Release
    Re: BW 7.0
    take a look presentation
    overview
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
    detail
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
    https://www.sdn.sap.com/irj/sdn/developerareas/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e [original link is broken]
    may useful .....
    https://www.sdn.sap.com/irj/sdn/developerareas/bi
    http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    Hope it helps,
    Thanks,
    Happy Life,
    Aravind

  • Types of Infocube & DSO in BI 7.0 version

    Hi,
    What are the Types of Infocube in BI 7.0 version, Please provide details and document also. what are the usage these types of infocube.
    What are the Types of DSO in BI 7.0 version, Please provide details and document also. what are the usage these types of DSO.
    Thanks,
    Vijay.

    Hi Gopi,
    Use a standard DataStore object and set the Unique Data Records flag if you want to use the following functions:
    ○       Delta calculation:
    ○       Single record reporting:
    ○       Unique data:
    Write optimized DSO
    ●      You use a write-optimized DataStore object as a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written to the DataStore object. The data can then be updated to further (smaller) InfoProviders. You only have to create the complex transformations once for all data.
    ●      You use write-optimized DataStore objects as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
    DataStore object for direct update
    you can use a DataStore object for direct update as a data target for an analysis process. The DataStore object for direct update is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM).
    http://wiki.sdn.sap.com/wiki/display/BI/AboutDSOtypesinBI
    Hope this helps.....

  • Where to check UPDATE TYPE in Transformation in BI

    Hi All
    In BI , Where to check UPDATE TYPE( Like whether the filed/infoobject is overwrite or Addition ) in Transformation in BI.
    In BW 3.5 we can check this in UPdate Rule Maintanenance,but in BI where do we check the same.
    Shankar

    Hi,
    you can check Update type in transformation :-
    -->in target, double click on first Column (Rule Type)
    -->Aggregation
    -->you can see both Option (Overwrite, Summation)
    but when target is DSO. in case of Cube, you will have only Summation
    you can check the Update Type in DSO Update Rule as well:-
    -->in Update Rule, Single Click on Key Fig (Amount, Qty....)
    -->Update Rule :Details will come
    -->in that you can see, the Update Type Section has three option (Addition, Overwrite, no update)
    in case of cube you only have ( Addition, no update)
    Best Regards
    Obaid

Maybe you are looking for

  • Safari quit unexpectedly while using the tasty apps plugin

    Is anyone konows what can i do fix it ? :S every time I try t open safari this happens.... :S please helpme !!!! Process:         Safari [1318] Path:            /Applications/Safari.app/Contents/MacOS/Safari Identifier:      com.apple.Safari Version:

  • Oracle9i reinstallation on Windows XP Pro

    Hello, I am having a problem of re-installing Oracle9i on my PC running WinXP Pro. Using the Oracle Universal Installer (OUI), at the Installation Types step, I select the Enterprise Edition and then the progress bar appear up to 31% then the OUI dro

  • Error in F-48 for posing a  Asset PO

    Hi Gurus When an down payment is made against an Asset PO, the system is not allowing it for posting through F-48. Other than Asset PO the system is accepting for making down payment. Can any one of you suggest me through which transaction can i post

  • Creating Billing document for WBS Element(Transaction: CJ02 )

    Hi Guys, I am using FM BILLING_SCHEDULE_MAINTAIN to create billing document with milestone data, it is giving sy-subrc eq 0. but billing document is not saving in  FPLA table, I am using FM GRSV_UPDATE_GRPGA_FROM_CJDW to update project. and more over

  • Acrobat 9 - "Title" for fillable field

    I'm new to creating forms with Acrobat, so I'm afraid I don't know the lingo. I apologize in advance. Is there a way to give a "title" to a fillable field that is only visable until the user selects the field? For example, if I want to create a secti