Tidied up tables with <br> tages

Author: RoelantVos

2000_Solution_Patterns/Solution Pattern - Data Modelling - Presentation Layer.md

@@ -65,18 +65,18 @@ For Type 2 dimensions a naming convention is used to differentiate the objects (
 
 | **View type**       | **Naming convention**                                        | **Mandatory attribute(s)**                                   | **Comment**                                                  |
 | ------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- | ------------------------------------------------------------ |
-| **Logic View**      | ben.<name>_VW                                                | <view name>_SK<br />OMD_INSERT_MODULE_INSTANCE_ID OMD\_INSERT_DATETIME    <br />OMD_INSERT_MODULE_INSTANCE_ID    <br />OMD_DELETED_RECORD_INDICATOR    OMD_UPDATE_MODULE_INSTANCE_ID OMD_CHECKSUM_TYPE_1    OMD_CHECKSUM_TYPE_2    OMD_EFFECTIVE_DATETIME    OMD_EXPIRY_DATETIME    OMD_CURRENT_RECORD_INDICATOR | Used to load a standard Dimension or Fact table supported by BIML.<br />The name of the view needs to match the name of the target table (except for the _VW suffix).<br /><br />The _VW suffix is required as there may be a table        with the original name in the ben schema.<br /><br />The checksums for Type 1 and Type 2 calculations will be handled by the BIML, and do not need to be present in the views. <br />This allows for a more automated update if required. All other OMD attributes required in the target table are handled by the BIML scripts. |
-| **Decoupling View** | pres.<name>   (for regular views)   pres.<name>_history   (for history or mixed-history views) | Underlying   ‘ben’ table or logic view, but without OMD attributes.   Surrogate   keys optional. | Business-facing,   e.g. DIM_CUSTOMER, or DIM_CUSTOMER_HISTORY. |
-
+| **Logic View**      | ben. "View Name" _VW | "View Name" _SK<br>OMD_INSERT_MODULE_INSTANCE_ID<br>OMD_INSERT_DATETIME<br>OMD_INSERT_MODULE_INSTANCE_ID<br>OMD_DELETED_RECORD_INDICATOR<br>OMD_UPDATE_MODULE_INSTANCE_ID<br>OMD_CHECKSUM_TYPE_1<br>OMD_CHECKSUM_TYPE_2<br>OMD_EFFECTIVE_DATETIME<br>OMD_EXPIRY_DATETIME<br>OMD_CURRENT_RECORD_INDICATOR | Used to load a standard Dimension or Fact table supported by BIML.<br />The name of the view needs to match the name of the target table (except for the _VW suffix).<br /><br />The _VW suffix is required as there may be a table        with the original name in the ben schema.<br /><br />The checksums for Type 1 and Type 2 calculations will be handled by the BIML, and do not need to be present in the views. <br />This allows for a more automated update if required. All other OMD attributes required in the target table are handled by the BIML scripts. |
+| **Decoupling View** | pres."View Name" (for regular views)<br>pres."View Name" _history (for history or mixed-history views) | Underlying ‘ben’ table or logic view, but without OMD attributes.<br>Surrogate keys optional. | Business-facing, e.g. DIM_CUSTOMER, or DIM_CUSTOMER_HISTORY. |
 
 
 The modelling conventions for the Presentation Layer **tables** are outlined in the table below. 
 
 | Table type     | Naming convention | Mandatory attribute(s)                                       | Comments                                                     |
 | -------------- | ----------------- | ------------------------------------------------------------ | :----------------------------------------------------------- |
-| **Dimension**  | ben.DIM_<name>    | <table_name>_SK OMD_INSERT_MODULE_INSTANCE_ID  OMD_DELETED_RECORD_INDICATOR    OMD_UPDATE_MODULE_INSTANCE_ID OMD_CHECKSUM_TYPE_1    OMD_CHECKSUM_TYPE_2    OMD_EFFECTIVE_DATETIME    OMD_EXPIRY_DATETIME    OMD_CURRENT_RECORD_INDICATOR | The first attribute (SK) is the primary key, and is a hash value (32 byte character).<br /><br />Optionally, a unique key / index is placed on the combination of level natural keys and the OMD_EFFECTIVE_DATETIME.<br />This represents a unique point in time record. See the consequences section for more details. Every attribute is specified as Type 0, Type 1, Type 2 (can be combined to type 3 or 6 - check the [relevant        pattern](file://aubriprfil06/display/BI/Design+Pattern+002+-+Generic+-+Types+of+History)). <br /><br />This is specified in the model / database as an extended property. |
-| **Fact Table** | ben.FACT_<name>   | <table_name>_SK<br /><Dimension Keys> OMD_INSERT_MODULE_INSTANCE_ID    OMD_INSERT_DATETIME    OMD_INSERT_MODULE_INSTANCE_ID    OMD_DELETED_RECORD_INDICATOR    OMD_UPDATE_MODULE_INSTANCE_ID OMD_CHECKSUM_TYPE_1    OMD_CHECKSUM_TYPE_2    OMD_EFFECTIVE_DATETIME    OMD_EXPIRY_DATETIME    OMD_CURRENT_RECORD_INDICATOR | The first attribute (SK) is the primary key. A unique key / index is placed on the combination of Dimension keys. |
-| **Other**      | ben.<name>        | <table name>_SK    OMD_INSERT_MODULE_INSTANCE_ID    OMD_INSERT_DATETIME    <br /><any OMD attributes required> | Not every delivery of information is necessarily in the form of a Star Schema /   Dimensional Model. <br /><br />If a dataset is better delivered in a different format (wide table, normalised) this is preferred. |
+| **Dimension**  | ben.DIM_"Table Name"    | <table_name>_SK<br>OMD_INSERT_MODULE_INSTANCE_ID<br>OMD_DELETED_RECORD_INDICATOR<br>OMD_UPDATE_MODULE_INSTANCE_ID OMD_CHECKSUM_TYPE_1<br>OMD_CHECKSUM_TYPE_2<br>OMD_EFFECTIVE_DATETIME<br>OMD_EXPIRY_DATETIME<br>OMD_CURRENT_RECORD_INDICATOR | The first attribute (SK) is the primary key, and is a hash value (32 byte character). Optionally, a unique key / index is placed on the combination of level natural keys and the OMD_EFFECTIVE_DATETIME. This represents a unique point in time record. See the consequences section for more details. Every attribute is specified as Type 0, Type 1, Type 2 (can be combined to type 3 or 6).<br>This is specified in the model / database as an extended property. |
+| **Fact Table** | ben.FACT_"Table Name"   | <table_name>_SK<br>"Dimension Keys" <br>OMD_INSERT_MODULE_INSTANCE_ID<br>OMD_INSERT_DATETIME<br>OMD_INSERT_MODULE_INSTANCE_ID<br>OMD_DELETED_RECORD_INDICATOR<br>OMD_UPDATE_MODULE_INSTANCE_ID<br>OMD_CHECKSUM_TYPE_1<br>OMD_CHECKSUM_TYPE_2<br>OMD_EFFECTIVE_DATETIME<br>OMD_EXPIRY_DATETIME<br>OMD_CURRENT_RECORD_INDICATOR | The first attribute (SK) is the primary key. A unique key / index is placed on the combination of Dimension keys. |
+| **Other** | ben."Table Name"| "Table Name" SK<br>OMD_INSERT_MODULE_INSTANCE_ID<br>OMD_INSERT_DATETIME<br>Any OMD attributes required | Not every delivery of information is necessarily in the form of a Star Schema /   Dimensional Model. If a dataset is better delivered in a different format (wide table, normalised) this is preferred. |
+