Relation between different tables in extended star schema

Hi Experts,
I searched all many threads to understand the how Attribute change run is used for
But a small question is going still.
Is attribute change run used for getting consistent data from aggregates or from infocubes.
Attribute change run is used to update  the master data .Then what is the use of "activate master data "
in context menu of the master data infoobject.
Somewhere I have read that Attribute change run is used for updating Aggregates but it has got nothing to
do with Infocubes,Is it right ?
Please clarify me
Thanks in advance
Sundar

Hi Sundar,
Is attribute change run used for getting consistent data from aggregates or from infocubes.
The purpose of ACR is to update the changes happened in master data to aggregates not for aggregates.
Attribute change run is used to update the master data .Then what is the use of "activate master data "
in context menu of the master data infoobject.
when you click on activate master data, the data in P or Q or X or Y tables will get activated(if any records with version M will turned to version A)
ACR is used to update the same changes to aggregates
Somewhere I have read that Attribute change run is used for updating Aggregates but it has got nothing to
do with Infocubes,Is it right ?
Yes you are wright.here we have small logic when ACR is running if you start any rollup step it will get fail.
While ACR is running aggregates will get locked
Regards,
Venkatesh

Similar Messages

  • What happens when i remove Dimension table in extended star schema

    *how to integrate the flex builder web dynpro and xcelsius?
    i found some scenarios like when the content of the table change the chart will changes for the changed data in the table using flash islands and web dynpro.
    my scenario is like this.
    when i changed the chart with sliders automatically the content in the table will update to the chart level ? but both table and chart will be in the same dashboard. how can i work out this scenario using flash islands, flex and web dynpro>
    thanks in Advance*

    Hi Sateesh,
    Please go through this URL you will get overall Idea about Extended Star schema with DIM ID's,SID's and Data flow.
    http://help.sap.com/saphelp_nw70/helpdata/EN/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
    I hope it will help you.
    Regards
    Suresh B.G.

  • Relation between different GUID and tables in RPM

    Hi All,
    can you tell me the relation between different GUID and tables in RPM. Many thanks.
    Regards,
    J B

    Hi Deepesh,
    Try the foll. join :
        SELECT  fragment_guid  INTO  (some internal Table)
             FROM  comm_pr_frg_rod
             WHERE  product_guid  = (your product guid list)
    This should give u a complete match of the products.
    Hope this helps.
    Regards,
    Raviraj

  • Regarding Extended star schema

    Hi Friends,
    In Extended star schema,master data will load separately ,which will connect through sid's to dimension table .
    My question is.. This master data tables can be used other than this cube ?
    Please tell me i am in confusion.
    Thanks in advace,
    Regards,
    ramnaresh.

    Hi
    InfoCubes are made up of a number of InfoObjects. All InfoObjects (characteristics and key figures) are available independent of the InfoCube. Characteristics refer to master data with their attributes and text descriptions.
    An InfoCube consists of several InfoObjects and is structured according to the star schema. This means there is a (large) fact table that contains the key figures for the InfoCube, as well as several (smaller) dimension tables which surround it. The characteristics of the InfoCube are stored in these dimensions.
    An InfoCube fact table only contains key figures, in contrast to a DataStore object, whose data part can also contain characteristics. The characteristics of an InfoCube are stored in its dimensions.
    The dimensions and the fact table are linked to one another using abstract identification numbers (dimension IDs) which are contained in the key part of the particular database table. As a result, the key figures of the InfoCube relate to the characteristics of the dimension. The characteristics determine the granularity (the degree of detail) at which the key figures are stored in the InfoCube.
    Characteristics that logically belong together (for example, district and area belong to the regional dimension) are grouped together in a dimension. By adhering to this design criterion, dimensions are to a large extent independent of each other, and dimension tables remain small with regards to data volume. This is beneficial in terms of performance. This InfoCube structure is optimized for data analysis.
    The fact table and dimension tables are both relational database tables.
    Characteristics refer to the master data with their attributes and text descriptions. All InfoObjects (characteristics with their master data as well as key figures) are available for all InfoCubes, unlike dimensions, which represent the specific organizational form of characteristics in one InfoCube.
    Integration
    You can create aggregates to access data quickly. Here, the InfoCube data is stored redundantly and in an aggregated form.
    You can either use an InfoCube directly as an InfoProvider for analysis and reporting, or use it with other InfoProviders as the basis of a MultiProvider or InfoSet.
    See also:
    Checking the Data Loaded in the InfoCube
    If the above info is useful, please grant me points

  • Wat is the use of sid in extended star schema rather than linking masterdat

    hi bw gurus,
    wat is the use of sid in extended star schema rather than linking masterdata with dimention tables?
    thanx in advace,
    i will assign points,
    srinivas

    hi,
        the sid are used instead of the data in order to avoid the redunduncy of data.
    and reduce the datastorage size.
    the data will be present in the sid table and the data is linked used the corerponding sid in the dimension.
    regards

  • Need help with an extended star schema.

    I have the following data in spreadsheet form and I need to transpose this into an extended star schema in order to prdouce my characteristics and key figures, however I'm having a little trouble understanding where to include the Product Group in the star schema and also what to do with the Sales Doc (Invoice Number) in the sales information spreadsheet. 
    I need to summarise the data into the following also:
    1.     Total quantity and revenue for each Channel and product group
    2.     Total quantity and revenue for each Channel and product group (July 2009 to September 2009)
    3.      Total Quantity and Revenue for iphone sales
    So my question in short is what would the star schema look like?  I'm hoping somebody can help me over this hurdle.
    The following are the details from the spreadsheet:
    Product Details (Attributes)
    File Name:  Product_Details.csv
    Structure     FieldName     Length     Description
         ProdID     5     Uniquely identifies a product
         PG_Group     20     Identifies products in specific groups (Navigational field)
    Sample Data
    ProdID,PG_Group
    PDS01,COMPUTER
    PDS02,COMPUTER
    PDS03,COMPUTER
    PDS04,ACCESSORIES
    PDS05,ACCESSORIES
    PDS06,ACCESSORIES
    PDS07,ACCESSORIES
    PDS08,HARDWARE
    Product Description (Text)
    File Name:  Product.csv
    Structure     FieldName     Length     Description
         ProdID     5     Uniquely identifies a product
         Prod_Desc     Medium Text     Represents the product description
    (Navigational field)
         Language     2     Represents the language descriptor
    Sample Data
    ProdID,Prod_Desc,Language
    PDS01,Notebook Speedy I,EN
    PDS02,Notebook Speedy II,EN
    PDS03,PC Thinkbox I,EN
    PDS04,USB Adaptor,EN
    PDS05,iPhones PX2,EN
    PDS06, Stereo Kit,EN
    PDS07,Camera Connector,EN
    PDS08,USB Storage,EN
    Transactional Data
    Sales information
    File Name:  Sales.txt
    Structure     FieldName     Length     Description
         Product     5     Uniquely identifies a product
         Sales Doc     4     Sales Document number (Invoice Number)
         Calendar Year     8     YYYYMMDD format
         Channel     1     Represents the distribution channel the product was sold by
         Quantity     4     Numeric value indicating the number of each product sold on a specific sales document
         Unit     2     Refers the unit specified by the quantity
         Revenue     8     Refers the sales amount of a specific product on a specific sales document
         Currency     3     Relates the revenue currency type
    Sample Data
    Product;Sales Doc ,Calendar Day,Channel,Quantity,Unit;Revenue,Currency
    ZD_PROD,0DOC_NUMBER,0CALDAY,ZD_CHAN,ZD_QTY,0UNIT,ZD_REV,0CURRENCY
    PDS07,7389,20090705,A,95,EA,151905,USD
    PDS08,7389,20090705,A,115,EA,264385,USD
    PDS02,7473,20090706,B,55,EA,3580445,USD
    PDS01,7472,20090706,C,110,EA,604989,USD
    PDS02,7472,20090706,C,43,EA,2799257,USD
    PDS03,7472,20090706,C,75,EA,4507425,USD
    PDS04,7472,20090706,A,339,EA,301032,USD
    PDS06,7472,20090706,A,120,EA,47976,USD
    PDS01,7473,20090718,D,55,EA,3024945,USD
    PDS02,6845,20090806,B,30,EA,195297,USD
    PDS07,6877,20090807,C,800,EA,12792,USD
    PDS08,6877,20090807,C,250,EA,57475,USD
    PDS03,6912,20090812,C,250,EA,1502475,USD
    PDS04,6900,20090812,B,70,EA,6216,USD
    PDS01,6899,20090812,C,12,EA,659988,USD
    PDS04,6899,20090812,D,55,EA,4884,USD
    PDS04,7479,20090815,C,80,EA,7104,USD
    PDS05,7479,20090815,C,300,EA,70497,USD
    PDS05,6809,20090818,A,1000,EA,234990,USD
    PDS06,6809,20090818,A,130,EA,51974,USD
    PDS03,6831,20090822,C,15,EA,901485,USD
    PDS04,6831,20090822,C,500,EA,4440,USD
    PDS03,6830,20090822,C,125,EA,7512375,USD
    PDS06,6830,20090822,C,400,EA,15992,USD
    PDS04,6841,20090825,C,53,EA,47064,USD
    PDS05,6841,20090825,C,350,EA,822465,USD
    Distribution Channel
    Channel (text)
    File Name:  Channel.csv
    Structure     FieldName     Length     Description
         ChanID     1     Uniquely identifies a specific distribution channel
         Chan_Desc     Medium
    Text     Full name of each distribution channel
    (Navigational field)
    Sample Data
    ChanID, Chan_Desc
    A,Phone
    B,Fax
    C,Internet
    D,Other
    Star Schema Model:

    Potentially the issue may be the combination of actual distance and the presence of any Wi-Fi interference at the location of the AirPort Express that may be the culprit here. The bottom line is you would want the Express to be within a 25+ dB range of the Extreme to be sure that it can consistently stay connected to it.
    For more details on proper base station placement, check out the following AirPort User tip. Please post back your results.

  • Why was the extended star schema scrapped?

    Hi,
    BW on HANA takes out the dimension tables and gives us back the original star schema structure.
    Now my questions are
    - How did the original extended star schema help the old BW on oracle or DB2 systems? I mean what was the need for such a design
    - If it offered some kind of optimization .. then why was it scrapped in BW on HANA? Couldn't it have added on to the performance that HANA DB brought?
    Regards,
    Sam

    Can anyone please explain.. ? Krishna Tangudu Thomas Jung Shyam Uthaman .. Any thoughts?

  • Extended Star Schema doubt

    Hi ALL,
    Fact table --- Dimension table -
    Sid Table -- master data values.
    Fact table:
    Contains Key Figures and Dimensional id's
    Dimension table:
    Contains Dim Id & SID
    SID table:
    SID and Master object ID ( eg: Customer ID)
    Master Data Table:
    contains Customer Attributes , Texts , Hierarchies for that Customer ID.
    THis is the Extended Star Schema design.
    MY DOUBT:
    1)In Dimension table itself if we place that Customer ID(No SID table next) what will happen?
    Fact table --> Dimension table --> Master data Table
    2)Instead of that SID table we can directly place that CustomerID in Dimension table , so we can reduce one layer inbetween Dimendion table and Master data table.Is it correct or not?
    Any one can clarify my doubt.
    Regards,
    Arun.M.D

    SID means 'surrogate ID'. That is an system created id as you know. Main purpose is fastening the search.
    Mostly, there exists a rule for Customer or Material ID's.
    Like it should be CHAR 10 or CHAR 16.
    This kind of alpha-numeric fields are harder to search when compared to integers. Moreover, your customer id can be 10 digits but, this does not mean you will have 1000000000 customers. This is the main reason that, an internal ID is produced. If you have 10000 customers, your SID will be at most 10000. 
    However, if your customer ID's are starting from 1 and growing up like integers, then your argument would be true. ( but still no way to skip SID creation and direct usage of characteristic ID in fact table)
    Also, as mentioned by other friends, there exist the Line Item dimension property if you have only one characteristic in one dimension. That simply does skip the DIM ID creation step, and puts your SID into the Fact table. ( Since you have only one char in the dimension, no combination is possible)
    Hope this helps.
    Derya

  • Relation between MSEG table and movement types in 2lis_03_bf

    Hi all,
    May i know the relation between MSEG table and 2lis_03 _bf xtractor stock type/stockcategory where we see the informarion in r/3 side for this, you answers gets rewarded.
    regards,
    Dan.

    Hi,
    Most of the data for IM comes from the tables MSEG andd MKPF. You can go to MSEG contents and see the data there. You will find all the movement types, stock types and stock categories there. You can also use the transactions MB5B, MB51 etc.. to see the related info in R/3. As I said most of the data comes from these tables but not all the data. It uses some internal programming to get the data.
    Hope it helps...

  • What is the Relation between System Tables and FND Table?

    Hi,
    I have two LOV's. First one is Module Name. Here I will select Module Name as GL, AP, AR.... In the second LOV it should populate all the API's available in the module. I tried with the following tablesFND_APPLICATION AND ALL_SOURCES. But there is no relation between these tables.
    Can anyone suggest me..
    Please help me out.
    Thanks in Advance,
    Sateesh

    Hi,
    I have two LOV's. First one is Module Name. Here I will select Module Name as GL, AP, AR.... In the second LOV it should populate all the API's available in the module. I tried with the following tablesFND_APPLICATION AND ALL_SOURCES. But there is no relation between these tables.
    Can anyone suggest me..
    Please help me out.
    Thanks in Advance,
    Sateesh

  • Extended Star Schema

    Hi
    Right now I'm trying to implement SAP HR Infotypes into SAP BW. I try to combine 10 infotypes (all Personal Administration) into one infocube. The confusing one is that when I see my dimension, there something strange (please see below)
    Dimension 1 (from PA0016)
    ZDATEFROM16
    ZDATETO16
    ZXXX (60 character, don't have master date attribute or text)
    ZYYY (30 character, don't have master date attribute or text)
    ZAAA(3 character, only master data text)
    Dimension 2 (from PA0023)
    ZDATEFROM23
    ZDATETO23
    ZCCC (60 character, don't have master date attribute or text)
    ZBBB (30 character, don't have master date attribute or text)
    ZDDD (20 character, don't have master date attribute or text)
    If i see my dimension, it seems strange because most of them don't have master data (text,attr,hierarchy).
    Is this violate the extended star schema design? Thank you.
    Regards,
    Satria

    You can use characteristics such as ZXXX without master data (text, attr, hier) in extended star schema. It is not a violation. This means in business, for this characteristic you really don't need its text, attribute or hierarchy.
    When perform data modeling for you HR cube, please do consider the design, can some characteristic be attribute of another one? Will you use hierarchy such organization level for some characteristic? characteristic with text, attribute or hierachy can provide more flexibility in reporting.

  • Relations Between MLCD table and material movements type

    Dear all,
    I Have a question about relations between MLCD table and Material movements.  For Example We have a movement type Z71 when we did a movevent with tis movement type from MB1C Transaction. System creates a record in Mlcd Table. in this table Category field is VN and  PCat field is V. How system decides about VN and V
    is there any table which contains these conversions or is there any custimization in MM or CO modules ?
    Could you please help me if you have any information about subject.
    Best Regards

    Hi Anupam
    Thanks for your speedy reply.sorry i forget to mention i need FG materials details for given plant,production version,metrial type.In
    MKAL i am not able to give material type as input parameter
    Regards
    Bala

  • How to check relation between two tables in same database

    How to check relation between two tables in same database using Oracle SQL developer. Version 2.1.1.64

    Hi,
    Try this,
    SELECT   cons.owner AS child_owner, cons.table_name AS child_table,
             cons.constraint_name constaint_name,
             cons.constraint_type constraint_type, col.owner parent_owner,
             col.table_name parent_table, col.column_name column_name
        FROM dba_cons_columns col, dba_constraints cons
       WHERE cons.r_owner = col.owner
         AND cons.r_constraint_name = col.constraint_name
         AND col.owner = 'MY_USER'
    ORDER BY child_table;Thanks,
    Shankar

  • Make relation between 2 table programilly

    how can I make a relation between 2 tables ( one to many) through code
    and also broke this relation through code

    You just need these commands:
    https://msdn.microsoft.com/en-US/library/zkyz3407%28v=vs.80%29.aspx
    https://msdn.microsoft.com/en-US/library/sdwsys0z(v=vs.80).aspx
    Bye, Olaf.
    Olaf Doschke - TMN Systemberatung GmbH http://www.tmn-systemberatung.de

  • Relation between different PP tables

    Hi All
    Can any one help me to know the all possible relations between the different PP (Production Planning) tables and
    What is the genral work flow of the data in PP module not regarding the functional aspect but in Technical aspect.
    Regards
    Pavan

    SAP PP Master Data Tables
    MASTER DATA
    Engineering Change Management
    AENR        Customer and priority
    AEOI          Revision Numbers
    Work Center
    CRHD         Workcenter Header Data
    CRCA         Workcenter Capacity Allocation
    CRCO         Workcenter Cost Center Assignment
    CRHH          Hierarchy Header
    CRHS           Hierarchy Structure
    CRTX          Workcenter Text
    KAKO         Capacity Header
    KAZY          Intervals of Capacity
    Routing
    PLPO          Routing Operation Details
    PLKO         Routing Header Details
    MAPL         Routing Link to Material
    PLAB          Relationships - Standard Network
    PLAS          Task List - Selection of Operations
    PLMZ         Component Allocation
    PLPH          CAPP Sub-operations
    PLFH          PRT Allocation
    PLWP         Maintenance Package Allocation
    PLMK         Inspection Characteristics
    Bill of Material
    STPO          BOM Item Details
    STPU          BOM Sub Items (designators)
    STKO         BOM Header Details
    MAST         BOM Group to Material
    STZU          BOM History Records
    STAS          BOM Item Selection
    STPF           BOM Explosion Structure
    Line Design
    LDLH          Line Hierarchy Header
    LDLP          Line Hierarchy Items
    LDLT          Line Hierarchy Takt Times
    LDLBC       Takts/No. Individual Capacities per Line
    LDLBH       Line Balance Header 
    LDLBP        Line Balance Items
    LDLBT        Line Hierarchy Entry and Exit Takts
    PRT's
    CRFH          PRT Master Data
    CRVD_A     Link of PRT to Document
    CRVD_B     Link of Document to PRT
    CRVE_A     Assignment of PRT data to Equipment
    CRVE_B     Assignment of equipment to PRT data
    CRVM_A    Link of PRT data to Material
    CRVM_B    Link of Material to PRT data
    CRVS_A     Link of PRT Internal number to PRT External number
    CRVS_B     Link of PRT External number to PRT Internal number 

Maybe you are looking for