Jump to: navigation, search

In the Column List:

  • P = Primary key
  • M = Mandatory field
  • F = Foreign key (where the term is used loosely to indicate a surrogate key reference to a field in another table, not a formal constraint)
  • DV = Default value
  • In the Data Type column, varchar/nvarchar means that the data type is varchar except in multi-language databases that use Unicode, in which case the data type is nvarchar. (The Info Mart database in Cloud deployments is not multi-language.) THIS BULLET DISPLAYS ONLY IN THE MSSQL AND CLOUD PDMs.
m (1 revision imported: Adding CX Contact (LDR) tables for Iteration 12)
(Added descriptions)
Line 5: Line 5:
 
{{PDMTable
 
{{PDMTable
 
|tableName = LDR_FACT
 
|tableName = LDR_FACT
|shortDesc = {{Editgrn_open}}Reserved for future use.{{Editgrn_close}}
+
|shortDesc = {{Editgrn_open}}TBD{{Editgrn_close}}
|tableDesc = {{Editgrn_open}}Reserved for future use.{{Editgrn_close}}
+
|tableDesc = {{Editgrn_open}}TBD{{Editgrn_close}}
 
|subjectAreas =  
 
|subjectAreas =  
 
|introduced = {{Editgrn_open}}8.5.012{{Editgrn_close}}
 
|introduced = {{Editgrn_open}}8.5.012{{Editgrn_close}}
Line 24: Line 24:
 
|foreignKey = yes
 
|foreignKey = yes
 
|default =
 
|default =
|colDesc =  
+
|colDesc = The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools--that is, applications that need to identify newly added data.
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 39: Line 39:
 
|foreignKey = yes
 
|foreignKey = yes
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}<font color="red">'''Writer's Question:''' Is this field populated if the LDR records are insert-only?</font>{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 54: Line 54:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}An identifier Genesys Info Mart generates based on the long UUID timestamp reported by CX Contact.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}id{{Editgrn_close}}
 
}}
 
}}
  
Line 69: Line 70:
 
|foreignKey = yes
 
|foreignKey = yes
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}Identifies the start of a 15-minute interval in which the event regarding the suppressed calling list records was generated by CX Contact Campaign Manager. The value is reported in ISO-8601 format. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}timestamp_iso8601{{Editgrn_close}}
 
}}
 
}}
  
Line 84: Line 86:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}The identifier of the record from the calling list.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}recordId{{Editgrn_close}}
 
}}
 
}}
  
Line 99: Line 102:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}The unique client identifier of the contact from the calling list.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}clientId{{Editgrn_close}}
 
}}
 
}}
  
Line 114: Line 118:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}The chain identifier of the record from the calling list.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}chainId{{Editgrn_close}}
 
}}
 
}}
  
Line 129: Line 134:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}The order of the calling list record within the chain.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}chainN{{Editgrn_close}}
 
}}
 
}}
  
Line 144: Line 150:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}TBD{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}contact_info{{Editgrn_close}}
 
}}
 
}}
  
Line 159: Line 166:
 
|foreignKey =  
 
|foreignKey =  
 
|default =
 
|default =
|colDesc =  
+
|colDesc = {{Editgrn_open}}TBD{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
 
|discontinued =  
 
|discontinued =  
 +
|xpath = {{Editgrn_open}}deviceMask{{Editgrn_close}}
 
}}
 
}}
  
Line 174: Line 182:
 
|foreignKey =  
 
|foreignKey =  
 
|default = -2
 
|default = -2
|colDesc =  
+
|colDesc = {{Editgrn_open}}The key that is used to join the LDR_CAMPAIGN dimension to the fact tables.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 189: Line 197:
 
|foreignKey =  
 
|foreignKey =  
 
|default = -2
 
|default = -2
|colDesc =  
+
|colDesc = {{Editgrn_open}}The key that is used to join the LDR_GROUP dimension to the fact tables.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 204: Line 212:
 
|foreignKey =  
 
|foreignKey =  
 
|default = -2
 
|default = -2
|colDesc =  
+
|colDesc = {{Editgrn_open}}The key that is used to join the LDR_LIST dimension to the fact tables.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 219: Line 227:
 
|foreignKey =  
 
|foreignKey =  
 
|default = -2
 
|default = -2
|colDesc =  
+
|colDesc = {{Editgrn_open}}The key that is used to join the LDR_RECORD dimension to the fact tables.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 234: Line 242:
 
|foreignKey =  
 
|foreignKey =  
 
|default = -2
 
|default = -2
|colDesc =  
+
|colDesc = {{Editgrn_open}}The key that is used to join the LDR_POSTAL_CODE dimension to the fact tables.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 249: Line 257:
 
|foreignKey =  
 
|foreignKey =  
 
|default = -2
 
|default = -2
|colDesc =  
+
|colDesc = {{Editgrn_open}}The key that is used to join the LDR_DEVICE dimension to the fact tables.{{Editgrn_close}}
 
|introduced =  
 
|introduced =  
 
|modified =  
 
|modified =  
Line 258: Line 266:
 
{{PDMIndexItem
 
{{PDMIndexItem
 
|indexName = I_LDR_FACT_SDT
 
|indexName = I_LDR_FACT_SDT
|indexDesc =
+
|indexDesc = {{Editgrn_open}}Improves access time, based on the Start Date Time key.{{Editgrn_close}}
 
|indexPresentInPartitioned = yes
 
|indexPresentInPartitioned = yes
 
|indexKey = START_DATE_TIME_KEY
 
|indexKey = START_DATE_TIME_KEY

Revision as of 03:30, February 9, 2019

Table LDR_FACT

Description

Introduced: 8.5.012

In partitioned databases, this table is partitioned.


TBD

Tip
To assist you in preparing supplementary documentation, click the following link to download a comma-separated text file containing information such as the data types and descriptions for all columns in this table: Download a CSV file.

Hint: For easiest viewing, open the downloaded CSV file in Excel and adjust settings for column widths, text wrapping, and so on as desired. Depending on your browser and other system settings, you might need to save the file to your desktop first.

Column List

Legend

Column Data Type P M F DV
CREATE_AUDIT_KEY Oracle: NUMBER(19)
MSSQL: numeric(19)
PostgreSQL: numeric(19)
X X
UPDATE_AUDIT_KEY Oracle: NUMBER(19)
MSSQL: numeric(19)
PostgreSQL: numeric(19)
X
ID Oracle: VARCHAR2(50 CHAR)
MSSQL: varchar(50)/nvarchar(50)
PostgreSQL: varchar(50)
X X
START_DATE_TIME_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X X X
RECORD_ID Oracle: NUMBER(19)
MSSQL: numeric(19)
PostgreSQL: numeric(19)
CLIENT_ID Oracle: VARCHAR2(64 CHAR)
MSSQL: nvarchar(64)
PostgreSQL: varchar(64)
CHAIN_ID Oracle: NUMBER(19)
MSSQL: numeric(19)
PostgreSQL: numeric(19)
CHAIN_NUMBER Oracle: NUMBER(19)
MSSQL: numeric(19)
PostgreSQL: numeric(19)
CONTACT_INFO Oracle: VARCHAR2(255 CHAR)
MSSQL: nvarchar(255)
PostgreSQL: varchar(255)
DEVICE_MASK Oracle: NUMBER(19)
MSSQL: numeric(19)
PostgreSQL: numeric(19)
LDR_CAMPAIGN_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X -2
LDR_GROUP_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X -2
LDR_LIST_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X -2
LDR_RECORD_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X -2
LDR_POSTAL_CODE_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X -2
LDR_DEVICE_KEY Oracle: NUMBER(10)
MSSQL: int
PostgreSQL: integer
X -2

CREATE_AUDIT_KEY

The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools--that is, applications that need to identify newly added data.

UPDATE_AUDIT_KEY

The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data.

ID

Based on application data attribute: id

An identifier Genesys Info Mart generates based on the long UUID timestamp reported by CX Contact.

START_DATE_TIME_KEY

Based on application data attribute: timestamp_iso8601

Identifies the start of a 15-minute interval in which the event regarding the suppressed contact list records was generated by CX Contact.

RECORD_ID

Based on application data attribute: recordId

The identifier of the record from the contact list.

CLIENT_ID

Based on application data attribute: clientId

The unique client identifier of the contact from the contact list.

CHAIN_ID

Based on application data attribute: chainId

The chain identifier of the record from the contact list.

CHAIN_NUMBER

Based on application data attribute: chainN

The order of the contact list record within the chain.

CONTACT_INFO

Based on application data attribute: contact_info

The contact information (device) for the contact from the contact list.

DEVICE_MASK

Based on application data attribute: deviceMask

The bit mask of the record from the contact list.

LDR_CAMPAIGN_KEY

The key that is used to join the LDR_CAMPAIGN dimension to the fact tables.

LDR_GROUP_KEY

The key that is used to join the LDR_GROUP dimension to the fact tables.

LDR_LIST_KEY

The key that is used to join the LDR_LIST dimension to the fact tables.

LDR_RECORD_KEY

The key that is used to join the LDR_RECORD dimension to the fact tables.

LDR_POSTAL_CODE_KEY

The key that is used to join the LDR_POSTAL_CODE dimension to the fact tables.

LDR_DEVICE_KEY

The key that is used to join the LDR_DEVICE dimension to the fact tables.

Index List

CODE U C Description
I_LDR_FACT_SDT Improves access time, based on the Start Date Time key.

Index I_LDR_FACT_SDT

Field Sort Comment
START_DATE_TIME_KEY Ascending

Subject Areas

No subject area information available.


References

The summary List of References will include the following entries for this table or view:


Child Table/View Child Table/View Column Parent Table/View Parent Table/View Column
LDR_FACT CREATE_AUDIT_KEY CTL_AUDIT_LOG AUDIT_KEY
LDR_FACT LDR_CAMPAIGN_KEY LDR_CAMPAIGN ID
LDR_FACT LDR_DEVICE_KEY LDR_DEVICE ID
LDR_FACT LDR_GROUP_KEY LDR_GROUP ID
LDR_FACT LDR_LIST_KEY LDR_LIST ID
LDR_FACT LDR_POSTAL_CODE_KEY LDR_POSTAL_CODE ID
LDR_FACT LDR_RECORD_KEY LDR_RECORD ID
LDR_FACT START_DATE_TIME_KEY DATE_TIME DATE_TIME_KEY
LDR_FACT UPDATE_AUDIT_KEY CTL_AUDIT_LOG AUDIT_KEY

 

Comments or questions about this documentation? Contact us for support!