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
Table LDR_LIST
Description
This dimension table allows CX Contact record facts to be described based on characteristics of contact lists. Each row describes one contact list.
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
| Column | Data Type | P | M | F | DV |
|---|---|---|---|---|---|
| ID | NUMBER(10) | X | X | ||
| CREATE_AUDIT_KEY | NUMBER(19) | X | X | ||
| LIST_NAME | VARCHAR2(255 CHAR) | X | unknown | ||
| LIST_ID | NUMBER(19) | X | -1 |
ID
The primary key of this table. This ID is referenced from other tables as LDR_LIST_KEY.
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.
LIST_NAME
The name of the contact list.
LIST_ID
DBID that Configuration Server assigned to the Calling List configuration object that represents the contact list.
Index List
| CODE | U | C | Description |
|---|---|---|---|
| I_LDR_LIST | X | Ensures that the combinations of values that are stored in the dimension table are unique. |
Index I_LDR_LIST
| Field | Sort | Comment |
|---|---|---|
| LIST_NAME | Ascending | |
| LIST_ID | Ascending |
Subject Areas
No subject area information available.
This page was last edited on January 10, 2020, at 20:48.
Comments or questions about this documentation? Contact us for support!