This page was last edited on January 10, 2020, at 20:48.
Comments or questions about this documentation? Contact us for support!
In the Column List:
Modified: 8.5.003 (in Oracle, fields with VARCHAR data types use explicit CHAR character-length semantics)
In partitioned databases, this table is not partitioned.
Allows facts to be described based on attributes of an outbound campaign contact information type. Each row describes one contact information type, such as Home Phone.
Column | Data Type | P | M | F | DV |
---|---|---|---|---|---|
CONTACT_INFO_TYPE_KEY | int | X | X | ||
CONTACT_INFO_TYPE | varchar(32)/nvarchar(32) | ||||
CONTACT_INFO_TYPE_CODE | varchar(32)/nvarchar(32) | ||||
CREATE_AUDIT_KEY | numeric(19) | X | X | ||
UPDATE_AUDIT_KEY | numeric(19) | X | X |
The surrogate key that is used to join the Contact Info Type dimension table to the fact tables.
The name of the contact information type. This field is set to one of the following values:
This value can change with localization.
The code for the contact information type. This field is set to one of the following values:
This value does not change with localization.
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.
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.
No indexes are defined.