ODI Naming Standards

Hi All,
If anyone has a naming standards document....can you please forward it to [email protected]
when i searched ...i found a thread regarding this..my replies to that thread is not working.....so opened this new thread.
Regards

hi,
Refer
Naming standard for creating a interface
Thanks,
Saichand.v

Similar Messages

  • ODI Naming standards guide

    Hi ,
    Is anybody having ODI best practices/ Naming standards guide?...
    Thanks and Regards,
    Durga Reddy Katta.

    Refer
    http://www.oracle.com/technetwork/middleware/data-integrator/overview/odi-bestpractices-datawarehouse-whi-129686.pdf

  • Naming standard for creating a interface

    Hi,
    This question to be silly but i want to know
    Is there any naming standards to create any interface
    like in staging i defined WC_Dim_DS ( warehousecustom table_name dimension staging )
    how normally a ODI project naming conventions......?
    For interfaces/packages
    Any suggestions?
    thanks,
    saichand.v

    My Suggestion is
    I_<Target DB>_<Target Schema>_<Target Table>
    But if you are loading the table with 2 or more interfaces then you should add an explanation at the end. Explanation can be source system or purpose.
    I_<Target DB>_<Target Schema>_<Target Table>_<Explanation>
    And definitely schema and table name should contain some kind of metadata. For example divide staging table and final target tables into different schema such as STG and DWH.

  • How to set naming standards for SQL Developer

    I am using SQL Developer version 3.0.04.
    In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
    Any help in setting such preferences would be appreciated.

    Hi,
    If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
    Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
    expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
    You can then drag Tables from SQL Developer's Connections tree onto the diagram.
    Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
    (or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
    Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
    David

  • Problem with Applying Naming Standards to Keys and Constraints

    Hi
    I have an issue, and not sure where to go. I have 3 relational models in 1 design. I set up my foreign key template. I applied it to the first relational model, and it worked like a charm. When I bring up the "Apply Naming Standards" window for the second model and click on OK, nothing happens. The window just stays there and the OK button turns gray. I checked the log, but no messages are written. I just have to click on cancel to close the window. Has anyone got any suggestions on what to do? I even went back in and changed a table name to make sure that a foreign key name should change, and still nothing happens.

    Hi Joep,
    thanks for design. I logged bug for that problem - some FK columns keep information about non existent foreign keys.
    Here is a transformation script you can run for relational model:
    columns = model.getColumnSet().toArray();
    for (var t = 0; t<columns.length;t++){
    column = columns[t];
    nodes = column.getRefColAndAssocIDs().toArray();
    for (var i = 0;i<nodes.length;i++){
       node = nodes;
    if(node.fkAssocId!=null){
    fk = column.getDesign().getDesignObject(node.fkAssocId);
    if(fk==null){
    column.removeFKAssociation(node.fkAssocId);
    column.setDirty(true);
    And of course you have to save design - it's better to use "save as".
    Philip                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Naming Standards: What are you using?

    I'd like to hear what different organizations are using for naming standards to manage their XI environment.
    When you have a new interface or need to call up an existing interface, how do you know where to find them?  
    Do you break out your interfaces by Sender SC, XI SC and receiver SC?
    How do you organize namespaces?

    Hi Mark,
        Well, The name space itself it means that it used for unique identifier.Normally in realtime business cases lot  of process would be involved..when you are developing the interface and when you start up with namespace..The name space should give you the what exactly the scenario..for which type of scenarios..
      Let me take an example suppose if u are implementing the all sales order scenario you can probably implement a name space such that it should reflect the all sales order related objects.
      <b>Ex: http://xyzcompany.com./salesorders</b>
      The above namespace tell you that the vendor is xyzcompany and the corresponding objects of slaes orders.
    Hope I am clear.
    Thanks and Regards,
    Chandu.

  • Datamodeler - Naming Standards - technical white paper no longer available?

    Hi,
    I am wondering, is this document no longer available?
    http://www.oracle.com/technology/products/database/datamodeler/pdf/DataModelerNamingStandards.pdf
    I a m trying to learn how to apply Naming standards in data modeler but i cannot retrieve this document.
    On the datamodeler homepage, on tab "Documentation"
    clicking "Naming Standards (Technical White paper - pdf)"
    keeps me redirecting into the tab "Overview"
    regards,
    E.
    As I look at the content description of this document(i found that content description somewhere on the www), i believe i would find it very helpfull
    Contents of this Oracle SQL Developer Data Modeler Naming Standardization reference guide
    Introduction ............ 1
    Overview . 2
    Defining Templates for Keys, Indexes and Constraints....... 3
    Applying the Templates to the Relational Model ............. 5
    Prefix Management ........... 6
    Setting Name Patterns for Elements..... 7
    Defining Word Classification Types .. 8
    Supporting Naming Patterns with SQL Developer Data Modeler ... 8
    Reviewing Separator Settings for Elements in a Logical Model ..... 9
    Reviewing Additional Settings for Elements in a Relational Model . 9
    Using a Glossary .. 10
    Defining Glossaries ......... 10
    Using the Glossary Editor 10
    Importing Glossaries........ 12
    Importing a CA Erwin Data Modeler Naming Standard Glossary . 13
    Using Abbreviations............. 13
    Using the Name Abbreviations Utility............. 14
    Name Translation . 16
    Setting Model Level Name Restrictions ............. 18
    Using Design Rules Validation Related to Naming Standards ......... 19
    Conclusion ........... 20
    Resources ............ 20

    it's temporary problem and document will be available soon.
    Meanwhile you can look at this thread Data Modeler: Naming
    Philip

  • DataModeler v3.3.0 - Naming standards template for surrogate keys creation

    I'm using DM 3.3.0.734 and in the logical model we now can define in the entity properties to "Create Surrogate Key".
    When we use Engineer to relational model, for each entity is automatically created a new column using the naming template {entity}_ID as NUMERIC (without precision) and is defined as primary key.
    My questions are:
    Is possible to define a different naming standard for surrogate key creation?. We define id_{entiry}
    Is possible to set the precision of NUMERIC surrogate key?
    If we define entity's column as Primary UID, these columns are included in an unique constraint, but are using the naming standards for PK.
    As consequence are created the following:
    Unique constraint name: entity_PK
    Primary key(surrogate)name: entity_PKv1
    There is any way to define naming standards like "{entity}_UID" for unique constraints, or even, "{entity}_SK" for surrogate primary key name?
    Can anyone help with some of these topics?
    Regards,
    Ariel.

    Hi Ariel,
    Naming standards template for surrogate keys creation I logged enhancement request for that.
    How to change those bad names (going to change them one by one is not an option):
    1) If those "transformed" unique keys are the only ones you have in relational model then simply can apply naming standards
    2) You can write transformation script to do that for you
    3) you can use new functionality - search, export to excel file, change the names there (using find/replace will be faster) and return changed data back to relational model
    you can find description for that here:
    https://apex.oracle.com/pls/apex/f?p=44785:24:13179871410726::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:6621,16
    http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-search/
    http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-collaborative-design-via-excel/
    You should search for _PK, then filter result on Index and you can export result using report functionality (to XLS or XLSX output format). You can create template and include only table and name (of index) as properties to be included into report.
    Regards,
    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

  • How to set naming standards templates

    I'm currently working with oracle sddm 4.0.0.833 and i'd like to change settings for objects like identifiant : emp_pk instead of employee_pk.
    In Sue Harper's book sqldeveloper 2.1, there's a menu naming standard. I cannot find it in my version!
    jm

    Hi,
    First find the node in the Browser for your Design (it's the node above "Logical Model") and then display its Properties dialog.
    In its left-hand panel, expand the Settings node.  Then expand the Naming Standard node, and you can select the Templates node to display the Template options.
    David

  • 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

  • Naming Standard in a XI Scenarios

    hi expects,
        what are naming standards are used in ECC 6.0 in SAP XI.please help me.

    Hi,
    This shld help u
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90b213c2-d311-2a10-89bf-956dbb63aa7f
    Naming Conventions for XI Content Packages Used for Certification
    REgards
    Seshagiri

  • NAMING STANDARDS FOR WEB DYNPRO ABAP

    Hi All,
    Do we need to follow any naming standards in WebDynpro ABAP, could you please send some documents or any links for Naming Standards .
    Thanks,
    Raju.

    Hi Raju,
    This is a very good question which we cant answer as we are not working in your company.
    Well, the naming conventions standards vary based on different company Standards. So the best I could say is, check out your company Standards documents to get to understand the Naming Convention standards.
    Regards
    Raja Sekhar

  • Smartforms Naming Standards

    Hi All,
    Can you  please tell me what should be the Smartforms Naming standards? I need to create a doc for coding standards for Smartforms that will be used in my company. Just like the ABAP Coding standards and naming conventions. This is super urgent!!
    Your help will be highly appreciated.
    Thanks,
    AD
    Message was edited by: AD
            Anagha Deshpande

    Hi AD,
    You can try something like this.
    Layout Sets:
    Layout sets may have names up to 30 characters in length, using the format
    Zx(2-30)
    Example: ZNEWLAYOUT –New layout is the layout set name.
    If you copy a standard layout set, insert a ‘Z’ as the first character .If the standard layout set already has 30 characters replace the first character with ‘Z’.
    Styles:
    Style may have names up to 30 characters in length, using the format
    Zx(2-30).
    Example: ZSTYLE.
    If you copy a standard layout set, insert a ‘Z’ as the first character .If the standard layout set already has 30 characters replace the first character with ‘Z’.
    Standard Text ID’s:
    Standard text ID’s may have name up to 4 character’s in length using the format
    Znnn.
    Example: ZTXH.
    If you copy a standard layout set, insert a ‘Z’ as the first character .If the standard layout set already has 4 characters replace the first character with ‘Z’.
    Standard Text Names:
    Standard text names may have names up to 32 characters in length using the format Zx(2-32).
    Example: ZSTANDARDTEXT.
    If you copy a SAP standard text name, insert a ‘Z’ as the first character .If the SAP standard text name set already has 32 characters replace the first character with ‘Z’.
    Regards,
    Ferry Lianto

  • 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

Maybe you are looking for