Data Model: generation questions

Hello,
i'm using a latest and greatest version of the tool.
I seemed to have problems generating the relational from logical.
2 questions :
1.
emp/dept relation. in emp table i create a UK on deptno. Deptno is a FK from dept table.
that's fine in the logical diagram, but once i hit generate it produces 2 columns in the emp - deptno ( as a fk ) and deptno2 with UK on it.
I can't figure out why it's doing it and how to prevent it from doing this.
2.
when i create a view . BTW, if you can please! make the process of creation more... user friendly - i think it would be great.
Anyway, step by step:
create view in logical.
add 3 tables using the query builder.
add where clause using all 3 tables.
generate to relational.
go back to logical and remove on table. save changes to logical, try to generate to the relational.
My end result - no changes to the relational view....
Please advise.
Also would be great if you can point me to smth more than a "help" about all those convoluted options in the "generate" menu(s).
And thank you for this neat tool. The more i use it the better i like it.

Maggie,
> .. That's really unusual, so I would ask why this isn't a single entity
you are right - it's making little sense. I agree. The reason been - I have to extend an existing schema. And i can't modify objects.
Here is the real life scenario ( maybe you will have a better approach - i'm all for it ).
1. I have a table Servers( server_name varchar2 - PK, + bunch of other columns )
2. Yes, it's not a mistake PK is defined on the varchar server_name.
3. I can't alter the table in any way.
4. I'm creating a new entity - Book.
Book should have only one entry per server, and have other information about the server, applications installed on it, etc.
5. there is an entity that describes applications, per server, per environment. Where PK is defined server_name, application_name,environment_name.
6. I think to combine these 2 ( server and applications) into Book . I'll have other entities off the Book.
So in logical I have:
applications:book => N:M
applications:servers => N:1
servers:book => 1:1
speaking of which... hmm.. i can actually have another entity where i'll store the server_name and other information from Book. and i can create a view where i'll display servers' + book's info joining them on the server_name. I'll have to put "on update/insert/delete" trigger to handle the DML. Plus i'll have to have a UK on server_name in the new entity...
I think it's good solution to avoid 1:1 relation.
But it seems that 1:1 will be more streamline at this point - faster to implement, lesser locks, better scaling...
... Which is the parent entity and which is the child entity? With a 1-1, how do you tell?Agree.. no way to distinguish.
... Let me ask this, on examples where you have a standard 1-to-many relationship between two entities, do you get just the one standard foreign key column?If you imply - "does modeler generate one column in rel model ?" - then my answer is "yes". It generates one column wo problem.
Happy New Year.
Andrew

Similar Messages

  • BIP 11g: Data Model Editor question

    In BIP 11g, when you create a parent query q1 and link it to child query q2, is it possible to refer to column from q1 in the select list of q2? Oracle Reports allows this and I am trying to re-create this Oracle Report to a BIP report and this does not seem to work...i.e.
    q1: select a.col1 col1_q1, a.col2 col2_q1from table_a
    q2: select b.col1, b.col2, round(:col2_q1/b.col3) calc from table_b
    while creating q2, the calculation refers to :col2_q1 which is the 2nd column of the parent query q1, BIP asks confirmation to create a bind variable for col2_q1. These type of references are common in Oracle Reports.
    Is there any workaround for this?
    Thanks,
    Manish

    I think it's "11835845 - 11G SQL DATA SET CREATION ORA-01756 ERROR BECAUSE COLON IS READ AS BIND VARIABLE" bug
    You can use CHR(58) instead of a colon.
    Regards,
    Igor

  • Basic questions on data modeling

    Hi experts,
    I have some basic questions regarding data modeling within MDM. I understand the available table types and the concept of lookup fields. I know that the MDM data modeling concept is different to the relational concept. But having a strong database background my first step was to design a relational data model which I would like to transfer to a MDM repository. Unfortunately I didn't found good information material on this. So here are some questions maybe you can help me:
    1) Is it the right approach to model n:m relationships with multivalued lookup fields? E.g. main table Users with lookup field from subtable SapAccounts (a user can have accounts in different SAP systems, that means more than one account).
    2) Has a record always be unique in MDM repositories (e.g. should we use Auto ID's in every table or do we have to mark a combination of fields as unique)? Is a composite key of 2 or more fields represented with marking these fields as unique?
    3) The concept of relationships in MDM is only based on relationships between single records (not valid for all records in a table)? Is it necessary to define all relationships similar to the relational data model in MDM? Is there something similar to referential integrity in MDM?
    4) Is it possible to change the main table to a sub table later on if we realize that it has also to be used as a lookup table for another table (when extending the data model) or do we have to create a new repository from scratch?
    Thank you for your answers.
    Regards, bd

    Yes you are correct. It is almost difficult to map relational database to mdm one. But again MDM is not 'just' a database. It holds much more 'master' information as compared to any relational db.
    1) Is it the right approach to model n:m relationships with multivalued lookup fields? E.g. main table Users with lookup field from subtable SapAccounts (a user can have accounts in different SAP systems, that means more than one account).
    Yes Here you need to use MV look up tables or can also try Qualifier tables if it gets more complex
    2) Has a record always be unique in MDM repositories (e.g. should we use Auto ID's in every table or do we have to mark a combination of fields as unique)? Is a composite key of 2 or more fields represented with marking these fields as unique?
    Concept of uniqueness differs here that you also have something called Display Fields (DF). A combination of DF can also be treated as Unique one. For instance while importing records if you select these DF as a combination, you will eliminate any possible of duplicates based on this combination. Auto Id is one of the ways to have a unique id once record is within MDM. While you use UF or DF to eliminate any possible duplicates at import level
    3) The concept of relationships in MDM is only based on relationships between single records (not valid for all records in a table)? Is it necessary to define all relationships similar to the relational data model in MDM? Is there something similar to referential integrity in MDM?
    Hmm... good one. Referencial Integrity. What I assume you are talking is that if you have relationships between tables then removing a record will not be possible as it is a foreign key for some record. Here MDM does not allow that. As Relationships within MDM are physical and not conceptual. For instance material can have components. Now if material does not exist then any relationship to components is not worthwile to maintain. Hence relationshsip is eliminated.  While in relational model relationships are more conceptual. Hence with MDM usage of lookups and main table you do not need to maintain these kind of relationships on your own.
    4) Is it possible to change the main table to a sub table later on if we realize that it has also to be used as a lookup table for another table (when extending the data model) or do we have to create a new repository from scratch?
    No. It is not possible to convert main table. There is only one main table and it cannot be changed.
    I went for the same option but it did not work. What I suggest is to look up your legacy system one by one and see what fields in general can be classified as Master, Reference, Transactional - You will start getting answers immediately.

  • Questions on Subviews and Import/Export in Data Modeler v3 EA1.

    I have a few questions about the capabilities of Data Modeler v3 EA1:
    1) Is it possible to rename subviews? Would like more meaningful names then Relational_x - Subview_x.
    2) Is it possible to save documents at subview level?
    3) Is it possible to import/export subsets of data?
    4) Having problems importing Erwin 7 .xml file, is there known problems with this import?
    Judy

    Hi Judy,
    1) To rename a subview just right click on it in the browser tree and select "Properties". In the properties dialog change the name and click OK button.
    2) You can save a subview as new Data Modeler design - from the File menu select Export -> To Data Modeling Design. In the newly opened dialog select the subview you want to export and click OK button.
    3) After saving a subview as new design (see answer #2) it can be imported in some other design (File -> Import -> Data Modeler Design).
    4) What kind of problems do you have with import of Erwin 7.* xml file?
    Regards,
    Ivan

  • Generation of DDL similar to Oracle Designer (Data Modeler 3.0 EA1.)

    Hi,
    Will the production version of SQL Data Modeler allow the creation of separate DDL files similar to that which Oracle Designer does? For example, I can create a sequence number generator in Data Modeler (DM) and then make a call to that in an Object Type method. However the DDL file that is generated by DM has all DDL in one file. This would allow to take dependencies were taken into consideration, that is create the sequences before object types, packages and tables, then object type bodies, package bodies, etc...
    Thanks,
    ScottK

    At this stage we do not support multiple files. We do plan to do this in the future. However you can work around this by repeating the DDL generation for the different objects types you want to have files for.
    Remember that you can vote on the Exchange for your most desired features.
    Sue

  • Data Modeler: Relational data model questions

    1. Can a different notation be specified for relational data models' constraints? Specifically, I'd like crow's feet. BTW, the docs show crow's feet and parent pointer (with the arrowhead), but there's no such thing in the actual modeler.
    2. Is there any way to manually route FK constraints lines?
    3. When forward engineering from logical, is there any way to indicate the preferred name for keys and indexes (primary, unique, foreign)?
    4. Mandatory/optional indicator on tables: what exactly does 'N' or 'A' stand for? I can understand 'N' meaning "Not optional", but 'A'? Wouldn't it be simpler to use '*' and 'o' like in the logical?
    Man, do I ever miss Designer!
    Thanks,
    Patrick

    Here's one more question:
    I've transformed several super/sub entities to relational, and some of the tables do not allow me to open Properties (on the table). I can use the navigator to open column properties, but cannot open table properties (neither from diagrammer nor from navigator). Some of the tables are two or three subtype levels deep, and I haven't figured out why some open and some don't.

  • Questions on select statement in the data model

    Hi,
    In the select statement, the order by statement seems only to work at the lowest level of the select statement. Is this true?
    What is the the purpose of the group by statement in the select statement?
    As far as I understand, the grouping is catered for in the data model.....
    Regards,
    Kin

    From the oracle report docs:
    The order of column values in a default group is
    determined by the ORDER BY clause of the query for
    SQL queries and by the sort column for Express queries.
    For column values in user-created groups, however, you
    must use Break Order to specify how to order the break
    column's values.So order by in your sql query is affected by groups in your data model.
    The purpose of a group by statement in your select statement is to group values for aggregation purposes, like
    select department_id,
           min(salary),
           max (salary)
      from employees
    group
        by department_id
    order
        by department_id;Grouping in the data model of a report is a little different than a group by clause, but not entirely.

  • Questions on the R12 Bank Data Model

    Hi All,
    I am trying to learn the R12 bank data model and have a couple of quns and was wondering if any of you can help me understand the same.
    I understand banks and bank branches are stored as party in hz_parties and all the other hz_* tables. The IBY_EXT_BANK_ACCOUNTS table (similar to hz_locations which just stores any physical address) purely stores any external bank accounts and the IBY_EXTERNAL_PAYEES_ALL table links the bank accounts to the supplier or the supplier site or the supplier party/party site.
    I also understand that internal bank accounts are stored in CE* tables.
    So,
    (1) What is the difference between IBY_EXT_BANK_ACCOUNTS and IBY_ACCOUNT_OWNERS table.
    (2) What is the significance of the IBY_PMT_INSTR_USES_ALL table? When does it actually get populated?
    (3) If the IBY_EXTERNAL_PAYEES_ALL stores only the link of banks and supplier (or supplier party), then where are the customer bank account details stored, because I dont see a column by name customer_id/customer_site_id or anything like that.
    (4) One another important thing is - on the IBY_EXTERNAL_PAYEES_ALL table I dont see a supplier_id in this table, so does it mean that this table stores only supplier site level bank information? So there is no way, we can store the supplier level bank information?
    Some of the assumptions I am making based on the various documentation available outside, please let me know if my assumptions are even wrong and please clarify the same.
    Thanks.
    Edited by: Srinivasa Vasu on Sep 17, 2009 7:02 AM

    Hi All,
    I am trying to learn the R12 bank data model and have a couple of quns and was wondering if any of you can help me understand the same.
    I understand banks and bank branches are stored as party in hz_parties and all the other hz_* tables. The IBY_EXT_BANK_ACCOUNTS table (similar to hz_locations which just stores any physical address) purely stores any external bank accounts and the IBY_EXTERNAL_PAYEES_ALL table links the bank accounts to the supplier or the supplier site or the supplier party/party site.
    I also understand that internal bank accounts are stored in CE* tables.
    So,
    (1) What is the difference between IBY_EXT_BANK_ACCOUNTS and IBY_ACCOUNT_OWNERS table.
    (2) What is the significance of the IBY_PMT_INSTR_USES_ALL table? When does it actually get populated?
    (3) If the IBY_EXTERNAL_PAYEES_ALL stores only the link of banks and supplier (or supplier party), then where are the customer bank account details stored, because I dont see a column by name customer_id/customer_site_id or anything like that.
    (4) One another important thing is - on the IBY_EXTERNAL_PAYEES_ALL table I dont see a supplier_id in this table, so does it mean that this table stores only supplier site level bank information? So there is no way, we can store the supplier level bank information?
    Some of the assumptions I am making based on the various documentation available outside, please let me know if my assumptions are even wrong and please clarify the same.
    Thanks.
    Edited by: Srinivasa Vasu on Sep 17, 2009 7:02 AM

  • SQL Developer Data Modeler - Relation to Foreign Key Generation

    SQL Developer Data Modeler 2.0.0 Build 584.
    I am having trouble with Relations to Foreign Keys when Forward Engineering a Relational Model from a Logical Model.
    First of all, the Naming Standard is not applied to the Foreign Keys when I perform the Engineer to Relational Model.
    So I right click on the Relational Model from the Browser and Apply Naming Standards to Keys and Constraints.
    I uncheck everything but Foreign Keys.
    Now, Foreign Keys are named according to my Naming Standards.
    However, this process also performs renames on the Column Foreign Keys even though I specifically unchecked that option.
    This appears to be a BUG in the software and I haven't found a way around it.
    I tried using {column} instead of {ref column} in the Naming Standard Template for Column Foreign Key, but that simply resulted in renaming my columns to "{column}".
    Please confirm and/or let me know of any work-around for this.
    Thanks,
    Dan

    Hi Philip,
    Thanks for the reply.
    Is this recorded as a bug to be addressed in the future?
    Should I submit this problem via Oracle Support?
    The other work-around I came up with is to override every Relation name in the Logical Model with the name I want to use in the Relational Model.
    When the Relational Model is Engineered, this becomes my Foreign Key name.
    Of course, this is not how I want to do things, so I am hoping for a bug fix someday.
    Regards,
    Dan

  • ADF BC: Active data model question

    Hello,
    can somebody confirm that row iterator of detail view object obtained from master view using view link is different from row iterator used by active data model (getDetails() in application module) ?
    My problem is:
    I have a detail view object with multiple updateable entities. When I create a new row like this:
       Row row = masterViewRow.getDetails().createRow();
       masterViewRow.getDetails().insertRow(row);I don't see this row on web page probably because multi upd entities view object doesn't notify other iterators about changes by default.
    I have to use
       Row row = appModule.getDetails().createRow();
       appModule.getDetails().createRow(row);to make it work
    Can I omit use of application module and use master view object only to work with details in model and have changes visible in layout?

    Nobody can answer this.
    Where are all the ADF experts.
    Please help solve this issue.

  • SQL Query Data Model Question

    Hi All,
    I'm new to XMLPublisher so i'll try to explain the best i can the problem i'm having creating a Data Model for my report.
    I'm using Database XE and have installed XMLPublisher, as XE is extremely flexible in creating apps i'm having huge trouble finding a reporting solution for my applicaiton. I have created an app to track and control time and expense which i want to generate timesheet, expense sheets, invoice etc from.
    Having done some read i think XML is the best approach for me however i'm having huge troubles with my data model.
    EXAMPLE:
    I have 2 tables to start with, first table holds client information and the second table holds project information. One client can have many projects.
    When i create the Data Model using SQL i get the obvious problem that when a client has more then one project my XML structure is incorrect.
    SELECT gc.name AS CLIENT,
    gp.name AS PROJECT
    FROM gte_client gc,
    gte_project gp
    WHERE gc.client_id = gp.client_id(+)
    The above SQL creates the following XML
    - <ROWSET>
    - <ROW>
    <NAME>Symatrix Ltd</NAME>
    <NAME>Symatrix Pre-Sales</NAME>
    </ROW>
    - <ROW>
    <NAME>Aston Carter</NAME>
    <NAME>MOD</NAME>
    </ROW>
    - <ROW>
    <NAME>Symatrix Ltd</NAME>
    <NAME>Fujitsu</NAME>
    </ROW>
    </ROWSET>
    Obvious problem here is the fact that client Symatrix appears twice as there are 2 projects.
    I have tried to write SQL/XML and i think i'm beginning to understand the structure of the XML functions however XMLPublisher doesn't appear to understand the syntax when creating a SQL Query for the data model.
    I hope all this makes sense.
    Kind Regards
    Glen

    Hi All,
    Ok, so with a little searching through documents and articles on the web i found this information.
    http://blogs.oracle.com/xmlpublisher/2006/05/05#a38
    this details the exact thing i'm trying to achieve so anyone else who searches this forum with a similar problem check this out.
    Regards
    Glen

  • Questions related SQL Developer Data Modeling

    1) Is it possible to import ERwin 3.5.2 version(called as Platinum Erwin) erx file to SQl developer data
    modeling tool?
    2) When this tool going to be released as a standalone Product?
    3) One of our requirements is calculating Table and Database size from Data model tool(as a volumetric
    report). Is it possible in this tool?. Also i couldn't able to define storage properties(like Tablespace).

    I have also replied to you in the feedback application where you logged your query. I have added my response here for others who may be interested.
    1)We currently only support import from ERwin 4.x
    2) It is company policy not to disclose release dates. We plant to release in 2009.
    3) You can define Tablespace using the Physical model. Expand the Relational node and then the physical model. The two nodes you can use for your tablespaces are the Tablespaces and Segment Templates nodes.
    Regards
    Sue Harper

  • Data Model Question

    I am new with XML Publisher. What I'm still not getting is how to define a data model containing parent-child relationship (e.g. customers - orders - order_lines). Do I have to use some tools to create it?
    Denes Kubicek

    Hi.  In my opinion, option A is the most straight forward solution. 
    One thing to keep in mind is how the % figures will roll up, say over the entity hierarchy.  The % accounts will simply sum as you roll up the entity heirarchy, which is generally incorrect.  So, at a parent level you will need to back calculate the % figure.  I hope this makes sense.  I am pointing this out to you because I am in the process of building a similar solution and clean forgot about this.  I have had to re-engineer the solution slightly to correct this.
    Hope this helps.
    Sean

  • Canonical data model  Question?

    How can XI support a canonical data model ?  We don't want point-to-point mappings....We always want to map to and from a central message/data model which will be based on canonical data model.
    regards,
    tony

    you can support that with using a sequence of message mappings within an Interface mapping. with that you could canonicalize your message mappings, where you map from legacy to canonical model and from canonical to other legacy model. your interface mapping however would always be point to point, including a sequence of mappings to and from canonical model.
    best regards
    christine

  • Header/Item extractor data modelling question

    Hi,
    I have installed the Business Content for CRM Activities. In the Business Content they have a separate extractor and cube for header and item level.
    However, for our reporting requirements we would like to use one cube. We don't consider a multicube as a valid solution since the item/header cubes have ofcourse not all fields in common what will lead to the famous not-assigned behaviour in Bex.
    Therefore I'm trying to enrich each item line with all header fields. I don't want to write a user-exit to enhance the item extractor on datasource side since this will be a lot of work and also not sure this would be delta-compatible. I have bad experiences with this on a previous project.
    So I would like to find a solution on BW (data modelling) side but at the moment I don't see any good alternatives. The only thing that I can think of is to build one ODS/master data object (transaction number) that contains all header information and to read this ODS/Master data object while loading the item lines from the ODS to the cube. This way I can copy all header fields to the item line. But this will force me to do FULL loads between the item ODS and the "global" cube and ofcourse I would like to avoid this. (if a header fields changes I want this to be changed in all item lines as well ofcourse)
    Does anyone have better solutions ?
    Thanks

    What I finally did is the following :
    1) Create a new cube with all characteristics and keyfigures from header/item level.
    2) Load Header ODS to new cube
    3) Load Item ODS to new cube but via a startroutine that enriches the item datasources with all header characteristics that are not yet available on item level.
    4) Make a query and put constant selection on a restricted keyfigure that contains the following :
    a) Product (item level) ==> CONSTANT SELECTION enabled
    b) Nr. of activities (header level)
    In Bex everything looks now fine with the nr. of activities header keyfigure, even when I do a filtering on material that still only exists on item level thanks to the constant selection but my result row is acting a little bit dissapointing. I hope that can be solved.
    Let me give an example : (i'm even excluding the header line in this query)
    1) all fine
       Transaction nr ; Nr. Of activities
       6000           ; 1
       ====================================
    Resultrow           1
    2) drilldown to material
       Transaction nr ; Material ; Nr of activities
       6000           ; 12D      ; 1
       6000           ; 13D      ; 1
    =====================================================
    Resultrow                      2
    ==> As you can see the resultrow changes to 2 after doing the drill-down.
    Note that I am using "calculate result as summation". If I use "nothing defined" the result will be fine in this case but then it is not correct in the case where I do filterings on e.g. a material number. It will then show the number of activities for the WHOLE query.
    Is there anything I can do to get the resultrow right in all circumstances using constant selection ?
    Thanks
    Message was edited by: Double U

Maybe you are looking for