ODI命名规则 - ODI Naming Conventions

下面是一个外企ODI项目中实际应用的命名规则。由于网上这方面公开资料不多，特此发布出来供大家开发Oracle Data Integrator项目时参考。欢迎有实际经验同行补充指正。

Topology  Objects	Naming Convention
Data Server  - BDMS	Format: DB_SOURCENAME Example: ORA_HR Note: Data Server name represents a database connection
Physical schema	Format: ORACLE SCHEMA NAME Example: DW_SALES
Work Schema (Staging Schema)	Format: ORACLE SCHEMA NAME Example: ODI_TMP
Work Tables Prefix	Error Table Format: E$_ Example: E$_SALES Note: E$_  prefix is ODI default value
Data Server  - FILE	Data Server Name Format: FILE_SOURCENAME Examples: FILE_COMPAGN
Physical Schema	Format: FILE_SOURCENAME.FILE DIRCTORY Example: FILE_COMPAGN.../../../demo/file Notes:  directory of both schema and work schema are same as each another
Agent Naming	Format: AGENTNAME_HOSTNAME_SEQUENCENUMBER Examples: ACCOUNTING_HR_01
Logical Schema	Format: <TECH_NAME>_<SCHEMA_NAME> Examples: ORA_SALES
Context	Format: <CONTEXT_NAME> Examples: DEVELOPMENT
Logical Agent	Format: <LOGICAL_NAME> Examples: SALES_HR                   SALES_SALES
Master Repository	Format: <MASTER_REPOSITORY_NAME> Examples: MASTER_REP
Work Repository	Format: <WORK_REPOSITORY_NAME> Examples: DEV_WORK_REP                   PROD_WORK_REP Note: each ID among all work repositories has to be unique
Project Name and Code	Project Name Format: <PROJ>_<PROJECT_NAME> Project Code: <PROJ>_<PROJECT_NAME> Examples: PROJ_HR                   PROJ_HR
Folder Name	Folder  Name Format:     <FUNCTION_ AREA>_<SUB_FUNCTION_AREA> Examples:  EDW_AM                    EDW_SHARED
Package Name	Package  Name Format:     <pkg>_<BUSINESS_AREA>  or     <pkg>_<TARGET_TABLE_NAME>_<TYPE> Examples:  pkg_AM                    pkg_DIM_CUST_DLY                    pkg_DIM_ACCT_WKL
Package Step	Package  Step Name Format: <stp>_<STEP_NAME> Examples:  stp_VAR_BATCH_ID                    stp_POP_DIM_PRODUCT                    stp_OdiSendEmail
Interface Name	Interface  Name Format:     <pop>_<TARGET_TABLE_NAME>_DEL     <pop>_<TARGET_TABLE_NAME>_UPD     <pop>_<TARGET_TABLE_NAME>_INS     <pop>_<TARGET_TABLE_NAME>_SCD     <pop>_<TARGET_TABLE_NAME>_FULL Examples:  pop_DIM_PRODUCT_UPD
Dataset Name
Procedure Name	Procedure  Name Format: <prc>_<PROCEDURE_NAME> Examples:  prc_Truncate_Table
Command Name	Step Name Format: <cmd>_<COMMAND_NAME> Examples: cmd_Truncate_Table
Variable Name	Variable  Name Format: <var>_<VARIABLE_NAME> Examples:  var_Batch_Id
Sequence Name	Sequencee  Name Format: <seq>_<TARGET_TABLE_NAME> Examples: seq_ DIM_PRODUCT
User Function Name	User Function  Name Format: <udf>_<FUNCTION_NAME> Examples:  udf_Julian_Conversion
Scenario Name	Step Name Format: <scn>_<CONPONEMT_NAME> Examples: scn_POP_DIM_PRODUCT                   scn_PKG_HR
Load Plan	Load Plan Name Format: <ldp>_<LOADPLAN_NAME> Examples: ldp_HR                   ldp_SALES
Knowledge Module	See ODI Developer’s Guide - 9.3.1 Knowledge Modules Naming Convention
Data Model Name DataStore Name	Same as  the name in the modeling and mapping document
Intermediate(temporary) Table Name	Intermedaite(temporary) Table Name Format:          <TMP>_<TABLE_NAME> Examples: TMP_DIM_PRODUCT Note:  intermediate tables are created and used to simplify data transformation or load if required. Those intermediate tables occur only in internal ETL.