Basic Training Manual
Common Practice
Object Naming Conventions
Object Type | Rules | Example |
Project and Folder | Capital letter, Business Area Name or Application Name | ASWI_SW, COMMON, RDA, NSFR |
Package Name | PKG_<Application Name>_<Package Name> | PKG_NSFR_BOND_SECURITY_MASTERPKG_RDA_CASH_STOCK |
Variable Name (Project Scope) | Project variable. VAR_<Variable Name> | VAR_RDA_HIVE_USER, VAR_RDA_IT_EMAIL |
Variable Name (Global Scope) | Global variable should be used if the variable is shared across Project. For example, Hive URL, SMTP Server name and Port number.GVR_<Variable Name> | GVR_BEELINE_URL |
Package Component – odi_OSCommand | Cmd_<Command Name> , Recommendation : Cmd_<Action Word>_<Logical Name> | Cmd_Del_Files, Cmd_Extract_Result |
Scenario | Same as Package Name. Scenario version naming convention: 1000, 1001, 1002. <Major Version>+<Running Number> | PKG_RDA_BOND_REPO_REQUEST Version 1004 |
Model Folder, Model | Model is linked to specific technology. It is not necessary to add technology in the model name. | |
Sub Model | Sub-model names can be assigned freely, but consider using the same constraints for the submodel codes as for the model codes. | ORACLE_COPS_INVENTORY_DETAILS |
Data Source, Columns | Usually, the data source (table name) follows source system. The naming objective is to understand what data type and content is stored of the table.For example, RPT_RDA_EQUITY. It means the table is report table, RDA project and content is equity information. |
Depends on the reverse-engineering strategy selected. When creating your own datastores and columns within ODI, it is recommended that you enter object names and codes in upper case and avoid special characters such as spaces, commas, semi-colons etc. This is the recommend naming convention for the data source is created by ODI or project.Report Table: RPT_ Working Table : WRK_Historical Table: HST_Master Table: MSTLookup Table: MAP_ or LUP_Source Table: SRC_Temp Table: TMP_ (The table is used for checking the intermediate transformation result and NOT output to CSV)Checking Table: CHK_ (The table is used for checking the intermediate transformation result and output to CSV)DB View : VW_ | ACCOUNTS INVOICE INVOICE_DETAILS etc. | |
Primary Key | PK_< Name of the datastore > | PK_CUSTOMER |
Reference | FK___number May depend on the way foreign keys are defined in the database or application | FK_CUSTOMER_SALES_REP_001 |
Check Constraint | CK__ May depend on the way check constraints are defined in the database or application | CK_CUSTOMER_VALID_AGE |
Physical Topology: Data Server | Same as Oracle Database server name | |
Physical Topology: Physical Schema | Same as Oracle Schema | |
Reference:
Oracle Data Integration Blog https://blogs.oracle.com/dataintegration/
DEV EPM Blog
Tips & Tricks