SSAS 2008 snowflake - dimensions with one-to-many relationship (NOT fact table) and hierarchy?

Hi, below is my data model for SSAS 2008 on snowflake schema.
Below is SQL Server DW tables:
DimStudent - StudentID [primarykey], StudentName, DateOfBirth, AddressID
DimStudentAddresses - AddressID [primarykey], StudentID [foreignkey], ddressLine1, AddressLine2, AddressType
FactEnrolment - StudentID, EnrolWeek, EnrolFees
So here FactEnrolement.StudentID is joined to DimStudent.StudentID column,
and relationship between DimStudent & DimeStudentAddresses is one to many I.e. one student can have multiple addresses like primary or secondry address.
To design snowflake schema in SSAS 2008 BIDS project :
 [Question-1] how to join one-to-many dimensions (NOT fact table) Like DimStudent & DimAddresses?
 [Question-2] At the end I want to have a single dimension only I.e. Student which should have both DimStudent & DimStudentAddresses tables attributes init. So I can create hierarchy from these two table into a single dimension? How
to do this?
Please reply with feedback particular to my above scenario as I refereed other MSDN forums but nothing solid I found.
Any STEP-BY-STEP guideline please. Many thanks.

Hello KM,
Have you solved this issue after refer to Bill's suggestion? Please let us know how things go.
If you have any feedback on our support, please click
here.
Best Regards,
Elvis Long
TechNet Community Support

Similar Messages

  • Confused with one to many relationship

    Hi Masters ,
    Reading about one to many : i came across this
    Each row in Table A can have many (zero or more)
    matching rows in Table B but each row in Table B
    has only one matching row in Table A.
    A ZipCode can have many Students but each Student has only
    one ZipCode
    Theoritically this would be fine but can anyone please make tables for the above so i want to see it pratical work.

    zip
    (zipcode varchar2(6)
    , low_street_number varchar2(10)
    , high_street_number varchar2(10)
    , odd_even char(1)
    , city varchar2(30)
    , constraint zip_pk primary key (zipcode)
    student
    (studentno number(10)
    , firstname varchar2(30)
    , lastname varchar2(30)
    , zipcode varchar2(6)
    , constraint zip_fk foreign key(zipcode) references zip_pk
    Sybrand Bakker
    Senior Oracle DBA

  • About inserting with one to many relationship

    db and dev 10g rel2 ,
    hi all ,
    using emp and dept tables of scott/tiger schema .
    if i have a form , how can i insert 4 new employees in a specific dept ? what blocks should i build , and how can the user inserts into these blocks ?
    thanks in advance

    the user should write "20" in the deptno field once , and write the 4 new employees' data .To do this, you create a relationship between the blocks with the Dept block to be the Master and the Emp block to be the detail block. Your Form layout would look something like the following:
    |---------------------------------------|
    | [     ] Department Number             |
    |---------------------------------------|
    | Employee data...                      |
    | [    ] Emp ID                         |
    | [               ] First Name          |
    | ...rest of the columns listed here... |
    |---------------------------------------|Once you have created the relationship, Forms will handle the rest. Just run your form, select department 20 and start adding new employees.
    Craig...

  • Formatting Issue - datatables with one to many relationship

    Hi...
    I am a newbie and I have designed a report in CR2008 and my datasource for the report is an XSD file. There are 2 tables Table A and B.
    Table A is as follows:
    AID     Name     Reference     Period          Manager
    5       Name 1     Ref 1          July 2009     User Name 1
    8     Name 2     Ref 2          August 2009     User Name 2
    9     Name 3     Ref 3          March 2009     User Name 9
    45     Name 4     Ref 4          May 2008     User Name 4
    88     Name 5     Ref 5          June 2009     User Name 1
    There are other coloumns too in the datatable, but that shouldnt matter.
    Table B is as follows:
    ID     A_ID     DateKey     DateValue          Name
    1     5     Date1     2009-09-29 00:00:00.000     Start Date
    2     5     Date2     2009-08-11 00:00:00.000     Fieldwork Complete
    3     5     Date3     2009-08-14 00:00:00.000     Report Issued
    4     5     Date4     2009-07-17 00:00:00.000     Report Finalised
    5     5     Date5     2009-07-10 00:00:00.000     Close Date
    6     8     Date1     2009-08-11 00:00:00.000     Start Date
    7     8     Date4     2009-09-29 00:00:00.000     Report Finalised
    I want the report to be in the following format:
    ID     Name     Reference     Period     Manager     StartDate     Fieldwork          ReportIssue     Finalised      Closed
    I have written a formula to display the date value where the date key matches for A_ID.
    But when I run the report I get the result as follows:
    ID     Name     Reference     Period     Manager     StartDate     Fieldwork          ReportIssue     Finalised      Closed
    5     Name1     Ref1          July 2009     UName 1     29/09/2009                                   
                                            11/08/2009                                                                                          14/08/2009                                                                                          17/07/2009                                                                                     10/07/2009     

    Hi
    I tried what you suggested, but it hasnt worked.
    In your code, you have used the date ID,
    if {b.id} = 1 then
      formula = {b.datevalue}
    end if
    but the table contains dates from several A_IDs, and I want to get the dates for the respective A_ID, So shouldnt I be matching the A_ID's first? I also dont understand how the max function helps here?
    My report is already grouped by Table A, ID.
    My report should be a join of the two tables, a left outer join to be exact.
    Also, if my XML data contains only one record for Table A, dates still come out in a separate line. I dont quite understand where the problem is?
    Thank you...

  • One-to-many relationship: problem with several tables on the one side...

    Hello
    I'm having problems developing a database for a content management system. Apart from details, I've got one main table, that holds the tree structure of the content ("resources") and several other tables that contain data of a particular datatype ("documents", "images", etc.). Now, there's one-to-many relationship between "resources" table and all the datatype tables - that is, in the "resources" table there's "resource_id" column, being a foreign key referenced to the "id" columns in the datatype tables.
    The problem is that this design is deficient. I can't tell form the "resource_id" column from which datatype table to get the data. It seems to me that one-to-many relationship only works with two tables. If the data on the one side of the relationship is contained in several tables, problems arise.
    Anybody knows a solution? I would be obliged.
    Regards
    Havocado

    Hi;
    A simple way may be create a view on referenced tables:
    Connected to Oracle Database 10g Express Edition Release 10.2.0.1.0
    Connected as hr
    SQL>
    SQL> drop table resources;
    Table dropped
    SQL> create table resources(id number, name varchar2(12));
    Table created
    SQL> insert into resources values(1,'Doc....');
    1 row inserted
    SQL> insert into resources values(2,'Img....');
    1 row inserted
    SQL> drop table documents;
    Table dropped
    SQL> create table documents(id number, resource_id number,type varchar2(12));
    Table created
    SQL> insert into documents values(1,1,'txt');
    1 row inserted
    SQL> drop table images;
    Table dropped
    SQL> create table images(id number, resource_id number,path varchar2(24));
    Table created
    SQL> insert into images values(1,2,'/data01/images/img01.jpg');
    1 row inserted
    SQL> create or replace view vw_resource_ref as
      2    select id, resource_id, type, null as path from documents
      3      union
      4     select id, resource_id, null as type, path from images;
    View created
    SQL> select * from resources r inner join vw_resource_ref rv on r.id = rv.resource_id;
            ID NAME                 ID RESOURCE_ID TYPE         PATH
             1 Doc....               1           1 txt         
             2 Img....               1           2              /data01/images/img01.jpg
    SQL> Regards....

  • Newbie: one to many relationship SQL error

    Greetings all-
    This is probably a slam dunk for you JDO experts. I'm a JDO newbie, working
    with an existing schema in MySQL. I have a one to many relationship between
    two tables:
    Table "company":
    Fields:
    company_id: int(11) -- primary key
    name : varchar(64)
    division : varchar(64)
    Table "company_products"
    Fields:
    company_id: int(11) -- foreign key to table company
    product_name: varchar(64)
    product_description: varchar(64)
    So, I created the corresponding classes:
    public class Company {
    private int companyID;
    private String company_name;
    private String division;
    // Array of CompanyProduct
    private ArrayList companyProducts;
    // .. methods omitted
    public class CompanyProduct {
    private int companyID;
    private String productName;
    private String productDesc;
    // Methods omitted
    Then I created the "package.jdo" file:
    <?xml version="1.0"?>
    <jdo>
    <package name="com.packexpo.db">
    <class name="Company">
    <extension vendor-name="tt" key="table" value="company"/>
    <extension vendor-name="tt" key="pk-column" value="company_id"/>
    <extension vendor-name="tt" key="lock-column" value="none"/>
    <extension vendor-name="tt" key="class-column" value="none"/>
    <field name="companyID">
    <extension vendor-name="tt" key="data-column" value="company_id"/>
    </field>
    <field name="name">
    <extension vendor-name="tt" key="data-column" value="name"/>
    <extension vendor-name="tt" key="column-length" value="64"/>
    </field>
    <field name="division">
    <extension vendor-name="tt" key="data-column" value="division"/>
    <extension vendor-name="tt" key="column-length" value="64"/>
    </field>
    <field name="companyProducts">
    <collection element-type="com.packexpo.db.CompanyProduct"/>
    <extension vendor-name="tt" key="inverse" value="companyID"/>
    </field>
    </class>
    <class name="CompanyProduct">
    <extension vendor-name="tt" key="table" value="company_product"/>
    <extension vendor-name="tt" key="pk-column" value="company_id"/>
    <extension vendor-name="tt" key="lock-column" value="none"/>
    <extension vendor-name="tt" key="class-column" value="none"/>
    <field name="companyID">
    <extension vendor-name="tt" key="data-column" value="company_id"/>
    </field>
    <field name="productName">
    <extension vendor-name="tt" key="data-column" value="product_name"/>
    <extension vendor-name="tt" key="column-length" value="64"/>
    </field>
    <field name="productDesc">
    <extension vendor-name="tt" key="data-column"
    value="product_description"/>
    <extension vendor-name="tt" key="column-length" value="64"/>
    </field>
    </class>
    </package>
    </jdo>
    Enhancement works fine. I successfully query and retrive Company objects
    from the database, but as soon as I try to get the list of CompanyProducts,
    I get an SQL Error:
    javax.jdo.JDODataStoreException: [SQL=SELECT company.COMPANYPRODUCTSX FROM
    company WHERE company.company_id = 82061]
    E0610 Error in executeQuery()
    E0606 executeQuery() error --
    E0701 Error in getResult().
    E0708 Command results in error - 1054 Unknown column
    'company.COMPANYPRODUCTSX' in 'field list'
    NestedThrowables:
    com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper: [SQL=SELECT
    company.COMPANYPRODUCTSX FROM company WHERE company.company_id = 82061]
    E0610 Error in executeQuery()
    E0606 executeQuery() error --
    E0701 Error in getResult().
    E0708 Command results in error - 1054 Unknown column
    'company.COMPANYPRODUCTSX' in 'field list'
    I know i have probably set up the package.jdo file incorrectly, but I'm at a
    loss for what I did wrong.
    Any suggestions?
    Thanks!
    -Mike

    Hi,
    915766 wrote:
    I need to write sql for below requirement:
    table structure is
    serial no LPN
    1 4
    2 4
    3 6
    4 6
    5 6
    6 3
    7 3
    8 3
    9 1
    I have to pick distinct 'LPN' like below:That sounds like a job for "GROUP BY lpn".
    (any serial no can be picked for the distinct LPN)It looks like you're displaying the lowest serial_no for each lpn. That's easy to do, using the aggregate MIN function.
    results needs to be as below:
    serial no LPN
    1 4
    3 6
    6 3
    9 1
    Please suggest with sql.Here's one way:
    SELECT    MIN (serial_no)   AS serial_no
    ,         lpn
    FROM      table_x
    GROUP BY  lpn
    ORDER BY  lpn     -- if wanted
    I hope this answers your question.
    If not, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only), and also post the results you want from that data.
    Explain, using specific examples, how you get those results from that data.
    Always say which version of Oracle you're using (e.g., 11.2.0.2.0).
    See the forum FAQ {message:id=9360002}

  • One-to-many relationships problem

    Hi,
    I'm having some problems with one-to-many relationships.
    I've a two way relationship beetwen Person and Document.
    Person has a collection of Documents (1-n).
    Document has an instance for Person.
    In my database schema Document has a FK for person.
    The problem occurs when I'm trying to save the Person object
    with a collection of Documents.
    Oracle gives me the following message:
    ORA-00001: unique constraint (SMS.PK_PERSON) violated
    In my kodo.properties file I put:
    kodo.jdbc.ForeignKeyConstraints: true
    It seems that when the collection of Documents is persisted, kodo tries to
    save a new Person object for each Document.
    When I have just one instance of Document in my collection kodo persists
    it ok, but when I have move instances I get
    that problem.
    Can somebody help me?
    Thanks in advance,
    Joan Caffee

    You need to make sure each Document references the same Person object in
    the JVM. JDO persists your object model as-is. Each distinct JVM
    object becomes a distinct database record. You can't have multiple JVM
    objects in the same PersistenceManager representing the same database
    record.

  • Using data from one-to-many relationship

    Hi,
    i have an one-to-many relationship among two tables similar to the structure as in the below reference:-
    [One-to-many-reference|http://docs.oracle.com/cd/E23507_01/Platform.20073/RepositoryGuide/html/s1204repositoryexamplefonetomanymappi01.html]
    taking this as an example, i have the city's name with me. using this data in the addr_tbl in the 'address' item-descriptor, i need to get the value of the 'name' in the usr_tbl in the 'user' item descriptor. i will have the list of 'city' with me which i have to iterate and display the corresponding 'name'.
    will i be able to perform this in the jsp itself or does it have to be done in java? a sample code snippet or reference for doing this will be of much help.
    thank you.

    Thanks a lot, Sheik.
    if i have to do the reverse, ie for the 'name' in the usr_tbl of user item-descriptor i have to fetch the 'city' values in the addr_tbl, will it suffice if i do the following?
    <dsp:droplet name="/atg/dynamo/droplet/RQLQueryForEach">
    <dsp:param name="queryRQL" value="name=\"sirius\""/>
    <dsp:param name="repository"
    value="/com/MyRepository"/>
    <dsp:param name="itemDescriptor" value="user"/>
    <dsp:oparam name="output">
    <dsp:valueof param="element.address.city"/>
    </dsp:oparam>
    </dsp:droplet>

  • ONE-to-MANY relationship between tables and forms in APEX

    I recently started using APEX and I have run into an issue.
    I have a ONE-TO-MANY relationship between two tables, A1 and A2, respectively.
    A1:
    A1_ID
    Item
    A2:
    A2_ID
    SubItem
    A1_ID
    I have 2 forms (lets call it F1 and F2) that I use to capture data for A1 and A2.
    On F2, I have the following fields that are setup to capture data:
         A2.A1_ID
    **A1.Item (this is a drop down that is populated using a SELECT statement where the select uses A1.Item field)
         A2.SubItem (user would enter SubItem)
    Note: A2.A2_ID is populated using a SEQ
    Everytime I pick **A1.Item on F2, is there a way to link to A1 table and display A1.A1_ID for every **A1.Item selected on F2?
    If so, I want to store the value captured in F2 for the A1_ID field into A2 table to maintain my 1-to-MANY relationship.
    If this will work, how do I go about implementing this solution?
    Can someone help me?

    I think it sounds like you are asking for a Master-Detail form. Try that and see what you get.
    chris.

  • TopLink11 Tutorial problems with one-to-many relation

    Hi,
    I installed TopLink 11 and the related tutorial to work in a simple Eclipse project.
    Everthing works fine except for the storing of the one-to-many relation in the database.
    The tutorial works with employee, address and phone tables/classes. Plain Objects can be stored and one-to-one relations too. However when trying to store a one-to-many relation not the key of the related object (which is at that tome well known) but the object is tried to be entered
    in the Logfile I find:
    [TopLink Fine]: 2008.01.10 10:27:28.748--DatabaseSessionImpl(12916846)--Connection(9550256)--Thread(Thread[main,5,main])--INSERT INTO EMPLOYEE (EMP_ID, L_NAME, F_NAME, ADDR_ID, VERSION) VALUES (?, ?, ?, ?, ?)
         bind => [1501, Pascal, Blaise, 2252, 1]
    [TopLink Finer]: 2008.01.10 10:27:28.748--DatabaseSessionImpl(12916846)--Connection(9550256)--Thread(Thread[main,5,main])--commit transaction
    [TopLink Finer]: 2008.01.10 10:27:28.748--UnitOfWork(14858725)--Thread(Thread[main,5,main])--end unit of work commit
    [TopLink Finer]: 2008.01.10 10:27:28.748--UnitOfWork(14858725)--Thread(Thread[main,5,main])--release unit of work
    [TopLink Finer]: 2008.01.10 10:27:28.748--UnitOfWork(14858725)--Thread(Thread[main,5,main])--release unit of work
    [TopLink Finest]: 2008.01.10 10:27:28.748--UnitOfWork(18511661)--Thread(Thread[main,5,main])--Register the object Employee: Blaise Pascal
    [TopLink Finest]: 2008.01.10 10:27:28.748--UnitOfWork(18511661)--Thread(Thread[main,5,main])--Execute query DoesExistQuery()
    [TopLink Finer]: 2008.01.10 10:28:58.370--UnitOfWork(18511661)--Thread(Thread[main,5,main])--begin unit of work commit
    [TopLink Finer]: 2008.01.10 10:28:58.370--DatabaseSessionImpl(12916846)--Connection(9550256)--Thread(Thread[main,5,main])--begin transaction
    [TopLink Finest]: 2008.01.10 10:28:58.370--UnitOfWork(18511661)--Thread(Thread[main,5,main])--Execute query UpdateObjectQuery(Employee: Blaise Pascal)
    [TopLink Finest]: 2008.01.10 10:28:58.386--UnitOfWork(18511661)--Thread(Thread[main,5,main])--Execute query InsertObjectQuery(PhoneNumber[desk]: (603) 123-4567)
    [TopLink Fine]: 2008.01.10 10:28:58.386--DatabaseSessionImpl(12916846)--Connection(9550256)--Thread(Thread[main,5,main])--INSERT INTO PHONE (P_NUMBER, EMP_ID, AREA_CODE, TYPE) VALUES (?, ?, ?, ?)
         bind => [1234567, {Employee: Blaise Pascal}, 603, desk]
    [TopLink Warning]: 2008.01.10 10:28:58.511--UnitOfWork(18511661)--Thread(Thread[main,5,main])--Local Exception Stack:
    Exception [TOPLINK-4002] (Oracle TopLink - 11g Technology Preview 3 (11.1.1.0.0) (Build 071214)): oracle.toplink.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Ungültiger Spaltentyp Error Code: 17004
    the highlighted section should be 1501 (the key of the employee record)
    Any ideas how to fix this?
    Thanks Erika

    Erika,
    You need to specify the other side of the relationship (on the PhoneNumber side), which is done by putting a @ManyToOne annotation on the "employee" attribute in PhoneNumber. That will cause TopLink to know that it is a relationship and not a basic mapping.
    -Mike

  • With one package of Adobe Creative Suite 2 and the upgrade CS5 how many computers can use it?

    With one package of Adobe Creative Suite 2 and the upgrade CS5 how many computers can use it?

    You have 2 activations and no more.
    Mylenium

  • Struggling with a one to many relationship in a sub-report

    Post Author: Scott_tansley
    CA Forum: General
    I have a database schema as per below: tblENQUIRY                 tblDatasheets                  tblReportParasIRSID (PK)       1 --> &  IRSID (FK)                       UID (PK)Attribute1                     SHEETID (PK)     1 > &  SHEETID (FK)Attribute2                     Attribute1                         LIST_ORDER                         tblStandardParasAttribute3                     Attribute2                         PARA_CODE (FK)    & < 1   CODE     (PK)etc...                            Attribute3                                                                     TEXT                                   etc...
    The PROBLEM I am a Crystal Reports Newbie, and having to work through things bit by bitu2026  I've managed to achieve quite a lot, but I'm totally stuck with this and would appreciate some help. I need to create a report (essentially a letter and some datasheets) around a one-to-many relationship, which I have managed to compile using a main report (for the one &#91;tblENQUIRY&#93;) and sub report (for the many &#91;tblDatasheets&#93;).  Essentially I need a covering letter, then the u2018manyu2019 datasheets, and then a number of other pages (which are largely static text). I have created a main report which includes the covering letter, holds a subreport for the datasheets, and then contains the text for the additional pages.  This all works fine, and I get the correct number of datasheets for each main report. My problem stems from the use of this sub report.  This sub-report needs to hold some attribute values for each datasheet, which is fine.  However, on each datasheet page I need to have some paragraphs, which are held in another one to many relationship.  Each datasheet may have up to six paragraphs held as a code in tblReportParas, with a relationship to the text as held in tblStandardParas. My original thought would have been to embed another sub report, containing the values from tblStandardParas!TEXT, into the first sub report.  However, I have found that it is not possible to have a sub-report inside another sub-report.  I had seperated the first sub-report out from the main report, and then embedded another sub-report into it.  This worked fine until I tried to stitch the sub-report back into the main report (at which point the sub-sub-report dissapeared from view). I have therefore reworked my sub-report a little, and the attribution is now stored in a pageheader, with the tblStandardParas!TEXT in a detail section below it.  This almost works! The only problem is that there is no relationship between the pageheader and detail sections.  To clarify, I would expect to have one datasheet, with the attribution at the top, and then the six paras below.  Then, the same on the next page (assuming there is a second datasheet) for that report.  Instead, I get the correct attribution, but the detail section actually gives every paragraph in the database, no matter which datasheet/or report it related to!  I therefore need to limit the detail section to only show those paragraphs where the SHEETID in tblReportParas is the same as the tblDatasheets SHEETID. Any offers of advice would be appreciated.

    Post Author: Scott_tansley
    CA Forum: General
    I managed to resolve this myself in the end.  I moves the tblEnquiry data into report header/footer sections, this allowed me to add the tblDatasheets information into the details section, which gave me multiple pages - and then finally, the Paragraphs were added through the use of a sub report. 
    There's probably an even better way, but for now it works, it's quick - and so I'm going to go with it!
    Thanks for your interest.

  • DIMENSION WITH ONE LEVEL

    When I create a dimension with just one level when I refresh I have this error:
    SQL> EXECUTE DBMS_AWM.REFRESH_AWDIMENSION(USER, 'M62_EN_AW', 'AW_D_M62_DIM_E');
    BEGIN DBMS_AWM.REFRESH_AWDIMENSION(USER, 'M62_EN_AW', 'AW_D_M62_DIM_E'); END;
    ERROR en línea 1:
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "OLAPSYS.DBMS_AWM", line 1143
    ORA-06512: at line 1
    can anyone help me?

    Hi!thank you for all. I dont know if I understand correctly what you said but
    this is the xml template that generates de awm creating a dimension with one level. Can you do something?
    <?xml version = '1.0' encoding = 'UTF-8' ?>
    <!-- <!DOCTYPE XMI SYSTEM 'Model.dtd' > -->
    <AWXML version = '1.0' timestamp = 'Mon Feb 11 13:29:11 2002' >
    <AWXML.content>
    <Create Id="Action6">
    <ActiveObject >
    <AW Name="M62.M62_EN_AW" LongName="M62.M62_EN_AW" ShortName="M62.M62_EN_AW" PluralName="M62.M62_EN_AW" Id="M62.M62_EN_AW.AW" Schema="M62">
    <Dimension Name="ENTID" LongName="ENTID" ShortName="ENTID" PluralName="ENTID" Id="ENTID.DIMENSION" Schema="M62" isTime="false" isMeasure="false" UseNativeKey="false">
    <Attribute Name="LONG_DESCRIPTION" LongName="Descripción Larga" ShortName="Descripción Larga" PluralName="Descripciones Largas" Id="ENTID.LONG_DESCRIPTION.ATTRIBUTE" DataType="TEXT" Classification="MEMBER_LONG_DESCRIPTION" InstallAsRelation="false" IsDefaultOrder="false" IsMultiLingual="true"/>
    <Attribute Name="SHORT_DESCRIPTION" LongName="Descripción Breve" ShortName="Descripción Breve" PluralName="Descripciones Breves" Id="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" DataType="TEXT" Classification="MEMBER_SHORT_DESCRIPTION" InstallAsRelation="false" IsDefaultOrder="false" IsMultiLingual="true"/>
    <Hierarchy Name="J_ENT" LongName="J_ENT" ShortName="J_ENT" PluralName="J_ENT" Id="ENTID.J_ENT.HIERARCHY" isDefault="true" Type="LEVEL">
    <AttributeProjection Name="OBJ1780952198" LongName="" ShortName="OBJ1780952198" PluralName="OBJ1780952198" Id="ENTID.J_ENT.OBJ1780952198.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
    <Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    </AttributeProjection>
    <AttributeProjection Name="OBJ1780952199" LongName="" ShortName="OBJ1780952199" PluralName="OBJ1780952199" Id="ENTID.J_ENT.OBJ1780952199.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
    <Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    </AttributeProjection>
    <HierarchyLevelAssociation Name="NIV1" LongName="HLA1" ShortName="HLA1" PluralName="HLA1" Id="ENTID.J_ENT.NIV1.HIERARCHYLEVELASSOCIATION">
    <AttributeProjection Name="OBJ1780952201" LongName="" ShortName="OBJ1780952201" PluralName="OBJ1780952201" Id="ENTID.J_ENT.NIV1.OBJ1780952201.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
    <Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    </AttributeProjection>
    <AttributeProjection Name="OBJ1780952202" LongName="" ShortName="OBJ1780952202" PluralName="OBJ1780952202" Id="ENTID.J_ENT.NIV1.OBJ1780952202.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
    <Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    </AttributeProjection>
    <SourceMappingGroup >
    <DimensionMapGroup Name="MAPGROUP1" LongName="MAPGROUP1" ShortName="MAPGROUP1" PluralName="MAPGROUP1" Id="ENTID.J_ENT.NIV1.MAPGROUP1.DIMENSIONMAPGROUP" Type="HIERARCHYLEVEL">
    <DimensionKeySourceExpression Name="KeyMap" LongName="KeyMap" ShortName="KeyMap" PluralName="KeyMap" Id="ENTID.J_ENT.NIV1.MAPGROUP1.KEYMAP.DIMENSIONKEYSOURCEEXPRESSION">
    <SourceColumn Name="OBJ1780952205" LongName="" ShortName="OBJ1780952205" PluralName="OBJ1780952205" Id="ENTID.J_ENT.NIV1.MAPGROUP1.KEYMAP.OBJ1780952205.SOURCECOLUMN" Column="M62.ENTIDADES.ID_ENTIDAD"/>
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    </DimensionKeySourceExpression>
    <AttributeSourceExpression Name="AttrMap1" LongName="AttrMap1" ShortName="AttrMap1" PluralName="AttrMap1" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP1.ATTRIBUTESOURCEEXPRESSION">
    <SourceColumn Name="OBJ1780952207" LongName="" ShortName="OBJ1780952207" PluralName="OBJ1780952207" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP1.OBJ1780952207.SOURCECOLUMN" Column="M62.ENTIDADES.DES_ENTIDAD_CAS"/>
    <TargetObject XMLIDref="ENTID.J_ENT.NIV1.OBJ1780952201.ATTRIBUTEPROJECTION" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    <BaseAttribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
    </AttributeSourceExpression>
    <AttributeSourceExpression Name="AttrMap2" LongName="AttrMap2" ShortName="AttrMap2" PluralName="AttrMap2" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP2.ATTRIBUTESOURCEEXPRESSION">
    <SourceColumn Name="OBJ1780952209" LongName="" ShortName="OBJ1780952209" PluralName="OBJ1780952209" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP2.OBJ1780952209.SOURCECOLUMN" Column="M62.ENTIDADES.DEC_ENTIDAD_CAS"/>
    <TargetObject XMLIDref="ENTID.J_ENT.NIV1.OBJ1780952202.ATTRIBUTEPROJECTION" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    <Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    <BaseAttribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
    </AttributeSourceExpression>
    </DimensionMapGroup>
    </SourceMappingGroup>
    <level XMLIDref="ENTID.NIV1.LEVEL" />
    </HierarchyLevelAssociation>
    </Hierarchy>
    <MemberSelection >
    <Level Name="NIV1" LongName="NIV1" ShortName="NIV1" PluralName="NIV1" Id="ENTID.NIV1.LEVEL" isDimensioned="false">
    <AttributeProjection Name="OBJ1780952195" LongName="" ShortName="OBJ1780952195" PluralName="OBJ1780952195" Id="ENTID.NIV1.OBJ1780952195.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
    <Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    </AttributeProjection>
    <AttributeProjection Name="OBJ1780952196" LongName="" ShortName="OBJ1780952196" PluralName="OBJ1780952196" Id="ENTID.NIV1.OBJ1780952196.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
    <Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    </AttributeProjection>
    </Level>
    </MemberSelection>
    </Dimension>
    <Cube Name="CUBO_ENT" LongName="CUBO_ENT" ShortName="CUBO_ENT" PluralName="CUBO_ENT" Id="CUBO_ENT.CUBE" Schema="M62" UseGlobalIndex="false" SparseType="STANDARD" DefaultDataType="DECIMAL" AutoSolve="YES">
    <SourceMappingGroup >
    <CubeMapGroup Name="MAPGROUP1" LongName="MAPGROUP1" ShortName="MAPGROUP1" PluralName="MAPGROUP1" Id="CUBO_ENT.MAPGROUP1.CUBEMAPGROUP">
    <CubeDimensionSourceExpression Name="KeyMap1" LongName="KeyMap1" ShortName="KeyMap1" PluralName="KeyMap1" Id="CUBO_ENT.MAPGROUP1.KEYMAP1.CUBEDIMENSIONSOURCEEXPRESSION">
    <SourceColumn Name="OBJ1780952236" LongName="" ShortName="OBJ1780952236" PluralName="OBJ1780952236" Id="CUBO_ENT.MAPGROUP1.KEYMAP1.OBJ1780952236.SOURCECOLUMN" Column="M62.EMAITZA_E.ID_ENTIDAD"/>
    <TargetObject XMLIDref="ENTID.DIMENSION" />
    <Level XMLIDref="ENTID.NIV1.LEVEL" />
    </CubeDimensionSourceExpression>
    <MeasureSourceExpression Name="AttrMap1" LongName="AttrMap1" ShortName="AttrMap1" PluralName="AttrMap1" Id="CUBO_ENT.MAPGROUP1.ATTRMAP1.MEASURESOURCEEXPRESSION">
    <SourceColumn Name="OBJ1780952238" LongName="" ShortName="OBJ1780952238" PluralName="OBJ1780952238" Id="CUBO_ENT.MAPGROUP1.ATTRMAP1.OBJ1780952238.SOURCECOLUMN" Column="M62.EMAITZA_E.CANTIDAD"/>
    <TargetObject XMLIDref="CUBO_ENT.MED1.MEASURE" />
    </MeasureSourceExpression>
    </CubeMapGroup>
    </SourceMappingGroup>
    <SolveDefinition >
    <AggregationDefinition Name="OBJ1780952211" LongName="" ShortName="OBJ1780952211" PluralName="OBJ1780952211" Id="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" Schema="AW$DEFAULT" AggIndex="NA" CacheStore="SESSION" CacheNa="NA">
    <CalculationSpecification >
    <AggregationHierarchySpecification Name="Relation1" LongName="Relation1" ShortName="Relation1" PluralName="Relation1" Id="CUBO_ENT.OBJ1780952211.RELATION1.AGGREGATIONHIERARCHYSPECIFICATION" CalculationOrder="1">
    <AggregationOperator >
    <BaseOperator Name="Base Operator" LongName="Base Operator" ShortName="Base Operator" PluralName="Base Operator" Id="CUBO_ENT.OBJ1780952211.RELATION1.BASE OPERATOR.BASEOPERATOR" opcode="SUM"/>
    </AggregationOperator>
    <Dimension XMLIDref="ENTID.DIMENSION" />
    <PreComputeClause Name="OBJ1780952231" LongName="" ShortName="OBJ1780952231" PluralName="OBJ1780952231" Id="CUBO_ENT.OBJ1780952211.RELATION1.OBJ1780952231.PRECOMPUTECLAUSE">
    <DimensionMemberExpression Name="OBJ1780952232" LongName="" ShortName="OBJ1780952232" PluralName="OBJ1780952232" Id="CUBO_ENT.OBJ1780952211.RELATION1.OBJ1780952231.OBJ1780952232.DIMENSIONMEMBEREXPRESSION" ExpressionType="EXCLUDE" Expression="ALL"/>
    </PreComputeClause>
    </AggregationHierarchySpecification>
    </CalculationSpecification>
    <SolveDefDimRef Name="OBJ1780952226" LongName="" ShortName="OBJ1780952226" PluralName="OBJ1780952226" Id="CUBO_ENT.OBJ1780952211.OBJ1780952226.SOLVEDEFDIMREF" CalcMemberSolveOrder="0">
    <Dimension XMLIDref="ENTID.DIMENSION" />
    <SolveDefinition XMLIDref="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" />
    </SolveDefDimRef>
    </AggregationDefinition>
    </SolveDefinition>
    <DefaultAggregationDefinition XMLIDref="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" />
    <CubeDimRef Name="OBJ1780952225" LongName="" ShortName="OBJ1780952225" PluralName="OBJ1780952225" Id="CUBO_ENT.OBJ1780952225.CUBEDIMREF" Sparse="true">
    <Dimension XMLIDref="ENTID.DIMENSION" />
    </CubeDimRef>
    <Measure Name="MED1" LongName="MED1" ShortName="MED1" PluralName="MED1" Id="CUBO_ENT.MED1.MEASURE" DataType="DECIMAL" isInternal="false" UseGlobalIndex="false" ForceCalc="false" ForceOrder="false" SparseType="STANDARD" AutoSolve="AUTO_SOLVE"/>
    <PartitionHierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
    <PartitionLevel XMLIDref="ENTID.NIV1.LEVEL" />
    </Cube>
    <ExtendedProperty Name="OBJ1780952192" LongName="" ShortName="OBJ1780952192" PluralName="OBJ1780952192" Id="OBJ1780952192.EXTENDEDPROPERTY" Creator="SYSTEM" ExtensionName="GLOBALATTRIBUTE" ExtensionValue="" ReferencedObjectId="ENTID.LONG_DESCRIPTION.ATTRIBUTE"/>
    <ExtendedProperty Name="OBJ1780952193" LongName="" ShortName="OBJ1780952193" PluralName="OBJ1780952193" Id="OBJ1780952193.EXTENDEDPROPERTY" Creator="SYSTEM" ExtensionName="GLOBALATTRIBUTE" ExtensionValue="" ReferencedObjectId="ENTID.SHORT_DESCRIPTION.ATTRIBUTE"/>
    </AW>
    </ActiveObject>
    </Create>
    </AWXML.content>
    </AWXML>

  • Help with One to Many Formula

    Post Author: Don
    CA Forum: Formula
    Hello Everyone,
    I need some assistance.  I have a one to many relationship...
    Example...
    TABLE 1
    FieldName = RecordID
    DATA, RecordID= 10
    TABLE 2, linked one to many to RecordID in TABLE1
    FieldNames = RecordID, Name, ContactType
    DATA, RecordID= 10, Name= Tom, ContactType= Sales
    DATA, RecordID= 10, Name= Dan, ContactType= Service
    DATA, RecordID=10, Name= Jon, ContactType= Sales
    What I am looking for is to create a formula that would return something that looks like this....
    Sales Contact Name
    Tom, Jon
    So... I want to grab all the "Contact Types" of "Sales" from TABLE 2 then pass in the "Name" field from TABLE 2 and if there is more then one "Name" of the sames "Contact Type" then comma seperate it.
    And...  I don't want to do this in a sub report.   I do know I can make a sub report and return both values but to my knowledge the values would be on top of one another and not beside each other comma separated.
    Ideas?

    Post Author: Don
    CA Forum: Formula
    That may work using a subreport...
    I think the root of this my problem is the fact I have a table relationship, left outer... one to many join.  So even if I drop your suggested formula in my report I still get repeating record details with blank names where all the other contact types would be.
    Ticket Number       Contact Name     Contact Type
    111111                  Dan, Jim               Sales
    111111                                                                 <---- where the other contact type appear
    111111                                                                 <---- where the other contact type appear
    I was trying to avoid having to create several subreports for each data field I need on the report.  However, I think I can use your formula in a subreport to allow the data to display in a comma separated row rather then a vertical list.
    I thought about suppressing but that won't work because I have other contact types I need to list.
    Thank you for responding.

  • How to combine multiple fact tables and dimensions in one worksheet?

    Hello Forum,
    I am encountering a reporting problem when trying to create a worksheet that uses more than one cube/fact table and common dimensions. I have used Oracle Warehouse Builder 10Gr2 to design and deploy a pretty simple ROLAP data mart. We are using Discoverer Plus for OLAP as our reporting tool. We have 5 dimension tables using a star schema and 3 fact tables, when I create the worksheet I bring in our sales measure from our sales item table and then Store_Name from my Stores Dimension and then day from my time dimension, everything looks good at the stage, we're just trying to get a sum of all sales for that store on that day. Then I bring in a measure from our advertising cost table and a join window pops up asking which join to use, if I choose either the Store or the Time dimension I get correct data for the first fact table (sales) and grossly incorrect data for the ad cost measure from the second fact table (advertsing costs)...... any help would be appreciated

    You have encountered one of the key limitations of Discoverer... which I complained about to the Discoverer product manager at OpenWorld in 2001....
    Anyhow, to get around this, you are going to have to deal with it either in the database, (views, materialized views, tables), or within the admin tool by creating a custom folder.
    Discoverer also calls this the "fan trap", but never really had a solution to the problem. [The solution only worked is you joined to one and only one dimension!]
    What you want (using Sales_Fact and Inventory_Fact as an example) is to join Sales to Time, Store, and Product, and save that result. Then join Inventory to Time, Store, and Product, save that result, then do a double outer join between the two intermediate temporary tables in order to calculate something useful like inventory turns by store and product line.
    This is also known a "multipass SQL", and is supported by some (but not many) other tools.
    So, to accomplish this with Discoverer, you'll either need to create a view, or table, or materialized view that has already put Sales and Inventory into a single (virtual?) fact table. Alternatively you can write the SQL for how to do this linkage (don't forget to handle missing data), and use the Discoverer admin tool to create a custom folder that uses your SQL.
    Hope this helps!

Maybe you are looking for