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

Table RECORD_FIELD_GROUP_2

Description

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.


This table allows contact attempt facts to be described by deployment-specific field values of outbound campaign calling lists. Each row describes a distinct combination of calling list field values. A new row is issued for each distinct combination of calling list field values that are encountered in the contact attempt source data. Calling list field values must be of low cardinality, to prevent this dimension from becoming as large as the fact tables.

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
RECORD_FIELD_GROUP_2_KEY NUMBER(10) X X
TENANT_KEY NUMBER(10) X X
CREATE_AUDIT_KEY NUMBER(19) X X
RECORD_FIELD_2_STRING_1 Through RECORD_FIELD_2_STRING_10 VARCHAR2(255 CHAR)
PURGE_FLAG NUMBER(1)

RECORD_FIELD_GROUP_2_KEY

The primary key of this table and the surrogate key that is used to join this dimension table to the fact tables.

TENANT_KEY

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

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.

RECORD_FIELD_2_STRING_1 Through RECORD_FIELD_2_STRING_10

The text string value number one through ten, respectively, of a custom record field.

PURGE_FLAG

This field is reserved.

Index List

No indexes are defined.

Subject Areas

  • Contact_Attempt — Represents outbound campaign contact record attempts. An attempt may or may not include dialing.
This page was last edited on January 10, 2020, at 20:48.
Comments or questions about this documentation? Contact us for support!