Syntax | Description |
---|---|
[a-z][A-Z]_ | Alphanumerical characters (a to z ; A to Z and 0 to 9) and _ only |
All object names should be written in UpperCamelCase
eg. | Description |
---|---|
MaterialId | Id for Material |
SalesOrganization | Sales Organization |
Prefixes are written in upper case and followed by "_"
Object Type | Prefix | Description |
---|---|---|
Tables and Views | F_ | Fact tables or views |
Tables and Views | D_ | Dimension / referential tables or views |
Tables and Views | A_ | Anomalies or Rejects tables or views |
Tables and Views | L_ | Links tables or views |
Tables and Views | T_ | Transformation tables (YTD,12RM…) or views |
Tables and Views | S_ | Subscriptions tables or views |
Tables and Views | Z_ | Temp or work tables |
Tables and Views | P_ | Parameters tables or views |
Tables and Views | M_ | Metadata tables or views |
Tables and Views | N_ | Logging, Notifications, Traces tables or views |
for example : use Customer and not Customers
No number at the beginning of the name of the object. For exemple avoid 0_PRODUCT
For column naming, avoid to use reserved word For example avoid naming a column Date and prefer RefDate
When we are not replicating source system names, all objects must be named in English Invoice and not Facture This applies to names and comment sections of the code
Name size should be limited as much as possible but respect all the formatting rules.