MDMDataDictionary

IBM InfoSphere Master Data Management Server Version 8.5.0

InfoSphere Master Data Management Server v8.5.0 Data Dictionary

Licensed Materials – Property of IBM

��

Note

Before using this information and the product it supports, read the general information under “Notices” on page 317.

Edition Notice

This edition applies to version 8.5.0 of IBM InfoSphere Master Data Management Server and to all subsequent

releases and modifications until otherwise indicated in new editions.

This document is licensed to you under the terms of the International Program License Agreement or other

applicable IBM agreement. You must ensure that anyone who uses this document complies with the terms of the

International Program License Agreement and any other applicable IBM agreement.

This document may only be used for your internal business purposes. This document may not be disclosed outside

your enterprise for any reason unless you obtain IBM’s prior written approval for such disclosure.

You may not use, copy, modify, or distribute this document except as provided in the International Program License

Agreement or other applicable IBM agreement.

© Copyright International Business Machines Corporation 1996, 2008.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.


Contents

Chapter 1. Entity report . . . . . . . . 1

Chapter 2. Tables . . . . . . . . . . 19

ACCESSDATEVAL Table . . . . . . . . . . 35

ADDACTIONTYPE Table . . . . . . . . . . 36

ADDRESS Table . . . . . . . . . . . . . 37

ADDRESSGROUP Table . . . . . . . . . . 40

AGREEMENTSPECVAL Table . . . . . . . . 41

ALERT Table . . . . . . . . . . . . . . 42

ANSWER Table . . . . . . . . . . . . . 43

ANSWERSET table . . . . . . . . . . . . 45

BANKACCOUNT Table . . . . . . . . . . 46

BILLINGSUMMARY Table . . . . . . . . . 47

CAMPAIGN Table . . . . . . . . . . . . 50

CAMPAIGNASSOCIAT Table . . . . . . . . 51

CATEGORY Table . . . . . . . . . . . . 52

CATEGORYNLS Table . . . . . . . . . . . 53

CATEQUIV Table . . . . . . . . . . . . 54

CATHIERARCHY Table . . . . . . . . . . 56

CATHIERARCHYNLS Table . . . . . . . . . 57

CATNODEREL Table . . . . . . . . . . . 58

CDACCETOCOMPTP Table . . . . . . . . . 59

CDACCOUNTREQUIREDTP Table . . . . . . 60

CDACCOUNTTP Table . . . . . . . . . . 61

CDACTIONADJREASTP Table . . . . . . . . 62

CDADDRUSAGETP Table . . . . . . . . . 63

CDADMINFLDNMTP Table . . . . . . . . . 64

CDADMINSYSTP Table . . . . . . . . . . 65

CDAGEVERDOCTP Table . . . . . . . . . 66

CDAGREEMENTSTTP Table . . . . . . . . 67

CDAGREEMENTTP Table . . . . . . . . . 68

CDALERTCAT Table . . . . . . . . . . . 69

CDALERTSEVTP Table . . . . . . . . . . 70

CDALERTTP Table . . . . . . . . . . . . 71

CDARRANGEMENTTP Table . . . . . . . . 72

CDAVAILABILITYTP Table . . . . . . . . . 73

CDBILLINGSTTP Table . . . . . . . . . . 74

CDBILLTP Table . . . . . . . . . . . . . 75

CDBUYSELLAGREETP Table . . . . . . . . 76

CDCAMPAIGNTP Table . . . . . . . . . . 77

CDCDCREJREASONTP Table . . . . . . . . 78

CDCDCSTTP Table . . . . . . . . . . . . 79

CDCHARGECARDTP Table . . . . . . . . . 80

CDCLAIMROLETP Table . . . . . . . . . . 81

CDCLAIMSTATUSTP Table . . . . . . . . . 82

CDCLAIMTP Table . . . . . . . . . . . . 83

CDCLIENTIMPTP Table . . . . . . . . . . 84

CDCLIENTPOTENTP Table . . . . . . . . . 85

CDCLIENTSTTP Table . . . . . . . . . . . 86

CDCOMPLCATTP Table . . . . . . . . . . 87

CDCOMPLDOCTP Table . . . . . . . . . . 88

CDCOMPLIANCETP Table . . . . . . . . . 89

CDCOMPLTARGETTP Table . . . . . . . . . 90

CDCONDITIONATTRIBUTETP Table . . . . . . 91

CDCONDITIONOWNERTP Table . . . . . . . 92

CDCONDITIONUSAGETP Table . . . . . . . 93

CDCONTMETHCAT Table . . . . . . . . . 94

CDCONTMETHTP Table . . . . . . . . . . 95

CDCONTRACTRELSTTP Table . . . . . . . . 96

CDCONTRACTRELTP Table . . . . . . . . . 97

CDCONTRACTROLETP Table . . . . . . . . 98

CDCONTRACTSTTP Table . . . . . . . . . 99

CDCONTRCOMPTP Table . . . . . . . . . 100

CDCOUNTRYTP Table . . . . . . . . . . 101

CDCURRENCYTP Table . . . . . . . . . . 102

CDDEMOGRAPHICSTP Table . . . . . . . . 103

CDDOMAINTP Table . . . . . . . . . . 104

CDDOMAINVALUETP Table . . . . . . . . 105

CDENDREASONTP Table . . . . . . . . . 106

CDENUMANSWERCATTP Table . . . . . . . 107

CDENUMANSWERTP Table . . . . . . . . 107

CDFREQMODETP Table . . . . . . . . . 108

CDGENERATIONTP Table . . . . . . . . . 109

CDGROUPINGCATTP Table . . . . . . . . 110

CDGROUPINGTP Table . . . . . . . . . . 111

CDHIERARCHYCATTP Table . . . . . . . . 112

CDHIERARCHYTP Table . . . . . . . . . 113

CDHIGHESTEDUTP Table . . . . . . . . . 114

CDHOLDINGTP Table . . . . . . . . . . 115

CDIDSTATUSTP Table . . . . . . . . . . 116

CDIDTP Table . . . . . . . . . . . . . 117

CDINACTREASONTP Table . . . . . . . . 118

CDINCOMESRCTP Table . . . . . . . . . 119

CDINDUSTRYTP Table . . . . . . . . . . 120

CDINTERACTIONCAT Table . . . . . . . . 121

CDINTERACTIONTP Table . . . . . . . . 122

CDINTERACTPTTP Table . . . . . . . . . 123

CDINTERACTRELTP Table . . . . . . . . . 124

CDINTERACTRESPTP Table . . . . . . . . 125

CDINTERACTSTTP Table . . . . . . . . . 126

CDLANGTP Table . . . . . . . . . . . . 127

CDLINKREASONTP Table . . . . . . . . . 128

CDLOBRELTP Table . . . . . . . . . . . 129

CDLOBTP Table . . . . . . . . . . . . 130

CDMARITALSTTP Table . . . . . . . . . 131

CDMATCHENGINETP Table . . . . . . . . 132

CDMATCHRELEVTP Table . . . . . . . . . 133

CDMETADATAINFOTP Table . . . . . . . . 134

CDMETADATAPACKAGETP Table . . . . . . 134

CDMETHODSTATUSTP Table . . . . . . . . 135

CDMISCVALUEATTRTP Table . . . . . . . 136

CDMISCVALUECAT Table . . . . . . . . . 137

CDMISCVALUETP Table . . . . . . . . . 138

CDNAMEUSAGETP Table . . . . . . . . . 139

CDNODEDESIGTP Table . . . . . . . . . 140

CDNODETP Table . . . . . . . . . . . . 141

CDORGNAMETP Table . . . . . . . . . . 142

CDORGTP Table . . . . . . . . . . . . 143

CDPAYMENTMETHODTP Table . . . . . . . 144

CDPPREFACTIONTP Table . . . . . . . . . 145

CDPPREFCAT Table . . . . . . . . . . . 146


© Copyright IBM Corp. 1996, 2008 iii

CDPPREFREASONTP Table . . . . . . . . 147

CDPPREFSEGTP Table . . . . . . . . . . 148

CDPPREFTP Table . . . . . . . . . . . . 149

CDPREFIXNAMETP Table . . . . . . . . . 151

CDPRIMARYTARGETMARKETTP Table . . . . 152

CDPRIORITYCATTP Table . . . . . . . . . 153

CDPRIORITYTP Table . . . . . . . . . . 154

CDPRODCONTRACTRELTP Table . . . . . . 155

CDPRODRELATIONTP Table . . . . . . . . 156

CDPRODRELTP Table . . . . . . . . . . 157

CDPRODSTRUCTURETP Table . . . . . . . 158

CDPRODTP Table . . . . . . . . . . . . 159

CDPRODUCTIDENTIFIERTP Table . . . . . . 160

CDPRODUCTSTATUSTP Table . . . . . . . 161

CDPROVSTATETP Table . . . . . . . . . 162

CDPURPOSETP Table . . . . . . . . . . 163

CDQUESTIONCATTP Table . . . . . . . . 164

CDQUESTIONNAIRETP Table . . . . . . . 164

CDQUESTIONTP Table . . . . . . . . . . 165

CDRELASSIGNTP Table . . . . . . . . . . 166

CDRELTP Table . . . . . . . . . . . . 167

CDREPOSITORYTP Table . . . . . . . . . 168

CDRESIDENCETP Table . . . . . . . . . . 168

CDROLECATTP Table . . . . . . . . . . 169

CDROLETP Table . . . . . . . . . . . . 170

CDRPTINGFREQTP Table . . . . . . . . . 171

CDSERVICELEVELTP Table . . . . . . . . 172

CDSHAREDISTTP Table . . . . . . . . . . 173

CDSOURCEIDENTTP Table . . . . . . . . 174

CDSPECCASCADETP Table . . . . . . . . 175

CDSPECUSETP Table . . . . . . . . . . . 176

CDSTATUSREASONTP Table . . . . . . . . 177

CDSUSPECTREASONTP Table . . . . . . . 178

CDSUSPECTSOURCETP Table . . . . . . . 179

CDSUSPECTSTATUSTP Table . . . . . . . . 180

CDSUSPECTTP Table . . . . . . . . . . . 181

CDTAXPOSITIONTP Table . . . . . . . . . 182

CDTERMINATIONREASONTP Table . . . . . 183

CDUNDELREASONTP Table . . . . . . . . 184

CDVALFREQTP Table . . . . . . . . . . 185

CHARGECARD Table . . . . . . . . . . 186

CLAIM Table . . . . . . . . . . . . . 187

CLAIMCONTRACT Table . . . . . . . . . 189

CLAIMROLE Table . . . . . . . . . . . 190

COMPLDOCUMENT Table . . . . . . . . . 191

COMPLENTITY Table . . . . . . . . . . 192

COMPLENTITYDOC Table . . . . . . . . . 193

COMPLENTITYTARGET Table . . . . . . . 194

COMPLIANCEREQ Table . . . . . . . . . 196

COMPLTARGET Table . . . . . . . . . . 197

CONDITIONATTRIBUTE Table . . . . . . . 198

CONTACT Table . . . . . . . . . . . . 199

CONTACTCDC Table . . . . . . . . . . 202

CONTACTDEMOGRAPHICS Table . . . . . . 203

CONTACTMETHOD Table . . . . . . . . . 204

CONTACTMETHODGROUP Table . . . . . . 206

CONTACTREL Table . . . . . . . . . . . 207

CONTEQUIV Table . . . . . . . . . . . 209

CONTMACROROLE Table . . . . . . . . . 210

CONTRACT Table . . . . . . . . . . . . 211

CONTRACTCOMPONENT Table . . . . . . 215

CONTRACTCOMPVAL Table . . . . . . . . 218

CONTRACTREL Table . . . . . . . . . . 219

CONTRACTROLE Table . . . . . . . . . . 220

CONTRACTROLEREL Table . . . . . . . . 222

CONTSUMMARY Table . . . . . . . . . . 223

DEFAULTSOURCEVAL Table . . . . . . . . 226

ENTITYCONDITIONREL Table . . . . . . . 228

ENTITYCONTENTREFERENCE Table . . . . . 229

ENTITYROLE Table . . . . . . . . . . . 230

ENTITYSPECUSE Table . . . . . . . . . . 231

ENUMANSWER Table . . . . . . . . . . 232

FINANCIALPRODUCT Table . . . . . . . . 233

GOODSPRODUCT Table . . . . . . . . . 234

GROUPING Table . . . . . . . . . . . . 235

GROUPINGASSOC Table . . . . . . . . . 236

HIERARCHY Table . . . . . . . . . . . 237

HIERARCHYNODE Table . . . . . . . . . 238

HIERARCHYREL Table . . . . . . . . . . 239

HIERARCHYULTPAR Table . . . . . . . . 240

HOLDING Table . . . . . . . . . . . . 241

IDENTIFIER Table . . . . . . . . . . . . 243

INACTIVATEDCONT Table . . . . . . . . 245

INACTIVECONTLINK Table . . . . . . . . 246

INCOMESOURCE Table . . . . . . . . . . 247

INSURANCEPRODUCT Table . . . . . . . . 248

INTERACTION Table . . . . . . . . . . 249

INTERACTIONREL Table . . . . . . . . . 251

LOBREL Table . . . . . . . . . . . . . 252

LOCATIONGROUP Table . . . . . . . . . 253

MACROROLEASSOC Table . . . . . . . . 255

MISCVALUE Table . . . . . . . . . . . 256

NATIVEKEY Table . . . . . . . . . . . 260

NLSENUMANSWER Table . . . . . . . . . 261

NLSQUESTION Table . . . . . . . . . . 262

NLSQUESTIONNAIRE Table . . . . . . . . 263

ORG Table . . . . . . . . . . . . . . 265

ORGNAME Table . . . . . . . . . . . . 266

PAYMENTSOURCE Table . . . . . . . . . 267

PAYROLLDEDUCTION Table . . . . . . . . 268

PERSON Table . . . . . . . . . . . . . 269

PERSONNAME Table . . . . . . . . . . 271

PERSONSEARCH Table . . . . . . . . . . 273

PHONENUMBER Table . . . . . . . . . . 275

PPREFACTIONOPT Table . . . . . . . . . 276

PPREFDEF Table . . . . . . . . . . . . 277

PPREFDEFREL Table . . . . . . . . . . . 278

PPREFENTITY Table . . . . . . . . . . . 279

PPREFINSTANCE Table . . . . . . . . . . 280

PRIVPREF Table . . . . . . . . . . . . 281

PRODTPREL Table . . . . . . . . . . . 282

PRODUCT Table . . . . . . . . . . . . 284

PRODUCTCATEGORYASSOC Table . . . . . . 285

PRODUCTCONTRACTREL Table . . . . . . 286

PRODUCTEQUIV Table . . . . . . . . . . 287

PRODUCTIDENTIFIER Table . . . . . . . . 288

PRODUCTNLS Table . . . . . . . . . . . 289

PRODUCTREL Table . . . . . . . . . . . 290

PRODUCTTYPE Table . . . . . . . . . . 291

PRODUCTTYPENLS Table . . . . . . . . . 292

PRODUCTVAL Table . . . . . . . . . . . 293

PRODUCTVALNLS Table . . . . . . . . . 294


iv InfoSphere MDM Server v8.5.0: Data Dictionary

PROPERTY Table . . . . . . . . . . . . 295

QUESTION Table . . . . . . . . . . . . 296

QUESTIONNAIRE Table . . . . . . . . . 297

ROLEIDENTIFIER Table . . . . . . . . . . 298

ROLELOCATION Table . . . . . . . . . . 300

ROLELOCPURPOSE Table . . . . . . . . . 301

ROLESITUATION Table . . . . . . . . . . 302

SEARCHXCLRULE Table . . . . . . . . . 303

SERVICEPRODUCT Table . . . . . . . . . 303

SPEC Table . . . . . . . . . . . . . . 304

SPECFMT Table . . . . . . . . . . . . 305

SPECFORMATTRANSLATION Table . . . . . 306

SUSPECT Table . . . . . . . . . . . . . 307

SUSPECTAUGMENT . . . . . . . . . . . 309

TERMCONDITION Table . . . . . . . . . 310

TERMCONDITIONNLS Table . . . . . . . . 311

VEHICLE Table . . . . . . . . . . . . 312

Chapter 3. Product information and

support . . . . . . . . . . . . . . 315

Notices . . . . . . . . . . . . . . 317

Trademarks . . . . . . . . . . . . 321


Contents v


vi InfoSphere MDM Server v8.5.0: Data Dictionary

Chapter 1. Entity report

This section contains the IBM® InfoSphere™ Master Data Management Server

(InfoSphere MDM Server) database entity report.

Note: To find a specific entry in the entity report, you may find it helpful to use

this help system’s Search feature.

Logical Entity Column Names and definitions

ACCESS TO COMPUTER TYPE LOOKUP

The type of access the PARTY has to a computer and related technologies.

For example, the Party has access to future and evolving technologies, such

as videophones.

ACCOUNT REQUIRED TYPE LOOKUP

Captures information regarding the account requirement for a given

product.

ACTION TYPE ADJUSTED REASON TYPE LOOKUP

Identifies the reason that the action taken as a result of suspect

identification was adjusted.

ACCOUNT TYPE LOOKUP

Contains values of the Account Type Code and its descriptions. Some

examples are ″Savings″ and ″Checking″.

ADD ACTION TYPE LOOKUP

Identifies the action taken as a result of suspect identification.

ADDRESS

A type of LOCATION used for mailing and other street addresses.

ADDRESS GROUP

A subtype of LOCATION GROUP that links parties to address and

contains rules specific to using an address when contacting a party.

ADDRESS USAGE TYPE LOOKUP

Contains information on the valid values for Address Usage Type Code,

such as primary residence, secondary address, or business address.

ADMINISTRATIVE NATIVE KEY FIELD NAME TYPE LOOKUP

Contains the valid values for the Native Key Field Name Type Code and

its descriptions.

ADMINISTRATIVE SYSTEM TYPE LOOKUP

Contains the valid values of administration source systems identified as

the system of record for the detail information concerning agreements and

products.

AGE VERIFICATION DOCUMENT TYPE LOOKUP

Contains the values for the age verification type code and its descriptions.

AGREEMENT STATUS TYPE LOOKUP

Stores the valid status for an agreement, such as Draft, Normal, or

Suspended.

AGREEMENT TYPE LOOKUP

Stores the type of the agreement, such as ″Value Package″.


© Copyright IBM Corp. 1996, 2008 1

ALERT

ALERTs or notes are put on a Party (CONTACT) or CONTRACT to inform

of important issues or additional non-structured information regarding that

Party or Contract. For example, it could detail past complaints or state that

the Party is a VIP.

ALERT CATEGORY TYPE LOOKUP

A categorization of types of alert that are useful for analysis and mining.

For example:

v Marketing Initiative

v Info Change

v Regular Mailing

v Complaint

ALERT SEVERITY TYPE LOOKUP

A grading of the severity or importance of ALERT.

ALERT TYPE LOOKUP

A list of lower level of alerts. For example: ″divorce preceding pending″,

″officer of the company″.

ANSWER

Identifies an answer belonging to a specific answer set.

ANSWER SET

Each answer set is comprised of a series of answers.

ARRANGEMENT TYPE LOOKUP

Contains the values and descriptions of the arrangement type code, which

further describes the type of agreement the party role has with the

contract. For example, a time delay arrangement may be active on the role.

AVAILABILITY TYPE LOOKUP

Captures information regarding how widely available the product is to its

target market.

BANK ACCOUNT RECORD

The bank account information used to pay one or more contracts or

accounts.

BILL TYPE LOOKUP

Contains the values for the bill type code and its descriptions.

BILLING STATUS TYPE LOOKUP

A code table that contains the status values and their descriptions

pertaining to the billing entity. Some examples are ″Closed″, ″Paid″,

″Pending″, and ″Disputed″.

BILLING SUMMARY

A summary bill for a contract or a contract component.

BUY SELL AGREEMENT TYPE LOOKUP

Contains the values for the buy sell agreement type code and its

descriptions.

CAMPAIGN

Captures the details of a campaign for customer solicitation. This includes

the priority order for customer presentation.

CAMPAIGN ASSOCIATION

Stores the association between a campaign and any associated entities.


2 InfoSphere MDM Server v8.5.0: Data Dictionary

CAMPAIGN TYPE LOOKUP

Identifies the type of campaign.

CATEGORY

Holds common platform attributes for categories. A category can

participate in one hierarchy at a time.

CATEGORY EQUIVALENCY

Holds information about a category equivalency.

CATEGORY HIERARCHY

This table holds information about a category hierarchy.

CATEGORY HIERARCHY LOCALIZED

Holds the language-sensitive fields for the CATHIERARCHY table.

CATEGORY LOCALIZED

Holds the language-sensitive fields for the CATEGORY table.

CATEGORY NODE RELATIONSHIP

Holds the definitions of relationships between category nodes in a category

hierarchy.

CDC REJECT REASON TYPE LOOKUP

Stores the reason type for which a critical data change is rejected.

CDC STATUS TYPE LOOKUP

Stores the status type of a critical data change request.

CHARGE CARD RECORD

The charge card information used to pay for one or more contracts or

accounts.

CHARGE CARD TYPE LOOKUP

Contains values of the Charge Card Type Code and its descriptions. Some

examples are ″Visa″, ″MasterCard″, and ″American Express″.

CLAIM

Records claim information for a coverage that may be insured in a

contract. For example: Auto Claim, break-in.

CLAIM AGREEMENT

Records a claim against a contract. For example: Automobile, Homeowners,

and Whole Life insurance policies.

CLAIM DETAIL COVERAGE

Records details of a claim, in relation to coverage. For example: ″Broken

windshield is covered by comprehensive coverage.″

CLAIM ROLE

Identifies the role a party plays on a claim. For example: Claimant,

Witness, and Third Party.

CLAIM ROLE TYPE LOOKUP

Contains the values for the Claim Role Type Code and its descriptions.

Some examples are ″Claimant″, ″Third Party″, ″Witness″, and ″Adjuster″.

CLAIM STATUS TYPE LOOKUP

Contains the values for the Status Type Code and its descriptions. Some

examples are ″Pending″, ″Closed″, ″Open″ and ″Rejected″.

CLAIM TYPE LOOKUP

Contains the values for the Claim Type Code and its descriptions.


Chapter 1. Entity report 3

COMPLIANCE CATEGORY TYPE LOOKUP

CDCOMPLCAT is the table that holds information about the compliance

category.

COMPLIANCE DOCUMENT

COMPLDOCUMENT is the table that holds information about candidating

documents to validate the target.

COMPLIANCE DOCUMENT TYPE LOOKUP

CDCOMPLDOCTP is the table that holds information about the

compliance document type.

COMPLIANCE ENTITY

This table holds information about which entity meets the compliance

requirement.

COMPLIANCE INSTANCE DOCUMENT

COMPLENTITYDOC is the table that holds information about which

document instances are used to validate the target instance.

COMPLIANCE REQUIREMENT

COMPLIANCEREQ is the table that holds information about compliance

requirement.

COMPLIANCE TARGET

COMPLTARGET is the table that holds information about the target that

needs to be validated.

COMPLIANCE TARGET INSTANCE

COMPLENTITYTARGET is the table that holds information about the

target instance.

COMPLIANCE TARGET TYPE LOOKUP

CDCOMPLTARGETTP is the table that holds information about the

compliance target type.

COMPLIANCE TYPE LOOKUP

CDCOMPLIANCETP is the table that holds information about the

compliance type.

COMPLIANCE VALIDATION FREQUENCY TYPE LOOKUP

CDVALFREQTP is the table that holds information about the compliance

validation frequency.

COMPONENT TYPE LOOKUP

Contains the values and descriptions for the component type code that

describes the type of component. For example: base, rider, or base increase.

COMPONENT VALUE TYPE LOOKUP

Contains the values and descriptions for the Value Type Code, which, in a

given domain, identifies the values that are captured. For example, within

banking, values captured may be ″account balance″ and ″account deposit.″

CONDITION ATTRIBUTES

The TermCondition entity can have attributes. When the condition has

attributes added to it, it gains an ″executable″ aspect, because attributes are

used by business rules to enforce the condition or to perform some kind of

calculation described by the condition.

CONDITION ATTRIBUTE TYPE

This table serves as a means to group condition attributes, allowing a

second level of granularity. For example: Core Account Type, Annual

Interest rate, and Minimum Charge.



CONDITION OWNER TYPE LOOKUP

Terms and Conditions is a common component, used by Product and

Account domains. This table categorizes the owner type, such as

PRODUCT or CONTRACT.

CONDITION USAGE TYPE LOOKUP

The CDCONDITIONUSAGETP table serves as a means to group condition

types, such as ValuePackage Integrity and Rate Fee.

CONTACTDEMOGRAPHICS

The table CONTACTDEMOGRAPHICS stores various party demographic

data for a party.

CONTACTCDC

Stores contact information for a critical data change.

CONTACT METHOD

A type of LOCATION used for email addresses, telephones, pagers, web

sites, faxes and various and sundry technologies available now and in the

future where a CLIENT can be contacted.

CONTACT METHOD CATEGORY TYPE LOOKUP

Contains information on the valid values for the Contact Method Category

Type Code and its descriptions. Some example values are phone, email, or

PDA.

CONTACT METHOD GROUP

A subtype of LOCATION GROUP and links parties to addresses and

contains rules specific to using an address when contacting a party.

CONTACT METHOD STATUS TYPE LOOKUP

Contains the values and descriptions for the Contact Method Status Type

Code. Some example contact method statuses are: ″disconnected″,

″unlisted″, and ″no longer available″.

CONTACT METHOD SUBTYPE LOOKUP

Contains information on the valid values for the Contact Method Type

Code, such as primary phone number, cell phone number, or work phone

number.

CONTACT SUMMARY

Contains a summary view of a contact record; specifically, it contains

indicators that track what information is stored about a particular party.

CONTRACT

The full name of this entity is POLICY OR ACCOUNT and it represents

the ’purchase’ of a PRODUCT. This purchase may include various

scenarios including a disability insurance plan, a savings account, a GIC,

and others.

CONTRACT COMPONENT

Contains information on components of a contract such as base, riders, or

others. A contract component represents a part of a contract. Every contract

must have at least one component, known as the base component.

CONTRACT COMPONENT VALUE

Provides a way to model numeric values on the Contract Component.

Since InfoSphere MDM Server is customer-centric and not product-centric,

the value presents a mechanism for implementers to extend the

information associated with a contract component that is only available



through back-end systems. Certain contract features such as Balances in

accounts, limits, terms and rates are typically what can be modeled using

the Value entity.

A contract component value has the following characteristics:

v Allows extending the information that is held within an contract

component or contract component row

v Any number of values can be associated with an contract component

v Allow values are defined through Code Tables

v Has a description

v Has a specific type

v Has a specific value

v Has a status

v Has a validity period or is indefinite

CONTRACT NATIVE KEY

Provides the InfoSphere MDM Server Contract ID to the administrative or

back office system’s native key for a given contract.

CONTRACT RELATIONSHIP

Represents the relationship that an agreement can have with another

agreement.

CONTRACT RELATIONSHIP STATUS TYPE LOOKUP

Contains the values and descriptions for the Contract Relationship Status

Code, which identifies the status of the relationship. For example:

″pending″, ″active″, and ″terminated″.

CONTRACT RELATIONSHIP TYPE LOOKUP

Contains the values and descriptions for the Contract Relationship Type

Code which identifies the purpose for the relationship.

CONTRACT ROLE TYPE LOOKUP

Represents the values of the Contract Role Type Code and its descriptions.

Examples of different roles that a party may have on an insurance contract

include:

v Owner

v Beneficiary

v Insured

v Payer

CONTRACT STATUS TYPE LOOKUP

Contains the values for the Contract Status Type Code and its descriptions.

COUNTRY TYPE LOOKUP

Contains the values of the Contract Type Code and its descriptions. Some

examples include ″USA″, ″Canada″, and ″England″.

CURRENCY TYPE LOOKUP

Contains the values for the current type code and its descriptions. For

example: US Dollar, Japanese Yen, and Euro.

DATE ACCESS VAL

Captures the last used date and last verified date around various entities

and attributes.

DEFAULT SOURCE VALUE

Identifies the business data element that was defaulted during data



collection or migration. For example, a date may be incomplete in the

source system and as a result must be defaulted in order to provide the

InfoSphere MDM Server system an accurate and complete date.

DOMAIN TYPE LOOKUP

Contains values and descriptions for the Domain Type Code that defines

the business area of the agreement component values. For example, the list

of values may relate to the banking system, the underwriting system, or

others.

END REASON TYPE LOOKUP

Contains the values and descriptions of the End Reason Type Code that

identifies the cause for why a relationship was ended.

ENTITY CONDITION RELATIONSHIP

This table stores the association between the TermCondition and the entity

represented by the column ENTITY_NAME (PRODUCT / CONTRACT).

ENTITY CONTENT REFERENCE

This table stores the content references of the content assets stored in

external CMS.

ENTITY ROLE

Stores information about the roles that a given entity can play in a

particular collection, such as a grouping, hierarchy, or party-to-party

relationship.

ENTITY SPEC USE

This table defines the way a spec will be used to define an entity such as a

product.

ENUMERATED ANSWER

ENUMANSWER identifies a possible answer of a question.

ENUMANSWER contains language independent fields of the enumerated

answer.

ENUMERATED ANSWER CATEGORY TYPE LOOKUP

Enumerated answer category type identifies an enumerated answer type

belongs to a specific category.

ENUMERATED ANSWER LOCALIZED

NLSEnumanswer contains language dependent fields of the enumerated

answer.

ENUMERATED ANSWER TYPE LOOKUP

Enum answer type identifies a type of enumerated answer.

FREQUENCY MODE TYPE LOOKUP

Contains the values for the Frequency Mode Type Code and its

descriptions. Some examples are ″Weekly″, ″Monthly″, ″Quarterly″, and

″Annual″.

FINANCIAL PRODUCT

Financial (such as banking) products that are a hardened subtype of

Product.

GENERATION OF NAME TYPE LOOKUP

Contains information on the valid set values for the Generation Name

Type Code, such as The First, The Second, Junior or Senior.

GOODS PRODUCT

Goods (physical) products that are a hardened subtype of Product.



GROUPING

Allows entities, such as Party, to be classified into groups. It also stores

different group types generated from other systems in the enterprise.

GROUPING ASSOCIATION

Identifies the Parties that belong to a Party Group. Identifies the entities,

such as Party, which are placed in a group.

GROUPING CATEGORY TYPE LOOKUP

Contains the values for the Grouping Category Type Code and its

descriptions.

GROUPING TYPE LOOKUP

Contains information on the valid values for group types, such as

Household, Over 40, or Platinum.

HIERARCHY

Represent generic hierarchies in the system.

HIERARCHY CATEGORY TYPE LOOKUP

Contains the values for the hierarchy category Type Code and its

descriptions.

HIERARCHY NODE

Represents a node in a hierarchy.

HIERARCHY RELATIONSHIP

Contains two hierarchy nodes to represent their direct parent-child

relationship.

HIERARCHY TYPE LOOKUP

Contains the values for the hierarchy Type Code and its descriptions.

HIERARCHY ULTIMATE PARENT

Identifies a node as the ultimate parent in a hierarchy.

HIGHEST EDUCATION TYPE LOOKUP

HIGHEST EDUCATION TYPE LOOKUP contains the values for the

Highest Education Type Code and its descriptions.

HOLDING

Records a party’s personal holdings. For example: a list of assets and

liabilities such as Vehicles, Dwellings and Mortgage.

HOLDING TYPE LOOKUP

Contains the values for the Holding Type Code and its descriptions. Some

examples are ″Vehicle″ and ″Property″.

IDENTIFICATION STATUS TYPE LOOKUP

Represents the values of the Identification Status Type Code and its

descriptions. For example:

v Applied For

v Certified

v Expired

IDENTIFICATION TYPE LOOKUP

Represents the values of the Identification Type Code and its descriptions.

Some types of identification are:

v Social Insurance Number

v Social Security Number

v Driver’s License



v Passport Number

INACTIVATED PARTY

A type of PARTY that is no longer considered active to a company. When a

PARTY becomes inactive, modifications to the INACTIVATED PARTY

records are ended.

INACTIVATED PARTY LINK

Maintains the linkage from the active PARTY (target Party) to an

INACTIVATED PARTY (source Party). Its function is to track PARTYs that

have been collapsed or split and are now an INACTIVATED PARTY, and

the link he has with the newly created PARTY (as a result of a collapse or

split).

INCOME SOURCE

This table, provided and attested to by the party, provides the details of

the PARTY’s investment experience and financial standing used in

determining a PARTY’s suitability in purchasing a new investment.

INSURANCE PRODUCT

Insurance (related to the insurance vertical) products that are a hardened

subtype of Product.

INTERACTION

The record of various communications that a service center and a customer

service represent have had with a customer or notes about a customer. The

communication is always for one customer and may optionally be in

regards to a TASK.

INTERACTION RELATIONSHIP

Shows the relationships between different interactions. An initial

interaction can generate a series of interactions with a customer.

INACTIVATED REASON TYPE LOOKUP

Contains information on the valid values for the Inactivated Reason Type

Code such as ’collapsed’, ’split’ and ’deceased’.

INCOME SOURCE TYPE LOOKUP

Contains information on the valid values for the Income Source Type Code

such as annual salary, net worth, and so on.

INDUSTRY TYPE LOOKUP

Contains the values for the industry type code and its descriptions. For

example: farming, industrial, insurance.

INTERACTION CATEGORY TYPE LOOKUP

The high level categorization of types of INTERACTIONS that are useful

for analysis and mining. For example: ″Marketing Initiative″, ″Info

Change″, ″Regular Mailing″, or ″Complaint″.

INTERACTION TYPE LOOKUP

The list of types of INTERACTIONS that may be useful for analysis and

mining. For example: ″Targeted for Marketing Effort″, ″First Contract/Cold

Call″, or ″Customer Complaint″.

INTERACTION CONTACT POINT TYPE LOOKUP

The type of correspondence or the media that was used during the

interaction. For example: ″Telephone,″ ″Fax,″ ″Email,″ ″In-Person,″ and

others.

INTERACTION RELATIONSHIP TYPE LOOKUP

Contains the values and descriptions for the interaction relationship type



code that describes the type of relationship that one interaction can have

with another, such as a follow-up, or escalation.

INTERACTION RESPONSE TYPE LOOKUP

Contains the values and descriptions for structured responses to particular

interactions. Examples include ″not interested″ and ″call later″.

INTERACTION STATUS TYPE LOOKUP

The list of types of status’s that is associated with an INTERACTION. For

example: ″Returned″, ″Success″, or ″Call not answered″.

LANGUAGE TYPE LOOKUP

Contains the values for the Language Type Code and its descriptions. For

example: ″English″, ″French″, or ″Spanish″.

LINK REASON TYPE LOOKUP

Identifies the reason why two parties are linked together. For example:

Collapsed, Split.

LINE OF BUSINESS AFFILIATION

Represents the party ownership by a line of business. For instance John

Smith owned by Home Insurance, Jane Doe owned by Retail banking, Jane

Doe owned by Life Insurance.

LINE OF BUSINESS AFFILIATION TYPE LOOKUP

Defines various LOB relationship types, such as ″owner″.

LINE OF BUSINESS TYPE LOOKUP

Contains the values and descriptions of all the line of businesses setup in

the system.

LOCATION GROUP

Links locations, such as addresses and telephone numbers, to parties and

contains rules for use.

MARITAL STATUS TYPE LOOKUP

Contains the values for the Marital Status Type Code and its descriptions.

Some examples are: ″married,″ ″separated,″ widowed,″ and ″common law″.

MATCH ENGINE TYPE LOOKUP

Holds the type and description of the Matching Engine used to match

parties.

MATCH RELEVANCY TYPE LOOKUP

Contains the values of the match relevancy type code and its description.

Some examples are LNAME, SSN and ADDRESS LINE 1.

METADATA INFORMATION TYPE LOOKUP

Stores the information that can be used to identify the metadata, such as

Task Definition, Spec, and more.

METADATA PACKAGE TYPE LOOKUP

Stores a list of metadata package names, which are used to identify the

location of the metadata in the MDM Server system, such as Task

Definition, Spec, and more.

MISCELLANEOUS VALUE

Records miscellaneous values that can be generated from other systems in

the enterprise or can specific details an institution would like to record

about their customer base. The miscellaneous value can be associated to a

party (contact).



MISCELLANEOUS VALUE ATTRIBUTE TYPE LOOKUP

This code identifies the miscellaneous value attributes types that are

captured.

MISCELLANEOUS VALUE CATEGORY TYPE LOOKUP

The high level categorization of types for Miscellaneous Values. Some

examples are Demographic Category, Risk Category, and Standard Industry

Codes.

MISCELLANEOUS VALUE TYPE LOOKUP

Identifies the miscellaneous value attributes types that are captured. These

attributes can be different value attribute types for a miscellaneous value

type or it can be additional information for a particular miscellaneous type

such as status, effective date, created date, and indicator.

NAME USAGE TYPE LOOKUP

Contains the values of the name usage type code and its description. For

example: legal name, nickname, maiden name.

NODE DESIGNATION TYPE LOOKUP

Contains the values for the Node Designation Type Code and its

descriptions. Examples include ″Local Parent″ and ″Geographical Parent″.

NODE TYPE LOOKUP

Captures metadata regarding how the subtype is represented within the

Product Type hierarchy.

ORGANIZATION

A subtype of PARTY and represents some form of legal entity other than a

human. This includes incorporated companies, non-profit organizations,

sole-proprietorships, partnerships, or trusts.

ORGANIZATION NAME

Contains the different names that may be used by an organization.

ORGANIZATION NAME TYPE LOOKUP

Contains the values of the Organization Name Type Code and its

descriptions. Some examples are ″Doing Business As″, ″Abbreviated

Name″, ″Legal Name″.

ORGANIZATION TYPE LOOKUP

Contains information on the valid values for the Organization Type Code,

such as charity, trust, estate, or corporation.

PARTY

Any PERSON or ORGANIZATION that is useful to keep track of in the

system. This includes CLIENTs (suspects, prospects and clients), CSRs,

AGENTs, competitors, contact persons, and anyone else whose name,

address, telephone, and relationship to another party.

PARTY CONTRACT ROLE

An association that links parties to the various roles they may have on a

contract.

PARTY CONTRACT ROLE LOCATION

An association between a Party’s roles on a contract to a particular location

group.

PARTY CONTRACT ROLE RELATIONSHIP

An association that links party contract roles together. For example, a role

relationship would be used to determine which custodian role is for which

minor owner on a given contract.



PARTY DEMOGRAPHICS TYPE LOOKUP

The code table CDDEMOGRAPHICSTP defines the demographics types.

PARTY EQUIVALENCY

Provides the link between the InfoSphere MDM Server Party ID and

Administrative system or back office Party (or client) native identification

system.

PARTY IDENTIFIER

An additional way of distinguishing a party that is natural to them. For

example: social security number, driver’s license number, or passport

number.

PARTY IMPORTANCE TYPE LOOKUP

Contains the values for the Party Importance Type Code and its

descriptions. The importance type can be used to indicated VIP situations

or other special services that may be applied to this party.

PARTY MACRO ROLE

Represents a high-level role a party plays in the system. For instance, the

party may be captured in the context of a prospect and as such its macro

role is recorded as ″Prospect″.

PARTY MACRO ROLE ASSOCIATION

An association between a party’s macro role and its child data. For

instance, as ″Prospect″ (macro role) the system may capture that party’s

email address (associated party child data): ″[email protected]″. This is

an association between the macro role and the contact method. Child data

must exist before it can be associated with a macro role.

PARTY POTENTIAL TYPE LOOKUP

Represents the Party Potential Type Code and its descriptions.

PARTY RELATIONSHIP

Represents the relationship between two parties.

For example:

FROM CONTACT: ’Sue Smith’

RELATIONSHIP: ’child of’

TO CONTACT: ’Greg Smith’

PARTY STATUS TYPE LOOKUP

Represents the values of Party Status Type Code and its description.

PAYMENT METHOD TYPE LOOKUP

A code table that contains various payment method type values and their

descriptions. Some examples are ″Cash″, ″Cheque″, ″Bank Account″,

″Credit Card″ and ″Payroll Deduction″.

PAYMENT SOURCE

An abstract supertype for various payment source types in the system such

as bank account, charge card or payroll deduction.

PAYROLL DEDUCTION

Represents a person’s payroll deduction payment source information used

to pay one or more contracts or accounts.

PERSON

A subtype of PARTY and represents a human being.



PERSON NAME

Contains the names that may be used by a person.

PERSON SEARCH

Contains the standardized or non-standardized versions of the PERSON

NAME table to facilitate searching.

PHONENUMBER

This table holds information of party’s phone number.

PREFIX OF NAME TYPE LOOKUP

Contains information on the valid set values for the Prefix of Name Type

Code, such as Mr., Mrs., Dr., and others. These values are displayed in the

user interface as a drop down box.

PRIORITY CAT TYPE LOOKUP

Contains the various categories of Priority that a Priority Type can belong

to. ″Task″ is a typical priority category that is specifically used by Task

Management services.

PRIORITY TYPE LOOKUP

Contains the various priorities for campaigns and the like, and includes

values such as high, medium, low.

PRIVACY PREFERENCE

Stores all Privacy and Preference records.

PRIVACY PREFERENCE ACTION TYPE LOOKUP

Contains the values of the privacy preference action type code and its

descriptions. Some examples are ″Call″, ″Do not call″, ″Opt In″ and ″Opt

Out″.

PRIVACY PREFERENCE ACTION OPTION

Stores the action types that are possible options for each privacy preference

Type.

PRIVACY PREFERENCE CATEGORY TYPE LOOKUP

A high level categorization of type of Privacy Preferences.

PRIVACY PREFERENCE DEFAULT

Captures the default Privacy Preference regulations for an institution. The

privacy preference default settings apply to all parties within InfoSphere

MDM Server. For example: Y or N.

PRIVACY PREFERENCE DEFAULT RELATIONSHIP

Define the parent child relationship between two Default Privacy

Preference records. This allows for different privacy preference regulations

to supersede other regulations that can be based on different criteria.

PRIVACY PREFERENCE ENTITY

Captures customized privacy and preferences informations for a Party,

Party Address, Party Contact Method and Contract Role Location.

PRIVACY PREFERENCE INSTANCE

Identifies the entity instance that is associated with the Privacy Preference

record. It records more information regarding the privacy preference that

InfoSphere MDM Server stores. For example, a party has a preference for a

new product.

PRIVACY PREFERENCE REASON TYPE LOOKUP

Identifies the reason for a privacy preference element.



PRIVACY PREFERENCE SEGMENT TYPE LOOKUP

Stores the segment that a privacy preference regulation applies to. This can

be based on geography such as country, state or province, or a particular

segment.

PRIVACY PREFERENCE TYPE LOOKUP

Contains the various types of Privacy or Preference information.

PRODUCT

Instances of products that are of interest to the business.

PRODUCT CATEGORY ASSOCIATION

A product’s association to a category.

PRODUCT CONTRACT RELATIONSHIP

The table that holds the relationship between a product and a contract.

PRODUCT CONTRACT RELATIONSHIP TYPE LOOKUP

The code table that holds the type of a product-contract relationship, such

as Party Selection.

PRODUCT EQUIVALENCE

Stores information about how a product is identified in a different system.

PRODUCT IDENTIFIER

A client-defined identifier for the product such as a part number or

product code.

PRODUCT IDENTIFIER TYPE LOOKUP

Captures information regarding the product identifier.

PRODUCT LOCALIZED

ProductNLS table is the localization table for the Product table. The

ProductNLS entity could represent the localization data of fields those

needs to be localized. It is Product table content in localized form.

PRODUCT RELATION TYPE LOOKUP

Captures information regarding the type of relationship held between two

products.

PRODUCT RELATIONSHIP

A relationship between two products. Products can be related together to

capture product substitutes, up-sells, cross-sells and so on. They can also

be related together to form bundles and coarser grain products made up of

product components.

PRODUCT STRUCTURE TYPE LOOKUP

Captures information regarding how the product is structured.

PRODUCT TYPE

A type of product that, unless it is the root product type, is a subtype of

another product type.

PRODUCT TYPE LOCALIZED

The ProductTypeNLS table is the localization table for the ProductType

table. A ProductTypeNLS entity could represent the localization data of

fields those needs to be localized.

PRODUCT TYPE LOOKUP

Contains the values for the Product Type Code and its descriptions.



PRODUCT TYPE RELATIONSHIP

This table stores the relationship type between two product records. These

relationships may be used in combinations to provide a hierarchy of

products.

PRODUCT TYPE RELATIONSHIP LOOKUP

Identifies all the relationship types that can exist between products.

PRODUCT VALUES

A set of values based on a spec format. The values decorate the product

based on the product’s association to some other entity such as the

product’s type. The values based on spec formats associated to the

product’s type are maintained in this table.

PRODUCT VALUES LOCALIZED

ProductValNLS table is the localization table for the table ProductVal.

ProductValNLS entity could represent the localization data of fields those

needs to be localized. Product values content in localized form.

PROPERTY

Contains all HOLDING records that are locations. For example: Cottage,

Private Residence, or Condominium.

PROVINCE STATE TYPE LOOKUP

Contains information on the valid values for the Province-State Type Code,

including both postal state codes, like WA and NJ, and foreign country

province codes.

PURPOSE TYPE LOOKUP

Identifies the purpose for the location as it relates to a role on a contract.

For example, statements are sent to the location for the owner of the

contract.

QUESTION

Question contains language independent fields of a question.

QUESTION CATEGORY TYPE LOOKUP

Question category type identifies a question type belongs to a specific

category.

QUESTION LOCALIZED

NLSQuestion contains language dependent fields of a question.

QUESTION TYPE LOOKUP

Question type identifies a type of question

QUESTIONNAIRE

A questionnaire is comprised of a series of Questions and Enumerated

Answers used to collect information. Questionnaire contains language

independent fields of a questionnaire.

QUESTIONNAIRE LOCALIZED

NLSQuestionnaire contains the language dependent fields of

Questionnaire.

QUESTIONNAIRE TYPE LOOKUP

Questionnaire type identifies a type of questionnaire.

RELATIONSHIP ASSIGNMENT TYPE LOOKUP

Contains the values for the relationship assignment type code and its

descriptions. Party-to-party relationships may be assigned by a court order

or judgment, or by another party.



RELATIONSHIP TYPE LOOKUP

The type of relationship that PARTY may have among one another and

that are useful for tracking. For each relationship, there is a ’from PARTY’

and a ’to PARTY’ and the relationship is usually named differently

depending on which PARTY is made the ’to Party’.

REPOSITORY TYPE LOOKUP

This table stores the content management systems and related repositories

for an organization.

RESIDENCE TYPE LOOKUP

Contains the valid values for the Residence Type Code and its descriptions.

Some examples are ″suite,″ apartment,″ ″building,″ and others. These

values are displayed in the user interface as a drop down box.

ROLE CATEGORY TYPE LOOKUP

The high level categorization of types for roles. Some examples are

Grouping Roles, Hierarchy Roles, Relationship Roles, and Party Macro

Roles.

ROLE TYPE LOOKUP

This code identifies various role types in the system. Examples include

″head of household″ and ″Prospect″.

REPORTING FREQUENCY TYPE LOOKUP

Represents the Reporting Frequency Type Code and its descriptions.

ROLE IDENTIFIER

Provides an identifier to a party’s specific role on a contract.

ROLE LOCATION PURPOSE

Describes why contract information for a particular role is addressed to a

defined location. The location can either be an address or a contact

method.

ROLE SITUATION

Defines the different arrangements that may be defined by a given party

contract role. For example: time delay, or common disaster arrangements

on life insurance policies.

SEARCH EXCLUSION RULE

Provides the initial search exclusion criteria for each search transaction. For

example: Last Name only, Last and Given Name One only, or Last Name

and City only.

SERVICE LEVEL TYPE LOOKUP

The code table that stores the service level agreements for an agreement.

For example: ″Service during business hours only″ or ″Service 24/7

through a Call Centre″.

SERVICE PRODUCT

Service (non-physical) products that are a hardened subtype of Product.

SHARE DISTRIBUTION LOOKUP

Contains the values and descriptions of the share distribution type code

that defines how the proceeds of the contract are distributed among the

party contract roles.

SOURCE IDENTIFIER TYPE LOOKUP

These type codes describe what Source Identifier Values represent in the

Default Source Value Table.

SPEC This table holds information about specs available in the system.



SPEC CASCADE TYPE LOOKUP

Captures information regarding the type of cascade action the spec will

have in a hierarchy.

SPEC FORMAT

This table holds all the various formats (or versions) for the system’s specs.

SPEC FORMAT TRANSLATION

This table holds locale specific translations for the attribute names of specs

SPEC USE TYPE LOOKUP

Captures information regarding the usage types the spec will be used for.

STATUS REASON TYPE LOOKUP

Captures information regarding the reason the product is in its current

state.

STATUS TYPE LOOKUP

Captures information regarding the lifecycle status of the product.

SUSPECT

Contains all the suspects (parties that are possibly duplicates of each other)

that a particular party has in the InfoSphere MDM Server database.

SUSPECTAUGMENT

Contains the augmented suspect processing results preformed by

additional Matching Engines.

SUSPECT REASON TYPE LOOKUP

Describes the relevancy of a potential suspect duplicate for a particular

party. For example, all elements for the party and the suspect matched.

SUSPECT SOURCE TYPE LOOKUP

Indicates how a potential suspect duplicate was identified. Examples

include system marked and user marked.

SUSPECT STATUS TYPE LOOKUP

Describes the current status of the investigation into a potential suspect

duplicate. Examples include ″parties not duplicate″ and ″critical change

resolved″.

SUSPECT TYPE LOOKUP

Enables the replacement of default suspect processing logic with custom

implementation. It also provides hooks to integrate with third party

software to perform suspect search and matching.

TARGET TYPE LOOKUP

Captures information regarding the primary market this product targets.

TAX TYPE LOOKUP

Captures information regarding the relative tax position offered by a

product.

TERM CONDITION

The TermCondition table represents a logical condition, containing

conditions for entities such as Product and Agreement. TermCondition can

be static or executable.

TERM CONDITION LOCALIZED

TermConditionNLS table is the localization table for the

TERMCONDITION table. The TermConditionNLS entity represents the

localization data of the fields which need to be localized.



TERMINATION REASON TYPE LOOKUP

The code table that stores the termination reasons for an agreement, such

as an ″Agreement Terms & Conditions violation″ in the case of a value

package breakage.

UNDELIVERABLE REASON TYPE LOOKUP

Contains information on the valid values for the Undeliverable Reason

Type Code. Some example values are bad addresses, wrong zip codes, and

so on.

VEHICLE

Contains all HOLDING records that are vehicles. For example: Mazda M3,

Subaru Outback, Honda Civic



Chapter 2. Tables

This section contains details about the InfoSphere MDM Server database tables.

Table name Comment

ACCESSDATEVAL ACCESSDATEVALUE captures the last used date

and last verified date around various entities and

attributes.

ADDACTIONTYPE ADDACTIONTYPE identifies the action taken as a

result of suspect identification.

ADDRESS ADDRESS is a type of LOCATION used for mailing

and other street addresses.

You can have only one address per ADDRESS

USAGE TYPE CD. Another words, only one

’Mailing’ address.

ADDRESSGROUP ADDRESS GROUP is a subtype of LOCATION

GROUP and links parties to address and contains

rules specific to using an address when contacting a

party.

AGREEMENTSPECVAL Contains spec values that are related to business

agreements. An example of a business agreement

can be represented by the contract business object.

ALERT ALERTs or Notes are put on a Party (CONTACT) or

CONTRACT to inform of important issues or

additional non-structured information regarding that

Party or Contract. For example: a warning that the

Party has previous complaints.

ANSWER ANSWER identifies an answer belongs to a specific

answer set.

ANSWERSET ANSWERSET is comprised of a series of answers.

BANKACCOUNT BANK ACCOUNT RECORD is the bank account

information used to pay one or more contracts or

accounts.

BILLINGSUMMARY Represents a summary bill for a contract or a

contract component.

CAMPAIGN This table capture the detail of a campaign for

customer solicitation. This include the priority order

for customer presentation.

CAMPAIGNASSOCIAT Store the association between a campaign and any

associated entities, such as parties.

CATEGORY This table holds common platform attributes for

categories. A category may participate in one

hierarchy at a time.

CATEGORYNLS This table holds the language sensitive fields for

CATEGORY table.

CATEQUIV This table holds information about a category

equivalency.

CATHIERARCHY This table holds information about a category

hierarchy.



Table name Comment

CATHIERARCHYNLS This table holds the language sensitive fields for

CATHIERARCHY table.

CATNODEREL This table holds the definition of relationships

between category nodes in a category hierarchy.

CDACCETOCOMPTP ACCESS TO COMPUTER TYPE LOOKUP is the

type of access the PARTY has to a computer &

related technologies. This may include the simplest

issue of whether the PARTY has access to a

computer to future and evolving technologies (such

as videophones).

CDACCOUNTREQUIREDTP Captures information regarding the account

requirement for a given product.

CDACCOUNTTP ACCOUNT TYPE LOOKUP contains values of the

Account Type Code and its descriptions. Some

examples are ″Savings,″ and ″Checking.″

CDACTIONADJREASTP Action Type Adjusted Reason Type identifies the

reason that the action taken as a result of suspect

identification was adjusted.

CDADDRUSAGETP ADDRESS USAGE TYPE LOOKUP contains

information on the valid values for the Address

Usage Type Code, such as primary residence,

secondary address, and business address.

CDADMINFLDNMTP ADMINISTRATIVE NATIVE KEY FIELD NAME

TYPE LOOKUP contains the valid values for the

Native Key Field Name Type Code and its

descriptions.

CDADMINSYSTP ADMINISTRATIVE SYSTEM TYPE LOOKUP

contains the valid values of administration source

systems identified as the system of record for the

detail information concerning agreements and

products.

CDAGEVERDOCTP AGE VERIFICATION DOCUMENT TYPE LOOKUP

contains the values for the age verification type code

and its descriptions.

CDAGREEMENTSTTP The code table that stores the valid status for an

agreement. For example: Draft, Normal, Suspended.

CDAGREEMENTTP The code table that stores the type of the agreement,

such as ValuePackage.

CDALERTCAT ALERT CATEGORY LOOKUP is a categorization of

types of alert that are useful for analysis and

mining. For example:

v Marketing Initiative

v Info Change

v Regular Mailing

v Complaint

CDALERTSEVTP ALERT SEVERITY TYPE LOOKUP is a grading of

the severity or importance of the ALERT. The

severity of the alert translates into a user interface

(UI) color change. For example, a ″red alert″ and

″yellow alert″ will signal the UI to provide a red or

yellow alert.



Table name Comment

CDALERTTP ALERT TYPE LOOKUP is a list of lower level of

alerts. For example: ″divorce preceding pending″ or

″officer of the company″.

CDARRANGEMENTTP ARRANGEMENT TYPE LOOKUP contains the

values and descriptions of the arrangement type

code, which further describes the type of agreement

the party role has with the contract. For examples, a

time delay arrangement may be active on the role.

CDAVAILABILITYTP Captures information regarding how widely

available the product is to its target market.

CDBILLINGSTTP Billing status type lookup is a code table, which

contains the status values and their description

pertaining to the billing entity. Some examples are

″Closed″, ″Paid″, ″Pending″ and ″Disputed″

CDBILLTP BILL TYPE LOOKUP contains the values for the bill

type code and its descriptions.

CDBUYSELLAGREETP BUY SELL AGREEMENT TYPE LOOKUP contains

the values for the buy sell agreement type code and

its descriptions.

CDCAMPAIGNTP Identifies the type of campaign.

CDCDCREJREASONTP ACCESS TO COMPUTER TYPE LOOKUP is the

type of access the PARTY has to a computer &

related technologies. This may include the simplest

issue of whether the PARTY has access to a

computer to future and evolving technologies such

as videophones.

CDCDCSTTP CRITICAL DATA CHANGE STATUS LOOKUP hold

the status type of the critical data change request.

CDCHARGECARDTP CHARGE CARD TYPE LOOKUP contains values of

the Charge Card Type Code and its descriptions.

Some examples are ″Visa,″ ″MasterCard,″ and

″American Express.″

CDCLAIMROLETP PRODUCT TYPE LOOKUP contains the values for

the Product Type Code and its descriptions.

CDCLAIMSTATUSTP PRODUCT TYPE LOOKUP contains the values for


CDCLAIMTP PRODUCT TYPE LOOKUP contains the values for


CDCLIENTIMPTP PARTY IMPORTANCE TYPE LOOKUP contains the

values for the Party Importance Type Code and its

descriptions. The importance type can be used to

indicated VIP situations or other special services that

may be applied to this party.

CDCLIENTPOTENTP PARTY POTENTIAL TYPE LOOKUP represents the

Party Potential Type Code and its descriptions.

CDCLIENTSTTP PARTY STATUS TYPE LOOKUP represents the

values of Party Status Type Code and its description.

CDCOMPLCATTP CDCOMPLCAT is the table holds information about

compliance category.

CDCOMPLDOCTP CDCOMPLDOCTP is the table that holds

information about compliance document type.


Chapter 2. Tables 21

Table name Comment

CDCOMPLIANCETP CDCOMPLIANCETP is the table that holds

information about compliance type.

CDCOMPLTARGETTP CDCOMPLTARGETTP is the table that holds

information about compliance target type.

CDCONDITIONATTRIBUTETP This table serves as a means to group condition

attributes, allowing a second level of granularity. For

example: Core Account Type, Annual Interest rate,

and Minimum Charge.

CDCONDITIONOWNERTP Terms and Conditions is a common component,

used by Product and Account domains. This table

categorizes the owner type. For example: PRODUCT

or CONTRACT.

CDCONDITIONUSAGETP The CDCONDITIONUSAGETP table serves as a

means to group condition types. For example:

ValuePackage Integrity, Rate Fee.

CDCONTMETHCAT CONTACT METHOD CATEGORY TYPE LOOKUP

contains information on the valid values for the

Contact Method Category Type Code and its

descriptions. Some example values are phone, email,

and PDA.

CDCONTMETHTP CONTACT METHOD SUBTYPE LOOKUP contains

information on the valid values for the Contact

Method Type Code, such as primary phone number

and cell phone number.

CDCONTRACTRELSTTP CONTRACT RELATIONSHIP STATUS TYPE

LOOKUP contains the values and descriptions for

the Contract Relationship Status Code, which

identifies the status of the relationship, for example,

″pending,″ ″active,″ and ″terminated.″

CDCONTRACTRELTP CONTRACT RELATIONSHIP TYPE LOOKUP

contains the values and descriptions for the Contract

Relationship Type Code which identifies the purpose

for the relationship.

CDCONTRACTROLETP CONTRACT ROLE TYPE LOOKUP represents the

values of the Contract Role Type Code and its

descriptions. Some examples of different roles that a

party may have on a contract include:

v Owner

v Beneficiary

v Insured

v Payer

CDCONTRACTSTTP CONTRACT STATUS TYPE LOOKUP contains the

values for the Contract Status Type Code and its

descriptions.

CDCONTRCOMPTP COMPONENT TYPE LOOKUP contains the values

and descriptions for the component type code that

describes the type of component. For example: base,

rider, base increase.

CDCOUNTRYTP COUNTRY TYPE LOOKUP contains the values of

the Contract Type Code and its descriptions. For

example: ″USA,″ ″Canada,″ ″England″.



Table name Comment

CDCURRENCYTP CURRENCY TYPE LOOKUP contains the values for

the current type code and its descriptions. For

example: Euro, US Dollar, Japanese Yen, British

Pound.

CDDEMOGRAPHICSTP The code table CDDEMOGRAPHICSTP defines the

demographics types.

CDDOMAINTP DOMAIN TYPE LOOKUP contains values and

descriptions for the Domain Type Code that defines

the business area of the agreement component

values. For example, the list of values may relate to

the banking system or the underwriting system.

CDDOMAINVALUETP COMPONENT VALUE TYPE LOOKUP contains the

values and descriptions for the Value Type Code,

which, in a given domain, identifies the values that

are captured. For example, within banking, values

captured may be ″account balance″ and ″account

deposit.″

CDENDREASONTP END REASON TYPE LOOKUP contains the values

and descriptions of the End Reason Type Code that

identifies the cause for why a relationship was

ended.

CDENUMANSWERCATTP Enum answer category type identifies an

enumerated answer type belongs to a specific

category.

CDENUMANSWERTP Enum answer type identifies a type of enumerated

answer

CDFREQMODETP FREQUENCY MODE TYPE LOOKUP contains the

values for the Frequency Mode Type Code and its

descriptions. Some examples are ″Weekly″,

″Monthly″, ″Quarterly″ and ″Annual″.

CDGENERATIONTP GENERATION OF NAME TYPE LOOKUP Contains

information on the valid set values for the

Generation Name Type Code, such as The First, The

Second, Junior or Senior.

CDGROUPINGCATTP GROUPING CATEGORY TYPE LOOKUP contains

the values for the Grouping Category Type Code

and its descriptions.

CDGROUPINGTP Identify all Group Types, such as Household, Over

40, Platinum.

CDHIERARCHYCATTP HIERARCHY CATEGORY TYPE LOOKUP contains

the values for the hierarchy category Type Code and

its descriptions.

CDHIERARCHYTP HIERARCHY TYPE LOOKUP contains the values

for the hierarchy Type Code and its descriptions.

CDHIGHESTEDUTP HIGHEST EDUCATION TYPE LOOKUP contains

the values for the Highest Education Type Code and

its descriptions.

CDHOLDINGTP HOLDING TYPE LOOKUP contains the values for

the Holding Type Code and its descriptions. Some

examples are ″Vehicle″ and ″Property″



Table name Comment

CDIDSTATUSTP IDENTIFICATION STATUS TYPE LOOKUP

represents the values of the Identification Status

Type Code and its descriptions. Some examples of

the statuses of a alternate party identifier are:

v Applied for

v Certified

v Expired

CDIDTP IDENTIFICATION TYPE LOOKUP represents the

values of the Identification Type Code and its

descriptions. Some types of identification are:

v Social Insurance Number

v Social Security Number

v Driver’s License

v Passport Number

v Tax Registration Number

CDINACTREASONTP INACTIVATED REASON TYPE LOOKUP contains

information on the valid values for the Inactivated

Reason Type Code such as ’collapsed’, ’split’ and

’deceased’.

CDINCOMESRCTP INCOME SOURCE TYPE LOOKUP contains

information on the valid values for the Income

Source Type Code such as annual salary and net

worth.

CDINDUSTRYTP INDUSTRY TYPE LOOKUP contains the values for

the industry type code and its descriptions. For

example: farming, industrial, insurance.

CDINTERACTIONCAT INTERACTION CATEGORY TYPE LOOKUP is the

high level categorization of types of

INTERACTIONS that are useful for analysis and

mining. Some examples are ″Marketing Initiative,″

″Info Change,″ ″Regular Mailing,″ and ″Complaint″.

CDINTERACTIONTP INTERACTION TYPE LOOKUP is the list of types

of INTERACTIONS that may be useful for analysis

and mining. Some examples are ″Targeted for

Marketing Effort,″ First Contract/Cold Call,″ and

″Customer Complaint″.

CDINTERACTPTTP INTERACTION CONTACT POINT TYPE LOOKUP

is the type of correspondence or the media that was

used during the interaction. For example,

″Telephone,″ ″Fax,″ ″Email,″ and ″In-Person.″

CDINTERACTRELTP INTERACTION RELATIONSHIP TYPE LOOKUP

contains the values and descriptions for the

interaction relationship type code which describes

the type of relationship that one interaction can have

with another, such as a follow-up, or escalation.

CDINTERACTRESPTP Identify the types of responses an interaction may

have.

CDINTERACTSTTP INTERACTION STATUS TYPE LOOKUP is the list

of types of status’s that is associated with an

INTERACTION. Some examples are ″Returned″,

″Success″, or ″Call not answered″.



Table name Comment

CDLANGTP LANGUAGE TYPE LOOKUP contains the values for

the Language Type Code and its descriptions. Some

examples of values are ″English,″ ″French,″ or

″Spanish″.

CDLINKREASONTP LINK REASON TYPE LOOKUP identifies the reason

why two parties are linked together. For example:

Collapsed or Split.

CDLOBRELTP Defines various LOB relationship types, such as

owner.

CDLOBTP Contains the values and descriptions of all the line

of businesses setup in the system.

CDMARITALSTTP MARITAL STATUS TYPE LOOKUP contains the

values for the Marital Status Type Code and its

descriptions. For example: ″married,″ ″separated,″

widowed″.

CDMATCHENGINETP MATCH ENGINE TYPE LOOKUP hold the type

information and description of Matching Engine use

for matching parties.

CDMATCHRELEVTP MATCH RELEVENCY TYPE LOOKUP contains the

values of the match relevancy type code and its

description. Some examples are LNAME, SSN and

ADDRESS LINE 1.

CDMETADATAINFOTP Stores the information that can be used to identify

the metadata, such as Task Definition and Spec.

CDMETADATAPACKAGETP Stores a list of meta data package names, which are

used to identify the location of the metadata in

InfoSphere MDM Server system, such as task

definition and spec.

CDMETHODSTATUSTP CONTACT METHOD STATUS TYPE LOOKUP

contains the values and descriptions for the Contact

Method Status Type Code. Some example contact

method statuses are: ″disconnected,″ ″unlisted,″ ″no

longer available″.

CDMISCVALUEATTRTP This code identifies the miscellaneous value attribute

types that are captured.

CDMISCVALUECAT CATEGORY TYPE LOOKUP is the high level

categorization of types for Miscellaneous Values.

Some examples are Demographic Category, Risk

Category, and Standard Industry Codes.

CDMISCVALUETP This code identifies the miscellaneous value types

that are captured. Some examples of miscvalue type

are number of employees, gold value, and credit

card risk score.

CDNAMEUSAGETP NAME USAGE TYPE LOOKUP contains the values

of the name usage type code and its description.

Some examples are legal name, nickname, and

maiden name.

CDNODEDESIGTP HIERARCHY CATEGORY TYPE LOOKUP contains

the values for the hierarchy category Type Code and

its descriptions.

CDNODETP Captures meta-data regarding how the subtype is

represented within the product type hierarchy.



Table name Comment

CDORGNAMETP ORGANIZATION NAME TYPE LOOKUP contains

the values of the Organization Name Type Code and

its descriptions. Some examples are ″Doing Business

As,″ ″Abbreviated Name,″ and ″Legal Name.″

CDORGTP ORGANIZATION TYPE LOOKUP contains

information on the valid values for the Organization

Type Code, such as charity, trust, estate, or

corporation.

CDPAYMENTMETHODTP Payment method type lookup is a code table, which

contains various payment method type values and

their descriptions.

CDPPREFACTIONTP Identifier the type of action to apply. This may be

used to identify varies options available for each

type of Privacy/Preference records. For example: Do

not Call, Do not mail.

CDPPREFCAT Allow Privacy Preference Type to be categorized.

CDPPREFREASONTP Identifier the reason for a privacy element.

CDPPREFSEGTP Store the segment that preference record should falls

into based on regulation.

CDPPREFTP Identifier the type of Privacy or Preference

information. For example: Pander Flag

CDPREFIXNAMETP PREFIX NAME TYPE LOOKUP contains

information on the valid set values for the Prefix of

Name Type Code, such as Mr., Mrs., and Dr. These

values are displayed in the user interface as a drop

down box.

CDPRIMARYTARGETMARKETTP Captures information regarding the primary market

this product targets.

CDPRIORITYCATTP Contain the various categories of priority that a

priority type can belong to. ″Task″ is a typical

priority category which is specifically used by task

management services.

CDPRIORITYTP PRIORITY TYPE LOOKUP contains the various

priorities for campaigns, and includes values such as

high, medium, low.

CDPRODCONTRACTRELTP The code table that holds the type of a

product-contract relationship (such as Party

Selection)

CDPRODRELATIONTP Captures information regarding the type of

relationship held between two products.

CDPRODRELTP identifier all the relationship types that can exist

between products

CDPRODSTRUCTURETP Captures information regarding how the product is

structured.

CDPRODTP PRODUCT TYPE LOOKUP contains the values for


CDPRODUCTIDENTIFIERTP Captures information regarding the product

identifier

CDPRODUCTSTATUSTP Captures information regarding the lifecycle status

of the product.



Table name Comment

CDPROVSTATETP PROVINCE STATE TYPE LOOKUP contains

information on the valid values for the Province -

State Type Code, including both postal state codes

(NJ, NY, AL, MI and so on) and foreign country

province codes.

CDPURPOSETP Purpose Type Code identifies the purpose for the

location as it relates to a role on a contract. For

example, statements are sent to the location for the

owner of the contract.

CDQUESTIONCATTP Question category type identifies a question type

belongs to a specific category.

CDQUESTIONNAIRETP Questionnaire type identifies a type of questionnaire.

CDQUESTIONTP Question type identifies a type of question.

CDRELASSIGNTP RELATIONSHIP ASSIGNMENT TYPE LOOKUP

contains the values for the relationship assignment

type code and its descriptions. Party to party

relationships may be assigned by a court

order/judgment, or by another party.

CDRELTP RELATIONSHIP TYPE LOOKUP is the type of

relationship that PARTY may have among one

another and that are useful for tracking. For each

relationship, there is a ’from PARTY’ and a ’to

PARTY’ and the relationship is usually named

differently depending on which PARTY you are

looking at (such as Parent/Child,

Employer/Employee).

CDREPOSITORYTP This table stores the content management systems

and related repositories for an organization.

CDRESIDENCETP RESIDENCE TYPE LOOKUP contains the valid

values for the Residence Type Code and its

descriptions. Some examples are ″suite,″ apartment,″

and ″building″. These values are displayed in the

user interface as a drop down box.

CDROLECATTP CATEGORY TYPE LOOKUP is the high level

categorization of types for Miscellaneous Values.

Some examples are Demographic Category, Risk

Category, and Standard Industry Codes.

CDROLETP This code identifies the miscellaneous value types

that are captured. Some examples of miscvalue type

are number of employees, gold value, and credit

card risk score.

CDRPTINGFREQTP REPORTING FREQUENCY TYPE LOOKUP

represents the Reporting Frequency Type Code and

its descriptions.

CDSERVICELEVELTP The Code table that stores the service level

agreements for an agreement. For example: Service

during business hours only, Service 24/7 through

Call Centre.

CDSHAREDISTTP SHARE DISTRIBUTION LOOKUP contains the

values and descriptions of the share distribution

type code which defines how the proceeds of the

contract are distributed among the party contract

roles.



Table name Comment

CDSOURCEIDENTTP These type codes describe what Source Identifer

Values represent in the Default Source Value Table.

CDSPECCASCADETP Captures information regarding the type of cascade

action the spec will have in a hierarchy.

CDSPECUSETP Captures information regarding the usage types the

spec will be used for.

CDSTATUSREASONTP Captures information regarding the reason the

product is in its current state.

CDSUSPECTREASONTP SUSPECT REASON TYPE describes the relevancy of

a potential suspect duplicate for a particular party

(contact). Examples include all elements matched,

first name, and last name.

CDSUSPECTSOURCETP SUSPECT SOURCE TYPE indicates how a potential

suspect duplicate was identified. Examples include

system marked and user marked.

CDSUSPECTSTATUSTP SUSPECT STATUS TYPE describes the current status

of the investigation into a potential suspect

duplicate. Examples include parties not duplicate,

critical change resolved, and more.

CDSUSPECTTP Allow the replacement of default suspect processing

logic with custom implementation. It also provides

hooks to integrate with 3rd party software to

perform suspect search and/or matching.

CDTAXPOSITIONTP Captures information regarding the relative tax

position offered by a product.

CDTERMINATIONREASONTP The code table that stores the termination reasons

for an agreement, such as Agreement Terms &

Conditions violation In case of a value package

breakage.

CDUNDELREASONTP UNDELIVERABLE REASON TYPE LOOKUP

contains information on the valid values for the

Undeliverable Reason Type Code. Some example

values are bad addresses and wrong zip codes.

CDVALFREQTP CDVALFREQTP is the table that holds information

about compliance validation frequency.

CHARGECARD CHARGE CARD RECORD is the charge card

information used to pay for one or more

CONTRACTs or accounts.

CLAIM Record claim information for a coverage that may be

insured in a contract. For example: Auto Claim,

break-in.

CLAIMCONTRACT Record a claim against a contract. For example:

Automobile, Homeowners and Whole Life insurance

policies.

CLAIMROLE Records to identify the role party plays on a claim

record. For example: Party 1 reported the broken

windshield, Party 2 at fault.

COMPLDOCUMENT COMPLDOCUMENT: Compliance Document is the

table that holds information about candidating

documents to validate the target.



Table name Comment

COMPLENTITY is the table that holds information about which

entity meets the compliance requirement.

COMPLENTITYDOC COMPLENTITYDOC is the table that holds

information about which document instances are

used to validate the target instance.

COMPLENTITYTARGET COMPLENTITYTARGET is the table that holds

information about target instance.

COMPLIANCEREQ COMPLIANCEREQ is the table that holds

information about compliance requirement.

COMPLTARGET COMPLTARGET: Compliance Target is the table that

holds information about the target need to be

validated.

CONDITIONATTRIBUTE TermCondition Entity can have attributes. When

condition has attributes added to it, it gains

″executable″ aspect, because attributes are used by

business rules to enforce the condition or to perform

some kind of calculation described by the condition.

CONTACT PARTY is any PERSON or ORGANIZATION that is

useful to keep track of in the system. This includes

CLIENTs (suspects, prospects and clients), CSRs,

AGENTs, competitors, contact persons, and anyone

else whose name/address/telephone and

relationship to anoth

CONTACTCDC CONTACTCDC hold the information of critical data

change on contact.

CONTACTDEMOGRAPHICS The table CONTACTDEMOGRAPHICS stores

various party demographic data for a party.

CONTACTMETHOD A type of LOCATION used for email addresses,

telephones, pagers, web sites, faxes and various and

sundry technologies available now and in the future

where a CLIENT can be contacted.

CONTACTMETHODGROUP CONTACT METHOD GROUP is a subtype of

LOCATION GROUP and links parties to addresses

and contains rules specific to using an address when

contacting a party.

CONTACTREL PARTY RELATIONSHIP represents the relationship

between two parties. For example:

v FROM CONTACT: ’Sue Smith’

v RELATIONSHIP: ’child of’

v TO CONTACT: ’Greg Smith’

CONTEQUIV PARTY EQUIVALENCY provides the link between

the InfoSphere MDM Server Party ID and the

administrative system, or back office, Party (or

client) native identification system.

CONTMACROROLE Represents a high-level role a party plays for being

in the system. For instance, the party may be

captured for being a prospect and as such its macro

role can be ″Prospect″.



Table name Comment

CONTRACT The full name of this entity is POLICY OR

ACCOUNT and it represents the ’purchase’ of a

PRODUCT. This purchase may include various

scenarios including a disability insurance plan, a

savings account, a GIC.

CONTRACTCOMPONENT CONTRACT COMPONENT contains information on

components of a contract such as base, riders, or

others. A contract component represents parts of a

contract - every contract must have at least one

component - representing the base component.

CONTRACTCOMPVAL CONTRACT COMPONENT VALUE provides a way

to model some numeric values on the Contract

Component. Since InfoSphere MDM Server is

customer centric and not product centric the value

presents a mechanism for implementers to extend

the information that can be associated with a

contract.

CONTRACTREL CONTRACT RELATIONSHIP represents the

relationship that an agreement can have with

another agreement.

CONTRACTROLE PARTY CONTRACT ROLE is an association that

links parties to the various roles they may have on a

contract.

CONTRACTROLEREL PARTY ROLE RELATIONSHIP is an association that

links party contract roles together. For example, a

role relationship would be used to determine which

custodian role is for which minor owner on a given

contract.

CONTSUMMARY CONTSUMMARY contains a summary view of a

contact record; specifically, it contains indicators that

track what information is stored about a particular

party.

DEFAULTSOURCEVAL DEFAULT SOURCE VALUE identifies the business

data element that was defaulted during data

collection/migration. For example, a date may be

incomplete in the source system and as a result must

be defaulted in order to provide the tCRM system

an accurate a

ENTITYCONDITIONREL This table stores the association between the

TermCondition and the entity represented by the

column ENTITY_NAME (PRODUCT / CONTRACT)

ENTITYCONTENTREFERENCE This table stores the content references of the content

assets stored in external CMS.

ENTITYROLE The ENTITY ROLE table stores information about

the role(s) a particular entity may play on a

particular collection (i.e., grouping, hierarchy,

party-to-party relationships).

ENTITYSPECUSE This table defines the way a spec will be used to

define an entity such as a product.

ENUMANSWER Enum answer identifies a possible answer of a

question. Enumanswer contains language

independent fields of the enumerated answer.



Table name Comment

FINANCIALPRODUCT Financial (such as banking) products that are a

hardened subtype of product.

GOODSPRODUCT Goods (physical) products that are a hardened

subtype of product.

GROUPING GROUP allows classifications of Parties into Groups.

GROUP allows entities, such as Party, to be

classified into groups. It also stores different group

types generated from other systems in the

enterprise.

GROUPINGASSOC Identify the Parties that belongs to a Party Group.

Identifies the entities, such as Party, which are

placed in a group

HIERARCHY It represents a hierarchy in the system.

HIERARCHYNODE HIERARCHY NODE represents a node in a

hierarchy.

HIERARCHYREL HIERARCHY RELATIONSHIP contains two

hierarchy nodes to represent their direct parent-child

relationship.

HIERARCHYULTPAR Identifies a node as the ultimate parent in a

hierarchy.

HOLDING PARTY HOLDING records a party’s personal

holdings. For example: A list of assets and liabilities

such as Vehicles, Dwellings and Mortgage.

IDENTIFIER PARTY IDENTIFIER in an additional way of

distinguishing a party that is natural to them. For

example, social security number, driver’s license

number, passport number, for example.

INACTIVATEDCONT INACTIVATED PARTY is a type of PARTY that is no

longer considered active to a company. When a

PARTY becomes inactive, modifications to the

INACTIVATED PARTY records are ended.

INACTIVECONTLINK INACTIVATED PARTY LINK maintains the linkage

from the active PARTY (target Party) to an

INACTIVATED PARTY (source Party). Its function is

to track parties that have been collapsed or split and

are now an INACTIVATED PARTY, and the link he

has with the new

INCOMESOURCE INCOME SOURCE, provided and attested to by the

party, provides the details of the PARTY’s

investment experience and financial standing used

in determining a PARTY’s suitability in purchasing a

new investment.

INSURANCEPRODUCT Insurance (related to the insurance vertical) products

that are a hardened subtype of product.

INTERACTION INTERACTION is the record of various

communications that a service center and a customer

service represent have had with a customer or notes

about a customer. The communication is always for

one customer and may optionally be in regards to a

TASK.



Table name Comment

INTERACTIONREL INTERACTION RELATIONSHIP shows the

relationships between different interactions. An

initial interaction can generated a series of

interactions with a customer.

LOBREL Represents the party ownership by a line of

business. For example: John Smith owned by Home

Insurance, Jane Doe owned by Retail banking, Jane

Doe owned by Life Insurance.

LOCATIONGROUP LOCATION GROUP links locations, such as

addresses and telephone numbers, to parties and

contains rules for use.

MACROROLEASSOC Represents an association between a party’s macro

role and its child data. For instance, as ″Prospect″

(macro role) the system may capture that party’s

email address (associated party child data) of

″[email protected]″.

MISCVALUE Record various values an institution measures on a

party or a group of parties. The value may be

associated to a particular contract role. It records

miscellaneous values that can be generated from

other systems in the enterprise or can be specific

details.

NATIVEKEY CONTRACT NATIVE KEY provides the link of the

InfoSphere MDM Server Contract ID to the

administrative system’s or back office systems native

key for a given contract.

NLSENUMANSWER NLSEnumanswer contains language dependent

fields of the enumerated answer.

NLSQUESTION NLSQuestion contains language dependent fields of

a question.

NLSQUESTIONNAIRE NLSQuestionnaire contains the language dependent

fields of Questionnaire.

ORG ORGANIZATION is a subtype of PARTY and

represents some form of legal entity other than a

human. This includes incorporated companies,

nonprofit organizations, sole-proprietorships,

partnerships, trusts, and more.

ORGNAME ORGANIZATION NAME contains the different

names that may be used by an organization.

PAYMENTSOURCE An abstract supertype for various payment source

types in the system such as bank account, charge

card or payroll deduction.

PAYROLLDEDUCTION Represents a person’s payroll deduction payment

source.

PERSON PERSON is a subtype of PARTY and represents a

human being.

PERSONNAME PERSON NAME contains the names that may be

used by a person.

PERSONSEARCH PERSON SEARCH contains the

standardized/non-standardized versions of the

PERSON NAME table to facilitate searching.

PHONENUMBER This table holds information of part’s phone number.



Table name Comment

PPREFACTIONOPT Stores the action types that are possible options for

each Privacy/Preference Type

PPREFDEF This table allow us to capture the default Privacy

information as well as default preferences setting (Y

or N).

PPREFDEFREL Defines the parent child relationship between two

Default Privacy Preference records

PPREFENTITY This table enables you to capture Privacy

information as well as preferences for a Party (Y or

N).

PPREFINSTANCE Identifies the entity instances that are associated

with the Privacy Preference record

PRIVPREF Store all Privacy and Preference records

PRODTPREL This table store the relationship type between two

product records. These relationships may be used in

combinations to provide a hierarchy of products

PRODUCT Instances of products that are of interest to the

business.

PRODUCTCATEGORYASSOC A product’s association to a category.

PRODUCTCONTRACTREL The table that holds the relationship between a

product and a contract.

PRODUCTEQUIV How a product is identified in a different system.

PRODUCTIDENTIFIER A client-defined identifier for the product such as a

part number or product code.

PRODUCTNLS PRODUCTNLS table is the localization table for the

table Product. ProductNLS entity could represent the

localization data of fields those needs to be

localized. Product content in localized form

PRODUCTREL A relationship between two products. Products can

be related together to capture product substitutes,

up-sells, cross-sells and so on. They can also be

related together to form bundles and coarser grain

products made up of product components.

PRODUCTTYPE A type of product that (unless is the root product

type) is a subtype of another product type.

PRODUCTTYPENLS PRODUCTTYPENLS table is the localization table

for the table ProductType. ProductTypeNLS entity

could represent the localization data of fields those

needs to be localized.

PRODUCTVAL A set of values based on a spec format. The values

decorate the product based on the product’s

association to some other entity such as the

product’s type. The values based on spec formats

associated to the product’s type are maintained in

this table.

PRODUCTVALNLS PRODUCTVALNLS table is the localization table for

the table ProductVal. ProductValNLS entity could

represent the localization data of fields those needs

to be localized. Product values content in localized

form.



Table name Comment

PROPERTY PROPERTY contains all HOLDING records that are

locations. For example: Cottage, Private Residence,

Secondary Residence, Condominium.

QUESTION QUESTION contains language independent fields of

a question.

QUESTIONNAIRE A questionnaire is comprised of a series of

Questions and Enum answers used to collect

information. QUESTIONNAIRE contains language

independent fields of a questionnaire.

ROLEIDENTIFIER ROLEIDENTIFIER provides an identifier to a party’s

specific role on a contract.

ROLELOCATION PARTYLOCATION is an association between a

Party’s roles on a contract to a particular location

group.

ROLELOCPURPOSE ROLELOCPURPOSE describes why contract

information for a particular role is addressed to a

defined location. The location can either be an

address or a contact method.

ROLESITUATION ROLESITUATION defines the different

arrangements that may be defined by a given party

contract role. For example, time delay, or common

disaster arrangements on life insurance policies.

SEARCHEXCLRULE This table provides the initial search exclusion

criteria (last name only, last & given name one only,

or last name & city only) for search transaction.

SERVICEPRODUCT Service (non-physical) products that are a hardened

subtype of product.

SPEC This table holds information about specs available in

the system.

SPECFMT This table holds all the various formats (or versions)

for the system’s specs.

SPECFORMATTRANSLATION This table holds locale specific translations for the

attribute names of specs

SUSPECT SUSPECT table contains all suspects (possible

duplicates) a particular party has within the

InfoSphere MDM Server database.

SUSPECTAUGMENT Contains the augmented suspect processing results

performed by the additional match engines

TERMCONDITION TERMCONDITION table represents a logical

condition, containing conditions for entities such as

Product and Agreement. TermCondition can be static

or executable.

TERMCONDITIONNLS TERMCONDITIONNLS table is the localization table

for the TERMCONDITION table. TermConditionNLS

entity represents the localization data of the fields

which need to be localized.

VEHICLE VEHICLE contains all HOLDING records that are

vehicles. For example: Mazda M3, Subaru Outback,

or Honda Civic.



ACCESSDATEVAL Table

Column Name Comment Datatype Null Option Is PK

acc_date_val_id A unique, system

generated key that

identifies a default

object row in the IBM

InfoSphere Master Data

Management Server

system.

BIGINT NOT NULL Yes

instance_pk The actual primary key

of the row in the logical

entity.

BIGINT NOT NULL No

entity_name The name of the

business entity.

VARCHAR(20) NOT NULL No

col_name The actual name of the

column where the

default occurred.

VARCHAR(20) NULL No

description A description of the

record.

VARCHAR(1000) NULL No

last_update_dt When a record is added

or updated, this field is

updated with the date

and time. On

subsequent updates,

InfoSphere MDM Server

uses this information to

ensure that the update

request includes a

matching date and time

on this field; if it does

not, the update fails.

TIMESTAMP NOT NULL No

last_update_user The ID of user who last

updated the data. Either

the user ID or user

group must be passed

in the XML header if

security or RoV is

turned on.

VARCHAR(20) NULL No

last_update_tx_id A unique, system

generated key that

identifies the specific

transaction within the

log system that either

created, updated, or

deleted the data row.

BIGINT NULL No

last_used_dt The date that this data

was last used. There is

no business logic

associated with this

field.

TIMESTAMP NULL No




last_verified_dt The date that this data

was last verified. There

is no business logic


field.

TIMESTAMP NULL No

ADDACTIONTYPE Table


add_action_id A unique, system

generated key that

identifies an add action

row in the IBM


Management Server

system.

BIGINT NOT NULL Yes

match_relev_tp_cd Identifies the Party

(CONTACT) match

relevancies - scores and

descriptions.

BIGINT NOT NULL No

susp_reason_tp_cd Describes the critical

data that was

considered ″matched″

between two particular

party (contact) records

during suspect

processing. Examples

include all elements

matched (first name, last

name, and others).

BIGINT NOT NULL No

org_tp_cd Identifies the

classification of the

organization. For

example: trust,

company, charity, estate,

and others.

BIGINT NULL No

person_org_code Indicates the type of

party - person or

organization.

CHAR(1) NOT NULL No

add_action_code Identifies the action

taken as a result of

suspect identification.

CHAR(2) NOT NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

suspect_tp_cd Suspect Type code

captures various suspect

types. One record exists

for each unique

add_action_code in the

addactiontype table.

BIGINT NULL No

ADDRESS Table


address_id A unique, system

generated key that

identifies an address in

the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes

country_tp_cd Identifies a country. BIGINT NULL No

residence_tp_cd A type of residence for a

given address. Some

examples include Home,

Apartment and Suite.

BIGINT NULL No

prov_state_tp_cd Identifies the US States,

US Possessions, US

military oversea

locations, and foreign

countries provinces. For

overseas military

locations, APO or FPO

designation along with

a two character ″state″

abbreviation of AE, AP,

or AA.

BIGINT NULL No

addr_line_one The first line of an

address.


p_addr_line_one The phonetic

representation of the

first line of an address.

Not currently used.

CHAR(8) NULL No

addr_line_two The second line of an

address.





p_addr_line_two The phonetic


second line of an

address. Not currently

used.

CHAR(8) NULL No

addr_line_three The third line of an

address.


p_addr_line_three The phonetic


third line of an address.

Not currently used.

CHAR(8) NULL No

city_name The city of an address. VARCHAR(50) NOT NULL No

postal_code Postal Code (Zip Code)

is used by the postal

system to uniquely

identify an address

location.

VARCHAR(20) NULL No

addr_standard_ind Indicates whether this

address be

standardized.

CHAR(1) NULL No

override_ind Indicates whether the

address standardization

process should be

overridden.

CHAR(1) NULL No

residence_num The apartment, suite, or

unit number of the

address.

VARCHAR(10) NULL No

county_code A three-digit postal code

used to identify the

county of the post

office.

CHAR(3) NULL No

latitude_degrees Latitude of Measure in

Degrees identifies an

angular distance north

or south. Latitude

Degrees is useful for

Mapping Software (for

example, to identify the

nearest doctors office).

VARCHAR(10) NULL No

longitude_degrees Longitude of Measure in

Degrees identifies an

angular distance east or

west. Longitude Degrees

is useful for Mapping

Software (for example,

to identify the nearest

doctors office).

VARCHAR(10) NULL No

p_city The phonetic key for

City.

VARCHAR(20) NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

postal_barcode The structure of the 12

digits postal bar code is

as follows:

v 5 digits for the ZIP

code.

v 4 digits for the ZIP+4

code.

v 2 digits representing

the last 2 digits of the

street address.

v 1 digit checksum

calculated as the sum

of the other digits

modulo 10

VARCHAR(30) NULL No

building_name The name of the

building.

VARCHAR(64) NULL No

street_number The street number of

the building. For

example: ″55″ in the

address ″55 Main Road

East″.

VARCHAR(16) NULL No

street_name The name of the street.

For example: ″Main″ in

the address ″55 Main

Road East″.

VARCHAR(64) NULL No

street_suffix The type of street. For

example: ″Road″ in the


East″.

VARCHAR(64) NULL No




pre_directional A directional element of

the address.

VARCHAR(16) NULL No

post_directional A directional element of

the address. For

example: ″East″ in the


East″.

VARCHAR(16) NULL No

box_designator Box designator. VARCHAR(16) NULL No

box_id Box identifier. VARCHAR(16) NULL No

stn_info Station information. VARCHAR(16) NULL No

stn_id Station identifier. VARCHAR(16) NULL No

region Further qualification of

area, in addition to City.

VARCHAR(32) NULL No

del_designator Delivery designator. VARCHAR(16) NULL No

del_id Delivery identifier. VARCHAR(16) NULL No

del_info Additional delivery

information.

VARCHAR(50) NULL No

ADDRESSGROUP Table


location_group_id A unique, system

generated key that

identifies a location

group row in the IBM


Management Server

system.

BIGINT NOT NULL Yes


generated key that


the IBM InfoSphere

Master Data

Management Server

system.

BIGINT NOT NULL No

care_of_desc In Care of Description is

placed above the

recipient line. It contains

information such as a

specific person or

department to provide

additional information,

facilitating delivery.

VARCHAR(50) NULL No

addr_usage_tp_cd Address Usage Type

Code identifies the

usage of an address

provided by a party.

Examples include

residence address,

business address, and

others.

BIGINT NOT NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

AGREEMENTSPECVAL Table


agreement_spec_val_id A system generated key

that uniquely identifies a

set of contract related spec

values.

BIGINT NOT NULL Yes

spec_id The spec that describes the

definition of the spec

values.

BIGINT NOT NULL No

spec_fmt_id The format (or version) of

the spec these spec values

validate to.

BIGINT NOT NULL No

entity_name The type of entity with

which the spec values are

associated. The types of

entities are expected to be

contract related.


instance_pk The primary key of the

related entity.

BIGINT NOT NULL No

value_xml The spec values as defined

by the associated spec

format.

XML NOT NULL No

start_dt The date the spec values

become effective.





end_dt The date the spec values are

no longer effective.

TIMESTAMP NULL No

last_update_dt When a record is added or

updated, this field is

updated with the date and

time. On subsequent

updates, InfoSphere MDM

Server uses this information

to ensure that the update

request includes a matching

date and time on this field;

if it does not, the update

fails.



updated the data. Either the

user ID or user group must

be passed in the XML

header if security or RoV is

turned on.

VARCHAR(20) NULL No

last_update_tx_id A unique, system generated

key that identifies the

specific transaction within

the log system that either

created, updated or deleted

the data row.

BIGINT NULL No

ALERT Table


alert_id A unique, system

generated key that

identifies an alert row in

the IBM InfoSphere

Master Data

Management Server

system.

BIGINT NOT NULL Yes


business entity that has

the alert or restriction.


instance_PK The actual primary key


entity that has the alert.

BIGINT NOT NULL No

removed_by_user The ID of user who

removed the alert.

VARCHAR(20) NULL No

created_by_user The ID of user who

created the alert.

VARCHAR(20) NULL No

alert_tp_cd Uniquely identifies the

type of alert placed on

the party. Examples of

alert types are ″court

order pending,″ ″divorce

pending,″ ″officer of the

company,″ and others.

BIGINT NOT NULL No




alert_sev_tp_cd An identifier that

uniquely separates one

type of alert severity

from another. Examples

include red, yellow and

green.

BIGINT NULL No

start_dt The date that this row

of data became valid.


end_dt The date that this row

of data became invalid.

TIMESTAMP NULL No

description Provides extra

information that can be

used either as an

additional definition of

the type code value or

as free form comments

used by the user to

provide further meaning

to the type code.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

ANSWER Table

Name Datatype Null Option Comment Is PK

answer_id BIGINT NOT NULL The primary key of

the answer record.

Yes




answer_set_id BIGINT NOT NULL The answer set id

that this answer

belongs to.

No

question_id BIGINT NOT NULL The question id that

this answer relative

to.

No

answer_index SMALLINT NULL Answer index. No

enum_ans_id BIGINT NULL Enum answer id that

this answer referred.

No

answer VARCHAR(120) NULL Answer text. No

recorded_dt TIMESTAMP NOT NULL Specifies the date

when this record

recorded.

No

last_update_dt TIMESTAMP NOT NULL Last Update Date is

used for technical

reasons; whenever a

record is updated,

this field is updated

with the date and

time. Ex. If 2 people

are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make

sure it hasn’t changed

(ie updated) since it

was retrieved,and

then allow the update

to go through. It is a

sort of record locking,

this way only one

user can update at a

time.

No

last_update_user VARCHAR(20) NULL Id of user who last

updated the data.

Either user ID or user


in the XML header, if

security/ROV is

turned on.

No

last_update_tx_id BIGINT NULL Transaction ID is a

unique, system

generated key that




created, updated or


No



ANSWERSET table


answer_set_id BIGINT NOT NULL The primary key of

the answer set record.

Yes

quesnr_id BIGINT NOT NULL The questionnaire

that this answerset

relative to.

No

lang_tp_cd BIGINT NOT NULL Language type code. No

answer_party VARCHAR(255) NULL The party id

identifies the party

who recorded this

answerset .

No

entity_name VARCHAR(20) NULL Entity Name is the

name of the physical

business entity which

this answer regarding

to.

No

instance_pk BIGINT NULL Entity Instance

Primary Key is the

actual primary key of

the row in the logical

entity which this

answer regarding to.

No

start_dt TIMESTAMP NOT NULL Specifies the date

when this record in

takes effect.

No

end_dt TIMESTAMP NULL Specifies the date

when this record

becomes inactive.

No


used for technical

reasons; whenever a

record is updated,


with the date and


are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make



was retrieved,and




this way only one


time.

No





updated the data.




security/ROV is

turned on.

No


unique, system

generated key that




created, updated or


No

BANKACCOUNT Table


payment_source_id A unique, system

generated key that

identifies a payment

source in the InfoSphere

MDM Server system.

BIGINT NOT NULL Yes

acct_tp_cd The type of bank

account provided by the

party. Some examples

are checking, savings,

etc.

BIGINT NOT NULL No

acct_num The alphanumeric

identifier assigned to

the bank account that

uniquely identifies it for

that given institution.


recorded_open_dt The date on which the

bank account was

actually opened, or

recorded as opened.

TIMESTAMP NULL No

recorded_closed_dt The date on which the

bank account was

actually closed, or

recorded as closed.

TIMESTAMP NULL No

branch_num The local office, or

branch, identifier used

by the bank to identify

that location of the

account.


bank_num A unique identifier for

the bank, assigned

outside of InfoSphere

MDM Server





depositor_name The Party’s name as

printed on a check (the

account registration

name).





and time. On

subsequent updates,



request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

BILLINGSUMMARY Table


billing_summary_id A unique ID generated

by the system to

identify a billing

summary in InfoSphere

MDM Server system.

BIGINT NOT NULL Yes

billing_st_tp_cd A unique type code

which uniquely defines

a billing status value.

Some examples are

closed, paid, and others.

BIGINT NOT NULL No

pymt_mthd_tp_cd A type code which

uniquely identifies a

payment method value

in the system. This

represents the next

payment method type.

Some examples are bank

account, charge card,

cash, and others.

BIGINT NULL No




last_py_md_tp_cd A type code which



in the system. This

represents the last

payment method type.

Some examples are bank


cash, and others.

BIGINT NULL No

effective_date The date from which

this billing summary is

effective.

TIMESTAMP NULL No

due_date The due date for this

billing summary.

TIMESTAMP NULL No

account_balance The total outstanding

balance.

DECIMAL(17,3) NOT NULL No

min_payment The minimum payment

required for this billing

summary.

DECIMAL(17,3) NULL No

max_payment The maximum payment

allowed for this billing

summary.


paid_to_date The date up to which

the account or contract

has been paid.

TIMESTAMP NULL No

invoice_id Links this billing

summary to an invoice;

external to InfoSphere

MDM Server system.

VARCHAR(50) NULL No

bill_from_date The start date of the

billing period of this

billing summary.

TIMESTAMP NULL No

bill_to_date The end date of the

billing period of this

billing summary.

TIMESTAMP NULL No

account_id An account ID is a free

form specific means by

which the account can

be distinguished from

all other accounts.

VARCHAR(50) NULL No


generated key that



MDM Server system.

BIGINT NULL No

withdrawal_date The date on which

payment will be

withdrawn from a

payment source for this

billing summary.

TIMESTAMP NULL No

last_payment_amt The amount paid or

withdrawn against the

last billing summary.





last_payment_dt The date when payment

was last received.

TIMESTAMP NULL No

payments_remaining The number of

payments remaining.

INTEGER NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

freq_mode_tp_cd The frequency of the

payments made on the

contract. Some examples

are monthly, annual,

and others.

BIGINT NULL No

contract_id A unique, system

generated key that

identifies a contract in

the InfoSphere MDM

Server system.

BIGINT NULL No

contr_component_id A unique, system

generated key that

identifies a contract

component in the


system.

BIGINT NULL No

accbala_cur_tp The currency type for

the account balance.

BIGINT NULL No

minpaym_cur_tp The currency type for

the minimum payment.

BIGINT NULL No

maxpaym_cur_tp The currency type for

the maximum payment.

BIGINT NULL No

lastpay_cur_tp The currency type for

the last payment.

BIGINT NULL No



CAMPAIGN Table


campaign_id The primary key of a

campaign record.

BIGINT NOT NULL Yes

campaign_tp_cd A numeric


campaign for customer.

BIGINT NULL No

campaign_source The source of the

campaign record.


name A short, meaningful

label for the Campaign.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No



TIMESTAMP NULL No

created_dt The date that the row

was created.




the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No




and time. On

subsequent updates,




request includes a






generated key that




created, updated or


BIGINT NULL No




priority_tp_cd The priority of a task, a

campaign, a value, and

so on. Examples include

high, medium, low.

BIGINT NULL No

CAMPAIGNASSOCIAT Table


campaignassoc_id The primary key of

Campaign Group

record.

BIGINT NOT NULL Yes


business entity that is

associated with the

Campaign.


instance_Pk The actual primary key


entity that is associated

with the Campaign.

BIGINT NOT NULL No

campaign_id The primary key of a

campaign record.

BIGINT NOT NULL No

associate_ind Identifies whether this is

a target association or

regarding association.

CHAR(1) NULL No






TIMESTAMP NULL No



the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No




and time. On

subsequent updates,




request includes a









generated key that




created, updated or


BIGINT NULL No

CATEGORY Table

Name Comment Datatype Null Option Is PK

category_id A unique,

system-generated key

that identifies a category

row in the InfoSphere

MDM Server system.

BIGINT NOT NULL Yes

cat_hierarchy_id A unique,



hierarchy row in the


system.

BIGINT NOT NULL No

category_code An identifier for a

category within a

particular hierarchy.


name Name is a short,

meaningful label for the

category


description Description provides

extra information, which

can be used either as an

additional definition as

free form comments

used by the user to


to the category


is_root Indicates that the

category is root in the

hierarchy (ultimate

parent)

CHAR(1) NOT NULL No

is_leaf Indicates if the category

may have subcategories

or not.

CHAR(1) NOT NULL No

assoc_ind Indicates if the category

permits associations to

be made with it (i.e.,

product-category)

CHAR(1) NOT NULL No

start_dt Specifies the date when

this record in takes

effect.





end_dt Specifies the date when

this record becomes

inactive

TIMESTAMP NULL No




and time. On

subsequent updates, the


system uses this

information to ensure

that the update request

includes a matching

date and time on this

field; if it does not, the

update fails.




the user ID or the user



security or ROV is

turned on.

VARCHAR(20) NULL No

last_update_tx_id Transaction ID is a

unique, system

generated key that




created, updated or


BIGINT NULL No

CATEGORYNLS Table


category_nls_id A unique,



localized NLS row in

the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes

category_id The primary key of the

NLS category record.

BIGINT NOT NULL No

lang_tp_cd Language type code. BIGINT NOT NULL No

name Localized name for the

category name.


description Localized description

for the category

description.





last_update_dt Whenever a record is

added/updated, this

field is updated with

the date and time. On

subsequent updates, we

utilize this information

to ensure that the

update request includes

a matching date/time




last_update_user Id of user who last


user ID or user group

must be passed in the

XML header, if

security/RoV is turned

on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

CATEQUIV Table


cat_equiv_id A unique,



equivalency row in the


system.

BIGINT NOT NULL Yes

category_id A unique,



in the InfoSphere MDM

Server system.

BIGINT NOT NULL No

admin_sys_tp_cd Administration System

Code uniquely identifies

the administrative

source system for a

contract. Examples

include Ingenium,

Alltel, Huon, etc.

BIGINT NOT NULL No

cat_equiv_key A key, or id, that

uniquely identifies the

category in the

administrative source

system.





key_1 A partial key, which in

conjunction with other

keys, identifies the

category in the


system.





category in the


system.

VARCHAR(30) NULL No




category in the


system.

VARCHAR(30) NULL No




category in the


system.

VARCHAR(30) NULL No




category in the


system.

VARCHAR(30) NULL No


added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No



CATHIERARCHY Table


cat_hierarchy_id A unique,



hierarchy row in the


system.

BIGINT NOT NULL Yes



category hierarchy.





additional definition as

free form comments

used by the user to


to the category

hierarchy.


hierarchy_tp_cd Code indicating

referencing category

hierarchy type (code

table).

BIGINT NULL No



effect



this record becomes

inactive

TIMESTAMP NULL No


added/updated, this





to ensure that the







unique, system

generated key that




created, updated or


BIGINT NULL No








XML header, if


on.

VARCHAR(20) NULL No

CATHIERARCHYNLS Table


cat_hierarchy_nls_id A unique,



hierarchy NLS row in

the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes

cat_hierarchy_id The primary key of the

NLS category hierarchy

record.

BIGINT NOT NULL No

lang_tp_cd Language type code. BIGINT NOT NULL No

name Localized name for the

category hierarchy

name.


description Localized description

for the category

hierarchy description.



added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No



CATNODEREL Table


cat_node_rel_id A unique,



node relationship row in

the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes

parent_node_id The primary key

(category_id) of the

parent hierarchy node

record

BIGINT NOT NULL No

child_node_id The primary key

(category_id) of the

child hierarchy node

record

BIGINT NOT NULL No



effect.



this record becomes

inactive

TIMESTAMP NULL No


added/updated, this





to ensure that the







unique, system

generated key that




created, updated or


BIGINT NULL No





XML header, if


on.

VARCHAR(20) NULL No



CDACCETOCOMPTP Table


lang_tp_cd Identifies a spoken

language, such as

English, French,

Spanish, or German.

When used as part of

the primary key of a

code value lookup table,

the Language Type

Code also represents the

language of the code

name.

BIGINT NOT NULL Yes

acce_comp_tp_cd Represents one of the

various types of access a

party may have to a

computer and related

technologies.

BIGINT NOT NULL Yes


label for the value of the

type code.




used either as an




used by the user to


to the type code.


expiry_dt The date that the type

code is no longer valid.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDACCOUNTREQUIREDTP Table


lang_tp_cd Language Type Code

identifies a spoken

language. For example,

English, French,

Spanish, etc. When used

as part of the primary

key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

account_required_tp_cd Indicates whether the

product requires an

account or not.

BIGINT NOT NULL Yes



value of the type code.








used by the user to


to the type code.


expiry_dt Expiry Date represents

the date that the type


TIMESTAMP NULL No


added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No



CDACCOUNTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

acct_tp_cd Identifies the type of

bank account provided

by the party. Some

examples are checking,

savings, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDACTIONADJREASTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

adj_action_tp_cd Action Type Adjusted

Reason Type Code

identifies the business

reasons for the action

code on the suspect

identification being

modified.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDADDRUSAGETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

addr_usage_tp_cd Identifies the usage of

an address provided by

a party.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDADMINFLDNMTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

admin_fld_nm_tp_cd Identifies the field name

that the native key

refers to, for example,

policy number, policy

suffix, account number,

branch, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.


admin_sys_tp_cd Uniquely identifies the


system for a contract.

Examples include

Ingenium, Alltel, Huon,

and others.

BIGINT NOT NULL No

size_num The length or number of

digits used by the

native key field.

NUMERIC(2,0) NULL No

datatype_name The name of the

datatype for the native

key field.

VARCHAR(40) NULL No

displayed_ind Indicates whether this is

the native key field to

be displayed to the user.

CHAR(1) NULL No

present_seq_num The order by which the

contract’s administrative

source system

understands the native

key fields.

SMALLINT NULL No



TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDADMINSYSTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes




Examples include


and others.

BIGINT NOT NULL Yes

native_key_tot The total number of

identifying fields used

in the administrative

source system to

uniquely point to a

contract record.

SMALLINT NULL No



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDAGEVERDOCTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

age_ver_doc_tp_cd An identifier that


type of document being

used to verify a client’s

age from another.

Examples include birth

certificate, driver’s

license, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDAGREEMENTSTTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

agreement_st_tp_cd Identifies the status of

the contract. These

values are provided by

the administrative

source systems of the

contract. For example, a

bank might have the

contract status types

active, pending, lapse

pending, and cancelled.

BIGINT NOT NULL Yes



type code.








used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDAGREEMENTTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

agreement_tp_cd Describes the type of

the contract. Some

examples include: Value

Package, Supplier

Agreement

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDALERTCAT Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

alert_cat_cd Identifies the high level

classification of alerts on

a business object. For

example: complaint,

court order, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDALERTSEVTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

alert_sev_tp_cd An identifier that


type of alert severity

from another.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDALERTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

alert_tp_cd Uniquely identifies the

type of alert, within a

particular alert category.

For example: divorce

pending, court order,

office of the company,

and others.

BIGINT NOT NULL Yes

alert_cat_cd Identifies the high level

classification of alerts on

a business object. For

example: complaint,

court order, and others.

BIGINT NOT NULL No



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDARRANGEMENTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

arrangement_tp_cd Describes the type of

agreement that the party

contract role has with

the contract. For

example: time delay

arrangement such as a

common disaster.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDAVAILABILITYTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

availability_tp_cd The availability status of

the product with respect

to its target market.

Determines whether the

product is generally

available, or has

restricted availability.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No

CDBILLINGSTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

billing_st_tp_cd A unique type code


a billing status value.

Some examples are

closed, paid, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDBILLTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

bill_tp_cd An identifier that


billing type from

another. Examples

include Regular, Direct,

Payroll deduction, and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDBUYSELLAGREETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

buy_sell_agr_tp_cd An identifier that


type of buy-sell

agreement from another.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCAMPAIGNTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

campaign_tp_cd A numeric


campaign for customer

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCDCREJREASONTP Table


LANG_TP_CD Language Type Code

identifies a spoken

language such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

REJ_REASON_TP_CD The reason for which a

critical data change has

been rejected.

BIGINT NOT NULL Yes

NAME The Name is a short,




DESCRIPTION The Description

provides extra


used either as an




to provide further

information about the

type code.


EXPIRY_DT The Expiry Date

represents the date on

which the type code

will no longer be valid.

TIMESTAMP NULL No




LAST_UDPATE_DT When a record is added



and time. On

subsequent updates,




request includes a





CDCDCSTTP Table


LANG_TP_CD Language Type Code

identifies a spoken

language such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

CDC_ST_TP_CD The CDC Status type

code indicates the status

of the critical data

change request.

BIGINT NOT NULL Yes

NAME The Name is a short,




DESCRIPTION The Description

provides extra


used either as an




to provide further


type code.


EXPIRY_DT The Expiry Date


which the type code


TIMESTAMP NULL No




LAST_UDPATE_DT When a record is added



and time. On

subsequent updates,




request includes a





CDCHARGECARDTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

charge_card_tp_cd Identifies one type of

charge card from

another. Some examples

are Visa, MasterCard,

American Express, and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCLAIMROLETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

claim_role_tp_cd A type of role a party

plays on a claim. Some

examples include

Claimant, Witness and

Third Party.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCLAIMSTATUSTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

claim_status_tp_cd Identifies the status of a

claim. Some examples

include Pending, Closed

and Rejected.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCLAIMTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

claim_tp_cd The type of claim that is

recorded. Some

examples include Fire,

Theft, Automobile,

Collision and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCLIENTIMPTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

client_imp_tp_cd An identifier that


client importance type


include high, medium,

and low.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCLIENTPOTENTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

client_poten_tp_cd An identifier that


client potential type

from another. For

example, an insurance

provider might have the

potential types ″client″,

″prospect″ and

″non-potential″.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.


expiry_dt The date upon which

given client potential

type is no longer valid.

TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCLIENTSTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

client_st_tp_cd An identifier that


client status type from

another. For example, a

telecommunications

company might have

the client status types

″active″, ″inactive″, and

″pending″.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDCOMPLCATTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

compl_cat_cd Compliance Category

Code identifies the high

level classification of

compliance requirement

on a business object.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDCOMPLDOCTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

compl_doc_tp_cd Compliance Document

Type Code uniquely

identifies the type of

Compliance Document.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDCOMPLIANCETP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

compl_tp_cd Compliance Type Code

uniquely identifies the

type of compliance, it

could be within a

particular compliance

category.

BIGINT NOT NULL Yes





compl_cat_cd Compliance Category

Code identifies the high

level classification of


on a business object.

BIGINT NULL No







used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDCOMPLTARGETTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

compl_target_tp_cd Compliance Target Type

Code uniquely identifies

the type of Compliance

Target.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDCONDITIONATTRIBUTETP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

condition_attr_tp_cd Describes the attribute

type of the condition.

For example : ″Core

Account Type″, ″Status″,

″Interest Rate″

BIGINT NOT NULL Yes

condition_usage_tp_cd Describes the usage

types for a condition.

For example : ″Value

Package Integrity″,

″Rate″, ″Fee″, ″Balance″

BIGINT NOT NULL No











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDCONDITIONOWNERTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

condition_owner_tp_cd Identifies the owner of

the condition.

BIGINT NOT NULL Yes



type code.








used by the user to


to the type code.





TIMESTAMP NULL No


added/updated, this





to ensure that the








CDCONDITIONUSAGETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

condition_usage_tp_cd Describes the usage

types for a condition.

For example: ″Value

Package Integrity″,

″Rate″, ″Fee″, ″Balance″.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.


expiry_dt The date on and after

which the type code is

no longer valid.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





rule_id The column represents

associated ruleId

VARCHAR(10) NULL No



CDCONTMETHCAT Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

cont_meth_cat_cd Identifies the type of

contact method. For

example: telephone,

e-mail, PDA, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCONTMETHTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

cont_meth_tp_cd Identifies the subtypes

of a Contact Method

Category Type Code.

For example, if the

category type is

telephone, then the

values of the subtype

code are home,

business, cell phone,

and others.

BIGINT NOT NULL Yes

cont_meth_cat_cd Identifies the type of

contact method. For

example: telephone,

e-mail, PDA, and others.

BIGINT NOT NULL No



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCONTRACTRELSTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

contr_rel_st_tp_cd Identifies the status of

the relationship between

two contracts, for

example, ″pending,″

″active,″ and

″terminated.″

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCONTRACTRELTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

contr_rel_tp_cd Describes the type of a

relationship. Reciprocal

in nature, examples

include child/parent

and supports/supported

by.

BIGINT NOT NULL Yes

to_from_name A short, meaningful

label for the ″to″ value

of the relationship.


from_to_name A short, meaningful

label for the ″from″

value of the

relationship.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCONTRACTROLETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

contr_role_tp_cd Contract Role Type

Code identifies the type

of role that a party may

have on a contract. For

example, an insurance

provider might have the

contract role types

″beneficiary,″ ″owner,″

″insured,″ and ″payer″.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCONTRACTSTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

contract_st_tp_cd Identifies the status of

the contract. These

values are provided by

the administrative

source systems of the

contract. For example, a

bank might have the

contract status types

″active,″ ″pending,″

lapse pending,″ and

″cancelled″.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCONTRCOMPTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

contr_comp_tp_cd A numeric


type of coverage for the

product.

For example:

v Base

v Rider

v Base Increase

v Integrated

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDCOUNTRYTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

country_tp_cd Identifies a country. BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





iso_code This field contains codes

for the names of

countries and

dependent territories as

published by the

International

Organization for

Standardization (ISO)

CHAR(2) NULL No



CDCURRENCYTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

currency_tp_cd Identifies the currency

of the amount columns.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





currency_code Captures the standard

currency code for each

currency.

CHAR(3) NULL No



CDDEMOGRAPHICSTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

demographics_tp_cd The Demographics ID

identifies the type of the

demographics record.

BIGINT NOT NULL Yes

name The name of the

demographics type.


spec_id The ID of the Spec used

for the demographics

type.

BIGINT NULL No

description The description of the

demographics type.





TIMESTAMP NULL No


added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No



CDDOMAINTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

domain_tp_cd Defines the types of

values can be stored.

Examples include

Integer, String, Decimal,

Date, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDDOMAINVALUETP Table


domain_value_tp_cd Domain Value Type

Code, in a given

domain, identifies the

specific values that are

captured.

For example: Integer

value, Date value, and

others.

BIGINT NOT NULL Yes


language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

prod_tp_cd Product Type Code


product associated with

the contract (or at some

level within the product

family). Examples

include Universal Life,

Savings, Checking, Term

Life, Auto, and others.

BIGINT NULL No



type code.


domain_tp_cd Defines the types of

values can be stored.

Examples include

Integer, String, Decimal,

Date, and others.

BIGINT NOT NULL No



used either as an




used by the user to


to the type code




TIMESTAMP NULL No




precision_value Defines the Value String

attribute in the Contract

Component Value by

identifying the number

of digits to be expected

for that given Value

Type Code.

SMALLINT NULL No




and time. On

subsequent updates,




request includes a





CDENDREASONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

end_reason_tp_cd Identifies the cause for

why a relationship was

ended. For example, a

spousal party to party

relationship may be

ended for a ″divorce,″

reason.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDENUMANSWERCATTP Table


enum_ans_cat_tp_cd Enum answer category

type code.

BIGINT NOT NULL Yes

lang_tp_cd Language type code. BIGINT NOT NULL Yes

name The name or value of

enum answer category

type.








used by the user to


to the type code.


expiry_dt The expiry date of the

code table record.

TIMESTAMP NULL No

last_update_dt The last update date of

current record.


CDENUMANSWERTP Table



enum_ans_tp_cd Enum answer type

code.

BIGINT NOT NULL Yes

enum_ans_cat_tp_cd The enumerated answer

category type code

BIGINT NULL No


enumerated answer

type











used by the user to


to the type code.



code table record.

TIMESTAMP NULL No


current record.


CDFREQMODETP Table



language Such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

freq_mode_tp_cd Identifies the frequency

of the payments made

on the contract.

For example: monthly,

annual, weekly, daily, or

other.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDGENERATIONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

generation_tp_cd Identifies the party’s

designated suffix.

Examples include ″the

first″, ″junior″, and so

on.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDGROUPINGCATTP Table



identifies a spoken

language such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

group_cat_tp_cd The Group Category

Type Code identifies the

category code type of a

grouping.

BIGINT NOT NULL Yes

name The Name is a short,




description The Description

provides extra


used either as an




to provide further


type code.


expiry_dt The Expiry Date


which the type code


TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDGROUPINGTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

grouping_tp_cd Identifies the code type

of a Group, or

classification associating

a number of like

entities, such as parties.

BIGINT NOT NULL Yes

grouping_cat_tp_cd Identifies the category

code type for a

grouping.

BIGINT NULL No


label for the node value.

The name of the group

type, such as Platinum

group.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDHIERARCHYCATTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

hier_cat_tp_cd Identifies the category

code type of a hierarchy.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDHIERARCHYTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

hierarchy_tp_cd Identifies the code type

of a hierarchy.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





hier_cat_tp_cd Identifies the category

code type of a hierarchy.

BIGINT NULL No

CDHIGHESTEDUTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

highest_edu_tp_cd Identifies the highest

level of schooling that

this person has received.

For example: high

school, college,

university, or

postgraduate.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDHOLDINGTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

hold_tp_cd Identifies a type of

party holding. For

example: Vehicles,

Property, Stocks, or

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDIDSTATUSTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

id_status_tp_cd Identifies the status of

the identifier provided

by the party. For

example: ″applied for,″

″expired,″ ″certified,″

and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDIDTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

id_tp_cd Identifies the type of

identifier provided by

the party. For example:

″social security number,″

″passport,″ ″driver’s

license number,″ and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





max_allowed_num maximum allowed

number

SMALLINT NULL No

CDINACTREASONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

inact_reason_tp_cd Identifies the reason for

the party information

being inactivated. For

example: splitting or

collapsing of party

records.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.



code is no longer valid

TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDINCOMESRCTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

income_src_tp_cd Identifies the type of

income source that the

party provided. For

example: ″annual

salary,″ ″estimated net

worth,″ ″Ownership of

Bonds,″ and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDINDUSTRYTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

industry_tp_cd Represents the industry

type for the

organization. Examples

include SIC, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDINTERACTIONCAT Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

interact_cat_cd Identifies the high level

category of the

interaction with the

customer. For example:

marketing initiative,

complaint, cold call, and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDINTERACTIONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

interact_tp_cd Identifies the type of


customer. The

Interaction SubType

Code is dependent on

the Interaction Category

Code. Some example

values are campaign,

incorrect billing, and

others.

BIGINT NOT NULL Yes

interact_cat_cd Identifies the high level

category of the customer

service representative’s



marketing initiative,

complaint, cold call, and

others.

BIGINT NOT NULL No



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDINTERACTPTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

interact_pt_tp_cd Identifies the media

through which the

interaction was made

possible. Some examples

are telephone, e-mail,

mail, and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDINTERACTRELTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

interact_rel_tp_cd Describes the type of

relationship that one

interaction can have

with another, such as a

follow-up or escalation.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDINTERACTRESPTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

interact_resp_tp The type of response for

an interaction.

BIGINT NOT NULL Yes



value of the

relationship.




used either as an




used by the user to


to the type code.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDINTERACTSTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

interact_st_tp_cd Describes the status of

the interaction. Some

examples are ’Awaiting

reply’, ’Returned’, ’No

answer’

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDLANGTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a








locale Captures the locale

string for the language

record.

VARCHAR(20) NULL NO

code_table_translation Indicates whether


provides the code table

translation for the given

language and locale.

CHAR(1) NULL NO

CDLINKREASONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

link_reason_tp_cd Describes the reason

why two parties are

linked. For example:

″Source collapsed into

target″, ″Source

duplicated as target″,

and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDLOBRELTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

lob_rel_tp_cd Identifies the unique

type code for a specific

line of business

relationship type.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDLOBTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

lob_tp_cd Identifies the unique


line of business.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDMARITALSTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

marital_st_tp_cd Identifies the marital

status of a person. For

example: single,

widowed, divorced, and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDMATCHENGINETP Table



identifies a spoken

language such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

match_eng_tp_cd The Matching Engine to

use for matching

parties.

BIGINT NOT NULL Yes

name The Name is a short,




description The Description

provides extra


used either as an




to provide further


type code.


expiry_dt The Expiry Date


which the type code


TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDMATCHRELEVTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

match_relev_tp_cd Identifies party match

relevancies, providing a

description of which

elements were matched.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.


relevency_score The score associated

with a match relevancy

type.

For example: LNAME

score = 30

SMALLINT NULL No

match_eng_tp_cd The matching engine

used for matching

parties.

BIGINT NULL No






TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDMETADATAINFOTP Table


metadata_info_tp_cd A code that identifies

the metadata

information.

BIGINT NOT NULL Yes

metadata_key Data that defines the

value of the metadata

information type code.

An example is:

’928749ae-f19c-41b6-babf-380467cea769’.


metadata_package_tp_cd A code that identifies

the metadata package.

BIGINT NULL No




TIMESTAMP NULL No




and time. On



to ensure that the






CDMETADATAPACKAGETP Table


metadata_package_tp_cd A code that identifies

the metadata package.

BIGINT NOT NULL Yes




metadata_package_name Data that defines the

value of a metadata

package type code, e.g.

‘com.ibm.mdm.System’.





TIMESTAMP NULL No




and time. On



to ensure that the






CDMETHODSTATUSTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

method_st_tp_cd Identifies the status of a

contact method. For

example: disconnected,

cancelled, and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDMISCVALUEATTRTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

valueattr_tp_cd The miscvalue attribute

can be used to provide

more information

regarding a miscvalue

type such as status,

effective date, created

date and others. Or the

miscvalue attribute type

can be used to populate

multiple values for a

party.

BIGINT NOT NULL Yes

name A short meaningful

label for the category.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDMISCVALUECAT Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

miscvalue_cat_cd The category allows

institutions to classify

the different types of

values. Some examples

are Demographic

Category, Risk Category,

Standard Industry

Codes,Party, Billing,

Address and others.

BIGINT NOT NULL Yes






used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDMISCVALUETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

miscvalue_tp_cd This is the misc. value

type that corresponds to

a particular misc. value

category. Some

examples of miscvalue

type are number of

employees, gold value,

credit card risk score,

loyalty, profitability and

others.

BIGINT NOT NULL Yes

miscvalue_cat_cd The category allows



values. Some examples

are Demographic

Category, Risk Category,

Standard Industry

Codes, Party, Billing,

Address and others.

BIGINT NULL No









used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDNAMEUSAGETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

name_usage_tp_cd Identifies the type of

name for this person.

For example: ″Legal,″

″Nick Name,″ ″Maiden

Name,″ and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





max_allowed_num The greatest number of

times a given Person

Name Usage Type Code

can be used.

SMALLINT NULL No

CDNODEDESIGTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

nodedesig_tp_cd Identifies the node

designate code type of a

hierarchy.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDNODETP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

node_tp_cd Identifies whether the

product type is the root

type, a hardened type

(i.e. a sub-type defined

through physical tables),

or a soft type (i.e. a

sub-type defined

through specs).

BIGINT NOT NULL Yes














used by the user to


to the type code.





TIMESTAMP NULL No




and time. On



to ensure that the






CDORGNAMETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

org_name_tp_cd Identifies the type of

name for this

organization. For

example: ″Legal,″

″Doing Business As,″

″Abbreviated,″ and

others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDORGTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes



organization. For

example: trust,


and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDPAYMENTMETHODTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

pymt_mthd_tp_cd A type code which



in the system. Some

examples are bank


cash, and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDPPREFACTIONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

ppref_action_tp_cd Identifies the action to

be taken based on the

privacy preference set

by the customer or by

company default setting.

For example: Do not

call, Do not mail

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDPPREFCAT Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

ppref_cat_cd Identifies the high level

category of the privacy

preference for the


Sharing of Data,

Solicitation, and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDPPREFREASONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

ppref_reason_tp_cd Identifies the reason

given by customer for

making a privacy

preference selection.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDPPREFSEGTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

ppref_seg_tp_cd Identifies the segment

associated with the

privacy preference

record. For example:

FCRA, FCC, and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





prov_state_tp_cd Province State Type

Code identifies the US

States, US Possessions,

US military oversea



overseas military





or AA and the zip code.

BIGINT NULL No

CDPPREFTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes




ppref_tp_cd The specific privacy

preference type within a

particular category For

example: Credit Info,

Personal Info, and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





ppref_cat_cd Privacy Preference

Category Code

identifies the high level

category of the privacy

preference for the


Sharing of Data,

Solicitation, and others.

BIGINT NULL No



CDPREFIXNAMETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

prefix_name_tp_cd Identifies the party’s

name prefix. Examples

include Mr., Mrs., Dr.,

and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDPRIMARYTARGETMARKETTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

primary_target_market_tp_cd A primary market this

product targets. For

example, ″Retail

Customer″, ″SMB″,

″Large Corporate″, etc.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No




and time. On



to ensure that the










XML header, if


on.

VARCHAR(20) NULL No



CDPRIORITYCATTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

priority_cat_tp_cd A code that classifies the

various types of priority.

An example of it is

″Task″.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No


added/updated, this





to ensure that the








CDPRIORITYTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

priority_tp_cd Identifies the priority of

a task, a campaign,

value and others.

Examples include high,

medium, low.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





PRIORITY_CAT_TP_CD A code that classifies the

various types of priority.

An example of a

priority category type

code is ″Task″.

BIGINT NULL No



CDPRODCONTRACTRELTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

prod_contr_rel_tp_cd Identifies the type of the

Product Contract

Relationship. For

example : ″Party

Selection″

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No




and time. On



to ensure that the








CDPRODRELATIONTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

product_rel_tp_cd Identifies the type of

relationship that two

products can have

between one another.

BIGINT NOT NULL Yes


description for the

″FROM″ value of the

relationship. For

example, ″Product 1 is

the bundle for Product

2″. This value

determines the relative

direction for the

relationship.



description for the ″TO″

value of the

relationship. For

example, ″Product 2 is

the bundle member for

Product 1″. This value

determines the relative

direction for the

relationship.








used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDPRODRELTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

prodrel_tp_cd Identifies the type of


products can have


For example:

″categorize″

BIGINT NOT NULL Yes



value of the

relationship.








used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDPRODSTRUCTURETP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

prod_struc_tp_cd Identifies whether the

product is a standalone

product or represents a

bundling of other

component products.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CDPRODTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

prod_tp_cd Identifies the type of




family). For example, a

manufacturing company

might have the product

types ″precision tools″,

″switches″, ″defence″,

″electronics″, and

″automotive″.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





prod_source identifies the source of

the code


CDPRODUCTIDENTIFIERTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

product_identifier_tp_cd Identifies the type of

identifier for the

product. For financial

products, examples

include an

“International Securities

Identification Number”,

“National Securities

Identification Number”,

etc.

BIGINT NOT NULL Yes











used by the user to


to the type code.





max_allowed_num Represents the

maximum number of

active identifiers that

can be added to the

same product for the

same identifier type.

SMALLINT NULL No




TIMESTAMP NULL No


added/updated, this





to ensure that the






CDPRODUCTSTATUSTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

status_tp_cd The lifecycle status of

the product. For

example, ″Available″,

″Unavailable″,

″Obsolete″, etc.

BIGINT NOT NULL Yes











used by the user to


to the type code.








TIMESTAMP NULL No




and time. On



to ensure that the










XML header, if


on.

VARCHAR(20) NULL No

CDPROVSTATETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

prov_state_tp_cd Identifies the US States,

US Possessions, US

military oversea



overseas military





or AA and the zip code.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDPURPOSETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

purpose_tp_cd Identifies the purpose

for the location as it

relates to a role on a

contract. For example,

the owner’s residence

address is associated

with the contract for the

purpose of sending

statements

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDQUESTIONCATTP Table



question_cat_tp_cd Question category type

code.

BIGINT NOT NULL Yes


question category type








used by the user to


to the type code.



code table record

TIMESTAMP NULL No


current record


CDQUESTIONNAIRETP Table


lang_tp_cd BIGINT NOT NULL Language type code. Yes




quesnr_tp_cd BIGINT NOT NULL Questionnaire type

code.

Yes

name VARCHAR(120) NOT NULL The name or value of

questionnaire type

No

description VARCHAR(255) NULL Description provides

extra information,

which can be used

either as an

additional definition

of the type code

value or as free form

comments used by

the user to provide

further meaning to

the type code.

No

expiry_dt TIMESTAMP NULL The expiry date of the

code table record

No

last_update_dt TIMESTAMP NOT NULL The last update date

of current code table

record

No

CDQUESTIONTP Table


lang_tp_cd BIGINT NOT NULL Language type code. Yes

question_tp_cd BIGINT NOT NULL Question type code. Yes

question_cat_tp_cd BIGINT NULL The question category

type code

No

name VARCHAR(120) NOT NULL The name or value of

question type

No


extra information,

which can be used

either as an


of the type code

value or as free form

comments used by

the user to provide

further meaning to

the type code.

No

expiry_dt TIMESTAMP NULL The expiry date of the

code table record

No

last_update_dt TIMESTAMP NOT NULL The last update date

of current record.

No



CDRELASSIGNTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

rel_assign_tp_cd Identifies how the

relationship between the

parties has been

assigned. For example, a

custodial relationship

between a minor and an

adult may be created by

a court order.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDRELTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

rel_tp_cd Identifies the type of


parties can have


For example: ″is parent

of″ or ″is employer of″.

BIGINT NOT NULL Yes



value of the

relationship.








used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







CDREPOSITORYTP Table


repository_tp_cd Uniquely identifies the

CMS Repository.

BIGINT NOT NULL Yes

name Name of the repository,

may point to the jndi

name, connector name

of the IICE etc.



extra information, that




as freeform comments

used by the user to


to the type code.


content_system Name of the CMS

system.


no_of_keys Number of parameters

defined by the CMS

System, to uniquely

identify a content

BIGINT NOT NULL No

expiry_dt The expiry Date is the

date from which the

record is no longer

effective.

TIMESTAMP NULL No


added/updated, this





to ensure that the






CDRESIDENCETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes




residence_tp_cd Identifies a type of

residence for a given

address. Some examples

include Home,

Apartment, and Suite.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDROLECATTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

role_cat_tp_cd This is the role category

type code.

BIGINT NOT NULL Yes









used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDROLETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

role_tp_cd This is the role type

code

BIGINT NOT NULL Yes

role_cat_tp_cd The category allows



roles. Some examples

are Party Relationship

Roles, Hierarchy Roles,

Grouping Roles, and

others.

BIGINT NULL No









used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDRPTINGFREQTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

rpting_freq_tp_cd Describes the frequency

that a particular Party

(CONTACT) would like

to receive consolidated

statements. Sample

values include annually,

semi-annually, monthly,

and others.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDSERVICELEVELTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

service_level_tp_cd Identifies the Service

level associated with the

contract. Some examples

include 24/7 call centre

service or Service

during business hours

only.

BIGINT NOT NULL Yes














used by the user to


to the type code.





TIMESTAMP NULL No




and time. On



to ensure that the






CDSHAREDISTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

share_dist_tp_cd Identifies how the

proceeds of the contract

component get

distributed among the

associated party contract

roles. Examples include

equal shares, 50% share,

and so on.

BIGINT NOT NULL Yes



type code.







used either as an




used by the user to


to the type code.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDSOURCEIDENTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

source_ident_tp_cd Identifies the type for

the source identifier.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDSPECCASCADETP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

spec_cascade_tp_cd The cascade action the

spec will have in a

hierarchy. For example,

″Cascaded to

descendents″, ″Not

cascaded to

descendents″, etc.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No







and time. On



to ensure that the






CDSPECUSETP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

spec_use_tp_cd The usage type that

dictates how the spec

will be used. For

example, the spec could

be used to govern

product common

attribute values.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No







and time. On



to ensure that the






CDSTATUSREASONTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

status_reason_tp_cd Identifies the reason

why the product is in its

current state.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No

CDSUSPECTREASONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

susp_reason_tp_cd Identifies the field that

caused the data match

to occur.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code


reason_score Reason Score is the

numeric score associated

with the suspect reason

code.

SMALLINT NULL No




match_eng_tp_cd The matching engine

used for matching

parties.

BIGINT NULL No



TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a





CDSUSPECTSOURCETP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

susp_source_tp_cd Identifies the source of

the Suspect Reason

Code: system marked or

user marked

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDSUSPECTSTATUSTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

susp_st_tp_cd Indicates the current

situation for a particular

suspect record - suspect

duplicate, not duplicate,

under investigation, and

others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDSUSPECTTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

suspect_tp_cd Captures various

suspect types. One

record exists for each

unique add_action_code

in the addactiontype

table.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





rule_id Primary key of the

External Rule Record


CDTAXPOSITIONTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

tax_position_tp_cd The relative tax position

offered by the product.


product is tax neutral,

provides the customer a

tax advantage, or

provides the FI with a

tax advantage.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No







and time. On



to ensure that the










XML header, if


on.

VARCHAR(20) NULL No

CDTERMINATIONREASONTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

termination_reason_tp_cd Describes the reason

why the contract is

terminated. For example

: ″Terms & Conditions

violated″, ″Core account

closed by owner″

BIGINT NOT NULL Yes











used by the user to


to the type code.








TIMESTAMP NULL No


added/updated, this





to ensure that the






CDUNDELREASONTP Table



language, such as

English, French,

Spanish, or German.




the Language Type



name.

BIGINT NOT NULL Yes

undel_reason_tp_cd Identifies the reason for

not using a particular

address. Some example

values are ″returned

mail,″ ″change in zip

code,″ and others.

BIGINT NOT NULL Yes



type code.




used either as an




used by the user to


to the type code.




TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a





CDVALFREQTP Table



identifies a spoken


English, French,



key of a code value

lookup table, the

Language Type Code

also represents the


name.

BIGINT NOT NULL Yes

val_freq_tp_cd Validation Frequency

Type Code uniquely


validation frequency.

BIGINT NOT NULL Yes











used by the user to


to the type code.





TIMESTAMP NULL No





added/updated, this





to ensure that the






CHARGECARD Table



generated key that



MDM Server system.

BIGINT NOT NULL Yes

charge_card_tp_cd Identifies one type of

charge card from

another. Some examples

are Visa, MasterCard,

American Express, and

others.

BIGINT NOT NULL No

charge_card_num The number that


charge card.


expiry_dt The date that the charge

card will expire.


on_card_name The account name of the

charge card as it exactly

appears on the charge

card.


bank_num A unique identifier for

the bank that issued the

chargecard, assigned

outside of InfoSphere

MDM Server.

VARCHAR(10) NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

CLAIM Table


claim_id A unique, system

generated key that

identifies a claim.

BIGINT NOT NULL Yes

admin_ref_num The reference

identification number

for the claim record.


claim_number The Claim Number

assigned to a claim is

the means by which the

claim can be

distinguished from all

other claims.

VARCHAR(20) NULL No

claim_detail_amt The value of the claim

detail.


claim_paid_amt The amount paid on the

claim.


outstanding_amt The amount that is to be

paid on the claim.


benefit_claim_amt The maximum amount

that can be paid on a

claim.


claim_tp_cd Identifies the type of

claim that is recorded.

Some examples include

Fire, Theft, Automobile,

Collision and others.

BIGINT NOT NULL No



line of business. Some

examples are Life,

Annuity, Disability, Auto

& Home, and others.

BIGINT NULL No




claim_status_tp_cd Identifies the status of a


include Pending, Closed

and Rejected.

BIGINT NULL No

claim_code A code that identifies

the procedure or claim

service. For example:

Orthodontics procedure

code is D8000.

VARCHAR(20) NULL No

status_dt The date that the claim

status was updated.

TIMESTAMP NULL No

claim_incurred_dt The date that the claim

was incurred.

TIMESTAMP NULL No

reported_dt The date that the claim

was reported.

TIMESTAMP NULL No


extra information about

the claim.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

detlamt_cur_tp The currency type for

the claim detail amount.

BIGINT NULL No

paidamt_cur_tp The currency type for

the total claim benefit

amount.

BIGINT NULL No

outsamt_cur_tp The currency type for

the outstanding amount.

BIGINT NULL No




Beneamt_cur_tp The currency type for

the Benefit Claim

amount.

BIGINT NULL No

CLAIMCONTRACT Table


claim_contr_id Primary key of the

claim contract record.

BIGINT NOT NULL Yes


generated key that

identifies a claim.

BIGINT NOT NULL No


generated key that


the InfoSphere MDM

Server system.

BIGINT NOT NULL No


extra information about

the record.


start_dt The date that the claim

contract record became

effective, or was

recorded.


end_dt The date that the claim

contract record is no

longer effective.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



CLAIMROLE Table


claim_role_id The primary key of a

claim detail role record.

BIGINT NOT NULL Yes

claim_role_tp_cd Identifies a type of role

a party plays on a


include Claimant,

Witness and Third Party.

BIGINT NOT NULL No

cont_id A unique, system

generated key that

identifies a party in the


system.

BIGINT NOT NULL No


generated key that

identifies a claim.

BIGINT NOT NULL No


information.


start_dt The date that the claim

role record became

effective, or was

recorded.


end_dt The date that the claim

role record is no longer

effective.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



COMPLDOCUMENT Table


compl_doc_id Compliance Document

ID is a unique, system

generated key that

identifies a Compliance

Document in the


system.

BIGINT NOT NULL Yes

compl_target_id Compliance Target ID

represents that which

compliance target this

compliance document to

validate.

BIGINT NOT NULL No

compl_doc_tp_cd A unique type code


a compliance document

value.

BIGINT NOT NULL No

application Application represents

the application name.

VARCHAR(50) NULL No

group_name Group Name represents

the group name for this

compliance document

type belongs to.

VARCHAR(50) NULL No

element_name Element Name

represents the element

name this compliance

document type mapping

to.

VARCHAR(50) NULL No

element_value Element value


value this compliance

target type mapping to.








used by the user to


to the type code.





and time. On



to ensure that the













XML header, if

security/ROV is turned

on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

COMPLENTITY Table


compl_entity_id Compliance Entity ID is

a unique, system

generated key that


Entity in the InfoSphere

MDM Server system.

BIGINT NOT NULL Yes

compl_req_id Compliance requirement

ID used for this

compliance entity

BIGINT NOT NULL No

entity_name Entity Name for this

compliance entity


instance_pk Instance Primary Key

for this compliance

entity.

BIGINT NOT NULL No

created_dt Created Date represents

the date that this row of

data become valid








used by the user to


to the type code.


next_verif_dt Next Verification Date

represents the date that

this compliance entity

need to be re-verified

based on the compliance

requirement.

TIMESTAMP NULL No




end_dt End Date represents the

date that this row of

data became invalid.

TIMESTAMP NULL No


added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

COMPLENTITYDOC Table


compl_ent_doc_id Compliance Entity

Document ID is a

unique, system

generated key that


Entity Document in the


system.

BIGINT NOT NULL Yes

compl_ent_targ_id Compliance Entity

Target ID represents

which this compliance

entity document

validated

BIGINT NOT NULL No

compl_doc_id Compliance Document

ID represents that to

which compliance

document this

compliance entity

document references.

BIGINT NOT NULL No




doc_instance_value Document value for this

compliance entity

document.

VARCHAR(30) NULL No

doc_expiry_dt Document Expiry Date

represents the date that

this document of data

became invalid.

TIMESTAMP NULL No







used by the user to


to the type code.



added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

COMPLENTITYTARGET Table


compl_ent_targ_id Compliance Entity

Target ID is a unique,

system generated key

that identifies a

Compliance Entity

Target in the InfoSphere

MDM Server system.

BIGINT NOT NULL Yes




compl_entity_id Compliance Entity ID

represents that to which

compliance entity this

compliance entity target

belongs.

BIGINT NOT NULL No

compl_target_id Compliance Target ID


compliance target this

compliance entity target

references.

BIGINT NOT NULL No

target_instance_pk Instance Primary Key

for this compliance

entity target.

BIGINT NOT NULL No







used by the user to


to the type code.



added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No



COMPLIANCEREQ Table


compl_req_id Compliance

Requirement ID is a

unique, system

generated key that


Requirement in the


system.

BIGINT NOT NULL Yes

compl_tp_cd A unique type code


a compliance value.

BIGINT NOT NULL No

effect_dt Date from which this


is effective.


end_dt End Date represents the

date that this row of

data became invalid.

TIMESTAMP NULL No

ext_ref_id External Reference Id

represents the external

reference Id for this

compliance requirement,

for example regulatory

number.

VARCHAR(30) NULL No







used by the user to


to the type code.


val_freq_tp_cd A unique type code


a compliance validation

frequency value.

BIGINT NULL No


added/updated, this





to ensure that the













XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

COMPLTARGET Table


compl_target_id Compliance Target ID is

a unique, system

generated key that


Target in the InfoSphere

MDM Server system.

BIGINT NOT NULL Yes

compl_req_id Compliance

Requirement ID



this compliance target

belongs.

BIGINT NOT NULL No

compl_target_tp_cd A unique type code


a compliance target

value.

BIGINT NOT NULL No

application Application represents

the application name.


group_name Group Name represents

the group name for this

compliance target type

belongs to.


element_name Element Name


name this compliance



element_value Element value


value this compliance












used by the user to


to the type code.



added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

CONDITIONATTRIBUTE Table


condition_attribute_id The primary key for the Condition

Attribute record.

BIGINT NOT NULL Yes

condition_id The id of the term condition

associated with this condition

attribute

BIGINT NOT NULL No

condition_attr_tp_cd The

CDCONDTIONATTRIBUTETYPE

table serves to group condition

attributes and allows another level

of detail.

BIGINT NOT NULL No

value The value associated with this

Condition Attribute






added/updated, this field is

updated with the date and time.

On subsequent updates, we utilize

this information to ensure that the

update request includes a

matching date/time on this field;

if it does not, the update fails.


last_update_tx_id Transaction ID is a unique, system

generated key that identifies the

specific transaction within the log

system that either created,

updated or deleted the data row.

BIGINT NULL No

last_update_user Id of user who last updated the

data. Either user ID or user group

must be passed in the XML

header, if security/RoV is turned

on.

VARCHAR(20) NULL No

CONTACT Table



generated key that



system.

BIGINT NOT NULL Yes

acce_comp_tp_cd Represents one of the

various types of access a

party may have to a

computer and related

technologies.

BIGINT NULL No

pref_lang_tp_cd Identifies a preferred

spoken language. For

example: English,

French, Spanish, and

others.

BIGINT NULL No

created_dt The date that the party

row was created.


contact_name Identifies the full name

of the person to be

contacted within the

corporation. For trusts,

this identifies the

trustee.





inactivated_dt The date which the

party row was

considered inactive

through business

processes such as

collapsing and splitting,

resulting in a new party

record created, and

others.

TIMESTAMP NULL No

person_org_code A pointer to the type of

party - person or

organization.

CHAR(1) NOT NULL No

solicit_ind Determines whether this

party can be solicited at

any location group.

CHAR(1) NULL No

confidential_ind Indicates whether this

party’s information

should be kept

confidential.

CHAR(1) NULL No

client_imp_tp_cd An identifier that


client importance type



low.

BIGINT NULL No

client_st_tp_cd An identifier that


client status type from

another. Examples

include prospect, active,

suspended.

BIGINT NULL No

client_poten_tp_cd An identifier that


client potential type



low.

BIGINT NULL No

rpting_freq_tp_cd Describes the frequency

that a particular Party

(CONTACT) would like

to receive consolidated

statements. Sample

values include annually,

semi-annually, monthly,

and others. No business

logic is currently being

invoked on this field.

BIGINT NULL No

last_statement_dt The last time a

consolidated statement

was sent to the Party.

No business logic is

currently being invoked

on this field.

TIMESTAMP NULL No




alert_ind Indicates whether there

is any kind of alert or

restriction on this party.

This field is set by


when an active alert is

associated with the

Party record.

CHAR(1) NULL No

since_dt Identifies the date that

the contact has been a

customer since.

TIMESTAMP NULL No

left_dt Identifies the date that

the contact stopped

being a customer.

TIMESTAMP NULL No

access_token_value An access token is a

means to protect a

resource from

unauthorized user or

group access. When an

access token value is

associated with a

resource such as a

database record, only

users or groups that are

assigned that token can

have access to that

resource.

VARCHAR(50) NULL No

pending_cdc_ind Indicates the presence of

a pending critical data

change (CDC) for a

party.

CHAR(1) NULL No




and time. On

subsequent updates,




request includes a





provided_by_cont The Party ID of the

party that referred this

Party to the

organization.

BIGINT NULL No



the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No

do_not_delete_ind Indicates whether the

Party record can or

cannot be deleted.

A value of ’Y’ means

party cannot be deleted.

A value of ’N’ or blank

means party can be

deleted.

CHAR(1) NULL No

source_ident_tp_cd The type for the source

identifier.

BIGINT NULL No



no business logic


field.

TIMESTAMP NULL No





field.

TIMESTAMP NULL No

CONTACTCDC Table


cdc_id BIGINT NOT NULL The primary key of

the entity.

Yes

cont_id BIGINT NOT NULL Party ID is a unique,

system generated key

that identifies a party

in the WCC system.

No

entity_name VARCHAR(120) NOT NULL The class name of the

entity holding the

critical data that was

requested for update.

No

instance_pk BIGINT NULL The primary key of

the entity holding

critical data that was


No

critdata CLOB(200K) NOT NULL An XML


entity that was


No

cdc_st_tp_cd BIGINT NOT NULL The status of the

critical data change

request.

No




rej_reason_tp_cd BIGINT NULL The reason for which

a critical data change

is rejected.

No

created_dt TIMESTAMP NOT NULL The timestamp when

the pending critical

data change is

created.

No

expiry_dt TIMESTAMP NULL The timestamp when

the pending critical

data change has been

resolved (either

accepted or rejected).

No


unique, system

generated key that




created, updated or


No


updated the data.




security/RoV is

turned on.

No

last_update_dt TIMESTAMP NOT NULL Whenever a record is

added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No

CONTACTDEMOGRAPHICS Table


demographics_id BIGINT NOT NULL Demographics ID

uniquely identifies

the demographics

record.

Yes

cont_id BIGINT NOT NULL The ID of the party to

whom the

demographics record

belongs.

No




demographics_tp_cd BIGINT NOT NULL Type of the

demographics

information defined

in code table

cddemographicstp.

No

spec_fmt_id BIGINT NOT NULL The ID of the spec

format

No

value CLOB(1G) NOT NULL Value is the

demographics xml.

No

start_dt TIMESTAMP NOT NULL The date when the

demographics

become valid.

No

end_dt TIMESTAMP NULL The date when the

demographics

become invalid.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No

last_update_tx_id BIGINT NULL Transaction ID

generated by the

system whenever the

record is

added/updated.

No

CONTACTMETHOD Table


contact_method_id A unique, system

generated key that

identifies a contact

method in the


system.

BIGINT NOT NULL Yes




cont_meth_cat_cd Ientifies the main

category of contact

method. For example:

telephone, email, PDA,

and others.

BIGINT NOT NULL No


generated key that


the InfoSphere MDM

Server system.

BIGINT NULL No

ref_num The actual text provided

for the contact method.

For example, if the

contact method category

type is telephone, then

this column contains the

actual 10 digits for the

phone number.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

CONT_METH_STD_IND Indicates if this contact

method has been

standardized.

CHAR(1) NULL No



CONTACTMETHODGROUP Table



generated key that


group row in the


system.

BIGINT NOT NULL Yes

contact_method_id A unique, system

generated key that


method in the


system.

BIGINT NOT NULL No

cont_meth_tp_cd Identifies the subtypes

of a Contact Method

Category Type Code.

For example, if the

category type is

telephone, then the

values of the subtype

code are home,

business, cell phone,

and others.

BIGINT NOT NULL No

method_st_tp_cd Identifies the status of a

contact method. For

example: disconnected,

cancelled, and others.

BIGINT NULL No

attach_allow_ind Indicates whether

attachments are allowed

to be sent with this

contact method. This

indicator should only be

used when the contact

method refers to an

email.

CHAR(1) NULL No

text_only_ind Indicates whether this

can be sent as text only.

This indicator should

only be used when the

contact method refers to

an email.

CHAR(1) NULL No

message_size Represents the

maximum size of

electronic message that

may be sent to this

contact method. This

indicator should only be

used when the contact

method refers to an

email.

VARCHAR(20) NULL No

comment_desc A comment or

description.








and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

CONTACTREL Table


cont_rel_id A unique, system

generated key that

identifies a party

relationship row in the


system.

BIGINT NOT NULL Yes



parties can have


For example: ″is parent

of,″ ″is employer of,″

and others.

BIGINT NOT NULL No

rel_desc Refers to comments that

a user may have

concerning the party

relationship.







TIMESTAMP NULL No




to_cont_id A unique, system

generated key that



system.

BIGINT NOT NULL No

from_cont_id A unique, system

generated key that



system.

BIGINT NOT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

rel_assign_tp_cd Identifies how the

relationship between the

parties has been

assigned. For example, a

custodial relationship

between a minor and an

adult may be created by

a court order.

BIGINT NULL No


generated key that




created, updated or


BIGINT NULL No

end_reason_tp_cd Identifies the cause for a

party to party

relationship being

ended. For example,

″divorce″ can be used as

an end reason.

BIGINT NULL No



CONTEQUIV Table


cont_equiv_Id A unique, system

generated key that

identifies a party

equivalency row in the


system.

BIGINT NOT NULL Yes


generated key that



system.

BIGINT NOT NULL No




Examples include


and others.

BIGINT NOT NULL No

admin_client_id Uniquely identifies the

primary key for the


system

VARCHAR(20) NULL No



used either as an


the record or as free

form comments used by

the user to provide

further meaning to the

record.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No

CONTMACROROLE Table


cont_macro_role_id A unique ID to identify

a party macro role in

the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes


generated key that



system.

BIGINT NOT NULL No

role_tp_cd The role type code. BIGINT NOT NULL No

start_dt The date when this role

becomes effective.


end_dt The date when this role

become inactive.

TIMESTAMP NULL No

description A free form description

for this role.






relationship may be


reason.

BIGINT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No

CONTRACT Table



generated key that


the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes

contr_lang_tp_cd Identifies a spoken

language, such as

English, French, Spanish,

or German.




the Language Type Code

also represents the


name.

BIGINT NULL No

currency_tp_cd Identifies the currency of

the amount columns.

BIGINT NULL No

freq_mode_tp_cd Identifies the frequency

of the payments made

on the contract. Some

examples are monthly,

annual, and others.

BIGINT NULL No

bill_tp_cd An identifier that


billing type from

another. Examples

include Regular, Direct,

Payroll deduction, and

others.

BIGINT NULL No

premium_amt The premium payment

due at the intervals

identified by the

frequency mode type

code.


next_bill_dt The date of the next bill

for the contract.

TIMESTAMP NULL No

curr_cash_val_amt The cash value of the

contract.





line_of_business Represents a high-level

product grouping (Life,

Annuity, Disability, Auto

& Home, and others.)

VARCHAR(30) NULL No

brand_name The title of the

subsidiary that sold this

contract.

VARCHAR(30) NULL No

service_org_name The organization that

services the contract.

VARCHAR(70) NULL No

bus_orgunit_id The lowest level of

identification within the

servicing organization of

this contract.

VARCHAR(30) NULL No

service_prov_id The unique identifier

that identifies the

servicing agent or

broker, and others. that

services this contract.

VARCHAR(30) NULL No

access_token_value An access token is a

means to protect a

resource from

unauthorized user or

group access. When an

access token value is

associated with a

resource such as a

database record, only

users or groups that are

assigned that token can

have access to that

resource.

VARCHAR(50) NULL No




and time. On subsequent

updates, InfoSphere

MDM Server uses this



includes a matching date

and time on this field; if

it does not, the update

fails.




the user ID or user

group must be passed in

the XML header if

security or RoV is

turned on.

VARCHAR(20) NULL No




repl_by_contract A unique, system

generated key that


the InfoSphere MDM

Server system, that is

replacing this particular

contract.

BIGINT NULL No


generated key that




created, updated or


BIGINT NULL No

issue_location Describes the location

where the contract was

issued.

VARCHAR(30) NULL No




Examples include


and others.

BIGINT NULL No

admin_contract_id The actual text or

number that is used in

the administrative source

system to identify a

contract.


premamt_cur_tp The currency type for

the premium amount.


cashval_cur_tp The currency type for

the current cash value

amount.


managed_account_ind Indicates whether or not

this contract is a

managed account. A

managed account is a

contract that is managed

by the InfoSphere MDM

Server system. The

opposite of a managed

account is a reference

account. A reference

account is a contract that

is managed by an

external system.

CHAR(1) NULL No

agreement_name The name of the

contract.


agreement_nickname The alternate name of

the contract.


signed_dt The date on which the

contract is signed.

TIMESTAMP NULL No

executed_dt The date on which the

contract becomes active.

TIMESTAMP NULL No




end_dt The date on which the

contract is considered

ended.

TIMESTAMP NULL No

replaces_contract The identifier of the

contract that this

contract replaces (if

applicable).

BIGINT NULL No

account_last_transaction_dt The date on which a

transaction was last

executed against this

contract.

TIMESTAMP NULL No

termination_dt The date on which the

contract is terminated.

TIMESTAMP NULL No

termination_reason_tp_cd The reason for which the

contract is terminated.

BIGINT NULL No

agreement_description The description of the

contract.


agreement_st_tp_cd The status of the

contract.

BIGINT NULL No

agreement_tp_cd The type of the contract. BIGINT NULL No

service_level_tp_cd The service level

provided for this

contract. For example:

″24/7 Call Center

service″ or ″Service

during business hours

only″.

BIGINT NULL No

last_verified_dt The date on which the

contract was last

verified.

TIMESTAMP NULL No

last_reviewed_dt The date on which the

contract was last

reviewed.

TIMESTAMP NULL No

product_id The Product identifier on

which the contract is

based.

BIGINT NULL No

cluster_key This column can

optionally be used as a

clustering index. A

clustering index is an

index that determines

how rows are physically

ordered (clustered) in a

table space. If not

specified, the default

value for this column is

NOT NULL.

BIGINT NULL No



CONTRACTCOMPONENT Table



generated key that


component in the


system.

BIGINT NOT NULL Yes

contract_st_tp_cd Identifies the status of

the contract. For

example: ″active″,

″pending″, lapse

pending″, or ″cancelled″.

These values are

provided by the


systems of the contract.

BIGINT NOT NULL No

prod_tp_cd Identifies the type of




family). Examples




BIGINT NULL No

curr_cash_val_amt The cash value of the

contract component.


premium_amt The premium payment

due at the intervals

identified by the

frequency mode type

code for this contract

component.


issue_dt The date which the

contract component was

issued.

TIMESTAMP NULL No




viatical_ind Determines whether this

contract is under a

viatical arrangement. A

viatical settlement is a

transaction that occurs

when a person with a

terminal or chronic

illness sells a life

insurance policy in

return for a discounted

amount of the death

benefit.

The viator, the

individual who sells the

policy, sells his or her

interest in a policy to a

viatical settlement

company. The beneficial

interest in the policy is

then purchased by third

party investors. A

viaticated policy is a life

insurance policy that

has been sold.

CHAR(1) NULL No

base_ind Used to identify the

base component of the

contract. Every contract

has at least one

component, the base

component.

CHAR(1) NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No




contr_comp_tp_cd A numeric


type of coverage for the

product.

For example:

v Base

v Rider

v Base Increase

v Integrated

BIGINT NULL No


generated key that




created, updated or


BIGINT NULL No

serv_arrange_tp_cd Indicates whether this

contract is administered

by the organization or a

third party.

BIGINT NULL No


generated key that


the InfoSphere MDM

Server system.

BIGINT NOT NULL No

holding_id The primary key of a

party holding record.

BIGINT NULL No



TIMESTAMP NULL No

premamt_cur_tp The currency type for

the premium amount.

BIGINT NULL No

cashval_cur_tp The currency type for

the current cash value

amount.

BIGINT NULL No

cluster_key This column can

optionally be used as a

clustering index. A

clustering index is an

index that determines

how rows are physically

ordered (clustered) in a

table space. If not

specified, the default

value for this column is

NOT NULL.

BIGINT NULL No



CONTRACTCOMPVAL Table


contr_comp_val_id A unique, system

generated key that


component value in the


system.

BIGINT NOT NULL Yes

domain_value_tp_cd Domain Value Type

Code, in a given

domain, identifies the

specific values that are

captured. For example:

Integer value, Date

value, etc.

BIGINT NOT NULL No

value_string The numeric value

associated with the

Value Type Code.



generated key that


component in the


system.

BIGINT NOT NULL No






TIMESTAMP NULL No


generated key that




created, updated or


BIGINT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No



CONTRACTREL Table


contract_rel_id A unique, system

generated key that


relationship in the


system.

BIGINT NOT NULL Yes

contr_rel_tp_cd Describes the type of

relationship. Examples

include master contract

and contract term.

BIGINT NOT NULL No

contr_rel_st_tp_cd Identifies the status of

the relationship between

two contracts, such as

″pending,″ ″active,″ and

″terminated.″

BIGINT NULL No

from_contract_id A unique, system

generated key that


the InfoSphere MDM

Server system.

BIGINT NOT NULL No

to_contract_id A unique, system

generated key that


the InfoSphere MDM

Server system.

BIGINT NOT NULL No






TIMESTAMP NULL No

rel_description Provides for comments

that a user may have

concerning the contract

relationship.



generated key that




created, updated or


BIGINT NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

CONTRACTROLE Table


contract_role_id A unique, system

generated key that

identifies a party

contract role row in the


system.

BIGINT NOT NULL Yes


generated key that



system.

BIGINT NOT NULL No


generated key that


component in the


system.

BIGINT NOT NULL No

contr_role_tp_cd Identifies the type of

role that a party may

have on a contract. For

example ″beneficiary,″

″owner,″ ″insured,″

″payer,″ and others.

BIGINT NOT NULL No

registered_name The party contract role

name as it appears on

the contract.


distrib_pct Used for beneficiary

type, it indicates the

share that this party has

interest in regarding this

contract component.


irrevoc_ind Indicates whether this

role can be changed

without consent.

CHAR(1) NULL No






TIMESTAMP NULL No




recorded_start_dt The date which the

party’s relationship to

the contract became

legally effective. This is

commonly the date

which the party signed

the contract.

TIMESTAMP NULL No

recorded_end_dt The date that the party’s

relationship to the

contract is no longer

effective.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

share_dist_tp_cd The values and

descriptions defining

how the proceeds of the

contract are distributed

among the party

contract roles.

BIGINT NULL No

arrangement_tp_cd The type of agreement

that the party contract

role has with the


time delay arrangement

such as a common

disaster.

BIGINT NULL No

arrangement_desc Provides extra


used either as an


the arrangement or as

free form comments

used by the user to


to the arrangement.






generated key that




created, updated or


BIGINT NULL No


why a role was ended.

For example, a

beneficiary relationship

may be ended for a

death reason.

BIGINT NULL No

CONTRACTROLEREL Table


contr_role_rel_id A unique, system

generated key that

identifies a party



system.

BIGINT NOT NULL Yes



parties can have

between one another,

within the context of the


″is custodian of,″ ″is

minor for,″ and others.

BIGINT NOT NULL No

role_rel_desc Provides a space to

store user comments the

party roles relationship.


contr_role_from_id A unique, system

generated key that

identifies a party



system.

BIGINT NOT NULL No

contr_role_to_id A unique, system

generated key that

identifies a party



system.

BIGINT NOT NULL No






TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No


why a role relationship

was ended. For

example, a custodial

relationship may be

ended for a ″coming of

age″ reason.

BIGINT NULL No

CONTSUMMARY Table



generated key that



system.

BIGINT NOT NULL Yes

privpref_ind Determines whether

there is any party

privacy preference on

this party. This field is

set by InfoSphere MDM

Server when a party

privacy preference is

associated with the

Party record.

SMALLINT NOT NULL No




miscvalue_ind Indicates whether there

is any party misc value

on this party. This field

is set by InfoSphere

MDM Server when a

party misc value is

associated with the

Party record.


contactrel_ind Indicates whether there

is any party relationship



MDM Server when a

party relationship is

associated with the

Party record.


bankaccount_ind Indicates whether there

is any party bank

account on this party.



when a party financial

profile is associated

with the Party record.


chargecard_ind Indicates whether there

is any party charge card



MDM Server when a

party financial profile is

associated with the

Party record.


payrolldeduct_ind Indicates whether there

is any party payroll

deduction on this party.







incomesource_ind Indicates whether there

is any party income

source on this party.







identifier_ind Indicates whether there

is any party identifier



MDM Server when a

party identifier is

associated with the

Party record.





alert_ind Indicates whether there

is any kind of alert or

restriction on this party.



when an active alert is

associated with the

Party record.


contequiv_ind Indicates whether there

is any contact

equivalent on this party.



when a contact

equivalent is associated



interaction_ind Is there any party

interaction on this

party? This field is set

by InfoSphere MDM

Server when a party

interaction is associated



addressgroup_ind Indicates whether there

is any party address

group on this party.



when a party address

group is associated with

the Party record.


contmethgroup_ind Indicates whether there

is any contact method

group on this party.



when a contact method

group is associated with

the Party record.


lobrel_ind Indicates whether there

is any party line of

business relationship on

this party. This field is

set by InfoSphere MDM

Server when a party line

of business relationship

is associated with the

Party record.








and time. On

subsequent updates,




request includes a






generated key that




created, updated or


BIGINT NULL No



the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

DEFAULTSOURCEVAL Table


default_src_val_id A unique, system

generated key that

identifies an default

object row in the


system.

BIGINT NOT NULL Yes



the defaulted values.




entity that has the

defaulted values.

BIGINT NULL No

column_name The actual name of the

column where the

default occurred.





source_value The value of the Logical

Column Name prior to

defaulted to the


database column value.

For example: established

date - Jan 31, 2002

Source Value is: Jan

2002.


default_value The value of the Logical

Column Name after it is

defaulted to the


database column value.

For example: established

date - Jan 2002. Default

Value is: Jan 31, 2002.




used either as an




the user to provide


record.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



BIGINT NULL No

source_identifier Identifies the source of

the value.




ENTITYCONDITIONREL Table

Name Comment Datatype

Null

Option Is PK

entity_condition_rel_id The primary key for the

Entity Condition

Relationship record.

BIGINT NOT

NULL

Yes

instance_pk The Primary key of the

entity to which the Term

Condition is related. It

can be the primary key of

either PRODUCT or

CONTRACT.

BIGINT NOT

NULL

No

entity_name Type of the Entity the

condition is related to. It

can be either PRODUCT

or CONTRACT.

VARCHAR(120) NOT

NULL

No

condition_id The identifier of the term

condition attached to the

Entity.

BIGINT NOT

NULL

No

start_dt The Start date from when

this relationship is valid

TIMESTAMP NOT

NULL

No

end_dt The End date till when

this relationship is valid

TIMESTAMP NULL No


added/updated, this field

is updated with the date


updates, we utilize this

information to ensure that

the update request

includes a matching

date/time on this field; if


fails.

TIMESTAMP NOT

NULL

No


unique, system generated


specific transaction within

the log system that either

created, updated or


BIGINT NULL No





XML header, if


on.

VARCHAR(20) NULL No



ENTITYCONTENTREFERENCE Table


content_ref_id A unique, system

generated key that

identifies a Content

Reference in the


system

BIGINT NOT NULL Yes

content_ref_1 Parameter defined in the

CMS system to identify

the Content Reference.














instance_pk The actual primary key of

the row in the logical


with the content reference.

BIGINT NULL No

entity_name The name of the business

entity.


content_version The version of the content

reference in the CMS

system.


start_date The Start Date is the first

date that the record is

effective.


end_date The End Date is the date

from which the record is

no longer effective.

TIMESTAMP NULL No

repository_tp_cd Identifies the Repository

within the CMS System.

BIGINT NULL No




time. On subsequent



the update request

includes a matching



fails.





last_update_tx_id Transaction ID is a unique,

system generated key that


transaction within the log


updated or deleted the

data row.

BIGINT NULL No





XML header, if

security/RoV is turned on.

VARCHAR(20) NULL No

ENTITYROLE Table


entity_role_id A unique ID to identify

an entity role in the

system.

BIGINT NOT NULL Yes

role_tp_cd The role type code. BIGINT NOT NULL No

contxt_entity_name The name of the entity

that a role is being

provided for.


contxt_instance_pk The primary key of the

entity.

BIGINT NOT NULL No

role_entity_name The entity name of the

role player.

VARCHAR(30) NULL No

role_instance_pk The primary key of the

role player.

BIGINT NULL No

start_dt The date when this role

becomes effective.


end_dt The date when this role

becomes inactive.

TIMESTAMP NULL No

description A freeform description

for this role.

VARCHAR(255)` NULL No

end_reason_tp_cd The reason why a

relationship ended.

For example, a spousal

party-to-party

relationship may be

ended by a ″divorce″

reason.

BIGINT NULL No







and time. On

subsequent updates,




request includes a





last_update_user The ID of the user who

last updated the data.

Either the user ID or

user group must be

passed in the XML

header if security or

RoV is turned on.

VARCHAR(20) NULL No


generated key that






BIGINT NULL No

ENTITYSPECUSE Table


spec_use_id A system generated key that

uniquely identifies the usage

of a spec with an entity

within the system.

BIGINT NOT NULL Yes

entity_name The type of entity this spec

use is related to.


instance_pk The primary key of the

related entity.

BIGINT NOT NULL No

spec_id A system generated key that

uniquely identifies a spec

within the system.

BIGINT NOT NULL No

spec_use_tp_cd The code assigned to the

spec use type.

BIGINT NOT NULL No

spec_cascade_tp_cd The code assigned to the

cascade action type for a

spec. For example, if this

spec is cascaded to

descendents in the entity’s

hierarchy.

BIGINT NOT NULL No

explicit_def_ind Indicates that the spec has

been defined for the first

time on this entity.

CHAR(1) NOT NULL No




metadata_info_tp_cd The code assigned to the

metadata info type.

BIGINT NOT NULL No

start_dt Specifies the date when this

record in takes effect.


end_dt Specifies the date when this

record becomes inactive

TIMESTAMP NULL No




time. On subsequent



the update request includes a

matching date/time on this

field; if it does not, the

update fails.


last_update_user Id of user who last updated

the data. Either user ID or

user group must be passed



VARCHAR(20) NULL No






updated or deleted the data

row.

BIGINT NULL No

destination_entity_name The destination entity this

spec use is related to.


ENUMANSWER Table


enum_ans_id BIGINT NOT NULL The primary key of

the Enumanswer

record

Yes

question_id BIGINT NOT NULL Identifies the question

that this enum

answer belongs to.

No

answer_sequence INTEGER NULL Answer sequence

number.

No

enum_ans_tp_cd BIGINT NOT NULL Enum answer type

code

No





used for technical

reasons; whenever a

record is updated,


with the date and


are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make



was retrieved,and




this way only one


time.

No


updated the data.




security/ROV is

turned on.

No


unique, system

generated key that




created, updated or


No

FINANCIALPRODUCT Table


product_id A system generated key

that uniquely identifies

a product within the

system.

BIGINT NOT NULL Yes

tax_position_tp_cd The relative tax position

offered by the product.


product is tax neutral,

provides the customer a

tax advantage, or

provides the FI with a

tax advantage.

BIGINT NULL No




account_required_tp_cd Indicates whether the

product requires an

account or not.

BIGINT NULL No


the product is traded in.

BIGINT NULL No


added/updated, this





to ensure that the










XML header, if


on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

GOODSPRODUCT Table


Null

Option Is PK



product within the system.

BIGINT NOT NULL Yes




time. On subsequent



the update request

includes a matching



fails.





Null

Option Is PK





XML header, if


VARCHAR(20) NULL No







data row.

BIGINT NULL No

GROUPING Table


grouping_id Primary key Value of a

Group

BIGINT NOT NULL Yes


label. For example

Platinum Group for

Credit Cards.


grouping_tp_cd Identifies the code type

of a Group, or

classification associating

a number of like

entities, such as parties.

BIGINT NOT NULL No



the defaulted values.

The target entity for the

group such contact.




used either as an




used by the user to


to the type code.







TIMESTAMP NULL No






the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No




and time. On

subsequent updates,




request includes a






generated key that




created, updated or


BIGINT NULL No

GROUPINGASSOC Table


grouping_assoc_id The primary key for

each group member

record

BIGINT NOT NULL Yes



entity that is being

associated to the group.

BIGINT NULL No

grouping_id The primary key Value

of a group.

BIGINT NOT NULL No



used either as an




the user to provide


record.


effect_start_dt The date that this row

of data comes into

effect.





effect_end_dt The date that this row

of data become

ineffective

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

HIERARCHY Table


hierarchy_id The primary key of the

hierarchy record.

BIGINT NOT NULL Yes


label.




used either as an




used by the user to


to the type code.


start_dt The date when this



end_dt The date when this


TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

hierarchy_tp_cd Identifies the code type

of a hierarchy.

BIGINT NULL No

HIERARCHYNODE Table


hierarchy_node_id The primary key of the

hierarchy node record

BIGINT NOT NULL Yes

hierarchy_id The primary key of the

hierarchy record

BIGINT NOT NULL No


physical business entity

which is part of this

relationship.




entity which is part of

this relationship.

BIGINT NOT NULL No



used either as an




used by the user to


to the type code.









record becomes inactive.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

nodedesig_tp_cd Identifies the node

designate code type of a

hierarchy.

BIGINT NULL No

localedescription A description of the

locale.


HIERARCHYREL Table


hierarchy_rel_id The primary key of the

hierarchy relationship

record.

BIGINT NOT NULL Yes

parent_node_id The primary key of the

parent hierarchy node

record.

BIGINT NOT NULL No

child_node_id The primary key of the

child hierarchy node

record.

BIGINT NOT NULL No






used either as an




used by the user to


to the type code.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

HIERARCHYULTPAR Table


hier_ult_par_id The primary key of the

hierarchy ultimate

parent record.

BIGINT NOT NULL Yes

hierarchy_node_id The primary key of the

hierarchy node record.

BIGINT NOT NULL No






used either as an




used by the user to


to the type code.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

HOLDING Table


holding_id Primary key of a party

holding record.

BIGINT NOT NULL Yes

hold_tp_cd Identifies a type of

party holding. Some

examples include

Vehicles, Property, and

Stocks etc.

BIGINT NOT NULL No




holding_code Identify the holding

code:

V - vehicle

P - property

CHAR(1) NOT NULL No

holding_value_amt The value of the specific

holding.



information.


start_dt The date that the

holding record became

effective, or was

recorded.


end_dt The date that the

holding record is no

longer effective

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

valuamt_cur_tp The currency type for

the holding value

amount.

BIGINT NULL No



IDENTIFIER Table


identifier_id A unique, system

generated key that

identifies a party

identification row in the


system.

BIGINT NOT NULL Yes

id_status_tp_cd Identifies the status of

the identifier provided

by the party. For

example: ″applied for,″

″expired,″ ″certified,″

and others.

BIGINT NULL No


generated key that



system.

BIGINT NOT NULL No

id_tp_cd Identifies the type of

identifier provided by

the party. For example:

″social security number,″

″passport,″ ″driver’s

license number,″ and

others.

BIGINT NOT NULL No

ref_num The actual identifier text

provided by a party. For

example, if the

Identification Type Code

indicates a social

security number was

provided, than this

column contains the

actual 9 characters.

VARCHAR(50) NULL No






TIMESTAMP NULL No

expiry_dt The date on which the

particular identification

expires, such as a

Passport expiry date.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

assigned_by Used to associate a

particular contract role

to a particular identifier.

For example: an

employee number may

be used as an identifier

on a group contract.

BIGINT NULL No

identifier_desc Provides extra


used either as an


the particular

identification or as free


the user to provide


record.


issue_location The issue location of the

identification item.

VARCHAR(30) NULL No



no business logic


field.

TIMESTAMP NULL No





field.

TIMESTAMP NULL No



BIGINT NULL No



INACTIVATEDCONT Table



generated key that



system.

BIGINT NOT NULL Yes

inact_by_user A unique, system

generated key that



system.

VARCHAR(20) NULL No

inact_reason_tp_cd Contains the valid

values for inactivating a

party record, such as

’collapsed’, ’split’ and

’deceased’.

BIGINT NOT NULL No

comments A free form text field

used for entering

additional information

concerning the

inactivated party.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



INACTIVECONTLINK Table


inact_cont_link_id A unique, system

generated key that

identifies an inactivated

party link row in the


system.

BIGINT NOT NULL Yes

link_reason_tp_cd Describes the reason

why two parties are

linked. For example:

″Source collapsed into

target″, ″Source

duplicated as target″,

etc.

BIGINT NOT NULL No

target_cont_id A unique, system

generated key that



system.

BIGINT NOT NULL No

source_cont_id A unique, system

generated key that



system.

BIGINT NOT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



INCOMESOURCE Table


income_source_id A unique, system

generated key that

identifies an income

source row in the


system.

BIGINT NOT NULL Yes


of the amount columns.

BIGINT NULL No


generated key that



system.

BIGINT NOT NULL No

income_src_tp_cd Identifies the type of

income source that the

party provided. For

example: ″annual

salary,″ ″estimated net

worth,″ ″Ownership of

Bonds,″ and others.

BIGINT NULL No

income_source_desc Stores comments

provided by the user

concerning the income

source provided by the

party.


annual_amt Annual Amount is used

when the Income Source

Type Code requires an

amount provided by the

party.

DECIMAL(17,3) NOT NULL No

invest_exper_yrs Investment Experience

in Years is used when

the Income Source Type

Code requires a length

of ownership in years to

be provided by the

party.

SMALLINT NULL No

info_obtained_dt The date that the

information was

obtained from the party.





and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

INSURANCEPRODUCT Table




product within the

system.

BIGINT NOT NULL Yes








includes a matching



fails.






XML header, if


on.

VARCHAR(20) NULL No


unique, system generated


specific transaction

within the log system

that either created,


data row.

BIGINT NULL No



INTERACTION Table


interaction_id A unique, system

generated key that

identifies an interaction


MDM Server system.

BIGINT NOT NULL Yes

recorded_by_user The identifier of the

user of the InfoSphere

MDM Server system

and recorded the

interaction


interact_pt_tp_cd Identifies the media

through which the

interaction was made

possible. Some examples

are telephone, email,

mail, and others.

BIGINT NOT NULL No

recorded_dt The date and time that

the interaction was

recorded.


subject_desc A short, textual

description of the

subject of the interaction

with the customer.


note_desc A free form text line

that allows for

additional comments to

be added for the

interaction.


interact_party The party ID of the

customer that is

involved in the

interaction.


interact_dt The date that the

interaction occurred.


invalid_ind Invalid indicator is used

to invalidate the

interaction record, either

due to error or

miscommunication. This

is used, rather than an

″end date″.

CHAR(1) NULL No

interact_st_tp_cd Interaction Status Type

Code describes the

status of the interaction.

Some examples are

’Awaiting reply’,

’Returned’, ’No answer’

BIGINT NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

interact_resp_tp The type of response for

an interaction.

BIGINT NULL No

entity_name Logical entity name of

the entity that the

interaction is regarding.

For example: CONTACT

or CONTRACT

VARCHAR(20) NULL No

instance_PK The primary key of the

entity that the

interaction is regarding.

BIGINT NULL No

interact_tp_cd Identifies the type of


customer. The

Interaction SubType

Code is dependent on

the Interaction Category

Code. Some example

values are campaign,

incorrect billing, and

others.

BIGINT NOT NULL No



INTERACTIONREL Table


interact_rel_id A unique, system

generated key that


relationship row in the


system.

BIGINT NOT NULL Yes

from_interact_id A unique, system

generated key that



MDM Server system.

BIGINT NOT NULL No

to_interact_id A unique, system

generated key that



MDM Server system.

BIGINT NOT NULL No

interact_rel_tp_cd Describes the types of

relationships

interactions can have

with one another. For

example: escalation,

follow up, and others.

BIGINT NOT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



LOBREL Table


lob_rel_id A unique, system

generated key that

identifies a lob

relationship with an

entity in the InfoSphere

MDM Server system.

BIGINT NOT NULL Yes

entity_name Entity Name is the

name of the physical


part of this relationship.


instance_Pk Entity Instance primary

key is the actual

primary key of the row

in the logical entity that

is part of this

relationship.

BIGINT NOT NULL No



line of business.

BIGINT NOT NULL No

lob_rel_tp_cd Identifies the unique


line of business

relationship type.

BIGINT NOT NULL No





record becomes inactive.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No

LOCATIONGROUP Table



generated key that


group row in the


system.

BIGINT NOT NULL Yes

undel_reason_tp_cd Identifies the reason for

not using a particular

address. Some example

values are ″returned

mail,″ ″change in zip

code,″ and others.

BIGINT NULL No


generated key that



system.

BIGINT NOT NULL No

member_ind Indicates that the party

is a member of the

″household″, in this case

a simplistic

representation, as it is

only used in conjunction

with common addresses.

CHAR(1) NULL No

preferred_ind Indicates that the Party

″prefers″ to use this

particular location for

correspondence.

CHAR(1) NULL No

solicit_ind Determines whether this

party be solicited at this

specific location group.

CHAR(1) NULL No

loc_group_tp_code Determines the type of

the location group. The

value ″A″ indicates an

address and the values

″C″ indicates contact

method.

CHAR(1) NOT NULL No




effect_start_mmdd The two digit month

and two digit day

which the Party wishes

this contact point to be

used. It is used with the

Effective End Month

Day to identify a date

range of when this

party contact point

relationship should be

used.

SMALLINT NULL No

effect_end_mmdd The two digit month

and two digit day

which the Party wishes

this contact point to be

used. It is used with the

Effective Start Month

Day to identify a date

range of when this

party contact point

relationship should be

used.

SMALLINT NULL No

effect_start_tm The time of day when a

party is available at this

location group.

INTEGER NULL No

effect_end_tm The time of day when a

party is no longer

available at this location

group.

INTEGER NULL No






TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No



no business logic


field.

TIMESTAMP NULL No





field.

TIMESTAMP NULL No



BIGINT NULL No

MACROROLEASSOC Table


macrorole_assoc_id A unique ID to

represent the party

macro role association

in the system.

BIGINT NOT NULL Yes

cont_macro_role_id A unique ID to identify

a party macro role in

the system.

BIGINT NOT NULL No

entity_name The name of the entity

which is being

associated with the

party macro role. This

will be the name of the

entity representing party

child data. Examples

includes

″PERSONNAME″,

″ADDRESSGROUP″ and

others.


instance_pk The ID of the entity that

is being associated with

the party macro role.

This will be the ID of

the entity representing

party child data.

BIGINT NULL No


association becomes

active.



association becomes

inactive.

TIMESTAMP NULL No








relationship may be


reason.

BIGINT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

MISCVALUE Table


miscvalue_Id The primary key of

Miscellaneous Value.

BIGINT NOT NULL Yes



entity that has the

value.

BIGINT NOT NULL No



the value. For example:

contact.





miscvalue_tp_cd This is the misc. value

type that corresponds to

a particular misc. value

category. Some

examples of miscvalue

type are number of



and others.

BIGINT NOT NULL No

value_string The value content. For

example, for a credit

risk score record 8.


priority_tp_cd Identifies the priority of

a task, a campaign,

value and others.

Examples include high,

medium, low.

BIGINT NULL No



BIGINT NULL No


information.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No




valueattr_tp_cd_0 The value attribute type

that corresponds to a

particular misc. value

type. Some examples of

the value attribute types

are number of



status, effective date,

number of products and

others.

BIGINT NULL No

attr0_value The Attribute Value

field.






the value attribute types

are number of



status, effective date,

number of products and

others.

BIGINT NULL No


field.






the value attribute type

are number of



customer loyalty, status,

credited date and

others.

BIGINT NULL No


field.






value attribute type are

number of employees,

gold value, credit card

risk score, status,

customer loyalty and

others.

BIGINT NULL No


field.












risk score, status,

number of products,

customer and others.

BIGINT NULL No


field.






miscvalue type are



risk score, status,

customer loyalty,

created date and others.

BIGINT NULL No


field.






value attribute types are



risk score, status,

created date, customer

loyalty and others.

BIGINT NULL No


field.









risk score, status,

effective date, customer

loyalty and others.

BIGINT NULL No


field.












risk score, status,


loyalty and others.

BIGINT NULL No


field.





type . Some examples of




risk score, status,


loyalty and others.

BIGINT NULL No


field.


NATIVEKEY Table


native_key_id A unique, system

generated key that


native key row in the


system.

BIGINT NOT NULL Yes

admin_contract_id The actual text or

number that is used in

the administrative

source system to

identify a contract.



generated key that


component in the


system.

BIGINT NOT NULL No

admin_fld_nm_tp_cd Identifies the field name

that the native key

refers to, for example,

policy number, policy

suffix, account number,

branch, and others.

BIGINT NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

contract_comp_ind Describes which table

the native key applies

to. If the contract

component indicator is

’Y’, the native key

applies to the Contract

Component. If the

contract indicator is not

’Y’, the native key

applies to the Contract.

The contract ID is the

value from the Contract

Component (the

contract component ID).

CHAR(1) NULL No

NLSENUMANSWER Table


nlsenum_ans_id The primary key of the

NLSEnumanswer record

BIGINT NOT NULL Yes

lang_tp_cd Language type code,

primary key of

NLSEnumanswer record

BIGINT NOT NULL Yes

question_id Identifies the question

that this enumerated

answer belongs to.

BIGINT NOT NULL No

answer Possible answer text. VARCHAR(120) NOT NULL No







additional definition or


used by the user to

provide further

meaning.


last_update_dt Last Update Date is

used for technical

reasons; whenever a

record is updated, this


the date and time. For

example, if two people

are looking at the same

record at the same time,

and both decide to do

an update, we look at

that field to make sure

it hasn’t changed (been

updated) since it was

retrieved, and then

allow the update to go

through. It is a sort of

record locking, this way

only one user can

update at a time.






XML header, if security

or ROV is turned on.

VARCHAR(20) NULL No


unique, system

generated key that




created, updated or


BIGINT NULL No

NLSQUESTION Table


nlsquestion_id BIGINT NOT NULL The primary key of

the nlsquestion record

Yes

lang_tp_cd BIGINT NOT NULL Language type,

primary key of the

NLSQuestion record.

Yes

quesnr_id BIGINT NOT NULL Questionnaire id that

this question belongs

to.

No




question VARCHAR(255) NOT NULL Question text No


extra information,

which can be used

either as an


or as free form

comments used by

the user to provide

further meaning.

No


used for technical

reasons; whenever a

record is updated,


with the date and


are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make



was retrieved,and




this way only one


time.

No


updated the data.




security/ROV is

turned on.

No


unique, system

generated key that




created, updated or


No

NLSQUESTIONNAIRE Table


lang_tp_cd BIGINT NOT NULL Language type code,

The primary key of

the NLSQuestionnaire

record.

Yes




nlsquesnr_id BIGINT NOT NULL The Primary Key of

the nlsquestionnaire

record

Yes

name VARCHAR(120) NOT NULL Name is a short,

meaningful label.

No


extra information,

which can be used

either as an


or as free form

comments used by

the user to provide

further meaning.

No


used for technical

reasons; whenever a

record is updated,


with the date and


are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make



was retrieved,and




this way only one


time.

No


updated the data.




security/ROV is

turned on.

No


unique, system

generated key that




created, updated or


No



ORG Table



generated key that



system.

BIGINT NOT NULL Yes



organization. For

example: trust,


etc.

BIGINT NOT NULL No

industry_tp_cd The industry type for

the organization. For

example: SIC.

BIGINT NULL No

established_dt The date that the

company or charity was

established. For trusts,

this is the inception

date.

TIMESTAMP NULL No

buy_sell_agr_tp_cd An identifier that


type of buy-sell

agreement from another.

BIGINT NULL No

profit_ind Indicates whether the

organization has a Profit

or Non-profit status.

CHAR(1) NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



ORGNAME Table


org_name_id A unique, system

generated key that

identifies a organization

name row in the


system.

BIGINT NOT NULL Yes

org_name_tp_cd Identifies the type of

name for this

organization. For

example: ″Legal,″

″Doing Business As,″

″Abbreviated,″ and

others.

BIGINT NOT NULL No


generated key that



system.

BIGINT NOT NULL No

org_name The actual text of the

organization name. The

text should correspond

to one of the types of

names identified in the

Organization Name

Type Code.


s_org_name A standardized spelling

of the organization’s

name that is used for

searching.


p_org_name The phonetic key for

Organization Name.

VARCHAR(20) NULL No

name_search_key Not currently used. VARCHAR(30) NULL No






TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



no business logic


field.

TIMESTAMP NULL No





field.

TIMESTAMP NULL No



BIGINT NULL No

PAYMENTSOURCE Table



generated key that



MDM Server system.

BIGINT NOT NULL Yes

payment_src_code Designates the type of

payment source as

follows:

P - Payroll deduction

C - Charge card

B - Bank account

CHAR(1) NOT NULL No

start_dt The date that the

payroll deduction or

charge card or bank

account record became

effective, or was

recorded.





end_dt The date that the

payroll deduction or

charge card or bank

account record is no

longer effective

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No


generated key that



system.

BIGINT NOT NULL No

PAYROLLDEDUCTION Table



generated key that



MDM Server system.

BIGINT NOT NULL Yes

employer_name The full name of the

employer when using

payroll deduction to

pay for a contract or

account.





payroll_no The identifier assigned

to uniquely identifies

the employee when

using payroll deduction

to pay for a contract or

account


description Extra information that



the payroll deduction or


used by the user to


to the payroll deduction.





and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

PERSON Table



generated key that



system.

BIGINT NOT NULL Yes

marital_st_tp_cd The marital status of a

person. For example:

single, widowed,

divorced, and others.

BIGINT NULL No




birthplace_tp_cd A Country Type Code

identifying the country

of birth.

BIGINT NULL No

citizenship_tp_cd The country where an

individual is a citizen.

BIGINT NULL No

highest_edu_tp_cd The level of schooling

that this person has

received. Examples

include high school,

college, university, and

others.

BIGINT NULL No

age_ver_doc_tp_cd An identifier that


type of document being

used to verify a client’s

age from another.

Examples include birth

certificate, driver’s

license, and others.

BIGINT NULL No

gender_tp_code Identifies the sex of a

Person.

CHAR(1) NULL No

birth_dt The date of birth of the

person.

TIMESTAMP NULL No

deceased_dt The date of death of the

person.

TIMESTAMP NULL No

children_ct The total number of

children that this person

has.

SMALLINT NULL No

disab_start_dt The date the person

became disabled

TIMESTAMP NULL No

disab_end_dt The date the person

ceased being disabled.

TIMESTAMP NULL No

user_ind Indicates whether this a

person is a user of the


system.

CHAR(1) NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

PERSONNAME Table


person_name_id A unique, system

generated key that

identifies a person name


MDM Server system.

BIGINT NOT NULL Yes

prefix_name_tp_cd Identifies the party’s

name prefix. Examples

include Mr., Mrs., Dr.,

and others.

BIGINT NULL No

prefix_desc The actual prefix of

name if the Prefix of

Name Type Code’s

value is ″other.″

VARCHAR(20) NULL No

name_usage_tp_cd Identifies the type of

name for this person.

For example: ″Legal,″

″Nick Name,″ ″Maiden

Name,″ and others.

BIGINT NOT NULL No

given_name_one The first given name

(commonly known as a

first name) of the

person.

VARCHAR(25) NULL No

given_name_two The second given name


middle name) of the

person.

VARCHAR(25) NULL No

given_name_three The third given name


middle name) of the

person.

VARCHAR(25) NULL No

given_name_four The fourth given name


middle name) of the

person.

VARCHAR(25) NULL No




last_name Identifies the last name

of a person.


p_last_name The phonetic key for

Last Name.

VARCHAR(20) NULL No

p_given_name_one The phonetic key for

Given Name One.

VARCHAR(20) NULL No

p_given_name_two The phonetic key for

Given Name Two.

VARCHAR(20) NULL No

p_given_name_three The phonetic key for

Given Name Three.

VARCHAR(20) NULL No

p_given_name_four The phonetic key for

Given Name Four.

VARCHAR(20) NULL No

generation_tp_cd Identifies the party’s

name generation.

Examples include ″the

first, the second, and

others.″.

BIGINT NULL No

suffix_desc Identifies the name

suffix of a person. For

example: ″Jr.,″ ″MD,″

″Esq,″ and others.

VARCHAR(20) NULL No






TIMESTAMP NULL No


generated key that



system.

BIGINT NOT NULL No

use_standard_ind Determines whether the

standardized name is

used for this party.

CHAR(1) NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No



no business logic


field.

TIMESTAMP NULL No





field.

TIMESTAMP NULL No



BIGINT NULL No

PERSONSEARCH Table


person_search_id A unique, system

generated key that

identifies a person

search record in the


system.

BIGINT NOT NULL Yes

person_name_id A unique, system

generated key that

identifies a person name


MDM Server system.

BIGINT NOT NULL No


generated key that



system.

BIGINT NOT NULL No

given_name_one The first given name


first name) of the

person. If

standardization of the

name has taken place,

the standardized version

of the name will be

stored here.

VARCHAR(25) NULL No




given_name_two The second given name


middle name) of the

person. If




of the name will be

stored here.

VARCHAR(25) NULL No

given_name_three The third given name


middle name) of the

person. If




of the name will be

stored here.

VARCHAR(25) NULL No

given_name_four The fourth given name


middle name) of the

person. If




of the name will be

stored here.

VARCHAR(25) NULL No

last_name The last name of a

person. If




of the name will be

stored here.




TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No

PHONENUMBER Table


phone_number_id BIGINT NOT NULL A unique, system

generated key that

identifies a phone

number.

Yes

country_code VARCHAR(4) NULL The part of the phone

number that

represents the

country.

No

area_code VARCHAR(6) NULL The part of the phone

number that

represents the area

(finer grained than

country). In North

America, for example,

it would be the ’905’

portion of (905)

555-1234. Germany

can have 2 to 5 digits

in their area code.

No

exchange VARCHAR(6) NULL The part of the phone

number that

represents the

exchange (finer

grained area than that

of the area code). In

North America, for

example, it would be

the ’555’ portion of

(905) 555-1234.

No

ph_number VARCHAR(20) NULL The part of the phone

number that

represents the local

number. In North

America, for example,

it would be the ’1234’

portion of (905)

555-1234

No




extension VARCHAR(8) NULL The part of the phone

number that

represents the

extension (this is

typically applicable

for business phone

numbers). It would

be the ’56789’ portion

of (905) 555-1234 ext.

56789.

No

last_update_dt TIMESTAMP NOT NULL When a record is

added or updated,


with the date and

time. On subsequent

updates, WCC uses

this information to

ensure that the

update request

includes a matching

date and time on this

field; if it does not,

the update fails.

No

last_update_user VARCHAR(20) NULL The ID of user who

last updated the data.

Either the user ID or

user group must be

passed in the XML

header if security or

ROV is turned on.

No

last_update_tx_id BIGINT NULL A unique, system

generated key that




created, updated or


No

contact_method_id BIGINT NOT NULL Contact Method ID is

a unique, system

generated key that


method in the WCC

system.

No

PPREFACTIONOPT Table


ppref_act_opt_id The Privacy Preference

Action Option primary

key. Identifies the action

type subset available as

options for a specific

privacy preference type.

BIGINT NOT NULL Yes




ppref_tp_cd Used to indicate the

type of privacy

preference being stored,

for example: credit

worthiness, personal

info, and others.

BIGINT NOT NULL No

ppref_action_tp_cd Identifies the action to

be taken based on the

privacy preference set

by the customer or by

company default setting.

For example: Do not

call, Do not mail.

BIGINT NOT NULL No






TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

PPREFDEF Table


ppref_id The Privacy Preference

Record primary key.

BIGINT NOT NULL Yes

ppref_seg_tp_cd The segment associated

with the privacy

preference record.

BIGINT NULL No




regulation_value The privacy preference

default regulation value

which can be the name

of the regulation.


default_ind This is the indicator for

the default privacy

preference.

CHAR(1) NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

PPREFDEFREL Table


pprefdefrel_id Identifies a relationship

that two privacy

preference records can

have between one

another.

BIGINT NOT NULL Yes

parent_ppref_id The primary key for the

″parent″ of the

relationship.

BIGINT NOT NULL No

child_ppref_Id The primary key for the

″child″ of the

relationship.

BIGINT NOT NULL No




rel_desc Provides extra


used either as an


the relationship or as

free form comments

used by the user to









TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

last_update_txn_id A unique, system

generated key that




created, updated or


BIGINT NULL No

PPREFENTITY Table


ppref_id A unique, system

generated key that

identifies a privacy

preference object in

InfoSphere MDM

Server.

BIGINT NOT NULL Yes

ppref_entity The name of the


the privacy preference.

VARCHAR(50) NULL No




ppref_instance_pk The actual primary key


entity that has the

privacy preference.

BIGINT NULL No

ppref_reason_tp_cd Identifies the reason

given by customer for

making a privacy

preference selection.

BIGINT NOT NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



BIGINT NOT NULL No

PPREFINSTANCE Table


ppref_inst_Id Uniquely identifies an

instance record

associated with a

privacy preference

record.

BIGINT NOT NULL Yes


Record primary key.

BIGINT NOT NULL No



associated with the

privacy preference

values.








with the privacy

preference values.

BIGINT NULL No




and time. On

subsequent updates,




request includes a





Last_Update_User The ID of user who last


the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

last_Update_Tx_Id A unique, system

generated key that




created, updated or


BIGINT NULL No

PRIVPREF Table



Record primary key.

BIGINT NOT NULL Yes

value_string Stores the actual

privacy/preference

value for the type

identified and the entity

or instance pk

identified.

For example: entity

″Contact″ instance

″10001″ has a preference

type ″Preferred

Salutation″ with a value

of ″Mike″

VARCHAR(50) NULL No






TIMESTAMP NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

ppref_act_opt_id The Privacy Preference

Action Option primary

key. Identifies the action

type subset available as

options for a specific

privacy preference type.

BIGINT NULL No

ppref_tp_cd Privacy Preference Type

Code identifies the

particular type of

privacy/preference

related to the entity.

BIGINT NOT NULL No

PRODTPREL Table


prod_tp_rel_id The Product Type

Relationship record

primary key.

BIGINT NOT NULL Yes

rel_desc The type of relationship

that two products can

have between one

another. For example:

″categorize″.





to_prod_tp_cd The type of product

associated with the

contract (or at some


family). Examples




BIGINT NOT NULL No

from_prod_tp_cd The type of product

associated with the

contract (or at some


family). Examples




BIGINT NOT NULL No






TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

last_update_txn_id A unique, system

generated key that




created, updated or


BIGINT NULL No

prodrel_tp_cd Identifies the type of


products can have


For example:

″categorize″.

BIGINT NOT NULL No



PRODUCT Table




a product within the

system.

BIGINT NOT NULL Yes

product_type_id The identifier that

describes what type of

product this is.

BIGINT NOT NULL No

name The name of the

product.


short_description A short description of

the product.


description A long description of

the product.


prod_struc_tp_cd The basic structure of

the product. Examples:

Standalone, Bundle Etc

BIGINT NOT NULL No

status_tp_cd The lifecycle status of

the product.

BIGINT NULL No

status_reason_tp_cd Why the product is in

its current lifecycle state.

BIGINT NULL No

availability_tp_cd How widely available

the product is to the

target market. For

example, general

availability, restricted

availability.

BIGINT NULL No

primary_target_market_tp_cd A primary market this

product targets.

BIGINT NULL No




and time. On



to ensure that the










XML header, if


on.

VARCHAR(20) NULL No





unique, system

generated key that




created, updated or


BIGINT NULL No

PRODUCTCATEGORYASSOC Table


product_category_assoc_id A system generated key


an association between

a product and category

within the system.

BIGINT NOT NULL Yes

product_id The product that is

associated to the

category.

BIGINT NOT NULL No

category_id The category the

product is associated to.

BIGINT NOT NULL No

hierarchy_id The hierarchy the

category belongs to.

BIGINT NOT NULL No

start_dt The date the association

is effective.


end_dt The date the association

is not longer effective.

TIMESTAMP NULL No




and time. On



to ensure that the










XML header, if


on.

VARCHAR(20) NULL No





unique, system

generated key that




created, updated or


BIGINT NULL No

PRODUCTCONTRACTREL Table


prod_cont_rel_id BIGINT NOT NULL The primary key of

the Product Contract

Relationship record.

Yes

product_id BIGINT NOT NULL A system generated

key that uniquely

identifies a product

within the system.

No

contract_id BIGINT NOT NULL Contract ID is a

unique, system

generated key that


in the WCC system.

No

start_dt TIMESTAMP NOT NULL The Start date from

when this

relationship is valid

No

end_dt TIMESTAMP NULL The End date till

when this

relationship is valid

No

prod_cont_rel_tp_cd BIGINT NULL The type of the

relationship between

the product and the

contract

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No

last_update_tx_id BIGINT NULL Id of user who last

updated the data.




security/RoV is

turned on.

No




last_update_user VARCHAR(20) NULL Transaction ID is a

unique, system

generated key that




created, updated or


No

PRODUCTEQUIV Table


product_equiv_id BIGINT NOT NULL A system generated

key that uniquely


equivalence record

within the system.

Yes

product_id BIGINT NOT NULL The product these

equivalencies are for.

No

admin_sys_tp_cd BIGINT NOT NULL The external system. No

product_equiv_key VARCHAR(160) NULL A representation of

the full key

concatenated and

formatted.

No

key_1 VARCHAR(30) NOT NULL First part of the key. No

key_2 VARCHAR(30) NULL Second part of the

key.

No

key_3 VARCHAR(30) NULL Third part of the key. No

key_4 VARCHAR(30) NULL Fourth part of the

key.

No

key_5 VARCHAR(30) NULL Fifth part of the key. No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No





unique, system

generated key that




created, updated or


No

PRODUCTIDENTIFIER Table


product_identifier_id BIGINT NOT NULL A system generated

key that uniquely


identifier within the

system.

Yes

product_id BIGINT NOT NULL The product the

identifier belongs to.

No

product_identifier_tp_cd BIGINT NOT NULL The code that

describes the

identifier.

No

ref_num VARCHAR(50) NULL The identifier value. No

start_dt TIMESTAMP NOT NULL The date the

identifier is effective.

No

end_dt TIMESTAMP NULL The date the

identifier is no longer

effective.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No





unique, system

generated key that




created, updated or


No

PRODUCTNLS Table


product_nls_id BIGINT NOT NULL A system generated

key that uniquely

identifies a localized

product within the

system.

Yes


Product NLS belong

to.

No

lang_tp_cd BIGINT NOT NULL Identifies a spoken

language such as

English, French,

Spanish, German, etc.

No

name VARCHAR(120) NOT NULL The localized name of

the product.

No

short_description VARCHAR(255) NULL A localized short

description of the

product.

No

description VARCHAR(500) NULL A localized long

description of the

product.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No





unique, system

generated key that




created, updated or


No

PRODUCTREL Table


product_rel_id BIGINT NOT NULL A system generated

key that uniquely

identifies a

relationship between

two products within

the system.

Yes

from_prod_id BIGINT NOT NULL The source product in

the relationship.

No

to_prod_id BIGINT NOT NULL The target product in

the relationship.

No

product_rel_tp_cd BIGINT NOT NULL The type of

relationship.

No

start_dt TIMESTAMP NOT NULL The date the

relationship becomes

effective.

No

end_dt TIMESTAMP NULL The date the

relationship is no

longer effective.

No

rel_desc VARCHAR(255) NULL description of the

product relationship.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No





unique, system

generated key that




created, updated or


No

PRODUCTTYPE Table


product_type_id BIGINT NOT NULL A type of product

that (unless is the

root product type) is

a subtype of another

product type.

Yes

name VARCHAR(50) NOT NULL The name of the

product type.

No

description VARCHAR(255) NULL The description of the

product type.

No

parent_prod_type_id BIGINT NULL The parent type for

this type.

No

metadata_info_tp_cd BIGINT NOT NULL The id of the

meta-data package

this spec belongs to

No

node_tp_cd BIGINT NOT NULL Describes the level of

the product type and

is required to

understand what is

hardened in the

database model or

not.

No

start_dt TIMESTAMP NOT NULL When the type

becomes effective and

can create products of

that type.

No

end_dt TIMESTAMP NULL When the type is no

longer effective and

can no longer create

products of that type.

Note that products of

the type will continue

to exist.

No





added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No


unique, system

generated key that




created, updated or


No

PRODUCTTYPENLS Table


product_type_nls_id BIGINT NOT NULL A system generated

key that uniquely


product type within

the system.

Yes

product_type_id BIGINT NOT NULL The product type

these

ProductTypeNLS

belong to.

No


language such as

English, French,


No

Identifies the language

for which the product

type has been localized.

name VARCHAR(120) NOT NULL The name of the

product type for a

particular locale.

No




description VARCHAR(500) NULL The description of the

product type for a

particular locale.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No


unique, system

generated key that




created, updated or


No

PRODUCTVAL Table


product_values_id BIGINT NOT NULL A system generated

key that uniquely


value within the

system.

Yes

spec_id BIGINT NOT NULL The spec that

describes the

definition of the

values.

No

spec_fmt_id BIGINT NOT NULL The format (or

version) of the spec

these values validate

to.

No


values belong to.

No

value_xml CLOB(1G) NOT NULL The values as defined


format.

No




start_dt TIMESTAMP NOT NULL The date the values

become effective.

No

end_dt TIMESTAMP NULL The date the values

are no longer

effective.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No


unique, system

generated key that




created, updated or


No

PRODUCTVALNLS Table


product_values_nls_id BIGINT NOT NULL A system generated

key that uniquely


product value within

the system.

Yes

product_values_id BIGINT NOT NULL A system generated

key that uniquely

identifies a source

product value within

the system.

No


language such as

English, French,


No

value_xml CLOB(1G) NOT NULL The values as defined


format.

No





added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No


unique, system

generated key that




created, updated or


No

PROPERTY Table




BIGINT NOT NULL Yes


generated key that


the InfoSphere MDM

Server system.

BIGINT NULL No




and time. On

subsequent updates,




request includes a










the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

QUESTION Table


question_id BIGINT NOT NULL The primary key of

the question record.

Yes

quesnr_id BIGINT NOT NULL Identifies the

questionnaire that

this question belongs

to.

No

question_sequence INTEGER NULL Question sequence

number.

No

question_tp_cd BIGINT NOT NULL Question type code. No

answer_data_tp_cd INTEGER NOT NULL The expected answer

type code.

No

mandatory CHAR(1) NOT NULL The answer

mandatory indicator.

No

answer_cardinality SMALLINT NOT NULL The expected answer

cardinality.

No

parent_ques_id BIGINT NULL The id of the parent

question.

No





used for technical

reasons; whenever a

record is updated,


with the date and


are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make



was retrieved,and




this way only one


time.

No


updated the data.




security/ROV is

turned on.

No


unique, system

generated key that




created, updated or


No

QUESTIONNAIRE Table


quesnr_id BIGINT NOT NULL The Primary Key of

the questionnaire

record

Yes

quesnr_tp_cd BIGINT NOT NULL Questionnaire type

code.

No

ref_num VARCHAR(50) NULL External reference

number

No

created_dt TIMESTAMP NOT NULL Specifies the date

when this record is

created

No

start_dt TIMESTAMP NULL Specifies the date

when this record in

takes effect.

No




end_dt TIMESTAMP NULL Specifies the date

when this record

becomes inactive

No


used for technical

reasons; whenever a

record is updated,


with the date and


are looking at the

same record at the

same time, and both

decide to do an

update, we look at

that field to make



was retrieved,and




this way only one


time.

No


updated the data.




security/ROV is

turned on.

No


unique, system

generated key that




created, updated or


No

ROLEIDENTIFIER Table


role_identifier_id A unique, system

generated key that

identifies a party

contract role identifier


MDM Server system.

BIGINT NOT NULL Yes





generated key that

identifies a party



system.

BIGINT NOT NULL No

identifier_id A unique, system

generated key that

identifies a party

identification row in the


system.

BIGINT NOT NULL No



used either as an




the user to provide

further meaning of the

record.


expiry_dt The date on which the

particular role

identification expires.

TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



ROLELOCATION Table


role_location_id A unique, system

generated key that

identifies a party

contract role location


MDM Server system.

BIGINT NOT NULL Yes


generated key that


group row in the


system.

BIGINT NOT NULL No


generated key that

identifies a party



system.

BIGINT NOT NULL No






TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

undel_reason_tp_cd A reason for not using a

particular address. Some

example values are

″returned mail,″ ″change

in zip code,″ and others.

BIGINT NULL No


generated key that




created, updated or


BIGINT NULL No



ROLELOCPURPOSE Table


role_loc_purp_id A unique, system

generated key that

identifies a party


reason row in the


system.

BIGINT NOT NULL Yes

purpose_tp_cd The purpose for the

location as it relates to a

role on a contract. For

example, the owner’s

residence address is

associated with the

contract for the purpose

of sending statements

BIGINT NOT NULL No



used either as an




used by the user to


to the type code.







TIMESTAMP NULL No




and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No





generated key that




created, updated or


BIGINT NULL No

role_location_id A unique, system

generated key that

identifies a party



MDM Server system.

BIGINT NOT NULL No

ROLESITUATION Table


role_situation_id A unique, system

generated key that

identifies a party

situation role row in the


system.

BIGINT NOT NULL Yes


generated key that

identifies a party



system.

BIGINT NOT NULL No

arrangement_tp_cd Describes the type of

agreement that the party

contract role has with

the contract. For

example: time delay

arrangement such as a

common disaster.

BIGINT NOT NULL No






TIMESTAMP NULL No



the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No







and time. On

subsequent updates,




request includes a






generated key that




created, updated or


BIGINT NULL No

SEARCHXCLRULE Table


LAST_NAME The last name value

from Person Name or

from Person Search.


P_LAST_NAME The last name phonetic

key from Person Name.


GIVEN_NAME_ONE The ’given name one’

value from Person

Name or from Person

Search.


P_GIVEN_NAME_ONE The ’given name one’

phonetic key from

Person Name.


CITY_NAME The city name value

from Address.


P_CITY_NAME The city name phonetic

key from Address.


FREQUENCY The number of times

this exclusion rule

combination occurred.

BIGINT NOT NULL No

SERVICEPRODUCT Table


product_id BIGINT NOT NULL A system generated

key that uniquely


within the system.

Yes





added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No


unique, system

generated key that




created, updated or


No

SPEC Table


spec_id BIGINT NOT NULL A unique,


that identifies a spec

in the MDM system

Yes

metadata_info_tp_cd BIGINT NOT NULL The id of the

meta-data package

this spec belongs to.

No

spec_name VARCHAR(100) NOT NULL Name given to the

spec

No

spec_namespace VARCHAR(500) NOT NULL Namespace this spec

belongs to

No

active_format_id BIGINT NOT NULL The spec format that

is ″active″ for this

spec

No

start_dt TIMESTAMP NOT NULL The date on which

this record becomes

active.

No

end_dt TIMESTAMP NULL The date on which

this record becomes

inactive.

No





added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


unique, system

generated key that




created, updated or


No


updated the data.




security/RoV is

turned on.

No

SPECFMT Table


spec_format_id BIGINT NOT NULL A unique,


that identifies a spec

format in the MDM

system.

Yes

spec_id BIGINT NOT NULL The id of the spec

this format is applies

to.

No

external_xsd CLOB(1G) NOT NULL Client XSD for this

format

No

internal_xsd CLOB(1G) NOT NULL Server XSD for this

format

No

localized_xsd CLOB(1G) NULL It contains the

localized xsd

information for the

mentioned spec

format.

No

format_version BIGINT NOT NULL The version number

for this format.

No





added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


updated the data.




security/RoV is

turned on.

No


unique, system

generated key that




created, updated or


No

SPECFORMATTRANSLATION Table


spec_format_translation_id BIGINT NOT NULL A unique,

system-generated

key that identifies a

spec format

translation in the

MDM system

Yes

spec_format_id BIGINT NOT NULL The id of the spec

format the

translation applies

to

No

lang_tp_cd BIGINT NOT NULL Code for the

translation’s locale

language

No

translation CLOB(1073741824) NOT NULL An XML document

holding the

translations of a

given spec’s

attributes for a

given locale

No




last_update_dt TIMESTAMP NOT NULL Whenever a record

is added/updated,


with the date and

time. On subsequent

updates, we utilize

this information to

ensure that the

update request

includes a matching

date/time on this

field; if it does not,

the update fails.

No


updated the data.

Either user ID or

user group must be

passed in the XML

header, if

security/RoV is

turned on.

No


unique, system

generated key that

identifies the

specific transaction

within the log

system that either

created, updated or

deleted the data

row.

No

SUSPECT Table


suspect_id A unique, system

generated key that

identifies a suspect row

in the InfoSphere MDM

Server system.

BIGINT NOT NULL Yes


generated key that



system.

BIGINT NOT NULL No

suspect_cont_id A unique, system

generated key that



system.

BIGINT NOT NULL No




susp_st_tp_cd Indicates the current

situation for a particular

suspect record - suspect

duplicate, not duplicate,

under investigation, and

others.

BIGINT NOT NULL No

source_tp_cd The source of the

Suspect Reason Code

(system marked or user

marked).

BIGINT NOT NULL No

susp_reason_tp_cd The field that caused

the data match to occur.

BIGINT NULL No

match_relev_tp_cd Identifies party match

relevancies, providing a

description of which

elements were matched.

BIGINT NULL No

adj_action_code When a PARTY is

identified as a

SUSPECT, the

SUSPECT(party ID) may

have relevancy scores

dictating a ’B’ action

type. The client may

take into account

relationships or roles on

a policy that may adjust

the SUSPECT to an ’A’

type action or

alternatively a ’C’ type

SUSPECT.

CHAR(2) NULL No

adj_action_tp_cd Identifies the business

reasons for the action

code on the suspect

identification being

modified.

BIGINT NULL No

cur_suspect_tp_cd Identifies the current

suspect type.

BIGINT NULL No

cur_mtch_eng_tp_cd The current matching

engine.

BIGINT NULL No

match_eng_tp_cd Identifies the matching

engine to use for

matching parties.

BIGINT NULL No

weight The calculated weight

used by the matching

engine.


created_by The ID of the user,

system, or other entity

that created the data.

VARCHAR(20) NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No

SUSPECTAUGMENT


SUSPECT_AUGMENT_ID The unique Suspect

Augmentation ID for

this record.

BIGINT NOT NULL Yes

SUSPECT_ID The Suspect ID


record.

BIGINT NOT NULL No

ADJ_ACTION_TP_CD The type code

indicating the Adjust

Action type.

BIGINT NOT NULL No

SUSPECT_TP_CD The type code

indicating the Suspect

type.

BIGINT NOT NULL No

WEIGHT The calculated weight

for this suspect

augmentation record.


MATCH_ENG_TP_CD The type code

indicating the matching

engine to use for

matching parties.

BIGINT NOT NULL No




LAST_UPDATE_DT When a record is added



and time. On

subsequent updates,




request includes a





LAST_UPDATE_USER The ID of user who last


the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No

LAST_UPDATE_TX_ID A unique, system

generated key that






BIGINT NULL No

TERMCONDITION Table


condition_id BIGINT NOT NULL The primary key of a

condition record.

Yes

condition_owner_tp_cd BIGINT NOT NULL Identifies the owner of the

Condition. The Condition

Attribute entity is common to

both Account and Product

Domain. Value is from the

code table

CDCONDITIONOWNERTP

No

condition_usage_tp_cd BIGINT NOT NULL Identifies the usage type of the

condition describing the

purpose of the condition.

Value is from the code table

CDCONDITIONUSAGETP.

No

name VARCHAR(120) NULL The name of this condition. No

description VARCHAR(3000) NULL The description for this

condition.

No

from_date TIMESTAMP NOT NULL The start date from when a

condition is valid.

No

to_date TIMESTAMP NULL The date till when a condition

is valid.

No




overrides_condition_id BIGINT NULL The condition Id which is

overridden by this Condition.

No

overridable_ind CHAR(1) NULL A flag that indicates if the

given condition can be

overridden.

No

mandatory_ind CHAR(1) NULL A flag that indicates if this

condition is mandatory

No

parent_condition_id BIGINT NULL The Term Condition that is the

parent of this condition. Used

in hierarchical / nested term

conditions

No


added/updated, this field is


time. On subsequent updates,

we utilize this information to

ensure that the update request

includes a matching date/time

on this field; if it does not, the

update fails.

No

last_update_tx_id BIGINT NULL Transaction ID is a unique,





updated or deleted the data

row.

No

last_update_user VARCHAR(20) NULL Id of user who last updated

the data. Either user ID or

user group must be passed in

the XML header, if


No

override_rule_id VARCHAR(10) NULL The column represents

associated ruleId if different

from the one set in

CdConditionUsageTp

No

TERMCONDITIONNLS Table


condition_nls_id BIGINT NOT NULL The primary key of

this table.

Yes

condition_id BIGINT NOT NULL The condition id of

the condition record

for which localization

data is added.

No

lang_tp_cd BIGINT NOT NULL The language code on

which data is

localized.

No

name VARCHAR(120) NULL The localized value of

the name field of this

condition.

No




description VARCHAR(3000) NULL The localized value of

the description field

of this condition.

No


added/updated, this



subsequent updates,

we utilize this


that the update

request includes a

matching date/time



No


unique, system

generated key that




created, updated or


No


updated the data.




security/RoV is

turned on.

No

VEHICLE Table




BIGINT NOT NULL Yes

vin_num The unique 17 digit

vehicle identification

number.

VARCHAR(20) NULL No

vehicle_make The manufacturer name

of the vehicle.

VARCHAR(20) NULL No

vehicle_model The vehicle model as

identified by the

manufacturer.

VARCHAR(20) NULL No

vehicle_year The vehicle year is the

year the vehicle was

built.

BIGINT NULL No







and time. On

subsequent updates,




request includes a







the user ID or user



security or RoV is

turned on.

VARCHAR(20) NULL No


generated key that




created, updated or


BIGINT NULL No



Chapter 3. Product information and support

Information about InfoSphere MDM Server and support information can be

obtained through the following methods.

On the Web

Go to http://www-306.ibm.com/software/data/infosphere/mdm_server/.

This site contains the InfoSphere MDM Server library, news, and links to

web resources.

By Telephone

If you are in North America, call 1-800-IBM-SERV (1-800-426-7378).

If you are outside of North America, check the web page

http://www.ibm.com/planetwide/ for contact information for your area.



http://www-306.ibm.com/software/data/infosphere/mdm_server/

http://www.ibm.com/planetwide/

Notices

This information was developed for products and services offered in the Canada.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not give you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country/region or send inquiries, in

writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other

country/region where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS

FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or

implied warranties in certain transactions; therefore, this statement may not apply

to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

This document may provide links or references to non-IBM Web sites and

resources. IBM makes no representations, warranties, or other commitments

whatsoever about any non-IBM Web sites or third-party resources that may be

referenced, accessible from, or linked from this document. A link to a non-IBM

Web site does not mean that IBM endorses the content or use of such Web site or



its owner. In addition, IBM is not a party to or responsible for any transactions you

may enter into with third parties, even if you learn of such parties (or use a link to

such parties) from an IBM site. Accordingly, you acknowledge and agree that IBM

is not responsible for the availability of such external sites or resources, and is not

responsible or liable for any content, services, products, or other materials on or

available from those sites or resources. Any software provided by third parties is

subject to the terms and conditions of the license that accompanies that software.

IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information that has been exchanged, should contact:

IBM Canada Limited

Office of the Lab Director

8200 Warden Avenue

Markham, Ontario

L6G 1C7

CANADA

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement, or any equivalent agreement

between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may

vary significantly. Some measurements may have been made on development-level

systems, and there is no guarantee that these measurements will be the same on

generally available systems. Furthermore, some measurements may have been

estimated through extrapolation. Actual results may vary. Users of this document

should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements, or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of

performance, compatibility, or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the

suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or

withdrawal without notice, and represent goals and objectives only.

This information may contain examples of data and reports used in daily business

operations. To illustrate them as completely as possible, the examples include the

names of individuals, companies, brands, and products. All of these names are

fictitious, and any similarity to the names and addresses used by an actual

business enterprise is entirely coincidental.

COPYRIGHT LICENSE:



This information may contain sample application programs, in source language,

which illustrate programming techniques on various operating platforms. You may

copy, modify, and distribute these sample programs in any form without payment

to IBM for the purposes of developing, using, marketing, or distributing

application programs conforming to the application programming interface for the

operating platform for which the sample programs are written. These examples

have not been thoroughly tested under all conditions. IBM, therefore, cannot

guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work must

include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.

Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights

reserved.


Notices 319

Trademarks

Company, product, or service names identified in the documents of the text may

be trademarks or service marks of International Business Machines Corporation or

other companies. Information on the trademarks of IBM Corporation in the United

States, other countries, or both is located at http://www.ibm.com/legal/copytrade.shtml.

Windows is a trademark of Microsoft Corporation in the United States, other

countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

UNIX is a registered trademark of The Open Group in the United States and other

countries.

Other company, product, or service names may be trademarks or service marks of

others.



http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

��


Printed in USA

MDMDataDictionary

Documents

Transcript of MDMDataDictionary