Using different logical tables in one dimension

Hello.
I have two fact tables and two dimension tables Country and Region. One fact table depend on one dimension table like it shown in this link - http://file.qip.ru/file/121151603/3b4ebdba/2_online.html. Table Country is received from table Region by DISTINCT.
At the presentation I have to realize one column in Presentation Catalog for both columns Country Name (or Country Id) from Country and Region, the user won't know that one fact table depends on COUNTRY and other on REGION.
Also I have to realize the dimention "Geography" (Country->District->Region) for fact table SALE_REGION.
Could Oracle BI automatically choose from which table get data and if it can, how I should make the logical model?
Thanks.
PS.
The best variant I realized it this - http://file.qip.ru/file/121154314/8d242b81/3_online.html where District is the shared child for second Country level, but it doesn't work properly.

Y don't u use union request in first request details of fact1 and its related dimensions and in 2nd request fact 2 and its related dimensions.
I guess this should work
Thanks
Subhash

Similar Messages

  • Multiple 'logical joins' between a fact table and one dimension table

    It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
    I seek an alternative approach.

    Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

  • HT4436 I have 2 I phone which is using same apple id to back to icloud and restore it. I want to use different id on the one phone what can I do or change the id?

    I have 2 I phone which is using same apple id to back to icloud and restore it. I want to use different id on the one phone what can I do or change the id?

    Welcome to the Apple community.
    In order to change your Apple ID or password for your iCloud account on your iOS device, you need to delete the account from your iOS device first, then add a new account by tapping the "create Apple ID" button. (Settings > iCloud, scroll down and hit "Delete Account")

  • How can I use different iTunes accounts on one iPad?

    How can I use different iTunes accounts on one iPad?

    You can't, well not easily anyway.  The iPad is not meant as a multi account device. 
    You can Sign Out of your iTunes account in Settings->iTunes and App Stores->Apple ID->Sign Out
    However if you sign in with another ID and then download past purchases with it you will lock out the previous ID for 90 days. Which means it will not be able to be used on the iPad for 90 days. 

  • Senarious for using different internal table types

    please give scenarios for  using different internal table types?

    Refer to the following.
    Internal table types
    This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the ABAP Dictionary.
    Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.
    TYPES <t> TYPE|LIKE <tabkind> OF <linetype> [WITH <key>]
    [INITIAL SIZE <n>].
    After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:
    <tabkind> OF <linetype> [WITH <key>]
    The type constructor defines the table type <tabkind>, the line type <linetype>, and the key <key> of the internal table <t>.
    You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
    Table type
    You can specify the table type <tabkind> as follows:
    Generic table types
    INDEX TABLE
    For creating a generic table type with index access.
    ANY TABLE
    For creating a fully-generic table type.
    Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic type INDEX TABLE includes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
    Fully-Specified Table Types
    STANDARD TABLE or TABLE
    For creating standard tables.
    SORTED TABLE
    For creating sorted tables.
    HASHED TABLE
    For creating hashed tables.
    Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
    Line type
    For the line type <linetype>, you can specify:
    Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the ABAP Dictionary. If you specify any of the generic elementary types C, N, P, or X, any attributes that you fail to specify (field length, number of decimal places) are automatically filled with the default values. You cannot specify any other generic types.
    Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and structures in the ABAP Dictionary (for compatibility reasons).
    All of the lines in the internal table have the fully-specified technical attributes of the specified data type.
    Key
    You can specify the key <key> of an internal table as follows:
    [UNIQUE|NON-UNIQUE] KEY <col1> ... <col n>
    In tables with a structured line type, all of the components <coli> belong to the key as long as they are not internal tables or references, and do not contain internal tables or references. Key fields can be nested structures. The substructures are expanded component by component when you access the table using the key. The system follows the sequence of the key fields.
    [UNIQUE|NON-UNIQUE] KEY TABLE LINE
    If a table has an elementary line type (C, D, F, I, N, P, T, X), you can define the entire line as the key. If you try this for a table whose line type is itself a table, a syntax error occurs. If a table has a structured line type, it is possible to specify the entire line as the key. However, you should remember that this is often not suitable.
    [UNIQUE|NON-UNIQUE] DEFAULT KEY
    This declares the fields of the default key as the key fields. If the table has a structured line type, the default key contains all non-numeric columns of the internal table that are not and do not contain references or internal tables. If the table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
    Specifying a key is optional. If you do not specify a key, the system defines a table type with an arbitrary key. You can only use this to define the types of field symbols and the interface parameters of procedures . For exceptions, refer to Special Features of Standard Tables.
    The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
    You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
    You must always specify the UNIQUE option when you create a hashed table.
    Initial Memory Requirement
    You can specify the initial amount of main memory assigned to an internal table object when you define the data type using the following addition:
    INITIAL SIZE <n>
    This size does not belong to the data type of the internal table, and does not affect the type check. You can use the above addition to reserve memory space for <n> table lines when you declare the table object.
    When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each are then allocated.
    You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The space occupied, depending on the line width, is 16 <= <n> <= 100.
    It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
    To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the length of the line. If you specify a larger value of <n>, the system calculates a new value so that n times the line width is around 12KB.
    Examples
    TYPES: BEGIN OF LINE,
    COLUMN1 TYPE I,
    COLUMN2 TYPE I,
    COLUMN3 TYPE I,
    END OF LINE.
    TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
    The program defines a table type ITAB. It is a sorted table, with line type of the structure LINE and a unique key of the component COLUMN1.
    TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
    TYPES: BEGIN OF LINE,
    COLUMN1 TYPE I,
    COLUMN2 TYPE I,
    COLUMN3 TYPE I,
    END OF LINE.
    TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
    TYPES: BEGIN OF DEEPLINE,
    FIELD TYPE C,
    TABLE1 TYPE VECTOR,
    TABLE2 TYPE ITAB,
    END OF DEEPLINE.
    TYPES DEEPTABLE TYPE STANDARD TABLE OF DEEPLINE
    WITH DEFAULT KEY.
    The program defines a table type VECTOR with type hashed table, the elementary line type I and a unique key of the entire table line. The second table type is the same as in the previous example. The structure DEEPLINE contains the internal table as a component. The table type DEEPTABLE has the line type DEEPLINE. Therefore, the elements of this internal table are themselves internal tables. The key is the default key - in this case the column FIELD. The key is non-unique, since the table is a standard table.
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm

  • Issue using one 2 Fact tables with one dimension Table.

    Hi,
    I have 1 Dimension table X and 2 Fact tables A and B
    X is joined to Both A and B for Loan Amount ( with A) and for colleatral amount (with B) when I am selecting the X.Product_Name, A.Loan_Amt, B.Collateral Amount, it is giving an error message
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table EIP Collateral FACT) does not contain mapping for [EIP Reporting FACT.PD ID]. (HY000)
    Any clues???
    Is there a Inner or Outer join which needs to be created or set in the RPD to get the desired results???

    Ok..
    I have one table which is Porfolio Details which has Portfolio name, Product Category , Product Name, Product ID, Product sources code.- This is my Dimension table.
    I have another 2 set of fact tables : EIP Reporting FACT and EIP Collateral FACT..
    These two tables are joined to Portfolio Details table.
    EIP Reprting FACT gives portfolio wise Loan Amount
    and EIP Collateral FACT gives Portfolio wise Collateral Amount details for same set of customer..
    Now, I am selecting Portfolio Name, Product Category, Product Name,SUM( EIP Reporting FACT.LOAN_AMOUNT), SUM(EIP Collaetral FACT.Collateral_Amt) in a report
    Now, on selecting these columns I am getting that error message which is related to mapping.
    If I take any column from Portfolio details table and any column from EIP Reporting FACT- It works.
    If I take any column from Portfolio details table and any column from EIP Colletral FACT- It works.
    But if I take any column from portfolio table and columns from both FACT tables it gives mapping error...
    Hope I am able to explain the issue in a better way now..
    Edited by: help-required on Mar 11, 2010 6:53 PM
    Edited by: help-required on Mar 11, 2010 6:53 PM

  • BMM Logical Table  -  Create Multiple dimension

    Hi All,
    In BMM , I want to create more than one Dimension for a Logical Table. Is it possible to create multiple dimensional hierarchies on a single logical table. Can one share the thoughts or provide inputs. Thanks is Advance
    S

    If I understood your requirements, you are basically trying to do the "Role Playing" dimensions. Is that correct? Ifso, You can create alias for the associated physical table, and then use those aliases as logical tables and then create dimensions of this.
    HTH
    Mahesh

  • How can i create Level Based Hierarchy using multiple logical table.

    Hi All,
    in my use case i have two master logical table.
    Division_Mst(divncd,DivnName)
    Department_Mst(deptcd,DeptName)
    and one logical table which contain both column Header (divncd,deptcd)
    and fact table detail where one measure column(empcd) using aggregation count on it.
    so i want to create levelbased hierarchy like this.
    DivnName
              |------DeptName
    which are come from(Division_Mst,Department_Mst) .
    so user can see no of employees division wise and drill down to Department wise.
    How can i achieved this?
    thanks
    Manish

    Check out Shay's blog https://blogs.oracle.com/shay/entry/adf_faces_dynamic_tags_-fora
    Timo

  • Call function 'Download' using different internal tables

    Hi everyone!
    i declare 10 different internal tables, with the same structure but different data.
    i need to create 10 different files (one from each internal table)
    i dont want to call 10 times the function download.
    is there someway to put a variable name(that refeer to my internal table)
    something like this.
    PERFORM Create_file USING mytable.
    PERFORM Create_file USING mytable2.
    PERFORM Create_file USING mytable3.
    PERFORM Create_file USING etc....
    FORM create_file USING table.
      DATA: file(128),
            zcancel(1).
      archivo = 'c:\loans.dat'.
      CALL FUNCTION 'DOWNLOAD'
           EXPORTING
                bin_filesize        = ' '
                codepage            = ' '
                filemask_all        = ' '
                filemask_mask       = ' '
                filemask_text       = ' '
                filename            = file
                filetype            = 'dat'
                filetype_no_change  = ' '
                filetype_no_show    = ' '
                item                = ' '
                mode                = ' '
                wk1_n_format        = ' '
                wk1_n_size          = ' '
                wk1_t_format        = ' '
                wk1_t_size          = ' '
           IMPORTING
                cancel              = zcancel
           TABLES
                data_tab            =  <b>TABLE</b>
           EXCEPTIONS
                invalid_filesize    = 01
                invalid_table_width = 02
                invalid_type        = 03
                no_batch            = 04
                unknown_error       = 05.
    ENDFORM.

    Hi,
    Check this example..
    It download t_mara1 & t_mara2..Modify the code according to your requirement..
    DATA: t_mara1  LIKE mara OCCURS 0 WITH HEADER LINE.
    DATA: t_mara2 LIKE mara OCCURS 0 WITH HEADER LINE.
    DATA: v_filename LIKE rlgrap-filename.
    DATA: v_char5(5).
    FIELD-SYMBOLS: <fs> TYPE table.
    DATA: v_variable(30).
    DO 2 TIMES.
      CLEAR: v_filename.
      v_char5 = sy-index.
      SHIFT v_char5 LEFT DELETING LEADING space.
      CONDENSE v_char5.
      CONCATENATE 'C:\TEST' v_char5 '.TXT' INTO v_filename.
      CONCATENATE 'T_MARA' v_char5 '[]' INTO v_variable.
      ASSIGN (v_variable) TO <fs>.
      CALL FUNCTION 'DOWNLOAD'
           EXPORTING
                filename                = v_filename
                filetype                = 'DAT'
           TABLES
                data_tab                = <fs>
           EXCEPTIONS
                invalid_filesize        = 1
                invalid_table_width     = 2
                invalid_type            = 3
                no_batch                = 4
                unknown_error           = 5
                gui_refuse_filetransfer = 6
                customer_error          = 7
                OTHERS                  = 8.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDDO.
    Thanks,
    Naren

  • How to link a fact table to one dimension many times

    I have fact table which contains four date fields and I want to connect all of them to the Time dimension. I think I probably must split this fact table to multiple tables and then link them to dimensions. What is the right way to solve this kind of problem?
    Example: Fact table: TimeIn, TimOut, TimeStart, TimeStop, InPlace, OutPlace, StartPlace, StopPlace, Speed, Weight, Width, Height .....
    Thank you

    Hello Kostis,
    thank you for your answer. I don't fully understand you. Can you show me short example, please? I create alias table for time dimension on Physical Layer - original table is TimeDayDim and I create aliases TimeDayDim1, TimeDayDim2, TimeDayDim3, TimeDayDim4. Then I create foreign key Fact.Time1 -> TimeDayDim1, Fact.Time2 -> TimeDayDim2, Fact.Time3 -> TimeDayDim3, Fact.Time4 -> TimeDayDim4. And what now? Must I create these table api Bussines Model and create new time dimensions at bussiness model????
    I need in Answers ONE Time dimension. I think I must split my fact table to four tables ... (time1, place1 ...) (time2, place2 ...) (time3 place3...) (time4 place4...) then link those tables to Time dimension (but I dont know where I can split those tables - on Physical Layer or on Bussines Layer).
    I suppose that I will have in Answers one time dimension and four facts tables and I will be able to query them. (for example: Time.Days, Fact1.Place1, Fact3.Speed, Fact4.Count Criteria: Time.Year = 2008)
    Best Regards Vlada

  • Using different levels of the same dimension

    If I have 2 fact tables and a conforming time dimension. Can I make a join so that one table will ignore different years completely? (1 table has only 1 year of data, so it should display same values for different years for other table -yet, I still want to be able to drill-down from Year-to-Detail). I am somewhat successful at seeing it ok on a Annual level (when setting the desired metric to Grand Total Level - but aggregate navigation doesn't work correctly -I'm locked at annual level). Thanks

    HI mma (and anyone else who was following).
    Here's an update:
    a) AGO function doesn't support anything non-integer - it's official and the product enhancement request has been filled. Go figure - they cancel time-series wizard - but at the same time - the AGO isn't fully scalable. Since we're developing a brand-new RPD - and we weren't using any YAGO, MAGO, etc. tables - this has bitten us later than sooner.
    b) using CASE statement is no panacea (change for each year).
    c) your method (time.key=time.key (of 2005) + MOD (time,key, 365) would probably work in my situation (I tried it - and it wasn't that difficult to implement), UNLESS I'd get the following RPD integrity error - "Error: Using a complex join in table that sources time dimension" (I tried aliases as well).
    d) Right now, I'm just doing that metric on Annual level. Creating a view in Oracle that only contains needed data (for 2006) , using it as a physical table in physical layer, and connecting with all foreign keys BUT time.
    I still think there must be a better way without complex ETL and without creating additional column. LOJ and ROJ and FOJ didn't work.
    Thanks for looking at this again.

  • Using different RFC's in one Application / Entity Service?

    Hello *,
    I just want to create my first Composite Application Service but before I begin I have some questions.
    The service will read out material master data from PLM. For that it has some findBy-operations with full-text search (creationDate, MatNr. ...) which return a result list and one operation which returns the material object for a given MatNr.
    For this operations I need to call different RFC's which are imported by external services.
    Now my questions:
    1. What kind of service should wrap my external services and provide the operations? Should I use one or more entity service to wrap external services and then realize the operations in an application service? Or should I just take an application service without entity services?
    2. The created service should not only be an internal CAF  service but also a Web service? How can I realize this?
    Thanks for your answers.
    Best regards
    Joschi

    Ok, thanks a lot. So nearly everything's clear now. Only one question remains:
    > 6. mark the entity service as "remote" and create a
    > web service from it
    > (note: this requires NW04s SP8)
    Is this possible? I can't find any checkbox to mark an entity service as "remote" like in an application service (NWDS 7.0.07 and NW04s SP8).
    So I have to map the findBy operations to an application service and create a web service from it!?
    Regards
    Joschi

  • Multiple VI's using different digital lines in one VI.

    I have created multiple vi's, each of which require either reading or wroting to a different digital line on the CB-68LP board. I need to put them all in one individual vi so that I can see everything on the front panel. When I have tried this the vi seems to send a confused signal and operate things which it shouldn't.
    Is it even possible to try and do what I am doing? If not, any ideas what I can do? Thanks.

    Multiple VIs are usually the better approach. What I would suggest is parallel loops. These are loops which do not have any data dependency on each other. One handles the User Interface - the front panel where you "see everything." Another which reads and writes from/to the digital lines. Maybe even a third which processes the data. Exchange data among the loops with queues or functional globals.
    Keep a record of the state of all the digital lines. When something is to be written to certain lines, use either a Write Line.VI ( I don't recall the exact name) or use AND and OR functions with masks to protect the states of line you do not want to change.
    BTW, the CB-68LP is merely a connection interface, not the digital I/O baord itself.
    Lynn

  • How to bring data from 3 different internal table to one

    hii all,
              i have 3 internal table ls_mat,which has around 20 fields,it_stpo,which has 3 fields,and it_mast,i need to bring all these 3 table data in one tabel...how do i do...plzz help...

    Hi ,
    Does this internal table have any fields in common in all the three.
    If yes , then loop ls_mat
    Declare a type will all the fields and create a structure and internal table with that type (for ex lx_final and lt_final respectively)
    Loop at ls_mat into lx_mat.
    1.copy all the fields of lx_mat to respective lx_final.
    2.read table it_stpo into lx_stpo with key field = lx_mat-field.
    3.Copy all fields of lx_stpo to respective lx_final.
    4. read table it_mast into lx_mast with key field = lx_mat-field.
    5. copy all fields of lx_mast to respective lx_final.
    6. now append lx_final to lt_final.
    Endloop.
    now you can get all values inside lt_final.
    Regards,
    sivaganesh

  • HT204074 So your telling me that me and my brother (using different apple IDs on one computer) have to alternate every 90 days on backing up our purchases from an Iphone.

    Trying to transfer the purchases from my iPhone to iTunes but my brother just did the same last week so it's saying i have to wait 84 days to back up purchases. Any ways around this? After using apple products for 10+ years, if i have to deal with this I won't be buying an iPhone 5 in a few months. because in the end the only think keeping me with the 4S was the fact that i already had a large music library but at this point my recent purchases a fairly useless for the next 3 months

    Correct.  You can only redownlaod previous purchases from one account every 90 days.
    You can still transfer them from your iphone ipod.  File>Transfer Purchases

Maybe you are looking for