Data Modeler: FK attribute name synchronization

I have this option enabled by default .
How can i disable this on per table basis?
thank you
Andrew

I don't understand, sorry.
"FK attribute name synchronization" is an option in the tools->general options->model -> logical . Once set it enforces the name of the PK column to be used as a name of the column in FK. this works as expected. The problem that i have is when i have self-reference relation ( employee_id -> manager_id ) - in this case the column name is the name of the PK column and number "1".
CREATE TABLE USER_STRATIFICATION_BIN
     user_stratification_bin_id NUMBER NOT NULL ,
     node_id VARCHAR2 (256) NOT NULL ,
     <skip>
     user_stratification_bin_id1 NUMBER ,
     user_stratification_display_id NUMBER NOT NULL
    ) LOGGING
ALTER TABLE USER_STRATIFICATION_BIN
    ADD CONSTRAINT USR_STRT_BIN_USR_STRT_BIN_FK FOREIGN KEY
     user_stratification_bin_id1
    REFERENCES RMBSWLOAN.USER_STRATIFICATION_BIN
     user_stratification_bin_id
    ON DELETE SET NULL
    NOT DEFERRABLE
;i need it to be smth else BUT "user_stratification_bin_id1".
Please advise.
Edited by: AndrewZ on Jan 26, 2010 9:17 AM

Similar Messages

Data Modeler foreign key names

Hi,
I've been using Data modeller for a while now and it works beautifully, anyhow there is an issue I would appreciate if anybody can help me in.
For foreign keys, if the master table primary key is names ID, the foriegn key will be ID also, and if already there is an ID column column in the detail table, it will be ID1, ID2 ....
Can I change the naming method to be like the oracle designer, or any convention I would like ??
Thanks
AK

I'm using the Logical Model V 1.5.1Paul,
it's pre-production release. Data Modeler is free now and you can download current published release - it.s version 2.0.0.584.
There is "Attributes" page in relationship dialog (version 2.0) and you can see attributes generated by that relationship.
For foreign keys in relational model - there is "Associated columns" page, you also can see referred key there.
Naming templates for FK columns and attributes can be defined in version 2.0.0.584.
Philip

Data Modeler - Source/Target Name

I have imported a logical model from Oracle Designer and need to show the "source/target" names. I could do this easily in version 2 of the Data Modeler through the Logical Model , "Show Source/Target Name" option of the Diagram pane (from Tools | General Options). The documentation for version 3 indicates that I should still be able to do the same thing (except Tools | Preferences), but I lack the "Show Source/Target Name" option in my version 3.0.0.665 of the Data Modeler. Is this a bug, or am I looking in the wrong place in this new version?

Hi,
Please see the Data Modeler Forum message option Show Source/Target Name “on” in the logic model for an answer to this question.
David

11g bi publisher data model generic columns names for obiee data source?

I'm just trying to figure out if this is a bug, expected behavior or installation problem. When I select an Oracle BI Analysis to add to the data model diagram the column names are not copied over. Instead they are all renamed as Column0-ColumnNN.
Thanks
Edited by: user13087422 on Apr 7, 2011 9:49 AM

I'm facing this same issue. Can you solve that? What's the problem with it?
Regards,
Ariel

Data Modeler EA1 - Changing name of subview in relational model

This doesn't appear to work, if I click apply or OK it simply drops the properties dialogue and name of subview stays the same.

it's fixed in EA2.
Philip

How to change "Relation UID" attribute name in logical model?

Beginner question here, sorry if it has been covered already.
In the Logical model in Data Modeler, how do I change an attribute name which is used as a "Relation UID"?
For example, I create two entities each with a Primary UID called "id", then create a 1:1 relationship. Each entity will now have an attribute called "id1" marked as a Relation UID, but I can find no way to change the attribute's name. Is there a way?
Thanks.

Hi GuyM,
you need to check setting in preferences - "Data Modeler>Model>logical" - FK attribute name synchronization - clear the check box if you want to set the name manually.
Philip

Sql Developer Data Modeler 3.0 EA1: Preference- Naming standard- Templates

I am trying to figure out how the naming standard templates work.
When I go to:
Preference -> Naming standard -> Templates
It says that 'Attribute Relation' is '{ref entity} {ref attribute}'
What is the consequence of this?
I thought, it would mean that when creating a primary key attribute (ID) on an entity (DEPARTMENT), the related "foreign key" attribute (that is automatically created in related detail entities, such as EMPLOYEES) would be named DEPARTMENT ID.
Instead it is just called ID. Is that the intended behavior?
- Marc de Oliveira
Edited by: marc66 on 2010-10-29 05:59

Marc,
you should check "FK Attribute name synchronization" setting in "Preferences>Data Modeler>Model>Logical model" - probably it's checked and you cannot change the name of FK attribute.
I found another bug here - FK attribute doesn't follow changes in referred entity - I logged it in bug database. As workaround you can apply defined templates at entity level (there is button in entity dialog) or for whole logical model (using pop-up menu in the browser).
Philip

Data Modeler: How to create a self reference in ER?

e.g. I create the entity EMP in a logical Subview. Two attributes are here essential for a self-reference: EMPNO and MGR. So each Employee has a reference to his boss. And this information is stored in MGR.
Now I create the entity EMP with the 8 columns from the SCOTT/TIGER schema. After that I define a 1:N-Relation between EMP and EMP. but it looks like I cannot define, which attributes are starting point of the relation and destination.
Who can help me here?
Gerd

Gerd,
you cannot select destination (as you said) attribute - they are automatically generated. However you can achieve what you want - it depends on your starting point:
1) start from logical model (analysis first)
- you create 1:n recursive relationship -
- change the name of created FK attribute to MGR or what ever you want - this is controlled by "FK Attribute name synchronization" setting at "General options>Model>Logical" page
2) start from relational model (reverse engineering of existing status)
- create self reference foreign key - select MGR as FK column;
- reverse engineer to logical model - you'll have FK attribute named MGR
Philip

Data Model on OTL-tables

Hi,
I need to know how the tables in OTL around table hxc_time_building_blocks is connected togehter. Does anybody have some information about this or can point me in the correct direction?
I have search Metalink, eTRM, OTN without any luck. I have the User Guide and a logical data model without table names.
Thanks...Daniel

Daniel,
Were you able to get what you wanted for timecards? Here is a query that I came up with. You may want to leverage it for your requirements.
select ppf.person_id, ppf.full_name, ppf.employee_number, fl.meaning state_working,a.segment1, a.task_number,
initcap(to_char(z.start_time,'DAY')) Weekday, z.start_time, z.tot_hrs
from (
select tbb_day.start_time,tbb_det.resource_id,trunc(hxc.stop_time) stop_time,
tbb_det.resource_type, tbb_det.measure tot_hrs, tbb_det.unit_of_measure uom
FROM hxc_time_building_blocks tbb_day,
hxc_time_building_blocks tbb_det,
hxc_timecard_summary hxc
WHERE tbb_det.scope = 'DETAIL'
and tbb_day.scope = 'DAY'
and tbb_det.date_to = hr_general.end_of_time
and tbb_det.parent_building_block_ovn = tbb_day.object_version_number
and tbb_det.parent_building_block_id = tbb_day.time_building_block_id
and tbb_day.parent_building_block_ovn = hxc.timecard_ovn
and tbb_day.parent_building_block_id = hxc.timecard_id
and tbb_day.start_time >= :p_date_from
and tbb_day.stop_time <= trunc(to_date(:p_date_to) + 1) - (1/24/60/60)
and tbb_det.resource_id = NVL(:p_person_id,tbb_det.resource_id)) z
,(select distinct pea.INCURRED_BY_PERSON_ID,ppf.full_name,ppa.project_id,ppa.segment1,pt.task_number,pei.expenditure_item_date,pei.quantity,
pea.EXPENDITURE_ENDING_DATE, pea.INITIAL_SUBMISSION_DATE
from pa_expenditures_all pea
, pa_expenditure_items_all pei
, pa_projects_all ppa
, pa_tasks pt
, per_all_people_f ppf
Where pea.expenditure_id = pei.expenditure_id
and pei.PROJECT_ID = ppa.project_id
and pei.TASK_ID = pt.task_id
and pea.INCURRED_BY_PERSON_ID = ppf.PERSON_ID
and ppf.person_id = :p_person_id) a
,per_people_f ppf
,per_addresses addr
,fnd_lookup_values fl
where ppf.person_id = z.resource_id
and ppf.person_id = addr.person_id
and ppf.person_id = a.incurred_by_person_id
and z.resource_id = a.incurred_by_person_id
and a.EXPENDITURE_ENDING_DATE = z.stop_time
and a.expenditure_item_date = z.start_time
and a.quantity = z.tot_hrs
and addr.primary_flag = 'Y'
and fl.lookup_code = addr.region_2
and fl.lookup_type = 'US_STATE'
and fl.enabled_flag = 'Y'
group by ppf.person_id, ppf.full_name, ppf.employee_number, addr.region_2, a.segment1, a.task_number,
z.start_time, fl.meaning, tot_hrs
order by z.start_time
Thanks
uds

New SQL Developer Data Modeler : name of attributes of foreign key

Hi,
with designer the name of column of foreign key was the " short name of entity/table master" + "_" + "the name of column attribute of the master table" .
Instead in the sql developer D.M. the system uses directly the name of the column/attribute of the master table and if the name exists in the slave table it uses a number to distinguish them .
So, if i have a table with short name gp and a primmary key id and a slave table with even a column id ,
with the D.M i'll have in the slave table a column named id2; in the designer instead the new column is gp_id .
Is possible to have the same behavior of designer even in the SQL Developer Data Modeler ?
Regards
Gianpaolo Giliberto

Hi Gianpaolo,
the columns of foreign keys are generated without the short name of master tablehow do you define that short name? Table and column have property "Abbreviation" - short name should be set there. You need also to set naming templates in "General Options>Naming Standard>Templates". Templates will be used when foreign key is created or you can apply them in Table dialog or for whole relational model using pop-up menu in the browser.
no foreign key index is generated on foreign key columns I assume, you want it for DDL generation only - this is controlled in "General Options>DDL"
Regards,
Philip

Invalid Name Pattern in SQL Developer Data Modeler

I am using Data Modeler version 3.3.0.747, I have exported a couple of data models (logical and physical) to an Oracle 11.2.0.3 database. I used the Reporting_Schema_Permissions.sql file to define the ID that owns the repository. Each data model that I exported returned the successful export message.
However when I use Oracle Data Modeler and connect (as a different user) to the repository to generate a report on one of the diagrams I immediately get an error returned. The error is (from the log file in datamodeler\log\datamodeler.log):
2013-04-19 08:36:12,233 [Thread-18] ERROR ReportsGenerationDialog - Generating report from Reporting Schema exception - invalid name pattern: username.OBJECTS_LIST
Where username is the name of the ID being used to generate the report (not the repository owner ID).
I have created public synonyms on the repository tables and views (though I must have missed where that was a requirement) so the repository objects can be seen by other users.
Has anyone encountered this and if so how did you resolve it. I have searched the web (and the Oracle forums) and so far had no hits on this issue. That seems to indicate that there is something I must have missed in the setup or such.
Thanks

Hi,
I think you didn't grant EXECUTE to package and types. Here is full working script:
DECLARE
CURSOR cur IS SELECT table_name, owner FROM all_tables WHERE owner='<owner>';
BEGIN
FOR rec IN cur LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON '||'<owner>'||'.'||rec.table_name||' to '||'<another_user>';
EXECUTE IMMEDIATE 'CREATE SYNONYM '||'<another_user>'||'.'||rec.table_name||' FOR '||'<owner>'||'.'||rec.table_name;
END LOOP;
END;
DECLARE
CURSOR cur IS SELECT view_name FROM all_views WHERE owner='<owner>';
BEGIN
FOR rec IN cur LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON '||'<owner>'||'.'||rec.view_name||' to '||'<another_user>';
EXECUTE IMMEDIATE 'CREATE SYNONYM '||'<another_user>'||'.'||rec.view_name||' FOR '||'<owner>'||'.'||rec.view_name;
END LOOP;
END;
DECLARE
CURSOR cur IS SELECT type_name FROM all_types WHERE owner='<owner>';
BEGIN
FOR rec IN cur LOOP
EXECUTE IMMEDIATE 'GRANT EXECUTE ON '||'<owner>'||'.'||rec.type_name||' to '||'<another_user>';
EXECUTE IMMEDIATE 'CREATE SYNONYM '||'<another_user>'||'.'||rec.type_name||' FOR '||'<owner>'||'.'||rec.type_name;
END LOOP;
END;
GRANT EXECUTE ON <owner>.pkg_osdm_utils to <another_user>;
CREATE SYNONYM <another_user>.pkg_osdm_utils FOR <owner>.pkg_osdm_utils;
There is no document for reporting repository install process. If you are exporting design for first time, the repository is automatically created for you.
When you get new version of DM you can
1. Use new repository
2. Upgrade existing one. If so, the simplest variant is to run /datamodeler/reports/DMRS_Upgrade_Script_<latest_vesrion>. Eventually compile single stored procedure.
Another variant for upgrade is with running osddm_upgr.sql, but there is some error, which is going to be fixed in the next release.

Data Modeler / Logical Model / How to display the "relationship name" ?

Hi,
Oracle SQL Developper Data Modeler 2.0.0 (build 584):
I would like to know if there is a way to display the "relationship name" in the diagram for the logical model in the GUI interface and/or to print it?
I checked in the different setup tool options and I did not find it...
Thanks for your help.
Regards,
Robin Ouellet

Hi Robin,
you cannot "show" relationship name on logical diagram - you can show "name on source" and "name on target" properties. You can set them at cardinality page of relationship dialog, And make them visible in "Tools>General options>Diagram>Logical model" settings - it's "Show Source/Target Name" option.
For printing - you can use "File>Print Diagram" to print in different format. Also "File>Print" allow diagram to be printed to printer, plotter or PDF printer if you have one installed.
Philip

Object Types Attributes (Data Modeler 3.0 EA1.)

Hi,
Will the attribute object type support in data modeler be upgraded to the same functionality as column relational table support in 3.0? For relational columns I can attach a domain to a column, I can't attach a domain to an attribute in an object type. Also for a column I can define a 'Units', that is VARCHAR2 (30 BYTE) orVARCHAR2 (30 CHAR). If can't do this with the (Data Modeler 3.0 EA1.) for an object type's attribute. Will this be included?
Thanks,
Scott

Sue,
Thanks to you and your team for extending this to the object type (structured type) portion of SDDM 3.3 EA1 and 3.3 EA2. The object type portion of SDDM is pretty robust now for modeling and actually generating useable structures in the database (Oracle) now. With 3.3 EA2 at this point it will be much easier to take advantage of the object type features in the database and our applications. I have been waiting since Oracle version 8 for the tools team to provide a modeling tool that mirrors the functionality the server team has provided when it comes object types.
Thanks for this in SDDM 3.3 EA1 and SDDM 3.3 EA2!
ScottK

Performance impacts of attributes versus entities in data model design

I'm trying to understand the performance implications of two possible data model designs.
Here's my entity structure:
global > the person > the account > the option
Typically at runtime I instantiate one person, one account, and five option 's.
There are various amounts determined by the person's age that need to be assigned to the correct option.
Here are my two designs:
Design one
attributes on the person entity:
the person's age
the person's option 1 amount
the person's option 2 amount
the person's option 3 amount
the person's option 4 amount
the person's option 5 amount
attributes on the option endity:
the option's amount
supporting rule table:
the option's amount =
the person's option 1 amount if the option is number 1
the person's option 2 amount if the option is number 2
the person's option 3 amount if the option is number 3
the person's option 4 amount if the option is number 4
the person's option 5 amount if the option is number 5
Design two
attributes on the person entity:
the person's age
attributes on the option entity:
the option's amount
the option's option 1 amount
the option's option 2 amount
the option's option 3 amount
the option's option 4 amount
the option's option 5 amount
supporting rule table:
the option's amount =
the option's option 1 amount if the option is number 1
the option's option 2 amount if the option is number 2
the option's option 3 amount if the option is number 3
the option's option 4 amount if the option is number 4
the option's option 5 amount if the option is number 5
Given the two designs, I can see what looks like an advantage for Design one in that at runtime you have less attributes (6 on the one pension member + 1 on each of 5 options =11) than Design two (1 on the one pension member + 6 on each of 5 options = 31), but I'm not sure. An advantage for Design two might be that the algorithm has to do less traversing of the entity structure: the supporting rule table finds everything for the option's amount on the option.
Either way there is a rule table to determine the amounts:
Design one
the person's option 1 amount =
2 if the person's age = 10
5 if the person's age = 11
7 if the person's age = 12, etc.
Design two
the option's option 1 amount =
2 if the person's age = 10
5 if the person's age = 11
7 if the person's age = 12, etc.
Here it looks like the rulebase would have to do more traversing of the entity structure for Design two.
Which design is going to have better performance with a large amount of rules, or would it make a difference at all?

Hi!
In our experience you only need to think about things like this if you were dealing with 100s or 1000s of instances (typically via ODS). As you have a very low number, the differences will be negligible, and you should (usually) go with the solution which is the most similar to the source material or the business user's understanding. I also assume this is an OWD project? Which can be even better, since the inferencing is done incrementally when new data is added to the rulebase, rather than in one "big bang" like ODS.
It looks like design 1 is the simplest to understand and explain. I'm just wondering why you need the option entity at all, since it seems like a to-one relationship? So the person can only have one option 1 amount, one option 2 amount etc, and there are only ever going to be (up to) 5 options...is that assumption correct? If so, you could just keep these as attributes on the person level without the need for instances. If there are other requirements for an option instance then of course, use them, but given the information here, the option entity doesnt seem to be needed. That would be the fastest of all :-)
Either way, as the number of instances is so low, you should have nothing to worry about in terms of performance.
Hope this helps! Write back if you have any more info / questions.
Cheers,
Ben

Needed SAP CRM Data model with Object, Entity and Attribute level details

Hello all,
We are working on a huge IS-U / CRM implementation and we are still in the data gathering phase. The client has a whole load of legacy systems that will be replaced with IS-U and CRM. Right now we are in the process of developing data models using Excel first and then presenting them to the client to go forward from there. For this we need to have all the business objects, entities and their attributes.
I know about the SD11 transaction, but we don't have a CRM system yet. My colleagues have access to a German ERP system and they were able to get models for HR, FI and Asset management. I tried for the Business partner / customer in there, but the models were not proper.
So, once again, I need the specific data models out of SD 11 for CRM business partner. If anybody has the information, please do pass it on to me as I need them urgently. It would be a great help if somebody can do so.
Regards
Rajesh

I suggest the following:
Please, check whether the system works if you activate the implementation BUPA_F4_AUGRP.
In addition check the notes 559662, 674869 and 782927. Maybe the notes are already implemented but you can try then the implementation of the BADI (SE19). It should resolve your issue.
I have implemented this Badi solution before, and after activation; the search help ; nor search result list did NOT show any Business partners anymore that had an authorization group I was not allowed to see.
kind regards
Davy Pelssers
SAP CRM/Security consultant

Data Modeler: FK attribute name synchronization

Similar Messages

Maybe you are looking for