Data Modeler - Naming Conventions

I was using Oracle Designer for several year.
This product could drive you crazy because sometimes, but the strength was in my opinion the datamodelling part.
It saved you a lot of time because you kept stuck to the logical model generated your relational model and had all scripts satisfying all naming conventions you needed.
In Data Modeler i really miss the naming conventions and can't understand some parts, sometimes somebody here can help me if i have overseen something or it is just not implemented.
Naming conventions as example:
We work with surrogate keys.
Two well known tables - Employees (abbreviation EMP), Departments (abbreviation DEP)
They have one relation 1:N one department has many employees
In Designer i would define the EMPLOYEE entity, would set the table-abbreviation, the attributes and the primary key.
The same with DEPARTMENT. I would design it WITHOUT any column for the foreign key constraint.
Then i would create a relation between this two tables.
Last step is to generate the relational model.
a) Designer automatically adds ID as surrogate key on every table (you could configure that, it was dependent on a domain)
b) it automatically adds the table abbreviation as prefix on every column (even here it's configurable)
c) it automatically adds the a foreign key column in the child table with the prefix of the master table (f.e. EMP_DEP_ID or DEP_ID if you prefer not to prefix every column... what i do)
It was really easy to get your scripts.
Things i don't understand in Data Modeler:
In a logical model you should design entities, attributes and relations and don't mess around with FK-columns.
Is there any support for surrogate keys? I don't wanna add an ID manually with every table.
In Data Modeler an additional COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automatically. The name can just be changed in the Relational View afterward.
P.S.
Surrogate Keys.... There are some pros and cons for/against this out there. I have seen a lot of Oracle Projects and in all except one i always had a surrogate key column. It really makes life
easier. In the one no-surrogate-key-project we began to add surrogate keys after a while...

COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automaticallyLook at "General options>Naming Standard>templates" - you can define template for FK columns/attributes and then apply them for whole relational/logical model using "Apply Naming .." functionality from pop-up menu in the browser. For Logical model (FK attributes) - you also need to clear related setting at "General options>Logical>Keep as the name of originating attribute".
Templates are also used when objects are created, thus when new FK is created, then templates are used to generate name for foreign key and FK columns. Well you have to define table and column abbreviation in order to get them used in generated names - Re: Data Modeler: Naming
There is no support for surrogate keys in current release.
Philip

Similar Messages

What is the WebCenter Content data prefix naming convention?

Hi all,
While working with RIDC I had some trouble understanding which data attributes relate to which concepts (folder, file, revision, document, ...). Some services I've been using return data from mulitple concepts, for example the DOC_INFO and FLD_INFO services return both file and document information. Sometimes I'm able to distinguish which data relates to which concept by the prefix used in the returned data element.
I made a small list of naming prefixes I encountered and where:
"d" => The majority... is there a clear definition when this prefix is used?
"dDoc" => Here and there, I assumed it is used when you clearly want to distinguish between a DOCument and a revision.
"dwf" => Document workflow data.
"dlink" => Document link data.
"f" => Framework Folders data.
"x" => DocMeta apart from "xClbraXXX" fields?
"ipm" => Imaging.
"dcollection" => Folders_g
"dclbra" => Collaboration project.
Am I heading in the right direction with these assumptions? Or is there a source on this subject (my search failed to turn up anything) ?
A second somewhat related question; I'm slowly getting a better grip on the domain model of WebCenter Content, has anyone ever produced a simplified ER-diagram of this? I think it could be a great help for newcomers. (I might give it a go if no-one has).
Regards,
Niels

d_ is a prefix for standard metadata x_ is a prefix for custom metadata
The best description of the data model is available in http://docs.oracle.com/cd/E10316_01/cs/cs_doc_10/documentation/admin/troubleshooting_10en.pdf , appendix A. (note: it's a 10g verstion!)

Data file naming convention!

Hi,
My question might be silly but I am not sure about the naming convention of my control/log/dbf file. I am oracle 11g and asm is configured with OMF enabled. When I checked the filename, I am getting filename with some numbers. What is that number refers to.
ASMCMD> ls
EXAMPLE.265.790927371
ONKAR.267.791219239
SYSAUX.257.790927221
SYSTEM.256.790927219
UNDOTBS1.258.790927221
USERS.259.790927223
ASMCMD> Could anyone please tell me what these numbers represents? I tried google but did not got any reasonable answers.
-Onkar

sybrand_b wrote:
I just searched the documentation on your behalf (as you know, the documentation is that what most people here refuse to read and avoid at all cost)
and came up with http://docs.oracle.com/cd/E11882_01/server.112/e25494/omf003.htm#ADMIN11492
by simply typing 'Oracle Managed Files' in the search bar.
I think ASM naming is different from OMF. The default OMF % formats are not used with the fully qualified name. its an ASM system generated dotted pair in the format
+diskgroup/dbname/filetype/filetypetag.file.incarnation
http://docs.oracle.com/cd/E11882_01/server.112/e18951/asmfiles.htm#i1010333
EDIT: cross post with previous poster. same info.
Edited by: deebee_eh on Aug 13, 2012 11:22 AM

Data Modeler: Naming

OK guys, I'm struggling.
I've watched the on-line tutorials, read the white papers (especially "Naming Standardization"), and looked through the help pages. There are so many options for controlling naming that I think I'm lost in the trees trying to find the forest. Between the name, short name, synonym, synonym to display, preferred abbreviation, naming rules, glossaries, naming standards, templates, object name prefixes, name abbreviations, name translations, design rules, and classification types, I'm a bit overwhelmed.
I'd like to take this logical model:
| facility category |
facility category identifier <PK>
     1:1
      |
      |
      |
     0:M
| facility |
facility identifier <PK>
facility category id <FK>and create the following relational model:
| t_fac_cat |
fac_cat_id <PK>
1:1
   |
   |
   |
0:M
| t_fac |
fac_id <PK>
fac_cat_id <NN,FK>which, in turn, generates this DDL:
create table t_fac (
     fac_id integer not null ,
     fac_cat_id integer not null ) ;
alter table t_fac add constraint pk_fac primary key ( fac_id ) ;
create table t_fac_cat ( fac_cat_id integer not null ) ;
alter table t_fac_cat add constraint pk_fac_cat primary key ( fac_cat_id ) ;
alter table t_fac
    add constraint fk_fac_cat_2_fac foreign key ( fac_cat_id )
    references t_fac_cat ( fac_cat_id ) ;Note: I could live with the relational model table names not being prefixed with a 't_' as long as the DDL includes it.
I think the tool has the ability to do what I want, but I'm missing how all the parts fit together to enable me to accomplish my goal.
Does anyone have a simple approach that might decrease the learning curve a bit?

Well,
I'll try to explain it in several posts.
I. Name abbreviations tool
this is something separate from big picture but can be useful in some cases.
1. Create a text file containing <name,abbreviation> pairs - name forum.csv and content:
facility,fac
category,cat
identifier,id
2. Set following template for PK name (it's in Naming standard>Templates):
pk_{table}
3. Set following template for FK column name:
{ref column}
4. Set following template for FK name:
fk_{parent abbr}_2_{child abbr}
2), 3) and 4) are according your example
5. Create tables (not entities) in relation model using full names, no abbreviations
following DDL is generated:
CREATE TABLE facility
facility_identifier INTEGER NOT NULL ,
facility_category_identifier INTEGER NOT NULL
ALTER TABLE facility
ADD CONSTRAINT pk_facility PRIMARY KEY ( facility_identifier ) ;
CREATE TABLE facility_category
facility_category_identifier INTEGER NOT NULL
ALTER TABLE facility_category
ADD CONSTRAINT pk_facility_category PRIMARY KEY ( facility_category_identifier ) ;
-- ERROR: FK name length exceeds maximum allowed length(30)
ALTER TABLE facility
ADD CONSTRAINT fk_facility_category_2_facility FOREIGN KEY
facility_category_identifier
REFERENCES facility_category
facility_category_identifier
6. Invoke "Name abbreviations" and select forum.csv file, leave the rest as it is, press ok - message appear with list of changed objects and here is the new status:
CREATE TABLE fac
fac_id INTEGER NOT NULL ,
fac_cat_id INTEGER NOT NULL
ALTER TABLE fac
ADD CONSTRAINT pk_fac PRIMARY KEY ( fac_id ) ;
CREATE TABLE fac_cat
fac_cat_id INTEGER NOT NULL
ALTER TABLE fac_cat
ADD CONSTRAINT pk_fac_cat PRIMARY KEY ( fac_cat_id ) ;
ALTER TABLE fac
ADD CONSTRAINT fk_fac_cat_2_fac FOREIGN KEY
fac_cat_id
REFERENCES fac_cat
fac_cat_id
7. Change abbreviations with related full name - it's possible to restore initial status if abbreviations in file (forum.csv in our example) are unique - they are in our case;
- repeat step 6) but now for "Direction" select "Abbreviation to name".
8. Well, if we want to have long names for table and columns (i.e. table "facility_category" and column "facility_category_identifier") we'll get into problem with names for objectors that use these names in their name template (see 'Naming standard>Templates"). We can use table abbreviation and column abbreviation in name templates however we have to define these abbreviations. This can be done manually using dialogs for each table/column or "Name abbreviations" toll can be used.
8.1 change template for primary key to *pk_{table abbr}* - (we already set template for FK as fk_{parent abbr}_2_{child abbr}
8.2 Invoke "Name abbreviations" and select forum.csv file, and select "Abbreviations" for "Scope"; press ok - report is shown for applied changes
9. We need to generate names according changed templates and defined abbreviations. This could be done at relation model level or at table level - at least this is the idea however bug was introduced in patch 1 (build 584) and "Apply naming standards for key and Constraints" at model level works only for foreign key columns. So, we have to apply naming templates at table level. And new DDL is:
CREATE TABLE facility
facility_identifier INTEGER NOT NULL ,
facility_category_identifier INTEGER NOT NULL
ALTER TABLE facility
ADD CONSTRAINT pk_fac PRIMARY KEY ( facility_identifier ) ;
CREATE TABLE facility_category
facility_category_identifier INTEGER NOT NULL
ALTER TABLE facility_category
ADD CONSTRAINT pk_fac_cat PRIMARY KEY ( facility_category_identifier ) ;
ALTER TABLE facility
ADD CONSTRAINT fk_fac_cat_2_fac FOREIGN KEY
facility_category_identifier
REFERENCES facility_category
facility_category_identifier
10. Logical model - at this point I will transform tables to entities in relational model in order to have starting point for next example. You can check that table abbreviation goes to "Short Name" for entity
Philip

Naming Standardization (SQL Data Modeler)??

Hi ,
Thanks in responding to my posting.
I am using SQL DM 3.0.0.665. I need your thoughs on following.
I find a Oracle white paper on Oracle SQL Developer Data Modeler
Naming Standardization (2009).
It suggests us to get to Tools > General Options menu. Expand Naming Standard.
I am not able to find it in my SQLDM. How do we get there?
Thanks in helping us out.

Hi,
For DM 3.0 it is Tools->Preferences->Data Modeler->Naming Standard

Enforcing use of class word as naming standard via data modeler preferences

Using data model preferences, I have set both the "attribute" and "column" naming standards to have mandatory name parts of both "prime word" and "class word". I have also used data model preferences to specify a glossary that has several terms of type "class word" defined.
My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a name part that is on the list of class words in the specified glossary. Is that assumption correct? If so, it doesn't seem to be working for me...
How does SDDM determine if a class word is missing? I.e., how can I enforce a naming standard that all attribute/column names must have a class word from our approved list of class words?
Thanks!

My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a >name part that is on the list of class words in the specified glossary. Is that assumption correct? yes it's correct.
If so, it doesn't seem to be working for me...one of the settings cannot be changed - it's "Abbreviated only" in "Preferences>Data Modeler>Naming Standard". So only abbreviated part from glossary is taken into account - I logged bug for that.
You can change it - it's in dl_settings.xml file in your design's directory - find - abbreviated_only="true".
How does SDDM determine if a class word is missingIt needs glossary and separator setting.
You can read more here http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
Also can look at examples here Data Modeler: Naming
Philip

Logical Model Naming Standard (Title Case) and Foward ENGINEERING how to???

Hi,
I just installed the datamodeler v3.3.0.747.
I want to use the Title Case style as separator style in my logic Model... To do this, i go to the Preferences Settings (Tools > Preferences > Naming Starndard > Logic Model) and set the Title Case as separator Style...
However, when i do foward engineering of the logical model... The Style is omitted and everything is like the logical model... For example,
If i create an entity called: ManagedAccount, i will expected that when i do fwd enginnering, the table associated to that entity will be call as Managed_Account; However, i still getting ManagedAccount...
So, What am i doing wrong??? or this is a bug???
Thanks!

Hi,
in order to get it working in current release you need to create glossary even empty one and set its property "Incomplete Modifiers" to true (check the check box with that name), and to to add that glossary in "Tools>Preferences>Data Modeler>Naming Standard".
We'll change it in next release to work without glossary for this particular case.
Philip

VC models...BeX naming conventions

Hello,
I have a problem in VC...with naming conventions.
The base Bex queries were not followed Naming Conventions and the VC models were completely designed based on the queries.
Now the management had decided to move the content only with naming conventions...from Bex we can do the query as Save As in a simple way. What about VC? Can we do it similar...i dont think so. Can someone help me with the best solution how to solve this issue.
what i did: I took the copy of VC model and added new datasource (Bex new query followed naming convention). Then i try to drag the input and output links to the new datasource i cant able to do that, is there a best way? my other question is if i change the links from old datasource to new datasource then all the fields and values for the rest of the model are blanked (not copied from the previous model). How to best solve this issue? Please advice...and consider this as high priority.
Note: If there is no solution to my question, how could SAP develop the tools with out thinking these constraints during the Product development. I feel like strange...please respond.
Thanks,
Pandu
Edited by: pandu on Jun 15, 2010 12:29 PM

Hi
I have a doubt regarding your requirement.
If you are creating new Bi queries, (with Save As) so what your are going to do with existing queries? If not, you can continue with same VC model, you just need to change model name as per convention.
Also for the second point you mentioned, VC is just for arranging the layout of the dashboard & the layout will remain same even if you delete exisitng queries & add new queries. Also the Data service (BI Query in this case) is a foundation of VC model & all other things like Input/ Output Form/Table are with reference to data service. So if you are deleting data service obviously all values will get reset. There are few constraints in VC but i dont think this is a constraint.
If possible, follow the naming convention in discripption of query for earlier queries which will not lead to duplication of efforts for earlier queries & Vc models. & You can start following naming convention for new queries.
Regards
Sandeep

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 - applying naming standards to relational model

Hi,
first of all thanks for the new data modeler build (584) - it really fixed some issues (e.g. unique keys with non mandatory referenced ids are now persistent) ...
BUT ... why is there an option to disable foreign key names when applying naming rule although it does not work?
I like my primary key names etc. to follow some naming rules, but I don't like foreign keys to follow rules, just because neither "Benutzer_Id3" follows the company internal naming rules nor is it very easy to understand at all.
Steps taken:
* logical model is complete
* generate relational model
* foreign key names are as intended (e.g. "User_Id_Modifier")
* right click the relational model
* click "Apply Naming Standards ..."
* remove the check mark from "Column Foreign Key"
* click "OK"
The foreign key column is changed regardless of checkbox state :-( - even deselecting all check boxes still applies naming rules to the foreign key columns.
Is there a fix/workaround for that or need I to go back to build 570?
Thanks god I still have my 570 compatible model ins SVN
regards stueckl

Hi,
unfortunately that functionality for all tables in relational model is broken - you still can use it at table level - "Naming rules" button in table dialog.
Philip

SAP Naming Conventions for DB Data Files

Hi Everyone!
We are about to install a SAP ECC 6.0 SR3 ABAP on Windows Server 2008 (R2) & SQL Server 2008 SP1 and we want to name the DB data files as follows:
<sid>DB_Data_001.MDF/NDF
Do you see any problem with this or think this could lead to a problem in the future?
We were unable to find a SAP note or SAP recommendation about this, we only found SAP Note 27428 but itu2019s for Oracle.
Thanks in advance!
Best Regards,
Nicolas

Hi Nicolas,
I thought about all corners where this could possibly lead to a problem (e.g. monitoring, DB13, ...) but couldn't think of a single report or transaction where this would cause problems.
To the database itself the names of the files do not matter at all and in the SAP transactions the datafiles are only read to display them in monitoring transactions like DB02 or RZ20. These transaction do not expect a certain naming convention so I don't see anything that would count against using different filenames.
Regards,
Beate Grötschnig

Meta Data Naming Conventions

Hi,
Can any one pls explain me on "Meta Data Naming Conventions".
Thanks in advance.

This is the approach you would use to create the labels for all your acocunts, custom members and entities, etc.. I would suggest using a convention that makes reporting and data loadinga s simple as possible.
Edited by: HFM_Peter on Dec 19, 2010 7:53 AM

Naming conventions for data types

In my functional specs I have been given field names
Client Number
Record Type
Customer Name and so on
I need to create custom data types for all these and assign them to std values (vbak-kunnr, adrc-name1)
I am trying to determine what is the best naming convention to use for my custom data types
Would the convention be to use, new_kunnr, new_adrc_name1 or perhaps just ClientNumber, RecordType, CustomerName and so on

I think its best I include my scenario so people can better answer my question
My report has four different parts, each has a filler, record type, customer number which need to be initialized to certain values that are different
The four parts are Name/Address, Credit Order, Sub total and Total
Name/Address has Record type = A , customer number = vbak-kunnr
Credit Order has Record type = R, customer number = vbak-kunnr
SubTotal has Record type= space and customer number = 99
Total has Record type = S and customer number = 9999
So I have to create variables for these and am trying to figure out a proper naming convention
I could do RecordType_Name, RecordType_CreditOrder and so on but that does not seem the best way to me. Any ideas!

Someone has nomenclature (naming conventions) for oracle data integrator?

Someone has nomenclature (naming conventions) for oracle data integrator?

You should really move this question over to the Oracle Data Integrator forum(Data Integrator for a more expedient response.

Data model in BW 7.0 (NW 2004s)

Hello friends.
The question is about the data model in BW 7.0 in comparison with BW 3.0, 3.1 and 3.5. Is is still the same? I mean, the database tables ofcubes and ODSes, are they still the same, with the same structure, naming convention and so on?
Thanks in advance,
Kooyot

hi,
The data models are same.
Some enhancements in Data warehousing is here. check it out.
http://help.sap.com/saphelp_nw2004s/helpdata/en/31/ec1342eb11de2ce10000000a1550b0/frameset.htm
if it is useful assign points
Regards,
Senthil Kumar.P

Data Modeler - Naming Conventions

Similar Messages

Maybe you are looking for