MDMData Dictionary

IBM InfoSphere Master Data Management Server Version 8.5.
Licensed Materials Property of IBM
InfoSphere Master Data Management Server v8.5.0 Data Dictionary
IBM InfoSphere Master Data Management Server Version 8.5.0
InfoSphere Master Data Management Server v8.5.0 Data Dictionary
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 IBMs 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 . . . . . ADDACTIONTYPE Table . . . . . ADDRESS Table . . . . . . . . ADDRESSGROUP Table . . . . . AGREEMENTSPECVAL Table . . . ALERT Table . . . . . . . . . ANSWER Table . . . . . . . . ANSWERSET table . . . . . . . BANKACCOUNT Table . . . . . BILLINGSUMMARY Table . . . . CAMPAIGN Table . . . . . . . CAMPAIGNASSOCIAT Table . . . CATEGORY Table . . . . . . . CATEGORYNLS Table . . . . . . CATEQUIV Table . . . . . . . CATHIERARCHY Table . . . . . CATHIERARCHYNLS Table . . . . CATNODEREL Table . . . . . . CDACCETOCOMPTP Table . . . . CDACCOUNTREQUIREDTP Table . CDACCOUNTTP Table . . . . . CDACTIONADJREASTP Table . . . CDADDRUSAGETP Table . . . . CDADMINFLDNMTP Table . . . . CDADMINSYSTP Table . . . . . CDAGEVERDOCTP Table . . . . CDAGREEMENTSTTP Table . . . CDAGREEMENTTP Table . . . . CDALERTCAT Table . . . . . . CDALERTSEVTP Table . . . . . CDALERTTP Table . . . . . . . CDARRANGEMENTTP Table . . . CDAVAILABILITYTP Table . . . . CDBILLINGSTTP Table . . . . . CDBILLTP Table . . . . . . . . CDBUYSELLAGREETP Table . . . CDCAMPAIGNTP Table . . . . . CDCDCREJREASONTP Table . . . CDCDCSTTP Table . . . . . . . CDCHARGECARDTP Table . . . . CDCLAIMROLETP Table . . . . . CDCLAIMSTATUSTP Table . . . . CDCLAIMTP Table . . . . . . . CDCLIENTIMPTP Table . . . . . CDCLIENTPOTENTP Table . . . . CDCLIENTSTTP Table . . . . . . CDCOMPLCATTP Table . . . . . CDCOMPLDOCTP Table . . . . . CDCOMPLIANCETP Table . . . . CDCOMPLTARGETTP Table. . . . CDCONDITIONATTRIBUTETP Table. CDCONDITIONOWNERTP Table . .
Copyright IBM Corp. 1996, 2008
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35 36 37 40 41 42 43 45 46 47 50 51 52 53 54 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92
CDCONDITIONUSAGETP Table . CDCONTMETHCAT Table . . . CDCONTMETHTP Table . . . . CDCONTRACTRELSTTP Table . . CDCONTRACTRELTP Table . . . CDCONTRACTROLETP Table . . CDCONTRACTSTTP Table . . . CDCONTRCOMPTP Table . . . CDCOUNTRYTP Table . . . . CDCURRENCYTP Table . . . . CDDEMOGRAPHICSTP Table . . CDDOMAINTP Table . . . . CDDOMAINVALUETP Table . . CDENDREASONTP Table . . . CDENUMANSWERCATTP Table . CDENUMANSWERTP Table . . CDFREQMODETP Table . . . CDGENERATIONTP Table . . . CDGROUPINGCATTP Table . . CDGROUPINGTP Table . . . . CDHIERARCHYCATTP Table . . CDHIERARCHYTP Table . . . CDHIGHESTEDUTP Table . . . CDHOLDINGTP Table . . . . CDIDSTATUSTP Table . . . . CDIDTP Table . . . . . . . CDINACTREASONTP Table . . CDINCOMESRCTP Table . . . CDINDUSTRYTP Table . . . . CDINTERACTIONCAT Table . . CDINTERACTIONTP Table . . CDINTERACTPTTP Table . . . CDINTERACTRELTP Table . . . CDINTERACTRESPTP Table . . CDINTERACTSTTP Table . . . CDLANGTP Table . . . . . . CDLINKREASONTP Table . . . CDLOBRELTP Table . . . . . CDLOBTP Table . . . . . . CDMARITALSTTP Table . . . CDMATCHENGINETP Table . . CDMATCHRELEVTP Table . . . CDMETADATAINFOTP Table . . CDMETADATAPACKAGETP Table CDMETHODSTATUSTP Table . . CDMISCVALUEATTRTP Table . CDMISCVALUECAT Table . . . CDMISCVALUETP Table . . . CDNAMEUSAGETP Table . . . CDNODEDESIGTP Table . . . CDNODETP Table . . . . . . CDORGNAMETP Table . . . . CDORGTP Table . . . . . . CDPAYMENTMETHODTP Table . CDPPREFACTIONTP Table . . . CDPPREFCAT Table . . . . .
. 93 . 94 . 95 . 96 . 97 . 98 . 99 . . . . . . 100 . . . . . . 101 . . . . . . 102 . . . . . . 103 . . . . . . 104 . . . . . . 105 . . . . . . 106 . . . . . . 107 . . . . . . 107 . . . . . . 108 . . . . . . 109 . . . . . . 110 . . . . . . 111 . . . . . . 112 . . . . . . 113 . . . . . . 114 . . . . . . 115 . . . . . . 116 . . . . . . 117 . . . . . . 118 . . . . . . 119 . . . . . . 120 . . . . . . 121 . . . . . . 122 . . . . . . 123 . . . . . . 124 . . . . . . 125 . . . . . . 126 . . . . . . 127 . . . . . . 128 . . . . . . 129 . . . . . . 130 . . . . . . 131 . . . . . . 132 . . . . . . 133 . . . . . . 134 . . . . . . 134 . . . . . . 135 . . . . . . 136 . . . . . . 137 . . . . . . 138 . . . . . . 139 . . . . . . 140 . . . . . . 141 . . . . . . 142 . . . . . . 143 . . . . . . 144 . . . . . . 145 . . . . . . 146
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
iii
Licensed Materials Property of IBM CDPPREFREASONTP Table . . . . CDPPREFSEGTP Table . . . . . . CDPPREFTP Table. . . . . . . . CDPREFIXNAMETP Table . . . . . CDPRIMARYTARGETMARKETTP Table CDPRIORITYCATTP Table . . . . . CDPRIORITYTP Table . . . . . . CDPRODCONTRACTRELTP Table . . CDPRODRELATIONTP Table . . . . CDPRODRELTP Table . . . . . . CDPRODSTRUCTURETP Table . . . CDPRODTP Table . . . . . . . . CDPRODUCTIDENTIFIERTP Table . . CDPRODUCTSTATUSTP Table . . . CDPROVSTATETP Table . . . . . CDPURPOSETP Table . . . . . . CDQUESTIONCATTP Table . . . . CDQUESTIONNAIRETP Table . . . CDQUESTIONTP Table . . . . . . CDRELASSIGNTP Table . . . . . . CDRELTP Table . . . . . . . . CDREPOSITORYTP Table . . . . . CDRESIDENCETP Table . . . . . . CDROLECATTP Table . . . . . . CDROLETP Table . . . . . . . . CDRPTINGFREQTP Table . . . . . CDSERVICELEVELTP Table . . . . CDSHAREDISTTP Table . . . . . . CDSOURCEIDENTTP Table . . . . CDSPECCASCADETP Table . . . . CDSPECUSETP Table . . . . . . . CDSTATUSREASONTP Table . . . . CDSUSPECTREASONTP Table . . . CDSUSPECTSOURCETP Table . . . CDSUSPECTSTATUSTP Table . . . . CDSUSPECTTP Table. . . . . . . CDTAXPOSITIONTP Table . . . . . CDTERMINATIONREASONTP Table . CDUNDELREASONTP Table . . . . CDVALFREQTP Table . . . . . . CHARGECARD Table . . . . . . CLAIM Table . . . . . . . . . CLAIMCONTRACT Table . . . . . CLAIMROLE Table . . . . . . . COMPLDOCUMENT Table . . . . . COMPLENTITY Table . . . . . . COMPLENTITYDOC Table . . . . . COMPLENTITYTARGET Table . . . COMPLIANCEREQ Table . . . . . COMPLTARGET Table . . . . . . CONDITIONATTRIBUTE Table . . . CONTACT Table . . . . . . . . CONTACTCDC Table . . . . . . CONTACTDEMOGRAPHICS Table . . CONTACTMETHOD Table . . . . . CONTACTMETHODGROUP Table . . CONTACTREL Table . . . . . . . CONTEQUIV Table . . . . . . . CONTMACROROLE Table . . . . . CONTRACT Table . . . . . . . . CONTRACTCOMPONENT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 148 149 151 152 153 154 155 156 157 158 159 160 161 162 163 164 164 165 166 167 168 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 189 190 191 192 193 194 196 197 198 199 202 203 204 206 207 209 210 211 215 CONTRACTCOMPVAL Table . . . CONTRACTREL Table . . . . . CONTRACTROLE Table. . . . . CONTRACTROLEREL Table . . . CONTSUMMARY Table . . . . . DEFAULTSOURCEVAL Table . . . ENTITYCONDITIONREL Table . . ENTITYCONTENTREFERENCE Table ENTITYROLE Table . . . . . . ENTITYSPECUSE Table . . . . . ENUMANSWER Table . . . . . FINANCIALPRODUCT Table . . . GOODSPRODUCT Table . . . . GROUPING Table . . . . . . . GROUPINGASSOC Table . . . . HIERARCHY Table . . . . . . HIERARCHYNODE Table . . . . HIERARCHYREL Table . . . . . HIERARCHYULTPAR Table . . . HOLDING Table . . . . . . . IDENTIFIER Table . . . . . . . INACTIVATEDCONT Table . . . INACTIVECONTLINK Table . . . INCOMESOURCE Table . . . . . INSURANCEPRODUCT Table . . . INTERACTION Table . . . . . INTERACTIONREL Table . . . . LOBREL Table . . . . . . . . LOCATIONGROUP Table . . . . MACROROLEASSOC Table . . . MISCVALUE Table . . . . . . NATIVEKEY Table . . . . . . NLSENUMANSWER Table . . . . NLSQUESTION Table . . . . . NLSQUESTIONNAIRE Table . . . ORG Table . . . . . . . . . ORGNAME Table . . . . . . . PAYMENTSOURCE Table . . . . PAYROLLDEDUCTION Table . . . PERSON Table . . . . . . . . PERSONNAME Table . . . . . PERSONSEARCH Table . . . . . PHONENUMBER Table . . . . . PPREFACTIONOPT Table . . . . PPREFDEF Table . . . . . . . PPREFDEFREL Table . . . . . . PPREFENTITY Table . . . . . . PPREFINSTANCE Table . . . . . PRIVPREF Table . . . . . . . PRODTPREL Table . . . . . . PRODUCT Table . . . . . . . PRODUCTCATEGORYASSOC Table . PRODUCTCONTRACTREL Table . PRODUCTEQUIV Table . . . . . PRODUCTIDENTIFIER Table . . . PRODUCTNLS Table . . . . . . PRODUCTREL Table . . . . . . PRODUCTTYPE Table . . . . . PRODUCTTYPENLS Table . . . . PRODUCTVAL Table . . . . . . PRODUCTVALNLS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 219 220 222 223 226 228 229 230 231 232 233 234 235 236 237 238 239 240 241 243 245 246 247 248 249 251 252 253 255 256 260 261 262 263 265 266 267 268 269 271 273 275 276 277 278 279 280 281 282 284 285 286 287 288 289 290 291 292 293 294
iv
InfoSphere MDM Server v8.5.0: Data Dictionary
Licensed Materials Property of IBM PROPERTY Table . . . . . . . QUESTION Table . . . . . . . QUESTIONNAIRE Table . . . . ROLEIDENTIFIER Table . . . . . ROLELOCATION Table . . . . . ROLELOCPURPOSE Table . . . . ROLESITUATION Table . . . . . SEARCHXCLRULE Table . . . . SERVICEPRODUCT Table . . . . SPEC Table . . . . . . . . . SPECFMT Table . . . . . . . SPECFORMATTRANSLATION Table SUSPECT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 296 297 298 300 301 302 303 303 304 305 306 307 SUSPECTAUGMENT . . . . TERMCONDITION Table . . TERMCONDITIONNLS Table . VEHICLE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 310 311 312
Chapter 3. Product information and support . . . . . . . . . . . . . . 315 Notices . . . . . . . . . . . . . . 317 Trademarks . . . . . . . . . . . . 321
Contents
vi
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 systems 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.
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 v v v Marketing Initiative Info Change Regular Mailing 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.
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.
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 systems 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 partys 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 Drivers 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 PARTYs investment experience and financial standing used in determining a PARTYs 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 statuss 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).
10
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 Partys 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.
11
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, drivers 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 partys macro role and its child data. For instance, as Prospect (macro role) the system may capture that partys email address (associated party child data): jsmith@example.com. 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 persons payroll deduction payment source information used to pay one or more contracts or accounts. PERSON A subtype of PARTY and represents a human being.
12
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 partys 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.
13
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 products 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.
14
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 products association to some other entity such as the products type. The values based on spec formats associated to the products 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.
15
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 partys 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.
16
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 systems 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.
17
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
18
Chapter 2. Tables
This section contains details about the InfoSphere MDM Server database tables.
Table name ACCESSDATEVAL Comment ACCESSDATEVALUE captures the last used date and last verified date around various entities and attributes. ADDACTIONTYPE identifies the action taken as a result of suspect identification. 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. Contains spec values that are related to business agreements. An example of a business agreement can be represented by the contract business object. 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 identifies an answer belongs to a specific answer set. ANSWERSET is comprised of a series of answers. BANK ACCOUNT RECORD is the bank account information used to pay one or more contracts or accounts. Represents a summary bill for a contract or a contract component. This table capture the detail of a campaign for customer solicitation. This include the priority order for customer presentation. Store the association between a campaign and any associated entities, such as parties. This table holds common platform attributes for categories. A category may participate in one hierarchy at a time. This table holds the language sensitive fields for CATEGORY table. This table holds information about a category equivalency. This table holds information about a category hierarchy.
ADDACTIONTYPE ADDRESS
AGREEMENTSPECVAL
ALERT
ANSWER ANSWERSET BANKACCOUNT
BILLINGSUMMARY CAMPAIGN
CAMPAIGNASSOCIAT CATEGORY
CATEGORYNLS CATEQUIV CATHIERARCHY
19
Licensed Materials Property of IBM Table name CATHIERARCHYNLS CATNODEREL CDACCETOCOMPTP Comment This table holds the language sensitive fields for CATHIERARCHY table. This table holds the definition of relationships between category nodes in a category hierarchy. 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). Captures information regarding the account requirement for a given product. ACCOUNT TYPE LOOKUP contains values of the Account Type Code and its descriptions. Some examples are Savings, and Checking. Action Type Adjusted Reason Type identifies the reason that the action taken as a result of suspect identification was adjusted. 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. 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. The code table that stores the valid status for an agreement. For example: Draft, Normal, Suspended. The code table that stores the type of the agreement, such as ValuePackage. 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.
CDACCOUNTREQUIREDTP CDACCOUNTTP
CDACTIONADJREASTP
CDADDRUSAGETP
CDADMINFLDNMTP
CDADMINSYSTP
CDAGEVERDOCTP
CDAGREEMENTSTTP CDAGREEMENTTP CDALERTCAT
20
Licensed Materials Property of IBM Table name CDALERTTP Comment ALERT TYPE LOOKUP is a list of lower level of alerts. For example: divorce preceding pending or officer of the company. 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. Captures information regarding how widely available the product is to its target market. 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 BILL TYPE LOOKUP contains the values for the bill type code and its descriptions. BUY SELL AGREEMENT TYPE LOOKUP contains the values for the buy sell agreement type code and its descriptions. Identifies the type of campaign. 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. CRITICAL DATA CHANGE STATUS LOOKUP hold the status type of the critical data change request. CHARGE CARD TYPE LOOKUP contains values of the Charge Card Type Code and its descriptions. Some examples are Visa, MasterCard, and American Express. PRODUCT TYPE LOOKUP contains the values for the Product Type Code and its descriptions. PRODUCT TYPE LOOKUP contains the values for the Product Type Code and its descriptions. PRODUCT TYPE LOOKUP contains the values for the Product Type Code and its descriptions. 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 POTENTIAL TYPE LOOKUP represents the Party Potential Type Code and its descriptions. PARTY STATUS TYPE LOOKUP represents the values of Party Status Type Code and its description. CDCOMPLCAT is the table holds information about compliance category. CDCOMPLDOCTP is the table that holds information about compliance document type.
Chapter 2. Tables
CDARRANGEMENTTP
CDAVAILABILITYTP CDBILLINGSTTP
CDBILLTP CDBUYSELLAGREETP
CDCAMPAIGNTP CDCDCREJREASONTP
CDCDCSTTP CDCHARGECARDTP
CDCLAIMROLETP CDCLAIMSTATUSTP CDCLAIMTP CDCLIENTIMPTP
CDCLIENTPOTENTP CDCLIENTSTTP CDCOMPLCATTP CDCOMPLDOCTP
21
Licensed Materials Property of IBM Table name CDCOMPLIANCETP CDCOMPLTARGETTP CDCONDITIONATTRIBUTETP Comment CDCOMPLIANCETP is the table that holds information about compliance type. CDCOMPLTARGETTP is the table that holds information about compliance target 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. Terms and Conditions is a common component, used by Product and Account domains. This table categorizes the owner type. For example: PRODUCT or CONTRACT. The CDCONDITIONUSAGETP table serves as a means to group condition types. For example: ValuePackage Integrity, Rate Fee. 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. 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. 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. 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. 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. COUNTRY TYPE LOOKUP contains the values of the Contract Type Code and its descriptions. For example: USA, Canada, England.
CDCONDITIONOWNERTP
CDCONDITIONUSAGETP
CDCONTMETHCAT
CDCONTMETHTP
CDCONTRACTRELSTTP
CDCONTRACTRELTP
CDCONTRACTROLETP
CDCONTRCOMPTP
CDCOUNTRYTP
22
Licensed Materials Property of IBM Table name CDCURRENCYTP Comment CURRENCY TYPE LOOKUP contains the values for the current type code and its descriptions. For example: Euro, US Dollar, Japanese Yen, British Pound. The code table CDDEMOGRAPHICSTP defines the demographics types. 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. 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. 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. Enum answer category type identifies an enumerated answer type belongs to a specific category. 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. 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. GROUPING CATEGORY TYPE LOOKUP contains the values for the Grouping Category Type Code and its descriptions. Identify all Group Types, such as Household, Over 40, Platinum. HIERARCHY CATEGORY TYPE LOOKUP contains the values for the hierarchy category Type Code and its descriptions. HIERARCHY TYPE LOOKUP contains the values for the hierarchy Type Code and its descriptions. HIGHEST EDUCATION TYPE LOOKUP contains the values for the Highest Education Type Code and its descriptions. HOLDING TYPE LOOKUP contains the values for the Holding Type Code and its descriptions. Some examples are Vehicle and Property
CDDEMOGRAPHICSTP CDDOMAINTP
CDDOMAINVALUETP
CDENDREASONTP
CDENUMANSWERCATTP
CDENUMANSWERTP CDFREQMODETP
CDGENERATIONTP
CDGROUPINGCATTP
CDGROUPINGTP CDHIERARCHYCATTP
CDHIERARCHYTP CDHIGHESTEDUTP
CDHOLDINGTP
Chapter 2. Tables
23
Licensed Materials Property of IBM Table name CDIDSTATUSTP Comment 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 Drivers 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. INCOME SOURCE TYPE LOOKUP contains information on the valid values for the Income Source Type Code such as annual salary and net worth. INDUSTRY TYPE LOOKUP contains the values for the industry type code and its descriptions. For example: farming, industrial, insurance. 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. 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. 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. 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. Identify the types of responses an interaction may have. INTERACTION STATUS TYPE LOOKUP is the list of types of statuss that is associated with an INTERACTION. Some examples are Returned, Success, or Call not answered.
CDINCOMESRCTP
CDINDUSTRYTP
CDINTERACTIONCAT
CDINTERACTIONTP
CDINTERACTPTTP
CDINTERACTRELTP
CDINTERACTRESPTP CDINTERACTSTTP
24
Licensed Materials Property of IBM Table name CDLANGTP Comment LANGUAGE TYPE LOOKUP contains the values for the Language Type Code and its descriptions. Some examples of values are English, French, or Spanish. LINK REASON TYPE LOOKUP identifies the reason why two parties are linked together. For example: Collapsed or Split. Defines various LOB relationship types, such as owner. Contains the values and descriptions of all the line of businesses setup in the system. MARITAL STATUS TYPE LOOKUP contains the values for the Marital Status Type Code and its descriptions. For example: married, separated, widowed. MATCH ENGINE TYPE LOOKUP hold the type information and description of Matching Engine use for matching parties. 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. Stores the information that can be used to identify the metadata, such as Task Definition and Spec. 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. 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. This code identifies the miscellaneous value attribute types that are captured. CATEGORY TYPE LOOKUP is the high level categorization of types for Miscellaneous Values. Some examples are Demographic Category, Risk Category, and Standard Industry Codes. 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. 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. HIERARCHY CATEGORY TYPE LOOKUP contains the values for the hierarchy category Type Code and its descriptions. Captures meta-data regarding how the subtype is represented within the product type hierarchy.
Chapter 2. Tables
CDLINKREASONTP
CDLOBRELTP CDLOBTP CDMARITALSTTP
CDMATCHENGINETP
CDMATCHRELEVTP
CDMETADATAINFOTP CDMETADATAPACKAGETP
CDMETHODSTATUSTP
CDMISCVALUEATTRTP CDMISCVALUECAT
CDMISCVALUETP
CDNAMEUSAGETP
CDNODEDESIGTP
CDNODETP
25
Licensed Materials Property of IBM Table name CDORGNAMETP Comment 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. ORGANIZATION TYPE LOOKUP contains information on the valid values for the Organization Type Code, such as charity, trust, estate, or corporation. Payment method type lookup is a code table, which contains various payment method type values and their descriptions. 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. Allow Privacy Preference Type to be categorized. Identifier the reason for a privacy element. Store the segment that preference record should falls into based on regulation. Identifier the type of Privacy or Preference information. For example: Pander Flag 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. Captures information regarding the primary market this product targets. 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. PRIORITY TYPE LOOKUP contains the various priorities for campaigns, and includes values such as high, medium, low. The code table that holds the type of a product-contract relationship (such as Party Selection) Captures information regarding the type of relationship held between two products. identifier all the relationship types that can exist between products Captures information regarding how the product is structured. PRODUCT TYPE LOOKUP contains the values for the Product Type Code and its descriptions. Captures information regarding the product identifier Captures information regarding the lifecycle status of the product.
CDORGTP
CDPAYMENTMETHODTP
CDPPREFACTIONTP
CDPPREFCAT CDPPREFREASONTP CDPPREFSEGTP CDPPREFTP CDPREFIXNAMETP
CDPRIMARYTARGETMARKETTP CDPRIORITYCATTP
CDPRIORITYTP
CDPRODCONTRACTRELTP
CDPRODRELATIONTP CDPRODRELTP CDPRODSTRUCTURETP CDPRODTP CDPRODUCTIDENTIFIERTP CDPRODUCTSTATUSTP
26
Licensed Materials Property of IBM Table name CDPROVSTATETP Comment 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. 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. Question category type identifies a question type belongs to a specific category. Questionnaire type identifies a type of questionnaire. Question type identifies a type of question. 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. 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). 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, and building. These values are displayed in the user interface as a drop down box. CATEGORY TYPE LOOKUP is the high level categorization of types for Miscellaneous Values. Some examples are Demographic Category, Risk Category, and Standard Industry Codes. 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. REPORTING FREQUENCY TYPE LOOKUP represents the Reporting Frequency Type Code and its descriptions. 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. 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.
Chapter 2. Tables
CDPURPOSETP
CDQUESTIONCATTP CDQUESTIONNAIRETP CDQUESTIONTP CDRELASSIGNTP
CDRELTP
CDREPOSITORYTP CDRESIDENCETP
CDROLECATTP
CDROLETP
CDRPTINGFREQTP
CDSERVICELEVELTP
CDSHAREDISTTP
27
Licensed Materials Property of IBM Table name CDSOURCEIDENTTP CDSPECCASCADETP CDSPECUSETP CDSTATUSREASONTP CDSUSPECTREASONTP Comment These type codes describe what Source Identifer Values represent in the Default Source Value Table. Captures information regarding the type of cascade action the spec will have in a hierarchy. Captures information regarding the usage types the spec will be used for. Captures information regarding the reason the product is in its current state. 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. SUSPECT SOURCE TYPE indicates how a potential suspect duplicate was identified. Examples include system marked and user marked. 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. 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. Captures information regarding the relative tax position offered by a product. The code table that stores the termination reasons for an agreement, such as Agreement Terms & Conditions violation In 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 and wrong zip codes. CDVALFREQTP is the table that holds information about compliance validation frequency. CHARGE CARD RECORD is the charge card information used to pay for one or more CONTRACTs or accounts. Record claim information for a coverage that may be insured in a contract. For example: Auto Claim, break-in. Record a claim against a contract. For example: Automobile, Homeowners and Whole Life insurance policies. Records to identify the role party plays on a claim record. For example: Party 1 reported the broken windshield, Party 2 at fault. COMPLDOCUMENT: Compliance Document is the table that holds information about candidating documents to validate the target.
CDSUSPECTSOURCETP
CDSUSPECTSTATUSTP
CDSUSPECTTP
CDTAXPOSITIONTP CDTERMINATIONREASONTP
CDUNDELREASONTP
CDVALFREQTP CHARGECARD
CLAIM
CLAIMCONTRACT
CLAIMROLE
COMPLDOCUMENT
28
Licensed Materials Property of IBM Table name COMPLENTITY COMPLENTITYDOC Comment is the table that holds information about which entity meets the compliance requirement. COMPLENTITYDOC is the table that holds information about which document instances are used to validate the target instance. COMPLENTITYTARGET is the table that holds information about target instance. COMPLIANCEREQ is the table that holds information about compliance requirement. COMPLTARGET: Compliance Target is the table that holds information about the target need to be validated. 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. 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 hold the information of critical data change on contact. The table CONTACTDEMOGRAPHICS stores various party demographic data for a party. 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 GROUP is a subtype of LOCATION GROUP and links parties to addresses and contains rules specific to using an address when contacting a party. 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. 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.
COMPLENTITYTARGET COMPLIANCEREQ COMPLTARGET
CONDITIONATTRIBUTE
CONTACT
CONTACTCDC CONTACTDEMOGRAPHICS CONTACTMETHOD
CONTACTMETHODGROUP
CONTACTREL
CONTMACROROLE
Chapter 2. Tables
29
Licensed Materials Property of IBM Table name CONTRACT Comment 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. 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. 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. CONTRACT RELATIONSHIP represents the relationship that an agreement can have with another agreement. PARTY CONTRACT ROLE is an association that links parties to the various roles they may have on a contract. 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 contains a summary view of a contact record; specifically, it contains indicators that track what information is stored about a particular party. 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 This table stores the association between the TermCondition and the entity represented by the column ENTITY_NAME (PRODUCT / CONTRACT) This table stores the content references of the content assets stored in external CMS. 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). This table defines the way a spec will be used to define an entity such as a product. Enum answer identifies a possible answer of a question. Enumanswer contains language independent fields of the enumerated answer.
CONTRACTCOMPONENT
CONTRACTCOMPVAL
CONTRACTREL
CONTRACTROLE
CONTRACTROLEREL
CONTSUMMARY
DEFAULTSOURCEVAL
ENTITYCONDITIONREL
ENTITYCONTENTREFERENCE ENTITYROLE
ENTITYSPECUSE ENUMANSWER
30
Licensed Materials Property of IBM Table name FINANCIALPRODUCT GOODSPRODUCT GROUPING Comment Financial (such as banking) products that are a hardened subtype of product. Goods (physical) products that are a hardened subtype of product. 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. Identify the Parties that belongs to a Party Group. Identifies the entities, such as Party, which are placed in a group It represents a hierarchy in the system. HIERARCHY NODE represents a node in a hierarchy. HIERARCHY RELATIONSHIP contains two hierarchy nodes to represent their direct parent-child relationship. Identifies a node as the ultimate parent in a hierarchy. PARTY HOLDING records a partys personal holdings. For example: A list of assets and liabilities such as Vehicles, Dwellings and Mortgage. PARTY IDENTIFIER in an additional way of distinguishing a party that is natural to them. For example, social security number, drivers license number, passport number, for example. 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. 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 INCOME SOURCE, provided and attested to by the party, provides the details of the PARTYs investment experience and financial standing used in determining a PARTYs suitability in purchasing a new investment. Insurance (related to the insurance vertical) products that are a hardened subtype of product. 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.
GROUPINGASSOC
HIERARCHY HIERARCHYNODE HIERARCHYREL
HIERARCHYULTPAR HOLDING
IDENTIFIER
INACTIVATEDCONT
INACTIVECONTLINK
INCOMESOURCE
INSURANCEPRODUCT INTERACTION
Chapter 2. Tables
31
Licensed Materials Property of IBM Table name INTERACTIONREL Comment INTERACTION RELATIONSHIP shows the relationships between different interactions. An initial interaction can generated a series of interactions with a customer. 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. LOCATION GROUP links locations, such as addresses and telephone numbers, to parties and contains rules for use. Represents an association between a partys macro role and its child data. For instance, as Prospect (macro role) the system may capture that partys email address (associated party child data) of jsmith@somedomain.com. 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. CONTRACT NATIVE KEY provides the link of the InfoSphere MDM Server Contract ID to the administrative systems or back office systems native key for a given contract. NLSEnumanswer contains language dependent fields of the enumerated answer. NLSQuestion contains language dependent fields of a question. NLSQuestionnaire contains the language dependent fields of Questionnaire. 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. ORGANIZATION NAME contains the different names that may be used by an organization. An abstract supertype for various payment source types in the system such as bank account, charge card or payroll deduction. Represents a persons payroll deduction payment source. PERSON is 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/non-standardized versions of the PERSON NAME table to facilitate searching. This table holds information of parts phone number.
LOBREL
LOCATIONGROUP
MACROROLEASSOC
MISCVALUE
NATIVEKEY
NLSENUMANSWER NLSQUESTION NLSQUESTIONNAIRE ORG
ORGNAME PAYMENTSOURCE
PAYROLLDEDUCTION PERSON PERSONNAME PERSONSEARCH
PHONENUMBER
32
Licensed Materials Property of IBM Table name PPREFACTIONOPT PPREFDEF Comment Stores the action types that are possible options for each Privacy/Preference Type This table allow us to capture the default Privacy information as well as default preferences setting (Y or N). Defines the parent child relationship between two Default Privacy Preference records This table enables you to capture Privacy information as well as preferences for a Party (Y or N). Identifies the entity instances that are associated with the Privacy Preference record Store all Privacy and Preference records This table store the relationship type between two product records. These relationships may be used in combinations to provide a hierarchy of products Instances of products that are of interest to the business. A products association to a category. The table that holds the relationship between a product and a contract. How a product is identified in a different system. A client-defined identifier for the product such as a part number or product code. 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 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. A type of product that (unless is the root product type) is a subtype of another product type. PRODUCTTYPENLS table is the localization table for the table ProductType. ProductTypeNLS entity could represent the localization data of fields those needs to be localized. A set of values based on a spec format. The values decorate the product based on the products association to some other entity such as the products type. The values based on spec formats associated to the products type are maintained in this table. 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.
PPREFDEFREL PPREFENTITY
PPREFINSTANCE PRIVPREF PRODTPREL
PRODUCT PRODUCTCATEGORYASSOC PRODUCTCONTRACTREL PRODUCTEQUIV PRODUCTIDENTIFIER PRODUCTNLS
PRODUCTREL
PRODUCTTYPE PRODUCTTYPENLS
PRODUCTVAL
PRODUCTVALNLS
Chapter 2. Tables
33
Licensed Materials Property of IBM Table name PROPERTY Comment PROPERTY contains all HOLDING records that are locations. For example: Cottage, Private Residence, Secondary Residence, Condominium. QUESTION contains language independent fields of a question. 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 provides an identifier to a partys specific role on a contract. PARTYLOCATION is an association between a Partys roles on a contract to a particular location group. 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 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. This table provides the initial search exclusion criteria (last name only, last & given name one only, or last name & city only) for search transaction. Service (non-physical) products that are a hardened subtype of product. This table holds information about specs available in the system. This table holds all the various formats (or versions) for the systems specs. This table holds locale specific translations for the attribute names of specs SUSPECT table contains all suspects (possible duplicates) a particular party has within the InfoSphere MDM Server database. Contains the augmented suspect processing results performed by the additional match engines TERMCONDITION table represents a logical condition, containing conditions for entities such as Product and Agreement. TermCondition can be static or executable. 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 contains all HOLDING records that are vehicles. For example: Mazda M3, Subaru Outback, or Honda Civic.
QUESTION QUESTIONNAIRE
ROLEIDENTIFIER ROLELOCATION
ROLELOCPURPOSE
ROLESITUATION
SEARCHEXCLRULE
SERVICEPRODUCT SPEC SPECFMT SPECFORMATTRANSLATION SUSPECT
SUSPECTAUGMENT TERMCONDITION
TERMCONDITIONNLS
VEHICLE
34
ACCESSDATEVAL Table
Column Name acc_date_val_id Comment A unique, system generated key that identifies a default object row in the IBM InfoSphere Master Data Management Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
instance_pk
The actual primary key BIGINT of the row in the logical entity. The name of the business entity. The actual name of the column where the default occurred. A description of the record. VARCHAR(20) VARCHAR(20)
NOT NULL
No
entity_name col_name
NOT NULL NULL
No No
description last_update_dt
VARCHAR(1000)
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated, or deleted the data row. The date that this data was last used. There is no business logic associated with this field. BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
last_used_dt
TIMESTAMP
NULL
No
Chapter 2. Tables
35
Licensed Materials Property of IBM Column Name last_verified_dt Comment The date that this data was last verified. There is no business logic associated with this field. Datatype TIMESTAMP Null Option NULL Is PK No
ADDACTIONTYPE Table
Column Name add_action_id Comment A unique, system generated key that identifies an add action row in the IBM InfoSphere Master Data Management Server system. Identifies the Party (CONTACT) match relevancies - scores and descriptions. Datatype BIGINT Null Option NOT NULL Is PK Yes
match_relev_tp_cd
BIGINT
NOT NULL
No
susp_reason_tp_cd
Describes the critical BIGINT 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). Identifies the BIGINT classification of the organization. For example: trust, company, charity, estate, and others. Indicates the type of party - person or organization. Identifies the action taken as a result of suspect identification. CHAR(1)
NOT NULL
No
org_tp_cd
NULL
No
person_org_code
NOT NULL
No
add_action_code
CHAR(2)
NOT NULL
No
last_update_dt
When a record is added TIMESTAMP 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.
NOT NULL
No
36
Licensed Materials Property of IBM Column Name last_update_user Comment Datatype Null Option NULL Is PK No
The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_tx_id
NULL
No
suspect_tp_cd
Suspect Type code BIGINT captures various suspect types. One record exists for each unique add_action_code in the addactiontype table.
NULL
No
ADDRESS Table
Column Name address_id Comment A unique, system generated key that identifies an address in the InfoSphere MDM Server system. Identifies a country. Datatype BIGINT Null Option NOT NULL Is PK Yes
country_tp_cd residence_tp_cd
BIGINT
NULL NULL
No No
A type of residence for a BIGINT given address. Some examples include Home, Apartment and Suite. 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. The first line of an address. The phonetic representation of the first line of an address. Not currently used. The second line of an address. BIGINT
prov_state_tp_cd
NULL
No
addr_line_one p_addr_line_one
VARCHAR(100) CHAR(8)
NOT NULL NULL
No No
addr_line_two
VARCHAR(100)
NULL
No
Chapter 2. Tables
37
Licensed Materials Property of IBM Column Name p_addr_line_two Comment The phonetic representation of the second line of an address. Not currently used. The third line of an address. The phonetic representation of the third line of an address. Not currently used. The city of an address. Postal Code (Zip Code) is used by the postal system to uniquely identify an address location. Indicates whether this address be standardized. Indicates whether the address standardization process should be overridden. The apartment, suite, or unit number of the address. Datatype CHAR(8) Null Option NULL Is PK No
addr_line_three p_addr_line_three
VARCHAR(100) CHAR(8)
NULL NULL
No No
city_name postal_code
VARCHAR(50) VARCHAR(20)
NOT NULL NULL
No No
addr_standard_ind
CHAR(1)
NULL
No
override_ind
CHAR(1)
NULL
No
residence_num
VARCHAR(10)
NULL
No
county_code
A three-digit postal code CHAR(3) used to identify the county of the post office. 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
latitude_degrees
NULL
No
longitude_degrees
Longitude of Measure in VARCHAR(10) Degrees identifies an angular distance east or west. Longitude Degrees is useful for Mapping Software (for example, to identify the nearest doctors office). The phonetic key for City. VARCHAR(20)
NULL
No
p_city
NULL
No
38
Licensed Materials Property of IBM Column Name last_update_dt Comment Datatype Null Option NOT NULL Is PK No
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. 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 BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
postal_barcode
VARCHAR(30)
NULL
No
building_name street_number
The name of the building. The street number of the building. For example: 55 in the address 55 Main Road East. The name of the street. For example: Main in the address 55 Main Road East. The type of street. For example: Road in the address 55 Main Road East.
NULL NULL
No No
street_name
VARCHAR(64)
NULL
No
street_suffix
VARCHAR(64)
NULL
No
Chapter 2. Tables
39
Licensed Materials Property of IBM Column Name pre_directional post_directional Comment Datatype Null Option NULL NULL Is PK No No
A directional element of VARCHAR(16) the address. A directional element of VARCHAR(16) the address. For example: East in the address 55 Main Road East. Box designator. Box identifier. Station information. Station identifier. VARCHAR(16) VARCHAR(16) VARCHAR(16) VARCHAR(16)
box_designator box_id stn_info stn_id region del_designator del_id del_info
NULL NULL NULL NULL NULL NULL NULL NULL
No No No No No No No No
Further qualification of VARCHAR(32) area, in addition to City. Delivery designator. Delivery identifier. Additional delivery information. VARCHAR(16) VARCHAR(16) VARCHAR(50)
ADDRESSGROUP Table
Column Name location_group_id Comment A unique, system generated key that identifies a location group row in the IBM InfoSphere Master Data Management Server system. A unique, system generated key that identifies an address in the IBM InfoSphere Master Data Management Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
address_id
BIGINT
NOT NULL
No
care_of_desc
In Care of Description is VARCHAR(50) placed above the recipient line. It contains information such as a specific person or department to provide additional information, facilitating delivery. Address Usage Type Code identifies the usage of an address provided by a party. Examples include residence address, business address, and others. BIGINT
NULL
No
addr_usage_tp_cd
NOT NULL
No
40
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
AGREEMENTSPECVAL Table
Column Name agreement_spec_val_id Comment A system generated key that uniquely identifies a set of contract related spec values. The spec that describes the definition of the spec values. The format (or version) of the spec these spec values validate to. The type of entity with which the spec values are associated. The types of entities are expected to be contract related. The primary key of the related entity. The spec values as defined by the associated spec format. The date the spec values become effective. Datatype BIGINT Null Option NOT NULL Is PK Yes
spec_id
BIGINT
NOT NULL
No
spec_fmt_id
BIGINT
NOT NULL
No
entity_name
VARCHAR(250)
NOT NULL
No
instance_pk value_xml
BIGINT XML
NOT NULL NOT NULL
No No
start_dt
TIMESTAMP
NOT NULL
No
Chapter 2. Tables
41
Licensed Materials Property of IBM Column Name end_dt last_update_dt Comment Datatype Null Option NULL NOT NULL Is PK No No
The date the spec values are TIMESTAMP no longer effective. When a record is added or TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated BIGINT key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
last_update_user
NULL
No
last_update_tx_id
NULL
No
ALERT Table
Column Name alert_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies an alert row in the IBM InfoSphere Master Data Management Server system. The name of the business entity that has the alert or restriction. VARCHAR(20)
entity_name
NOT NULL
No
instance_PK
The actual primary key BIGINT of the row in the logical entity that has the alert. The ID of user who removed the alert. The ID of user who created the alert. VARCHAR(20) VARCHAR(20)
NOT NULL
No
removed_by_user created_by_user alert_tp_cd
NULL NULL NOT NULL
No No No
Uniquely identifies the BIGINT type of alert placed on the party. Examples of alert types are court order pending, divorce pending, officer of the company, and others.
42
Licensed Materials Property of IBM Column Name alert_sev_tp_cd Comment An identifier that uniquely separates one type of alert severity from another. Examples include red, yellow and green. The date that this row of data became valid. The date that this row of data became invalid. Datatype BIGINT Null Option NULL Is PK No
start_dt end_dt description
TIMESTAMP TIMESTAMP
NOT NULL NULL NULL
No No No
Provides extra VARCHAR(1000) 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. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
ANSWER Table
Name answer_id Datatype BIGINT Null Option NOT NULL Comment The primary key of the answer record. Is PK Yes
Chapter 2. Tables
43
Licensed Materials Property of IBM Name answer_set_id Datatype BIGINT Null Option NOT NULL Comment The answer set id that this answer belongs to. The question id that this answer relative to. Answer index. Enum answer id that this answer referred. Answer text. Specifies the date when this record recorded. Is PK No
question_id
BIGINT
NOT NULL
No
answer_index enum_ans_id answer recorded_dt
SMALLINT BIGINT VARCHAR(120) TIMESTAMP
NULL NULL NULL NOT NULL
No No No No
last_update_dt
TIMESTAMP
NOT NULL
Last Update Date is No 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 hasnt 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. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/ROV is turned on. Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
44
ANSWERSET table
Name answer_set_id quesnr_id Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Comment Is PK The primary key of Yes the answer set record. The questionnaire that this answerset relative to. Language type code. The party id identifies the party who recorded this answerset . No
lang_tp_cd answer_party
BIGINT VARCHAR(255)
NOT NULL NULL
No No
entity_name
VARCHAR(20)
NULL
Entity Name is the No name of the physical business entity which this answer regarding to. Entity Instance No Primary Key is the actual primary key of the row in the logical entity which this answer regarding to. Specifies the date when this record in takes effect. Specifies the date when this record becomes inactive. No
instance_pk
BIGINT
NULL
start_dt
TIMESTAMP
NOT NULL
end_dt
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
Last Update Date is No 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 hasnt 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.
Chapter 2. Tables
45
Licensed Materials Property of IBM Name last_update_user Datatype VARCHAR(20) Null Option NULL Comment Is PK
Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/ROV is turned on. Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
last_update_tx_id
BIGINT
NULL
BANKACCOUNT Table
Column Name payment_source_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a payment source in the InfoSphere MDM Server system. The type of bank BIGINT account provided by the party. Some examples are checking, savings, etc. The alphanumeric VARCHAR(30) identifier assigned to the bank account that uniquely identifies it for that given institution. The date on which the bank account was actually opened, or recorded as opened. The date on which the bank account was actually closed, or recorded as closed. The local office, or branch, identifier used by the bank to identify that location of the account. A unique identifier for the bank, assigned outside of InfoSphere MDM Server TIMESTAMP
acct_tp_cd
NOT NULL
No
acct_num
NOT NULL
No
recorded_open_dt
NULL
No
recorded_closed_dt
TIMESTAMP
NULL
No
branch_num
VARCHAR(10)
NOT NULL
No
bank_num
VARCHAR(10)
NOT NULL
No
46
Licensed Materials Property of IBM Column Name depositor_name Comment The Partys name as printed on a check (the account registration name). When a record is added or updated, this field is updated with the date and time. On subsequent updates, 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. Datatype VARCHAR(255) Null Option NULL Is PK No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
BILLINGSUMMARY Table
Column Name billing_summary_id Comment A unique ID generated by the system to identify a billing summary in InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
billing_st_tp_cd
A unique type code BIGINT which uniquely defines a billing status value. Some examples are closed, paid, and others. A type code which BIGINT 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.
NOT NULL
No
pymt_mthd_tp_cd
NULL
No
Chapter 2. Tables
47
Licensed Materials Property of IBM Column Name last_py_md_tp_cd Comment Datatype Null Option NULL Is PK No
A type code which BIGINT uniquely identifies a payment method value in the system. This represents the last payment method type. Some examples are bank account, charge card, cash, and others. The date from which this billing summary is effective. The due date for this billing summary. The total outstanding balance. The minimum payment required for this billing summary. The maximum payment allowed for this billing summary. The date up to which the account or contract has been paid. Links this billing summary to an invoice; external to InfoSphere MDM Server system. The start date of the billing period of this billing summary. The end date of the billing period of this billing summary. An account ID is a free form specific means by which the account can be distinguished from all other accounts. TIMESTAMP
effective_date
NULL
No
due_date account_balance min_payment
TIMESTAMP DECIMAL(17,3) DECIMAL(17,3)
NULL NOT NULL NULL
No No No
max_payment
DECIMAL(17,3)
NULL
No
paid_to_date
TIMESTAMP
NULL
No
invoice_id
VARCHAR(50)
NULL
No
bill_from_date
TIMESTAMP
NULL
No
bill_to_date
TIMESTAMP
NULL
No
account_id
VARCHAR(50)
NULL
No
payment_source_id
A unique, system BIGINT generated key that identifies a payment source in the InfoSphere MDM Server system. The date on which payment will be withdrawn from a payment source for this billing summary. The amount paid or withdrawn against the last billing summary. TIMESTAMP
NULL
No
withdrawal_date
NULL
No
last_payment_amt
DECIMAL(17,3)
NULL
No
48
Licensed Materials Property of IBM Column Name last_payment_dt payments_remaining last_update_dt Comment Datatype Null Option NULL NULL NOT NULL Is PK No No No
The date when payment TIMESTAMP was last received. The number of payments remaining. INTEGER
last_update_user
NULL
No
last_update_tx_id
NULL
No
freq_mode_tp_cd
The frequency of the BIGINT payments made on the contract. Some examples are monthly, annual, and others. A unique, system generated key that identifies a contract in the InfoSphere MDM Server system. BIGINT
NULL
No
contract_id
NULL
No
contr_component_id
A unique, system BIGINT generated key that identifies a contract component in the InfoSphere MDM Server system. The currency type for the account balance. The currency type for the minimum payment. The currency type for the maximum payment. The currency type for the last payment. BIGINT BIGINT BIGINT BIGINT
NULL
No
accbala_cur_tp minpaym_cur_tp maxpaym_cur_tp lastpay_cur_tp
NULL NULL NULL NULL
No No No No
Chapter 2. Tables
49
CAMPAIGN Table
Column Name campaign_id campaign_tp_cd Comment The primary key of a campaign record. A numeric representation of the campaign for customer. The source of the campaign record. A short, meaningful label for the Campaign. Datatype BIGINT BIGINT Null Option NOT NULL NULL Is PK Yes No
campaign_source name description
NULL NOT NULL NULL
No No No
Provides extra VARCHAR(255) 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. The date that this row of data became valid. The date that this row of data became invalid. The date that the row was created. TIMESTAMP TIMESTAMP TIMESTAMP
start_dt end_dt created_dt last_update_user
NULL NULL NOT NULL NULL
No No No No
The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. When a record is added TIMESTAMP 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. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_dt
NOT NULL
No
last_update_tx_id
NULL
No
50
Licensed Materials Property of IBM Column Name priority_tp_cd Comment Datatype Null Option NULL Is PK No
The priority of a task, a BIGINT campaign, a value, and so on. Examples include high, medium, low.
CAMPAIGNASSOCIAT Table
Column Name campaignassoc_id Comment The primary key of Campaign Group record. The name of the business entity that is associated with the Campaign. Datatype BIGINT Null Option NOT NULL Is PK Yes
entity_name
VARCHAR(20)
NOT NULL
No
instance_Pk
The actual primary key BIGINT of the row in the logical entity that is associated with the Campaign. The primary key of a campaign record. BIGINT
NOT NULL
No
campaign_id associate_ind
NOT NULL NULL
No No
Identifies whether this is CHAR(1) a target association or regarding association. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
start_dt end_dt last_update_user
NOT NULL NULL NULL
No No No
The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. When a record is added TIMESTAMP 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.
last_update_dt
NOT NULL
No
Chapter 2. Tables
51
Licensed Materials Property of IBM Column Name last_update_tx_id Comment A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Datatype BIGINT Null Option NULL Is PK No
CATEGORY Table
Name category_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, BIGINT system-generated key that identifies a category row in the InfoSphere MDM Server system. A unique, BIGINT system-generated key that identifies a category hierarchy row in the InfoSphere MDM Server system. An identifier for a category within a particular hierarchy. VARCHAR(255)
cat_hierarchy_id
NOT NULL
No
category_code
NULL
No
name
Name is a short, VARCHAR(120) meaningful label for the category Description provides VARCHAR(255) extra information, which can be used either as an additional definition as free form comments used by the user to provide further meaning to the category Indicates that the category is root in the hierarchy (ultimate parent) Indicates if the category may have subcategories or not. Indicates if the category permits associations to be made with it (i.e., product-category) Specifies the date when this record in takes effect. CHAR(1)
NOT NULL
No
description
NULL
No
is_root
NOT NULL
No
is_leaf
CHAR(1)
NOT NULL
No
assoc_ind
CHAR(1)
NOT NULL
No
start_dt
TIMESTAMP
NOT NULL
No
52
Licensed Materials Property of IBM Name end_dt Comment Specifies the date when this record becomes inactive Datatype TIMESTAMP Null Option NULL Is PK No
last_update_dt
When a record is added TIMESTAMP or updated, this field is updated with the date and time. On subsequent updates, the InfoSphere MDM Server 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 ID of user who last VARCHAR(20) updated the data. Either the user ID or the user group must be passed in the XML header if security or ROV is turned on. 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
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
CATEGORYNLS Table
Name category_nls_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, BIGINT system-generated key that identifies a category localized NLS row in the InfoSphere MDM Server system. The primary key of the NLS category record. Language type code. Localized name for the category name. Localized description for the category description. BIGINT BIGINT VARCHAR(120) VARCHAR(255)
category_id lang_tp_cd name description
NOT NULL NOT NULL NOT NULL NULL
No No No No
Chapter 2. Tables
53
Licensed Materials Property of IBM Name last_update_dt Comment 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 on this field; if it does not, the update fails. Datatype TIMESTAMP Null Option NOT NULL Is PK No
last_update_user
Id of user who last VARCHAR(20) updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on. 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_tx_id
NULL
No
CATEQUIV Table
Name cat_equiv_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, BIGINT system-generated key that identifies a category equivalency row in the InfoSphere MDM Server system. A unique, BIGINT system-generated key that identifies a category in the InfoSphere MDM Server system. Administration System BIGINT Code uniquely identifies the administrative source system for a contract. Examples include Ingenium, Alltel, Huon, etc. A key, or id, that uniquely identifies the category in the administrative source system. VARCHAR(160)
category_id
NOT NULL
No
admin_sys_tp_cd
NOT NULL
No
cat_equiv_key
NULL
No
54
Licensed Materials Property of IBM Name key_1 Comment A partial key, which in conjunction with other keys, identifies the category in the administrative source system. A partial key, which in conjunction with other keys, identifies the category in the administrative source system. A partial key, which in conjunction with other keys, identifies the category in the administrative source system. A partial key, which in conjunction with other keys, identifies the category in the administrative source system. A partial key, which in conjunction with other keys, identifies the category in the administrative source system. 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 on this field; if it does not, the update fails. Datatype VARCHAR(30) Null Option NOT NULL Is PK No
key_2
VARCHAR(30)
NULL
No
key_3
VARCHAR(30)
NULL
No
key_4
VARCHAR(30)
NULL
No
key_5
VARCHAR(30)
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
55
CATHIERARCHY Table
Name cat_hierarchy_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, BIGINT system-generated key that identifies a category hierarchy row in the InfoSphere MDM Server system. Name is a short, VARCHAR(120) meaningful label for the category hierarchy. Description provides VARCHAR(255) extra information, which can be used either as an additional definition as free form comments used by the user to provide further meaning to the category hierarchy. Code indicating referencing category hierarchy type (code table). Specifies the date when this record in takes effect Specifies the date when this record becomes inactive 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 on this field; if it does not, the update fails. 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
name
NOT NULL
No
description
NULL
No
hierarchy_tp_cd
NULL
No
start_dt
TIMESTAMP
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_tx_id
BIGINT
NULL
No
56
Licensed Materials Property of IBM Name last_update_user Comment Datatype Null Option NULL Is PK No
Id of user who last VARCHAR(20) updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on.
CATHIERARCHYNLS Table
Name cat_hierarchy_nls_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, BIGINT system-generated key that identifies a category hierarchy NLS row in the InfoSphere MDM Server system. The primary key of the NLS category hierarchy record. Language type code. Localized name for the category hierarchy name. Localized description for the category hierarchy description. 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 on this field; if it does not, the update fails. BIGINT
cat_hierarchy_id
NOT NULL
No
lang_tp_cd name
BIGINT VARCHAR(120)
NOT NULL NOT NULL
No No
description
VARCHAR(255)
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
57
CATNODEREL Table
Name cat_node_rel_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, BIGINT system-generated key that identifies a category node relationship row in the InfoSphere MDM Server system. The primary key (category_id) of the parent hierarchy node record The primary key (category_id) of the child hierarchy node record Specifies the date when this record in takes effect. Specifies the date when this record becomes inactive 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 on this field; if it does not, the update fails. 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
parent_node_id
NOT NULL
No
child_node_id
BIGINT
NOT NULL
No
start_dt
TIMESTAMP
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_tx_id
BIGINT
NULL
No
last_update_user
NULL
No
58
CDACCETOCOMPTP Table
Column Name lang_tp_cd Comment 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. acce_comp_tp_cd Represents one of the BIGINT various types of access a party may have to a computer and related technologies. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt last_update_dt
NULL NOT NULL
No No
Chapter 2. Tables
59
CDACCOUNTREQUIREDTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Indicates whether the product requires an account or not. BIGINT
account_required_tp_cd
NOT NULL
Yes
name
Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. 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 on this field; if it does not, the update fails. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
60
CDACCOUNTTP Table
Column Name lang_tp_cd Comment 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. acct_tp_cd Identifies the type of bank account provided by the party. Some examples are checking, savings, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
61
CDACTIONADJREASTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
62
CDADDRUSAGETP Table
Column Name lang_tp_cd Comment 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. addr_usage_tp_cd Identifies the usage of an address provided by a party. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
63
CDADMINFLDNMTP Table
Column Name lang_tp_cd Comment 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. admin_fld_nm_tp_cd Identifies the field name BIGINT that the native key refers to, for example, policy number, policy suffix, account number, branch, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. Uniquely identifies the administrative source system for a contract. Examples include Ingenium, Alltel, Huon, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
admin_sys_tp_cd
NOT NULL
No
size_num
The length or number of NUMERIC(2,0) digits used by the native key field. The name of the datatype for the native key field. VARCHAR(40)
NULL
No
datatype_name
NULL
No
displayed_ind
Indicates whether this is CHAR(1) the native key field to be displayed to the user. The order by which the SMALLINT contracts administrative source system understands the native key fields. The date that the type code is no longer valid. TIMESTAMP
NULL
No
present_seq_num
NULL
No
expiry_dt
NULL
No
64
CDADMINSYSTP Table
Column Name lang_tp_cd Comment 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. admin_sys_tp_cd Uniquely identifies the administrative source system for a contract. Examples include Ingenium, Alltel, Huon, and others. The total number of identifying fields used in the administrative source system to uniquely point to a contract record. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
native_key_tot
SMALLINT
NULL
No
name
NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
65
CDAGEVERDOCTP Table
Column Name lang_tp_cd Comment 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. age_ver_doc_tp_cd An identifier that uniquely separates one type of document being used to verify a clients age from another. Examples include birth certificate, drivers license, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
66
CDAGREEMENTSTTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. 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
agreement_st_tp_cd
NOT NULL
Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
67
CDAGREEMENTTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Describes the type of BIGINT the contract. Some examples include: Value Package, Supplier Agreement Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
agreement_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
68
CDALERTCAT Table
Column Name lang_tp_cd Comment 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. alert_cat_cd Identifies the high level BIGINT classification of alerts on a business object. For example: complaint, court order, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
69
CDALERTSEVTP Table
Column Name lang_tp_cd Comment 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. alert_sev_tp_cd An identifier that uniquely separates one type of alert severity from another. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
70
CDALERTTP Table
Column Name lang_tp_cd Comment 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. alert_tp_cd Uniquely identifies the BIGINT type of alert, within a particular alert category. For example: divorce pending, court order, office of the company, and others. Identifies the high level BIGINT classification of alerts on a business object. For example: complaint, court order, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
alert_cat_cd
NOT NULL
No
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
71
CDARRANGEMENTTP Table
Column Name lang_tp_cd Comment 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. arrangement_tp_cd Describes the type of BIGINT agreement that the party contract role has with the contract. For example: time delay arrangement such as a common disaster. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
72
CDAVAILABILITYTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. The availability status of BIGINT the product with respect to its target market. Determines whether the product is generally available, or has restricted availability. Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
availability_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
73
last_update_user
NULL
No
CDBILLINGSTTP Table
Column Name lang_tp_cd Comment 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. billing_st_tp_cd A unique type code BIGINT which uniquely defines a billing status value. Some examples are closed, paid, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
74
CDBILLTP Table
Column Name lang_tp_cd Comment 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. bill_tp_cd An identifier that uniquely separates one billing type from another. Examples include Regular, Direct, Payroll deduction, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
75
CDBUYSELLAGREETP Table
Column Name lang_tp_cd Comment 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. buy_sell_agr_tp_cd An identifier that BIGINT uniquely separates one type of buy-sell agreement from another. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
76
CDCAMPAIGNTP Table
Column Name lang_tp_cd Comment 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. campaign_tp_cd A numeric representation of the campaign for customer BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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 The date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
77
CDCDCREJREASONTP Table
Column Name LANG_TP_CD Comment Language Type Code 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. REJ_REASON_TP_CD The reason for which a critical data change has been rejected. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
NAME
The Name is a short, VARCHAR(120) meaningful label for the value of the type code. The Description provides extra information that can be used either as an additional definition of the type code value or as free form comments to provide further information about the type code. The Expiry Date represents the date on which the type code will no longer be valid. VARCHAR(255)
NOT NULL
No
DESCRIPTION
NULL
No
EXPIRY_DT
TIMESTAMP
NULL
No
78
Licensed Materials Property of IBM Column Name LAST_UDPATE_DT Comment Datatype Null Option NOT NULL Is PK No
CDCDCSTTP Table
Column Name LANG_TP_CD Comment Language Type Code 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. CDC_ST_TP_CD The CDC Status type BIGINT code indicates the status of the critical data change request. The Name is a short, VARCHAR(120) meaningful label for the value of the type code. The Description provides extra information that can be used either as an additional definition of the type code value or as free form comments to provide further information about the type code. The Expiry Date represents the date on which the type code will no longer be valid. VARCHAR(255) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
NAME
NOT NULL
No
DESCRIPTION
NULL
No
EXPIRY_DT
TIMESTAMP
NULL
No
Chapter 2. Tables
79
Licensed Materials Property of IBM Column Name LAST_UDPATE_DT Comment Datatype Null Option NOT NULL Is PK No
CDCHARGECARDTP Table
Column Name lang_tp_cd Comment 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. charge_card_tp_cd Identifies one type of BIGINT charge card from another. Some examples are Visa, MasterCard, American Express, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
80
CDCLAIMROLETP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
81
CDCLAIMSTATUSTP Table
Column Name lang_tp_cd Comment 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. claim_status_tp_cd Identifies the status of a BIGINT claim. Some examples include Pending, Closed and Rejected. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
82
CDCLAIMTP Table
Column Name lang_tp_cd Comment 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. claim_tp_cd The type of claim that is BIGINT recorded. Some examples include Fire, Theft, Automobile, Collision and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
83
CDCLIENTIMPTP Table
Column Name lang_tp_cd Comment 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. client_imp_tp_cd An identifier that uniquely separates one client importance type from another. Examples include high, medium, and low. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
84
CDCLIENTPOTENTP Table
Column Name lang_tp_cd Comment 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. client_poten_tp_cd An identifier that BIGINT uniquely separates one client potential type from another. For example, an insurance provider might have the potential types client, prospect and non-potential. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date upon which given client potential type is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
85
CDCLIENTSTTP Table
Column Name lang_tp_cd Comment 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. client_st_tp_cd An identifier that uniquely separates one client status type from another. For example, a telecommunications company might have the client status types active, inactive, and pending. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
86
CDCOMPLCATTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Compliance Category BIGINT Code identifies the high level classification of compliance requirement on a business object. Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
compl_cat_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
87
CDCOMPLDOCTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Compliance Document Type Code uniquely identifies the type of Compliance Document. BIGINT
compl_doc_tp_cd
NOT NULL
Yes
name
Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
88
CDCOMPLIANCETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Compliance Type Code uniquely identifies the type of compliance, it could be within a particular compliance category. BIGINT
compl_tp_cd
NOT NULL
Yes
name
Name is a short, VARCHAR(120) meaningful label for the value of the type code. Compliance Category BIGINT Code identifies the high level classification of compliance requirement on a business object. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
compl_cat_cd
NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
89
CDCOMPLTARGETTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Compliance Target Type BIGINT Code uniquely identifies the type of Compliance Target. Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
compl_target_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
90
CDCONDITIONATTRIBUTETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Describes the attribute BIGINT type of the condition. For example : Core Account Type, Status, Interest Rate Describes the usage types for a condition. For example : Value Package Integrity, Rate, Fee, Balance BIGINT
condition_attr_tp_cd
NOT NULL
Yes
condition_usage_tp_cd
NOT NULL
No
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
91
CDCONDITIONOWNERTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Identifies a spoken BIGINT 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. Identifies the owner of the condition. BIGINT
condition_owner_tp_cd name
NOT NULL NOT NULL
Yes No
A short, meaningful VARCHAR(120) label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. 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 on this field; if it does not, the update fails. TIMESTAMP
description
NULL
No
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
92
CDCONDITIONUSAGETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Identifies a spoken BIGINT 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. Describes the usage types for a condition. For example: Value Package Integrity, Rate, Fee, Balance. BIGINT
NOT NULL
Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date on and after which the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
last_update_dt
When a record is added TIMESTAMP 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. The column represents associated ruleId VARCHAR(10)
NOT NULL
No
rule_id
NULL
No
Chapter 2. Tables
93
CDCONTMETHCAT Table
Column Name lang_tp_cd Comment 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. cont_meth_cat_cd Identifies the type of BIGINT contact method. For example: telephone, e-mail, PDA, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
94
CDCONTMETHTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
cont_meth_cat_cd
Identifies the type of BIGINT contact method. For example: telephone, e-mail, PDA, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
95
CDCONTRACTRELSTTP Table
Column Name lang_tp_cd Comment 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. contr_rel_st_tp_cd Identifies the status of BIGINT the relationship between two contracts, for example, pending, active, and terminated. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
96
CDCONTRACTRELTP Table
Column Name lang_tp_cd Comment 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. contr_rel_tp_cd Describes the type of a BIGINT relationship. Reciprocal in nature, examples include child/parent and supports/supported by. A short, meaningful label for the to value of the relationship. A short, meaningful label for the from value of the relationship. VARCHAR(120) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
to_from_name
NOT NULL
No
from_to_name
VARCHAR(120)
NULL
No
description
Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
97
CDCONTRACTROLETP Table
Column Name lang_tp_cd Comment 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. contr_role_tp_cd Contract Role Type BIGINT 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. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
98
CDCONTRACTSTTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
99
CDCONTRCOMPTP Table
Column Name lang_tp_cd Comment 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. contr_comp_tp_cd A numeric representation of the type of coverage for the product. For example: v Base v Rider v Base Increase v Integrated name A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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 The date that the type code is no longer valid. TIMESTAMP NOT NULL No BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
NULL NOT NULL
No No
100
CDCOUNTRYTP Table
Column Name lang_tp_cd Comment 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. country_tp_cd name Identifies a country. BIGINT NOT NULL NOT NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. This field contains codes CHAR(2) for the names of countries and dependent territories as published by the International Organization for Standardization (ISO)
iso_code
NULL
No
Chapter 2. Tables
101
CDCURRENCYTP Table
Column Name lang_tp_cd Comment 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. currency_tp_cd name Identifies the currency of the amount columns. BIGINT NOT NULL NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. Captures the standard currency code for each currency. CHAR(3)
currency_code
NULL
No
102
CDDEMOGRAPHICSTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. The Demographics ID BIGINT identifies the type of the demographics record. The name of the demographics type. VARCHAR(120)
demographics_tp_cd
NOT NULL
Yes
name spec_id
NOT NULL NULL
No No
The ID of the Spec used BIGINT for the demographics type. The description of the demographics type. Expiry Date represents the date that the type code is no longer valid. 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 on this field; if it does not, the update fails. VARCHAR(255) TIMESTAMP
description expiry_dt
NULL NULL
No No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
Chapter 2. Tables
103
CDDOMAINTP Table
Column Name lang_tp_cd Comment 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. domain_tp_cd Defines the types of values can be stored. Examples include Integer, String, Decimal, Date, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
104
CDDOMAINVALUETP Table
Column Name domain_value_tp_cd Comment Domain Value Type Code, in a given domain, identifies the specific values that are captured. For example: Integer value, Date value, and others. 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. prod_tp_cd Product Type Code BIGINT identifies the type of product associated with the contract (or at some level within the product family). Examples include Universal Life, Savings, Checking, Term Life, Auto, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Defines the types of values can be stored. Examples include Integer, String, Decimal, Date, and others. BIGINT NULL No BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
domain_tp_cd
NOT NULL
No
description
Provides extra VARCHAR(255) 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 The date that the type code is no longer valid. TIMESTAMP
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
105
Licensed Materials Property of IBM Column Name precision_value Comment Datatype Null Option NULL Is PK No
Defines the Value String SMALLINT attribute in the Contract Component Value by identifying the number of digits to be expected for that given Value Type Code. When a record is added TIMESTAMP 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.
last_update_dt
NOT NULL
No
CDENDREASONTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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.
NOT NULL
No
description
NULL
No
106
Licensed Materials Property of IBM Column Name expiry_dt last_update_dt Comment The date that the type code is no longer valid. Datatype TIMESTAMP Null Option NULL NOT NULL Is PK No No
CDENUMANSWERCATTP Table
Name enum_ans_cat_tp_cd lang_tp_cd name Comment Enum answer category type code. Language type code. The name or value of enum answer category type. Datatype BIGINT BIGINT VARCHAR(120) Null Option NOT NULL NOT NULL NOT NULL Is PK Yes Yes No
description
Description provides VARCHAR(255) 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. The expiry date of the code table record. The last update date of current record. TIMESTAMP TIMESTAMP
NULL
No
NULL NOT NULL
No No
CDENUMANSWERTP Table
Name lang_tp_cd enum_ans_tp_cd enum_ans_cat_tp_cd name Comment Language type code. Enum answer type code. Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL NULL NOT NULL Is PK Yes Yes No No
The enumerated answer BIGINT category type code The name or value of enumerated answer type VARCHAR(120)
Chapter 2. Tables
107
Licensed Materials Property of IBM Name description Comment Datatype Null Option NULL Is PK No
Description provides VARCHAR(255) 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. The expiry date of the code table record. The last update date of current record. TIMESTAMP TIMESTAMP
NULL NOT NULL
No No
CDFREQMODETP Table
Column Name lang_tp_cd Comment 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. freq_mode_tp_cd Identifies the frequency of the payments made on the contract. For example: monthly, annual, weekly, daily, or other. name A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL No BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
expiry_dt
NULL
No
108
CDGENERATIONTP Table
Column Name lang_tp_cd Comment 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. generation_tp_cd Identifies the partys designated suffix. Examples include the first, junior, and so on. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
109
CDGROUPINGCATTP Table
Column Name lang_tp_cd Comment Language Type Code 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. group_cat_tp_cd The Group Category BIGINT Type Code identifies the category code type of a grouping. The Name is a short, VARCHAR(120) meaningful label for the value of the type code. The Description provides extra information that can be used either as an additional definition of the type code value or as free form comments to provide further information about the type code. The Expiry Date represents the date on which the type code will no longer be valid. VARCHAR(255) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
TIMESTAMP
NULL
No
110
CDGROUPINGTP Table
Column Name lang_tp_cd Comment 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. grouping_tp_cd Identifies the code type BIGINT of a Group, or classification associating a number of like entities, such as parties. Identifies the category code type for a grouping. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
grouping_cat_tp_cd
NULL
No
name
A short, meaningful VARCHAR(120) label for the node value. The name of the group type, such as Platinum group. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
111
CDHIERARCHYCATTP Table
Column Name lang_tp_cd Comment 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. hier_cat_tp_cd name Identifies the category BIGINT code type of a hierarchy. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL NOT NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
expiry_dt
NULL
No
112
CDHIERARCHYTP Table
Column Name lang_tp_cd Comment 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. hierarchy_tp_cd name Identifies the code type of a hierarchy. BIGINT NOT NULL NOT NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
113
When a record is added TIMESTAMP 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. Identifies the category BIGINT code type of a hierarchy.
hier_cat_tp_cd
NULL
No
CDHIGHESTEDUTP Table
Column Name lang_tp_cd Comment 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. highest_edu_tp_cd Identifies the highest BIGINT level of schooling that this person has received. For example: high school, college, university, or postgraduate. name A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL No NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
expiry_dt
NULL
No
114
CDHOLDINGTP Table
Column Name lang_tp_cd Comment 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. hold_tp_cd Identifies a type of party holding. For example: Vehicles, Property, Stocks, or others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
115
CDIDSTATUSTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NULL
No
description
NULL
No
expiry_dt
NULL
No
116
CDIDTP Table
Column Name lang_tp_cd Comment 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. id_tp_cd Identifies the type of BIGINT identifier provided by the party. For example: social security number, passport, drivers license number, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
117
When a record is added TIMESTAMP 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. maximum allowed number SMALLINT
max_allowed_num
NULL
No
CDINACTREASONTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
118
CDINCOMESRCTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
119
CDINDUSTRYTP Table
Column Name lang_tp_cd Comment 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. industry_tp_cd Represents the industry type for the organization. Examples include SIC, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
120
CDINTERACTIONCAT Table
Column Name lang_tp_cd Comment 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. interact_cat_cd Identifies the high level BIGINT category of the interaction with the customer. For example: marketing initiative, complaint, cold call, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
121
CDINTERACTIONTP Table
Column Name lang_tp_cd Comment 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. interact_tp_cd Identifies the type of BIGINT interaction with the customer. The Interaction SubType Code is dependent on the Interaction Category Code. Some example values are campaign, incorrect billing, and others. Identifies the high level BIGINT category of the customer service representatives interaction with the customer. For example: marketing initiative, complaint, cold call, and others. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
interact_cat_cd
NOT NULL
No
name
NOT NULL
No
122
Licensed Materials Property of IBM Column Name description Comment Datatype Null Option NULL Is PK No
NULL NOT NULL
No No
CDINTERACTPTTP Table
Column Name lang_tp_cd Comment 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. interact_pt_tp_cd Identifies the media BIGINT through which the interaction was made possible. Some examples are telephone, e-mail, mail, and others. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
123
NULL NOT NULL
No No
CDINTERACTRELTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code.
NOT NULL
No
124
NULL NOT NULL
No No
CDINTERACTRESPTP Table
Column Name lang_tp_cd Comment 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. interact_resp_tp name The type of response for BIGINT an interaction. A short, meaningful label for the from value of the relationship. VARCHAR(120) NOT NULL NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
description
Provides extra VARCHAR(255) 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.
NULL
No
Chapter 2. Tables
125
CDINTERACTSTTP Table
Column Name lang_tp_cd Comment 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. interact_st_tp_cd Describes the status of the interaction. Some examples are Awaiting reply, Returned, No answer BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
126
CDLANGTP Table
Column Name lang_tp_cd Comment 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. name A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL No Datatype BIGINT Null Option NOT NULL Is PK Yes
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
127
Licensed Materials Property of IBM Column Name locale Comment Captures the locale string for the language record. Datatype VARCHAR(20) Null Option NULL Is PK NO
code_table_translation
Indicates whether CHAR(1) InfoSphere MDM Server provides the code table translation for the given language and locale.
NULL
NO
CDLINKREASONTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
128
CDLOBRELTP Table
Column Name lang_tp_cd Comment 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. lob_rel_tp_cd Identifies the unique type code for a specific line of business relationship type. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
129
CDLOBTP Table
Column Name lang_tp_cd Comment 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. lob_tp_cd Identifies the unique type code for a specific line of business. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
130
CDMARITALSTTP Table
Column Name lang_tp_cd Comment 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. marital_st_tp_cd Identifies the marital BIGINT status of a person. For example: single, widowed, divorced, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
131
CDMATCHENGINETP Table
Column Name lang_tp_cd Comment Language Type Code 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. match_eng_tp_cd The Matching Engine to BIGINT use for matching parties. The Name is a short, VARCHAR(120) meaningful label for the value of the type code. The Description provides extra information that can be used either as an additional definition of the type code value or as free form comments to provide further information about the type code. The Expiry Date represents the date on which the type code will no longer be valid. VARCHAR(255) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
TIMESTAMP
NULL
No
132
CDMATCHRELEVTP Table
Column Name lang_tp_cd Comment 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. match_relev_tp_cd Identifies party match BIGINT relevancies, providing a description of which elements were matched. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The score associated with a match relevancy type. For example: LNAME score = 30 match_eng_tp_cd The matching engine used for matching parties. BIGINT NULL No SMALLINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
relevency_score
NULL
No
Chapter 2. Tables
133
CDMETADATAINFOTP Table
Name metadata_info_tp_cd Comment A code that identifies the metadata information. Data that defines the value of the metadata information type code. An example is: 928749ae-f19c-41b6babf-380467cea769. Datatype BIGINT Null Option NOT NULL Is PK Yes
metadata_key
VARCHAR(255)
NOT NULL
No
metadata_package_tp_cd A code that identifies the metadata package. expiry_dt Expiry Date represents the date that the type code is no longer valid. When a record is added or 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.
BIGINT TIMESTAMP
NULL NULL
No No
last_update_dt
TIMESTAMP
NOT NULL
No
CDMETADATAPACKAGETP Table
Name Comment Datatype BIGINT Null Option NOT NULL Is PK Yes metadata_package_tp_cd A code that identifies the metadata package.
134
Licensed Materials Property of IBM Name Comment Datatype VARCHAR(255) Null Option NOT NULL Is PK No
metadata_package_name Data that defines the value of a metadata package type code, e.g. com.ibm.mdm.System. expiry_dt Expiry Date represents the date that the type code is no longer valid. When a record is added or 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.
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
CDMETHODSTATUSTP Table
Column Name lang_tp_cd Comment 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. method_st_tp_cd Identifies the status of a BIGINT contact method. For example: disconnected, cancelled, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
135
CDMISCVALUEATTRTP Table
Column Name lang_tp_cd Comment 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. valueattr_tp_cd The miscvalue attribute BIGINT 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. A short meaningful label for the category. VARCHAR(120) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name description
NULL NULL
No No
expiry_dt
NULL
No
136
CDMISCVALUECAT Table
Column Name lang_tp_cd Comment 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. miscvalue_cat_cd The category allows BIGINT institutions to classify the different types of values. Some examples are Demographic Category, Risk Category, Standard Industry Codes,Party, Billing, Address and others. A short meaningful label for the category. VARCHAR(120) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name description
NOT NULL NULL
No No
expiry_dt
NULL
No
Chapter 2. Tables
137
CDMISCVALUETP Table
Column Name lang_tp_cd Comment 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. miscvalue_tp_cd This is the misc. value BIGINT 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. The category allows BIGINT institutions to classify the different types of values. Some examples are Demographic Category, Risk Category, Standard Industry Codes, Party, Billing, Address and others. A short meaningful label for the category. VARCHAR(120) NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
miscvalue_cat_cd
NULL
No
name
NULL
No
138
NULL NOT NULL
No No
CDNAMEUSAGETP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
139
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. The greatest number of SMALLINT times a given Person Name Usage Type Code can be used.
max_allowed_num
NULL
No
CDNODEDESIGTP Table
Column Name lang_tp_cd Comment 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. nodedesig_tp_cd Identifies the node BIGINT designate code type of a hierarchy. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
140
NULL NOT NULL
No No
CDNODETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Identifies whether the BIGINT 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). Name is a short, VARCHAR(120) meaningful label for the value of the type code.
node_tp_cd
NOT NULL
Yes
name
NOT NULL
No
Chapter 2. Tables
141
Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. When a record is added or 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. TIMESTAMP
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
CDORGNAMETP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
142
NULL NOT NULL
No No
CDORGTP Table
Column Name lang_tp_cd Comment 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. org_tp_cd Identifies the BIGINT classification of the organization. For example: trust, company, charity, estate, and others. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
143
NULL NOT NULL
No No
CDPAYMENTMETHODTP Table
Column Name lang_tp_cd Comment 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. pymt_mthd_tp_cd A type code which uniquely identifies a payment method value in the system. Some examples are bank account, charge card, cash, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
144
NULL NOT NULL
No No
CDPPREFACTIONTP Table
Column Name lang_tp_cd Comment 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. ppref_action_tp_cd Identifies the action to BIGINT be taken based on the privacy preference set by the customer or by company default setting. For example: Do not call, Do not mail name A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL No NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
Chapter 2. Tables
145
NULL NOT NULL
No No
CDPPREFCAT Table
Column Name lang_tp_cd Comment 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. ppref_cat_cd Identifies the high level category of the privacy preference for the customer. For example: Sharing of Data, Solicitation, and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
146
NULL NOT NULL
No No
CDPPREFREASONTP Table
Column Name lang_tp_cd Comment 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. ppref_reason_tp_cd Identifies the reason given by customer for making a privacy preference selection. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
147
NULL NOT NULL
No No
CDPPREFSEGTP Table
Column Name lang_tp_cd Comment 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. ppref_seg_tp_cd Identifies the segment BIGINT associated with the privacy preference record. For example: FCRA, FCC, and others. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
148
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. Province State Type BIGINT Code 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 and the zip code.
prov_state_tp_cd
NULL
No
CDPPREFTP Table
Column Name lang_tp_cd Comment 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. Datatype BIGINT Null Option NOT NULL Is PK Yes
Chapter 2. Tables
149
Licensed Materials Property of IBM Column Name ppref_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes
The specific privacy BIGINT preference type within a particular category For example: Credit Info, Personal Info, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. Privacy Preference Category Code identifies the high level category of the privacy preference for the customer. For example: Sharing of Data, Solicitation, and others. BIGINT
ppref_cat_cd
NULL
No
150
CDPREFIXNAMETP Table
Column Name lang_tp_cd Comment 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. prefix_name_tp_cd Identifies the partys name prefix. Examples include Mr., Mrs., Dr., and others. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
151
CDPRIMARYTARGETMARKETTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. A primary market this product targets. For example, Retail Customer, SMB, Large Corporate, etc. BIGINT
primary_target_market_tp_cd
NOT NULL
Yes
name
Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. When a record is added or 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. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
152
CDPRIORITYCATTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. A code that classifies the BIGINT various types of priority. An example of it is Task. Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. 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 on this field; if it does not, the update fails. TIMESTAMP
priority_cat_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
Chapter 2. Tables
153
CDPRIORITYTP Table
Column Name lang_tp_cd Comment 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. priority_tp_cd Identifies the priority of a task, a campaign, value and others. Examples include high, medium, low. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
When a record is added TIMESTAMP 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. A code that classifies the BIGINT various types of priority. An example of a priority category type code is Task.
PRIORITY_CAT_TP_CD
NULL
No
154
CDPRODCONTRACTRELTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Identifies the type of the BIGINT Product Contract Relationship. For example : Party Selection Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. When a record is added or 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. TIMESTAMP
prod_contr_rel_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
Chapter 2. Tables
155
CDPRODRELATIONTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Identifies the type of relationship that two products can have between one another. A short, meaningful 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. BIGINT
product_rel_tp_cd
NOT NULL
Yes
from_to_name
VARCHAR(120)
NULL
No
to_from_name
A short, meaningful VARCHAR(120) 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. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
156
CDPRODRELTP Table
Column Name lang_tp_cd Comment 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. prodrel_tp_cd Identifies the type of relationship that two products can have between one another. For example: categorize A short, meaningful label for the from value of the relationship. A short, meaningful label for the to value of the relationship. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
from_to_name
VARCHAR(120)
NULL
No
to_from_name
VARCHAR(120)
NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
157
CDPRODSTRUCTURETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Identifies whether the product is a standalone product or represents a bundling of other component products. BIGINT
prod_struc_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
158
CDPRODTP Table
Column Name lang_tp_cd Comment 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. prod_tp_cd Identifies the type of BIGINT product associated with the contract (or at some level within the product family). For example, a manufacturing company might have the product types precision tools, switches, defence, electronics, and automotive. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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 The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
159
When a record is added TIMESTAMP 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. identifies the source of the code VARCHAR(100)
prod_source
NULL
No
CDPRODUCTIDENTIFIERTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. BIGINT
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. name
NOT NULL
Yes
Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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.
NOT NULL
No
description
NULL
No
160
Licensed Materials Property of IBM Name max_allowed_num Comment Represents the maximum number of active identifiers that can be added to the same product for the same identifier type. Expiry Date represents the date that the type code is no longer valid. 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 on this field; if it does not, the update fails. Datatype SMALLINT Null Option NULL Is PK No
expiry_dt
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
CDPRODUCTSTATUSTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. The lifecycle status of the product. For example, Available, Unavailable, Obsolete, etc. BIGINT
status_tp_cd
NOT NULL
Yes
name
Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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.
NOT NULL
No
description
NULL
No
Chapter 2. Tables
161
Licensed Materials Property of IBM Name expiry_dt Comment Expiry Date represents the date that the type code is no longer valid. When a record is added or 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. Datatype TIMESTAMP Null Option NULL Is PK No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
CDPROVSTATETP Table
Column Name lang_tp_cd Comment 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. prov_state_tp_cd Identifies the US States, BIGINT 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 and the zip code. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
162
NULL NOT NULL
No No
CDPURPOSETP Table
Column Name lang_tp_cd Comment 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. purpose_tp_cd Identifies the purpose BIGINT for the location as it relates to a role on a contract. For example, the owners residence address is associated with the contract for the purpose of sending statements A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
163
NULL NOT NULL
No No
CDQUESTIONCATTP Table
Name lang_tp_cd question_cat_tp_cd name description Comment Language type code. Question category type code. The name or value of question category type Datatype BIGINT BIGINT VARCHAR(120) Null Option NOT NULL NOT NULL NOT NULL NULL Is PK Yes Yes No No
Description provides VARCHAR(255) 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. The expiry date of the code table record The last update date of current record TIMESTAMP TIMESTAMP
NULL NOT NULL
No No
CDQUESTIONNAIRETP Table
Name lang_tp_cd Datatype BIGINT Null Option NOT NULL Comment Language type code. Is PK Yes
164
Licensed Materials Property of IBM Name quesnr_tp_cd name description Datatype BIGINT VARCHAR(120) VARCHAR(255) Null Option NOT NULL NOT NULL NULL Comment Questionnaire type code. Is PK Yes
The name or value of No questionnaire type 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
TIMESTAMP TIMESTAMP
NULL NOT NULL
The expiry date of the No code table record The last update date of current code table record No
CDQUESTIONTP Table
Name lang_tp_cd question_tp_cd question_cat_tp_cd name description Datatype BIGINT BIGINT BIGINT VARCHAR(120) VARCHAR(255) Null Option NOT NULL NOT NULL NULL NOT NULL NULL Comment Language type code. Question type code. Is PK Yes Yes
The question category No type code The name or value of No question type 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
TIMESTAMP TIMESTAMP
NULL NOT NULL
The expiry date of the No code table record The last update date of current record. No
Chapter 2. Tables
165
CDRELASSIGNTP Table
Column Name lang_tp_cd Comment 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. rel_assign_tp_cd Identifies how the BIGINT 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. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NULL
No
description
NULL
No
NULL NOT NULL
No No
166
CDRELTP Table
Column Name lang_tp_cd Comment 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. rel_tp_cd Identifies the type of relationship that two parties can have between one another. For example: is parent of or is employer of. A short, meaningful label for the from value of the relationship. A short, meaningful label for the to value of the relationship. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
from_to_name
VARCHAR(120)
NULL
No
to_from_name
VARCHAR(120)
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
Chapter 2. Tables
167
CDREPOSITORYTP Table
Name repository_tp_cd name Comment Uniquely identifies the CMS Repository. Name of the repository, may point to the jndi name, connector name of the IICE etc. Datatype BIGINT VARCHAR(120) Null Option NOT NULL NOT NULL Is PK Yes No
description
Description provides VARCHAR(255) extra information, that can be used either as an additional definition of the type code value or as freeform comments used by the user to provide further meaning to the type code. Name of the CMS system. Number of parameters defined by the CMS System, to uniquely identify a content The expiry Date is the date from which the record is no longer effective. 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 on this field; if it does not, the update fails. VARCHAR(250) BIGINT
NULL
No
content_system no_of_keys
NULL NOT NULL
No No
expiry_dt
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
CDRESIDENCETP Table
Column Name lang_tp_cd Comment 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. Datatype BIGINT Null Option NOT NULL Is PK Yes
168
Licensed Materials Property of IBM Column Name residence_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes
Identifies a type of BIGINT residence for a given address. Some examples include Home, Apartment, and Suite. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP
name
NOT NULL
No
description
NULL
No
NULL NOT NULL
No No
CDROLECATTP Table
Column Name lang_tp_cd Comment 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. role_cat_tp_cd name This is the role category BIGINT type code. A short meaningful label for the category. VARCHAR(120) NOT NULL NOT NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
Chapter 2. Tables
169
NULL NOT NULL
No No
CDROLETP Table
Column Name lang_tp_cd Comment 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. role_tp_cd role_cat_tp_cd This is the role type code The category allows institutions to classify the different types of roles. Some examples are Party Relationship Roles, Hierarchy Roles, Grouping Roles, and others. A short meaningful label for the category. BIGINT BIGINT NOT NULL NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
name
VARCHAR(120)
NULL
No
170
NULL NOT NULL
No No
CDRPTINGFREQTP Table
Column Name lang_tp_cd Comment 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. rpting_freq_tp_cd Describes the frequency BIGINT that a particular Party (CONTACT) would like to receive consolidated statements. Sample values include annually, semi-annually, monthly, and others. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
171
NULL NOT NULL
No No
CDSERVICELEVELTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Identifies the Service BIGINT level associated with the contract. Some examples include 24/7 call centre service or Service during business hours only. Name is a short, VARCHAR(120) meaningful label for the value of the type code.
service_level_tp_cd
NOT NULL
Yes
name
NOT NULL
No
172
Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. When a record is added or 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. TIMESTAMP
expiry_dt
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
CDSHAREDISTTP Table
Column Name lang_tp_cd Comment 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. share_dist_tp_cd Identifies how the BIGINT proceeds of the contract component get distributed among the associated party contract roles. Examples include equal shares, 50% share, and so on. A short, meaningful VARCHAR(120) label for the value of the type code. NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
Chapter 2. Tables
173
NULL NOT NULL
No No
CDSOURCEIDENTTP Table
Column Name lang_tp_cd Comment 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. source_ident_tp_cd name Identifies the type for the source identifier. BIGINT NOT NULL NOT NULL Yes No Datatype BIGINT Null Option NOT NULL Is PK Yes
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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.
description
NULL
No
174
CDSPECCASCADETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. The cascade action the spec will have in a hierarchy. For example, Cascaded to descendents, Not cascaded to descendents, etc. BIGINT
spec_cascade_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
175
Licensed Materials Property of IBM Name last_update_dt Comment When a record is added or 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. Datatype TIMESTAMP Null Option NOT NULL Is PK No
CDSPECUSETP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. 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
spec_use_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
176
CDSTATUSREASONTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Identifies the reason BIGINT why the product is in its current state. Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
status_reason_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
177
last_update_user
NULL
No
CDSUSPECTREASONTP Table
Column Name lang_tp_cd Comment 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. susp_reason_tp_cd Identifies the field that caused the data match to occur. BIGINT NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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 Reason Score is the SMALLINT numeric score associated with the suspect reason code.
NOT NULL
No
description
NULL
No
reason_score
NULL
No
178
Licensed Materials Property of IBM Column Name match_eng_tp_cd Comment The matching engine used for matching parties. The date that the type code is no longer valid. Datatype BIGINT Null Option NULL Is PK No
TIMESTAMP
NULL NOT NULL
No No
CDSUSPECTSOURCETP Table
Column Name lang_tp_cd Comment 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. susp_source_tp_cd Identifies the source of BIGINT the Suspect Reason Code: system marked or user marked A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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. The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
179
CDSUSPECTSTATUSTP Table
Column Name lang_tp_cd Comment 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. susp_st_tp_cd Indicates the current BIGINT situation for a particular suspect record - suspect duplicate, not duplicate, under investigation, and others. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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 The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
180
CDSUSPECTTP Table
Column Name lang_tp_cd Comment 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. suspect_tp_cd Captures various BIGINT suspect types. One record exists for each unique add_action_code in the addactiontype table. A short, meaningful VARCHAR(120) label for the value of the type code. Provides extra VARCHAR(255) 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 The date that the type code is no longer valid. TIMESTAMP NOT NULL Yes Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
181
When a record is added TIMESTAMP 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. Primary key of the External Rule Record VARCHAR(10)
rule_id
NOT NULL
No
CDTAXPOSITIONTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. The relative tax position BIGINT offered by the product. Determines whether the product is tax neutral, provides the customer a tax advantage, or provides the FI with a tax advantage. Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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. Expiry Date represents the date that the type code is no longer valid. TIMESTAMP
tax_position_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
182
last_update_user
NULL
No
CDTERMINATIONREASONTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Describes the reason BIGINT why the contract is terminated. For example : Terms & Conditions violated, Core account closed by owner Name is a short, VARCHAR(120) meaningful label for the value of the type code. Description provides VARCHAR(255) 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.
termination_reason_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
Chapter 2. Tables
183
Licensed Materials Property of IBM Name expiry_dt Comment Expiry Date represents the date that the type code is no longer valid. 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 on this field; if it does not, the update fails. Datatype TIMESTAMP Null Option NULL Is PK No
last_update_dt
TIMESTAMP
NOT NULL
No
CDUNDELREASONTP Table
Column Name lang_tp_cd Comment 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. 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 Datatype BIGINT Null Option NOT NULL Is PK Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
184
CDVALFREQTP Table
Name lang_tp_cd Comment Datatype Null Option NOT NULL Is PK Yes Language Type Code BIGINT 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 language of the code name. Validation Frequency Type Code uniquely identifies the type of validation frequency. BIGINT
val_freq_tp_cd
NOT NULL
Yes
name
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
Chapter 2. Tables
185
CHARGECARD Table
Column Name payment_source_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a payment source in the InfoSphere MDM Server system. Identifies one type of BIGINT charge card from another. Some examples are Visa, MasterCard, American Express, and others. The number that uniquely identifies a charge card. VARCHAR(30)
charge_card_tp_cd
NOT NULL
No
charge_card_num
NOT NULL
No
expiry_dt on_card_name
The date that the charge TIMESTAMP card will expire. The account name of the VARCHAR(100) charge card as it exactly appears on the charge card. A unique identifier for VARCHAR(10) the bank that issued the chargecard, assigned outside of InfoSphere MDM Server. When a record is added TIMESTAMP 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.
NOT NULL NULL
No No
bank_num
NULL
No
last_update_dt
NOT NULL
No
186
last_update_tx_id
NULL
No
CLAIM Table
Column Name claim_id Comment A unique, system generated key that identifies a claim. The reference identification number for the claim record. The Claim Number assigned to a claim is the means by which the claim can be distinguished from all other claims. The value of the claim detail. Datatype BIGINT Null Option NOT NULL Is PK Yes
admin_ref_num
VARCHAR(150)
NULL
No
claim_number
VARCHAR(20)
NULL
No
claim_detail_amt claim_paid_amt outstanding_amt benefit_claim_amt
DECIMAL(17,3)
NULL NULL NULL NULL
No No No No
The amount paid on the DECIMAL(17,3) claim. The amount that is to be DECIMAL(17,3) paid on the claim. The maximum amount that can be paid on a claim. Identifies the type of claim that is recorded. Some examples include Fire, Theft, Automobile, Collision and others. DECIMAL(17,3)
claim_tp_cd
BIGINT
NOT NULL
No
lob_tp_cd
Identifies the unique BIGINT type code for a specific line of business. Some examples are Life, Annuity, Disability, Auto & Home, and others.
NULL
No
Chapter 2. Tables
187
Licensed Materials Property of IBM Column Name claim_status_tp_cd Comment Datatype Null Option NULL Is PK No
Identifies the status of a BIGINT claim. Some examples include Pending, Closed and Rejected. A code that identifies the procedure or claim service. For example: Orthodontics procedure code is D8000. The date that the claim status was updated. The date that the claim was incurred. The date that the claim was reported. Description provides extra information about the claim. VARCHAR(20)
claim_code
NULL
No
status_dt claim_incurred_dt reported_dt description
TIMESTAMP TIMESTAMP TIMESTAMP VARCHAR(255)
NULL NULL NULL NULL
No No No No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
detlamt_cur_tp paidamt_cur_tp
The currency type for BIGINT the claim detail amount. The currency type for the total claim benefit amount. BIGINT
NULL NULL
No No
outsamt_cur_tp
The currency type for BIGINT the outstanding amount.
NULL
No
188
Licensed Materials Property of IBM Column Name Beneamt_cur_tp Comment The currency type for the Benefit Claim amount. Datatype BIGINT Null Option NULL Is PK No
CLAIMCONTRACT Table
Column Name claim_contr_id claim_id Comment Primary key of the claim contract record. A unique, system generated key that identifies a claim. A unique, system generated key that identifies a contract in the InfoSphere MDM Server system. Description provides extra information about the record. The date that the claim contract record became effective, or was recorded. The date that the claim contract record is no longer effective. Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Is PK Yes No
contract_id
BIGINT
NOT NULL
No
description
VARCHAR(255)
NULL
No
start_dt
TIMESTAMP
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
189
CLAIMROLE Table
Column Name claim_role_id claim_role_tp_cd Comment The primary key of a claim detail role record. Datatype BIGINT Null Option NOT NULL NOT NULL Is PK Yes No
Identifies a type of role BIGINT a party plays on a claim. Some examples include Claimant, Witness and Third Party. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. A unique, system generated key that identifies a claim. Provides extra information. The date that the claim role record became effective, or was recorded. The date that the claim role record is no longer effective. BIGINT
cont_id
NOT NULL
No
claim_id
NOT NULL
No
description start_dt
VARCHAR(255) TIMESTAMP
NULL NOT NULL
No No
end_dt
TIMESTAMP
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
190
COMPLDOCUMENT Table
Name compl_doc_id Comment Datatype Null Option NOT NULL Is PK Yes Compliance Document BIGINT ID is a unique, system generated key that identifies a Compliance Document in the InfoSphere MDM Server system. Compliance Target ID BIGINT represents that which compliance target this compliance document to validate. A unique type code which uniquely defines a compliance document value. Application represents the application name. Group Name represents the group name for this compliance document type belongs to. BIGINT
compl_target_id
NOT NULL
No
compl_doc_tp_cd
NOT NULL
No
application group_name
NULL NULL
No No
element_name
Element Name VARCHAR(50) represents the element name this compliance document type mapping to. Element value represents the element value this compliance target type mapping to. VARCHAR(255)
NULL
No
element_value
NULL
No
description
Description provides VARCHAR(255) 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. When a record is added or 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. TIMESTAMP
NULL
No
last_update_dt
NOT NULL
No
Chapter 2. Tables
191
Id of user who last VARCHAR(20) updated the data. Either user ID or user group must be passed in the XML header, if security/ROV is turned on. 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
last_update_tx_id
NULL
No
COMPLENTITY Table
Name compl_entity_id Comment Datatype Null Option NOT NULL Is PK Yes Compliance Entity ID is BIGINT a unique, system generated key that identifies a Compliance Entity in the InfoSphere MDM Server system. Compliance requirement BIGINT ID used for this compliance entity Entity Name for this compliance entity Instance Primary Key for this compliance entity. VARCHAR(120) BIGINT
compl_req_id
NOT NULL
No
entity_name instance_pk
NOT NULL NOT NULL
No No
created_dt
Created Date represents TIMESTAMP the date that this row of data become valid Description provides VARCHAR(255) 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. Next Verification Date TIMESTAMP represents the date that this compliance entity need to be re-verified based on the compliance requirement.
NOT NULL
No
description
NULL
No
next_verif_dt
NULL
No
192
Licensed Materials Property of IBM Name end_dt Comment End Date represents the date that this row of data became invalid. 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 on this field; if it does not, the update fails. Datatype TIMESTAMP Null Option NULL Is PK No
last_update_dt
TIMESTAMP
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
COMPLENTITYDOC Table
Name compl_ent_doc_id Comment Datatype Null Option NOT NULL Is PK Yes Compliance Entity BIGINT Document ID is a unique, system generated key that identifies a Compliance Entity Document in the InfoSphere MDM Server system. Compliance Entity Target ID represents which this compliance entity document validated Compliance Document ID represents that to which compliance document this compliance entity document references. BIGINT
compl_ent_targ_id
NOT NULL
No
compl_doc_id
BIGINT
NOT NULL
No
Chapter 2. Tables
193
Licensed Materials Property of IBM Name doc_instance_value Comment Datatype Null Option NULL Is PK No
Document value for this VARCHAR(30) compliance entity document. Document Expiry Date represents the date that this document of data became invalid. TIMESTAMP
doc_expiry_dt
NULL
No
description
Description provides VARCHAR(255) 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. 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 on this field; if it does not, the update fails. TIMESTAMP
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
COMPLENTITYTARGET Table
Name compl_ent_targ_id Comment Datatype Null Option NOT NULL Is PK Yes Compliance Entity BIGINT Target ID is a unique, system generated key that identifies a Compliance Entity Target in the InfoSphere MDM Server system.
194
Licensed Materials Property of IBM Name compl_entity_id Comment Datatype Null Option NOT NULL Is PK No
Compliance Entity ID BIGINT represents that to which compliance entity this compliance entity target belongs. Compliance Target ID BIGINT represents that to which compliance target this compliance entity target references. Instance Primary Key for this compliance entity target. BIGINT
compl_target_id
NOT NULL
No
target_instance_pk
NOT NULL
No
description
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
195
COMPLIANCEREQ Table
Name compl_req_id Comment Datatype Null Option NOT NULL Is PK Yes Compliance BIGINT Requirement ID is a unique, system generated key that identifies a Compliance Requirement in the InfoSphere MDM Server system. A unique type code which uniquely defines a compliance value. Date from which this compliance requirement is effective. End Date represents the date that this row of data became invalid. BIGINT
compl_tp_cd
NOT NULL
No
effect_dt
TIMESTAMP
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
ext_ref_id
External Reference Id VARCHAR(30) represents the external reference Id for this compliance requirement, for example regulatory number. Description provides VARCHAR(255) 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. A unique type code which uniquely defines a compliance validation frequency value. 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 on this field; if it does not, the update fails. BIGINT
NULL
No
description
NULL
No
val_freq_tp_cd
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
No
196
last_update_tx_id
NULL
No
COMPLTARGET Table
Name compl_target_id Comment Datatype Null Option NOT NULL Is PK Yes Compliance Target ID is BIGINT a unique, system generated key that identifies a Compliance Target in the InfoSphere MDM Server system. Compliance BIGINT Requirement ID represents that to which compliance requirement this compliance target belongs. A unique type code which uniquely defines a compliance target value. Application represents the application name. Group Name represents the group name for this compliance target type belongs to. Element Name represents the element name this compliance target type mapping to. Element value represents the element value this compliance target type mapping to. BIGINT
compl_req_id
NOT NULL
No
compl_target_tp_cd
NOT NULL
No
application group_name
NOT NULL NOT NULL
No No
element_name
VARCHAR(50)
NOT NULL
No
element_value
VARCHAR(255)
NOT NULL
No
Chapter 2. Tables
197
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
CONDITIONATTRIBUTE Table
Name condition_attribute_id condition_id Comment Datatype Null Option NOT NULL NOT NULL Is PK Yes No The primary key for the Condition BIGINT Attribute record. The id of the term condition associated with this condition attribute BIGINT
condition_attr_tp_cd
The BIGINT CDCONDTIONATTRIBUTETYPE table serves to group condition attributes and allows another level of detail. The value associated with this Condition Attribute VARCHAR(250)
NOT NULL
No
value
NULL
No
198
Licensed Materials Property of IBM Name last_update_dt Comment Datatype Null Option NOT NULL Is PK No
Whenever a record is TIMESTAMP 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. Transaction ID is a unique, system BIGINT generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. 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)
last_update_tx_id
NULL
No
last_update_user
NULL
No
CONTACT Table
Column Name cont_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Represents one of the BIGINT various types of access a party may have to a computer and related technologies. Identifies a preferred spoken language. For example: English, French, Spanish, and others. The date that the party row was created. Identifies the full name of the person to be contacted within the corporation. For trusts, this identifies the trustee. BIGINT
acce_comp_tp_cd
NULL
No
pref_lang_tp_cd
NULL
No
created_dt contact_name
TIMESTAMP VARCHAR(255)
NOT NULL NULL
No No
Chapter 2. Tables
199
Licensed Materials Property of IBM Column Name inactivated_dt Comment Datatype Null Option NULL Is PK No
The date which the TIMESTAMP party row was considered inactive through business processes such as collapsing and splitting, resulting in a new party record created, and others. A pointer to the type of party - person or organization. CHAR(1)
person_org_code
NOT NULL
No
solicit_ind
Determines whether this CHAR(1) party can be solicited at any location group. Indicates whether this partys information should be kept confidential. An identifier that uniquely separates one client importance type from another. Examples include high, medium, low. CHAR(1)
NULL
No
confidential_ind
NULL
No
client_imp_tp_cd
BIGINT
NULL
No
client_st_tp_cd
An identifier that BIGINT uniquely separates one client status type from another. Examples include prospect, active, suspended. An identifier that uniquely separates one client potential type from another. Examples include high, medium, low. BIGINT
NULL
No
client_poten_tp_cd
NULL
No
rpting_freq_tp_cd
Describes the frequency BIGINT 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. The last time a consolidated statement was sent to the Party. No business logic is currently being invoked on this field. TIMESTAMP
NULL
No
last_statement_dt
NULL
No
200
Licensed Materials Property of IBM Column Name alert_ind Comment Datatype Null Option NULL Is PK No
Indicates whether there CHAR(1) is any kind of alert or restriction on this party. This field is set by InfoSphere MDM Server when an active alert is associated with the Party record. Identifies the date that the contact has been a customer since. Identifies the date that the contact stopped being a customer. 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. TIMESTAMP
since_dt
NULL
No
left_dt
TIMESTAMP
NULL
No
access_token_value
VARCHAR(50)
NULL
No
pending_cdc_ind
Indicates the presence of CHAR(1) a pending critical data change (CDC) for a party. When a record is added TIMESTAMP 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. The Party ID of the party that referred this Party to the organization. BIGINT
NULL
No
last_update_dt
NOT NULL
No
provided_by_cont
NULL
No
last_update_user
The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on.
NULL
No
Chapter 2. Tables
201
Licensed Materials Property of IBM Column Name last_update_tx_id Comment A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. 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. source_ident_tp_cd last_used_dt The type for the source identifier. The date that this data was last used. There is no business logic associated with this field. The date that this data was last verified. There is no business logic associated with this field. BIGINT TIMESTAMP NULL NULL No No Datatype BIGINT Null Option NULL Is PK No
do_not_delete_ind
CHAR(1)
NULL
No
last_verified_dt
TIMESTAMP
NULL
No
CONTACTCDC Table
Name cdc_id cont_id Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Comment The primary key of the entity. Is PK Yes
Party ID is a unique, No system generated key that identifies a party in the WCC system. The class name of the No entity holding the critical data that was requested for update. The primary key of the entity holding critical data that was requested for update. An XML representation of the entity that was requested for update. The status of the critical data change request. No
entity_name
VARCHAR(120)
NOT NULL
instance_pk
BIGINT
NULL
critdata
CLOB(200K)
NOT NULL
No
cdc_st_tp_cd
BIGINT
NOT NULL
No
202
Licensed Materials Property of IBM Name rej_reason_tp_cd Datatype BIGINT Null Option NULL Comment The reason for which a critical data change is rejected. The timestamp when the pending critical data change is created. The timestamp when the pending critical data change has been resolved (either accepted or rejected). Is PK No
created_dt
TIMESTAMP
NOT NULL
No
expiry_dt
TIMESTAMP
NULL
No
last_update_tx_id
BIGINT
NULL
Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on. Whenever a record is No 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_user
VARCHAR(20)
NULL
last_update_dt
TIMESTAMP
NOT NULL
CONTACTDEMOGRAPHICS Table
Name demographics_id Datatype BIGINT Null Option NOT NULL Comment Demographics ID uniquely identifies the demographics record. Is PK Yes
cont_id
BIGINT
NOT NULL
The ID of the party to No whom the demographics record belongs.
Chapter 2. Tables
203
Licensed Materials Property of IBM Name demographics_tp_cd Datatype BIGINT Null Option NOT NULL Comment Type of the demographics information defined in code table cddemographicstp. The ID of the spec format Value is the demographics xml. The date when the demographics become valid. The date when the demographics become invalid. Is PK No
spec_fmt_id value start_dt
BIGINT CLOB(1G) TIMESTAMP
NOT NULL NOT NULL NOT NULL
No No No
end_dt
TIMESTAMP
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
Whenever a record is No 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. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on. Transaction ID generated by the system whenever the record is added/updated. No
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
CONTACTMETHOD Table
Column Name contact_method_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a contact method in the InfoSphere MDM Server system.
204
Licensed Materials Property of IBM Column Name cont_meth_cat_cd Comment Ientifies the main category of contact method. For example: telephone, email, PDA, and others. A unique, system generated key that identifies an address in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK No
address_id
BIGINT
NULL
No
ref_num
The actual text provided VARCHAR(255) 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. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Indicates if this contact method has been standardized. BIGINT
NOT NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
CONT_METH_STD_IND
CHAR(1)
NULL
No
Chapter 2. Tables
205
CONTACTMETHODGROUP Table
Column Name location_group_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a location group row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a contact method in the InfoSphere MDM Server system. 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
contact_method_id
NOT NULL
No
cont_meth_tp_cd
NOT NULL
No
method_st_tp_cd
Identifies the status of a BIGINT contact method. For example: disconnected, cancelled, and others. Indicates whether CHAR(1) attachments are allowed to be sent with this contact method. This indicator should only be used when the contact method refers to an email. Indicates whether this CHAR(1) can be sent as text only. This indicator should only be used when the contact method refers to an email. Represents the VARCHAR(20) 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. A comment or description. VARCHAR(100)
NULL
No
attach_allow_ind
NULL
No
text_only_ind
NULL
No
message_size
NULL
No
comment_desc
NULL
No
206
last_update_user
NULL
No
last_update_tx_id
NULL
No
CONTACTREL Table
Column Name cont_rel_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party relationship row in the InfoSphere MDM Server system. Identifies the type of relationship that two parties can have between one another. For example: is parent of, is employer of, and others. BIGINT
rel_tp_cd
NOT NULL
No
rel_desc
Refers to comments that VARCHAR(255) a user may have concerning the party relationship. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
NULL
No
start_dt end_dt
NOT NULL NULL
No No
Chapter 2. Tables
207
Licensed Materials Property of IBM Column Name to_cont_id Comment Datatype Null Option NOT NULL Is PK No
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. Identifies how the BIGINT 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. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
from_cont_id
NOT NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
rel_assign_tp_cd
NULL
No
last_update_tx_id
NULL
No
end_reason_tp_cd
Identifies the cause for a BIGINT party to party relationship being ended. For example, divorce can be used as an end reason.
NULL
No
208
CONTEQUIV Table
Column Name cont_equiv_Id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party equivalency row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Uniquely identifies the administrative source system for a contract. Examples include Ingenium, Alltel, Huon, and others. Uniquely identifies the primary key for the administrative source system BIGINT
cont_id
NOT NULL
No
admin_sys_tp_cd
NOT NULL
No
admin_client_id
VARCHAR(20)
NULL
No
description
Provides extra VARCHAR(255) information that can be used either as an additional definition of the record or as free form comments used by the user to provide further meaning to the record. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on.
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
Chapter 2. Tables
209
CONTMACROROLE Table
Column Name cont_macro_role_id Comment A unique ID to identify a party macro role in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. The role type code. The date when this role becomes effective. The date when this role become inactive. A free form description for this role. 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 TIMESTAMP TIMESTAMP VARCHAR(255) BIGINT
NOT NULL
No
role_tp_cd start_dt end_dt description end_reason_tp_cd
NOT NULL NOT NULL NULL NULL NULL
No No No No No
last_update_dt
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on.
NOT NULL
No
last_update_user
NULL
No
210
CONTRACT Table
Column Name contract_id Comment A unique, system generated key that identifies a contract in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
contr_lang_tp_cd
Identifies a spoken BIGINT 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.
NULL
No
currency_tp_cd freq_mode_tp_cd
Identifies the currency of BIGINT the amount columns. Identifies the frequency of the payments made on the contract. Some examples are monthly, annual, and others. An identifier that uniquely separates one billing type from another. Examples include Regular, Direct, Payroll deduction, and others. The premium payment due at the intervals identified by the frequency mode type code. The date of the next bill for the contract. The cash value of the contract. BIGINT
NULL NULL
No No
bill_tp_cd
BIGINT
NULL
No
premium_amt
DECIMAL(17,3)
NULL
No
next_bill_dt curr_cash_val_amt
TIMESTAMP DECIMAL(17,3)
NULL NULL
No No
Chapter 2. Tables
211
Licensed Materials Property of IBM Column Name line_of_business Comment Datatype Null Option NULL Is PK No
Represents a high-level VARCHAR(30) product grouping (Life, Annuity, Disability, Auto & Home, and others.) The title of the subsidiary that sold this contract. The organization that services the contract. VARCHAR(30)
brand_name
NULL
No
service_org_name bus_orgunit_id
VARCHAR(70)
NULL NULL
No No
The lowest level of VARCHAR(30) identification within the servicing organization of this contract. The unique identifier that identifies the servicing agent or broker, and others. that services this contract. 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(30)
service_prov_id
NULL
No
access_token_value
VARCHAR(50)
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
212
Licensed Materials Property of IBM Column Name repl_by_contract Comment A unique, system generated key that identifies a contract in the InfoSphere MDM Server system, that is replacing this particular contract. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Describes the location where the contract was issued. Uniquely identifies the administrative source system for a contract. Examples include Ingenium, Alltel, Huon, and others. Datatype BIGINT Null Option NULL Is PK No
last_update_tx_id
BIGINT
NULL
No
issue_location
VARCHAR(30)
NULL
No
admin_sys_tp_cd
BIGINT
NULL
No
admin_contract_id
The actual text or VARCHAR(150) number that is used in the administrative source system to identify a contract. The currency type for the premium amount. The currency type for the current cash value amount. DECIMAL(17,3) DECIMAL(17,3)
NULL
No
premamt_cur_tp cashval_cur_tp
NULL NULL
No No
managed_account_ind
Indicates whether or not CHAR(1) 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. The name of the contract. The alternate name of the contract. The date on which the contract is signed. The date on which the contract becomes active. VARCHAR(120) VARCHAR(120) TIMESTAMP TIMESTAMP
NULL
No
agreement_name agreement_nickname signed_dt executed_dt
NULL NULL NULL NULL
No No No No
Chapter 2. Tables
213
Licensed Materials Property of IBM Column Name end_dt Comment The date on which the contract is considered ended. The identifier of the contract that this contract replaces (if applicable). The date on which a transaction was last executed against this contract. The date on which the contract is terminated. Datatype TIMESTAMP Null Option NULL Is PK No
replaces_contract
BIGINT
NULL
No
account_last_transaction_dt
TIMESTAMP
NULL
No
termination_dt termination_reason_tp_cd agreement_description agreement_st_tp_cd agreement_tp_cd service_level_tp_cd
TIMESTAMP
NULL NULL NULL NULL NULL NULL
No No No No No No
The reason for which the BIGINT contract is terminated. The description of the contract. The status of the contract. The type of the contract. The service level provided for this contract. For example: 24/7 Call Center service or Service during business hours only. The date on which the contract was last verified. The date on which the contract was last reviewed. VARCHAR(250) BIGINT BIGINT BIGINT
last_verified_dt
TIMESTAMP
NULL
No
last_reviewed_dt
TIMESTAMP
NULL
No
product_id
The Product identifier on BIGINT which the contract is based. 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
cluster_key
NULL
No
214
CONTRACTCOMPONENT Table
Column Name contr_component_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a contract component in the InfoSphere MDM Server system. Identifies the status of BIGINT the contract. For example: active, pending, lapse pending, or cancelled. These values are provided by the administrative source systems of the contract. Identifies the type of BIGINT product associated with the contract (or at some level within the product family). Examples include Universal Life, Savings, Checking, Term Life, Auto, and others. The cash value of the contract component. The premium payment due at the intervals identified by the frequency mode type code for this contract component. DECIMAL(17,3) DECIMAL(17,3)
contract_st_tp_cd
NOT NULL
No
prod_tp_cd
NULL
No
curr_cash_val_amt premium_amt
NULL NULL
No No
issue_dt
The date which the TIMESTAMP contract component was issued.
NULL
No
Chapter 2. Tables
215
Licensed Materials Property of IBM Column Name viatical_ind Comment Datatype Null Option NULL Is PK No
Determines whether this CHAR(1) 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.
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
last_update_dt
NOT NULL
No
last_update_user
NULL
No
216
Licensed Materials Property of IBM Column Name contr_comp_tp_cd Comment A numeric representation of the type of coverage for the product. For example: v Base v Rider v Base Increase v Integrated 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 Datatype BIGINT Null Option NULL Is PK No
serv_arrange_tp_cd
Indicates whether this BIGINT contract is administered by the organization or a third party. A unique, system generated key that identifies a contract in the InfoSphere MDM Server system. The primary key of a party holding record. The date that the type code is no longer valid. The currency type for the premium amount. The currency type for the current cash value amount. BIGINT
NULL
No
contract_id
NOT NULL
No
holding_id expiry_dt premamt_cur_tp cashval_cur_tp
BIGINT TIMESTAMP BIGINT BIGINT
NULL NULL NULL NULL
No No No No
cluster_key
This column can BIGINT 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.
NULL
No
Chapter 2. Tables
217
CONTRACTCOMPVAL Table
Column Name contr_comp_val_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a contract component value in the InfoSphere MDM Server system. Domain Value Type Code, in a given domain, identifies the specific values that are captured. For example: Integer value, Date value, etc. The numeric value associated with the Value Type Code. BIGINT
domain_value_tp_cd
NOT NULL
No
value_string
VARCHAR(50)
NOT NULL
No
contr_component_id
A unique, system BIGINT generated key that identifies a contract component in the InfoSphere MDM Server system. The date that this row of data became valid. The date that this row of data became invalid. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. TIMESTAMP TIMESTAMP BIGINT
NOT NULL
No
start_dt end_dt last_update_tx_id
NOT NULL NULL NULL
No No No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
218
CONTRACTREL Table
Column Name contract_rel_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a contract relationship in the InfoSphere MDM Server system. Describes the type of relationship. Examples include master contract and contract term. BIGINT
contr_rel_tp_cd
NOT NULL
No
contr_rel_st_tp_cd
Identifies the status of BIGINT the relationship between two contracts, such as pending, active, and terminated. A unique, system generated key that identifies a contract in the InfoSphere MDM Server system. A unique, system generated key that identifies a contract in the InfoSphere MDM Server system. The date that this row of data became valid. The date that this row of data became invalid. Provides for comments that a user may have concerning the contract relationship. 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
from_contract_id
NOT NULL
No
to_contract_id
BIGINT
NOT NULL
No
start_dt end_dt rel_description
TIMESTAMP TIMESTAMP VARCHAR(255)
NOT NULL NULL NULL
No No No
last_update_tx_id
BIGINT
NULL
No
last_update_dt
NOT NULL
No
Chapter 2. Tables
219
CONTRACTROLE Table
Column Name contract_role_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a contract component in the InfoSphere MDM Server system. Identifies the type of role that a party may have on a contract. For example beneficiary, owner, insured, payer, and others. The party contract role name as it appears on the contract. BIGINT
cont_id
NOT NULL
No
contr_component_id
NOT NULL
No
contr_role_tp_cd
NOT NULL
No
registered_name
VARCHAR(255)
NULL
No
distrib_pct
Used for beneficiary DECIMAL(5,2) type, it indicates the share that this party has interest in regarding this contract component. Indicates whether this role can be changed without consent. The date that this row of data became valid. The date that this row of data became invalid. CHAR(1)
NULL
No
irrevoc_ind
NULL
No
start_dt end_dt
TIMESTAMP TIMESTAMP
NOT NULL NULL
No No
220
Licensed Materials Property of IBM Column Name recorded_start_dt Comment The date which the partys relationship to the contract became legally effective. This is commonly the date which the party signed the contract. Datatype TIMESTAMP Null Option NULL Is PK No
recorded_end_dt
The date that the partys TIMESTAMP relationship to the contract is no longer effective. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. The values and BIGINT descriptions defining how the proceeds of the contract are distributed among the party contract roles. The type of agreement that the party contract role has with the contract. For example: time delay arrangement such as a common disaster. BIGINT
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
share_dist_tp_cd
NULL
No
arrangement_tp_cd
NULL
No
arrangement_desc
Provides extra VARCHAR(255) information that can be used either as an additional definition of the arrangement or as free form comments used by the user to provide further meaning to the arrangement.
NULL
No
Chapter 2. Tables
221
Licensed Materials Property of IBM Column Name last_update_tx_id Comment A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Identifies the cause for why a role was ended. For example, a beneficiary relationship may be ended for a death reason. Datatype BIGINT Null Option NULL Is PK No
end_reason_tp_cd
BIGINT
NULL
No
CONTRACTROLEREL Table
Column Name contr_role_rel_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. Identifies the type of BIGINT relationship that two parties can have between one another, within the context of the contract. For example: is custodian of, is minor for, and others. Provides a space to VARCHAR(255) store user comments the party roles relationship. A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
rel_tp_cd
NOT NULL
No
role_rel_desc
NULL
No
contr_role_from_id
NOT NULL
No
contr_role_to_id
NOT NULL
No
start_dt end_dt
NOT NULL NULL
No No
222
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Identifies the cause for why a role relationship was ended. For example, a custodial relationship may be ended for a coming of age reason. BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
end_reason_tp_cd
BIGINT
NULL
No
CONTSUMMARY Table
Column Name cont_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Determines whether SMALLINT 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.
privpref_ind
NOT NULL
No
Chapter 2. Tables
223
Licensed Materials Property of IBM Column Name miscvalue_ind Comment 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. Datatype SMALLINT Null Option NOT NULL Is PK No
contactrel_ind
Indicates whether there SMALLINT is any party relationship on this party. This field is set by InfoSphere MDM Server when a party relationship is associated with the Party record. Indicates whether there SMALLINT is any party bank account on this party. This field is set by InfoSphere MDM Server when a party financial profile is associated with the Party record. Indicates whether there SMALLINT is any party charge card on this party. This field is set by InfoSphere MDM Server when a party financial profile is associated with the Party record. Indicates whether there SMALLINT is any party payroll deduction on this party. This field is set by InfoSphere MDM Server when a party financial profile is associated with the Party record. Indicates whether there SMALLINT is any party income source on this party. This field is set by InfoSphere MDM Server when a party financial profile is associated with the Party record. Indicates whether there is any party identifier on this party. This field is set by InfoSphere MDM Server when a party identifier is associated with the Party record. SMALLINT
NOT NULL
No
bankaccount_ind
NOT NULL
No
chargecard_ind
NOT NULL
No
payrolldeduct_ind
NOT NULL
No
incomesource_ind
NOT NULL
No
identifier_ind
NOT NULL
No
224
Licensed Materials Property of IBM Column Name alert_ind Comment Datatype Null Option NOT NULL Is PK No
Indicates whether there SMALLINT is any kind of alert or restriction on this party. This field is set by InfoSphere MDM Server when an active alert is associated with the Party record. Indicates whether there SMALLINT is any contact equivalent on this party. This field is set by InfoSphere MDM Server when a contact equivalent is associated with the Party record. Is there any party interaction on this party? This field is set by InfoSphere MDM Server when a party interaction is associated with the Party record. SMALLINT
contequiv_ind
NOT NULL
No
interaction_ind
NOT NULL
No
addressgroup_ind
Indicates whether there SMALLINT is any party address group on this party. This field is set by InfoSphere MDM Server when a party address group is associated with the Party record. Indicates whether there SMALLINT is any contact method group on this party. This field is set by InfoSphere MDM Server when a contact method group is associated with the Party record. Indicates whether there SMALLINT 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.
NOT NULL
No
contmethgroup_ind
NOT NULL
No
lobrel_ind
NOT NULL
No
Chapter 2. Tables
225
When a record is added TIMESTAMP 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. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_tx_id
NULL
No
last_update_user
NULL
No
DEFAULTSOURCEVAL Table
Column Name default_src_val_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies an default object row in the InfoSphere MDM Server system. The name of the business entity that has the defaulted values. VARCHAR(20)
entity_name
NOT NULL
No
instance_pk
The actual primary key BIGINT of the row in the logical entity that has the defaulted values. The actual name of the column where the default occurred. VARCHAR(20)
NULL
No
column_name
NOT NULL
No
226
Licensed Materials Property of IBM Column Name source_value Comment Datatype Null Option NULL Is PK No
The value of the Logical VARCHAR(100) Column Name prior to defaulted to the InfoSphere MDM Server database column value. For example: established date - Jan 31, 2002 Source Value is: Jan 2002. The value of the Logical VARCHAR(100) Column Name after it is defaulted to the InfoSphere MDM Server database column value. For example: established date - Jan 2002. Default Value is: Jan 31, 2002. Provides extra VARCHAR(1000) information that can be used either as an additional definition of the record or as free form comments used by the user to provide further meaning to the record. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Identifies the type for the source identifier. Identifies the source of the value. BIGINT
default_value
NULL
No
description
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
source_ident_tp_cd source_identifier
BIGINT VARCHAR(100)
NULL NULL
No No
Chapter 2. Tables
227
ENTITYCONDITIONREL Table
Name Comment Datatype BIGINT Null Option NOT NULL NOT NULL Is PK Yes
entity_condition_rel_id The primary key for the Entity Condition Relationship record. instance_pk
The Primary key of the BIGINT entity to which the Term Condition is related. It can be the primary key of either PRODUCT or CONTRACT. Type of the Entity the condition is related to. It can be either PRODUCT or CONTRACT. The identifier of the term condition attached to the Entity. The Start date from when this relationship is valid The End date till when this relationship is valid
No
entity_name
VARCHAR(120) NOT NULL
No
condition_id
BIGINT
NOT NULL NOT NULL NULL NOT NULL
No
start_dt end_dt last_update_dt
TIMESTAMP TIMESTAMP
No No No
Whenever a record is TIMESTAMP 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. Transaction ID is a BIGINT unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. 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)
last_update_tx_id
NULL
No
last_update_user
NULL
No
228
ENTITYCONTENTREFERENCE Table
Name content_ref_id Comment A unique, system generated key that identifies a Content Reference in the InfoSphere MDM Server system Parameter defined in the CMS system to identify the Content Reference. Parameter defined in the CMS system to identify the Content Reference. Parameter defined in the CMS system to identify the Content Reference. Parameter defined in the CMS system to identify the Content Reference. Datatype BIGINT Null Option Is PK NOT NULL Yes
content_ref_1
VARCHAR(250)
NULL
No
content_ref_2
VARCHAR(250)
NULL
No
content_ref_3
VARCHAR(250)
NULL
No
content_ref_4
VARCHAR(250)
NULL
No
instance_pk
The actual primary key of BIGINT the row in the logical entity that is associated with the content reference. The name of the business entity. The version of the content reference in the CMS system. The Start Date is the first date that the record is effective. The End Date is the date from which the record is no longer effective. Identifies the Repository within the CMS System. VARCHAR(250) VARCHAR(250)
NULL
No
entity_name content_version
NULL NULL
No No
start_date
TIMESTAMP
NOT NULL
No
end_date
TIMESTAMP
NULL
No
repository_tp_cd last_update_dt
BIGINT
NULL NOT NULL
No No
When a record is added or TIMESTAMP 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.
Chapter 2. Tables
229
Licensed Materials Property of IBM Name last_update_tx_id Comment Datatype Null Option Is PK NULL No
Transaction ID is a unique, BIGINT system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Id of user who last VARCHAR(20) updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on.
last_update_user
NULL
No
ENTITYROLE Table
Column Name entity_role_id Comment A unique ID to identify an entity role in the system. The role type code. The name of the entity that a role is being provided for. The primary key of the entity. The entity name of the role player. The primary key of the role player. The date when this role becomes effective. The date when this role becomes inactive. A freeform description for this role. The reason why a relationship ended. For example, a spousal party-to-party relationship may be ended by a divorce reason. Datatype BIGINT Null Option NOT NULL Is PK Yes
role_tp_cd contxt_entity_name
BIGINT VARCHAR(30)
NOT NULL NOT NULL
No No
contxt_instance_pk role_entity_name role_instance_pk start_dt end_dt description end_reason_tp_cd
BIGINT VARCHAR(30) BIGINT TIMESTAMP TIMESTAMP VARCHAR(255)` BIGINT
NOT NULL NULL NULL NOT NULL NULL NULL NULL
No No No No No No No
230
When a record is added TIMESTAMP 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. 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. A unique, system generated key that identifies the specific transaction within the log system that either created, updated, or deleted the data row. VARCHAR(20)
last_update_user
NULL
No
last_update_tx_id
BIGINT
NULL
No
ENTITYSPECUSE Table
Name spec_use_id Comment A system generated key that uniquely identifies the usage of a spec with an entity within the system. The type of entity this spec use is related to. The primary key of the related entity. A system generated key that uniquely identifies a spec within the system. The code assigned to the spec use type. The code assigned to the cascade action type for a spec. For example, if this spec is cascaded to descendents in the entitys hierarchy. Indicates that the spec has been defined for the first time on this entity. Datatype BIGINT Null Option NOT NULL Is PK Yes
entity_name instance_pk spec_id
VARCHAR(250) BIGINT BIGINT
No No No
spec_use_tp_cd spec_cascade_tp_cd
BIGINT BIGINT
NOT NULL NOT NULL
No No
explicit_def_ind
CHAR(1)
NOT NULL
No
Chapter 2. Tables
231
Licensed Materials Property of IBM Name metadata_info_tp_cd start_dt end_dt last_update_dt Comment The code assigned to the metadata info type. Specifies the date when this record in takes effect. Specifies the date when this record becomes inactive Datatype BIGINT TIMESTAMP TIMESTAMP Null Option NOT NULL NOT NULL NULL NOT NULL Is PK No No No No
When a record is added or TIMESTAMP 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. 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. 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. The destination entity this spec use is related to. VARCHAR(20)
last_update_user
NULL
No
last_update_tx_id
BIGINT
NULL
No
destination_entity_name
VARCHAR(250)
NULL
No
ENUMANSWER Table
Name enum_ans_id Datatype BIGINT Null Option NOT NULL Comment The primary key of the Enumanswer record Is PK Yes
question_id
BIGINT
NOT NULL
Identifies the question No that this enum answer belongs to. Answer sequence number. Enum answer type code No No
answer_sequence enum_ans_tp_cd
INTEGER BIGINT
NULL NOT NULL
232
Licensed Materials Property of IBM Name last_update_dt Datatype TIMESTAMP Null Option NOT NULL Comment Is PK
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
FINANCIALPRODUCT Table
Name product_id Comment A system generated key that uniquely identifies a product within the system. Datatype BIGINT Null Option NOT NULL Is PK Yes
tax_position_tp_cd
The relative tax position BIGINT offered by the product. Determines whether the product is tax neutral, provides the customer a tax advantage, or provides the FI with a tax advantage.
NULL
No
Chapter 2. Tables
233
Licensed Materials Property of IBM Name account_required_tp_cd Comment Indicates whether the product requires an account or not. Datatype BIGINT Null Option NULL Is PK No
currency_tp_cd last_update_dt
Identifies the currency BIGINT the product is traded in. 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 on this field; if it does not, the update fails. TIMESTAMP
NULL NOT NULL
No No
last_update_user
NULL
No
last_update_tx_id
NULL
No
GOODSPRODUCT Table
Name product_id Comment Datatype Null Option Is PK
A system generated key BIGINT that uniquely identifies a product within the system. When a record is added or TIMESTAMP 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.
NOT NULL Yes
last_update_dt
NOT NULL No
234
Licensed Materials Property of IBM Null Option NULL
Name last_update_user
Comment
Datatype
Is PK No
Id of user who last VARCHAR(20) updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on. Transaction ID is a unique, BIGINT system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
last_update_tx_id
NULL
No
GROUPING Table
Column Name grouping_id name Comment Primary key Value of a Group A short, meaningful label. For example Platinum Group for Credit Cards. Datatype BIGINT VARCHAR(30) Null Option NOT NULL NOT NULL Is PK Yes No
grouping_tp_cd
Identifies the code type BIGINT of a Group, or classification associating a number of like entities, such as parties. The name of the business entity that has the defaulted values. The target entity for the group such contact. VARCHAR(20)
NOT NULL
No
entity_name
NOT NULL
No
description
Provides extra VARCHAR(255) 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. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
NULL
No
start_dt end_dt
NOT NULL NULL
No No
Chapter 2. Tables
235
The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. When a record is added TIMESTAMP 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. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_dt
NOT NULL
No
last_update_tx_id
NULL
No
GROUPINGASSOC Table
Column Name grouping_assoc_id Comment The primary key for each group member record Datatype BIGINT Null Option NOT NULL Is PK Yes
instance_pk
The actual primary key BIGINT of the row in the logical entity that is being associated to the group. The primary key Value of a group. BIGINT
NULL
No
grouping_id description
NOT NULL NULL
No No
Provides extra VARCHAR(255) information that can be used either as an additional definition of the record or as free form comments used by the user to provide further meaning to the record. The date that this row of data comes into effect. TIMESTAMP
effect_start_dt
NOT NULL
No
236
Licensed Materials Property of IBM Column Name effect_end_dt Comment The date that this row of data become ineffective Datatype TIMESTAMP Null Option NULL Is PK No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
HIERARCHY Table
Column Name hierarchy_id name description Comment The primary key of the hierarchy record. A short, meaningful label. Datatype BIGINT VARCHAR(30) Null Option NOT NULL NOT NULL NULL Is PK Yes No No
Provides extra VARCHAR(255) 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. The date when this record in takes effect. The date when this record becomes inactive TIMESTAMP TIMESTAMP
start_dt end_dt
NOT NULL NULL
No No
Chapter 2. Tables
237
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Identifies the code type of a hierarchy. BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
hierarchy_tp_cd
BIGINT
NULL
No
HIERARCHYNODE Table
Column Name hierarchy_node_id hierarchy_id entity_name Comment The primary key of the hierarchy node record The primary key of the hierarchy record The name of the physical business entity which is part of this relationship. Datatype BIGINT BIGINT VARCHAR(20) Null Option NOT NULL NOT NULL NOT NULL Is PK Yes No No
instance_Pk
The actual primary key BIGINT of the row in the logical entity which is part of this relationship. Provides extra VARCHAR(255) 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.
NOT NULL
No
description
NULL
No
238
Licensed Materials Property of IBM Column Name start_dt end_dt last_update_dt Comment The date when this record in takes effect. Datatype TIMESTAMP Null Option NOT NULL NULL NOT NULL Is PK No No No
The date when this TIMESTAMP record becomes inactive. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
nodedesig_tp_cd
Identifies the node BIGINT designate code type of a hierarchy. A description of the locale. VARCHAR(255)
NULL
No
localedescription
NULL
No
HIERARCHYREL Table
Column Name hierarchy_rel_id Comment The primary key of the hierarchy relationship record. The primary key of the parent hierarchy node record. The primary key of the child hierarchy node record. Datatype BIGINT Null Option NOT NULL Is PK Yes
parent_node_id
BIGINT
NOT NULL
No
child_node_id
BIGINT
NOT NULL
No
Chapter 2. Tables
239
NOT NULL NULL NOT NULL
No No No
last_update_user
NULL
No
last_update_tx_id
NULL
No
HIERARCHYULTPAR Table
Column Name hier_ult_par_id Comment The primary key of the hierarchy ultimate parent record. The primary key of the hierarchy node record. Datatype BIGINT Null Option NOT NULL Is PK Yes
hierarchy_node_id
BIGINT
NOT NULL
No
240
No No No
last_update_user
NULL
No
last_update_tx_id
NULL
No
HOLDING Table
Column Name holding_id hold_tp_cd Comment Primary key of a party holding record. Identifies a type of party holding. Some examples include Vehicles, Property, and Stocks etc. Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Is PK Yes No
Chapter 2. Tables
241
Licensed Materials Property of IBM Column Name holding_code Comment Identify the holding code: V - vehicle P - property holding_value_amt description start_dt The value of the specific DECIMAL(17,3) holding. Provides extra information. The date that the holding record became effective, or was recorded. The date that the holding record is no longer effective VARCHAR(255) TIMESTAMP NULL NULL NOT NULL No No No Datatype CHAR(1) Null Option NOT NULL Is PK No
end_dt
TIMESTAMP
NULL
No
last_update_dt
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. The currency type for the holding value amount. BIGINT
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
valuamt_cur_tp
BIGINT
NULL
No
242
IDENTIFIER Table
Column Name identifier_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party identification row in the InfoSphere MDM Server system. Identifies the status of the identifier provided by the party. For example: applied for, expired, certified, and others. BIGINT
id_status_tp_cd
NULL
No
cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Identifies the type of BIGINT identifier provided by the party. For example: social security number, passport, drivers license number, and others. The actual identifier text VARCHAR(50) 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. The date that this row of data became valid. The date that this row of data became invalid. The date on which the particular identification expires, such as a Passport expiry date. TIMESTAMP TIMESTAMP TIMESTAMP
NOT NULL
No
id_tp_cd
NOT NULL
No
ref_num
NULL
No
start_dt end_dt expiry_dt
NOT NULL NULL NULL
No No No
last_update_dt
NOT NULL
No
Chapter 2. Tables
243
last_update_tx_id
NULL
No
assigned_by
Used to associate a BIGINT particular contract role to a particular identifier. For example: an employee number may be used as an identifier on a group contract. Provides extra VARCHAR(255) information that can be used either as an additional definition of the particular identification or as free form comments used by the user to provide further meaning to the record. The issue location of the VARCHAR(30) identification item. The date that this data was last used. There is no business logic associated with this field. The date that this data was last verified. There is no business logic associated with this field. Identifies the type for the source identifier. TIMESTAMP
NULL
No
identifier_desc
NULL
No
issue_location last_used_dt
NULL NULL
No No
last_verified_dt
TIMESTAMP
NULL
No
source_ident_tp_cd
BIGINT
NULL
No
244
INACTIVATEDCONT Table
Column Name cont_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. A unique, system VARCHAR(20) generated key that identifies a party in the InfoSphere MDM Server system. Contains the valid BIGINT values for inactivating a party record, such as collapsed, split and deceased. A free form text field used for entering additional information concerning the inactivated party. VARCHAR(255)
inact_by_user
NULL
No
inact_reason_tp_cd
NOT NULL
No
comments
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
245
INACTIVECONTLINK Table
Column Name inact_cont_link_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies an inactivated party link row in the InfoSphere MDM Server system. Describes the reason why two parties are linked. For example: Source collapsed into target, Source duplicated as target, etc. BIGINT
link_reason_tp_cd
NOT NULL
No
target_cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
NOT NULL
No
source_cont_id
NOT NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
246
INCOMESOURCE Table
Column Name income_source_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies an income source row in the InfoSphere MDM Server system. Identifies the currency of the amount columns. BIGINT
currency_tp_cd cont_id
NULL NOT NULL
No No
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Identifies the type of income source that the party provided. For example: annual salary, estimated net worth, Ownership of Bonds, and others. Stores comments provided by the user concerning the income source provided by the party. BIGINT
income_src_tp_cd
NULL
No
income_source_desc
VARCHAR(255)
NULL
No
annual_amt
Annual Amount is used DECIMAL(17,3) when the Income Source Type Code requires an amount provided by the party. Investment Experience SMALLINT in Years is used when the Income Source Type Code requires a length of ownership in years to be provided by the party. The date that the TIMESTAMP information was obtained from the party. When a record is added TIMESTAMP 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.
NOT NULL
No
invest_exper_yrs
NULL
No
info_obtained_dt
NOT NULL
No
last_update_dt
NOT NULL
No
Chapter 2. Tables
247
last_update_tx_id
NULL
No
INSURANCEPRODUCT Table
Name product_id Comment Datatype Null Option Is PK NOT NULL Yes A system generated key BIGINT that uniquely identifies a product within the system. When a record is added TIMESTAMP or 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. 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.
last_update_dt
NOT NULL
No
last_update_user
VARCHAR(20) NULL
No
last_update_tx_id
Transaction ID is a BIGINT unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
NULL
No
248
INTERACTION Table
Column Name interaction_id Comment A unique, system generated key that identifies an interaction row in the InfoSphere MDM Server system. The identifier of the user of the InfoSphere MDM Server system and recorded the interaction Datatype BIGINT Null Option NOT NULL Is PK Yes
recorded_by_user
VARCHAR(255)
NULL
No
interact_pt_tp_cd
Identifies the media BIGINT through which the interaction was made possible. Some examples are telephone, email, mail, and others. The date and time that the interaction was recorded. TIMESTAMP
NOT NULL
No
recorded_dt
NOT NULL
No
subject_desc
A short, textual VARCHAR(100) description of the subject of the interaction with the customer. A free form text line that allows for additional comments to be added for the interaction. The party ID of the customer that is involved in the interaction. The date that the interaction occurred. VARCHAR(1000)
NOT NULL
No
note_desc
NULL
No
interact_party
VARCHAR(255)
NULL
No
interact_dt invalid_ind
TIMESTAMP
NOT NULL NULL
No No
Invalid indicator is used CHAR(1) to invalidate the interaction record, either due to error or miscommunication. This is used, rather than an end date. Interaction Status Type BIGINT Code describes the status of the interaction. Some examples are Awaiting reply, Returned, No answer
interact_st_tp_cd
NULL
No
Chapter 2. Tables
249
last_update_user
NULL
No
last_update_tx_id
NULL
No
interact_resp_tp entity_name
The type of response for BIGINT an interaction. Logical entity name of VARCHAR(20) the entity that the interaction is regarding. For example: CONTACT or CONTRACT The primary key of the entity that the interaction is regarding. BIGINT
NULL NULL
No No
instance_PK
NULL
No
interact_tp_cd
Identifies the type of BIGINT interaction with the customer. The Interaction SubType Code is dependent on the Interaction Category Code. Some example values are campaign, incorrect billing, and others.
NOT NULL
No
250
INTERACTIONREL Table
Column Name interact_rel_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies an interaction relationship row in the InfoSphere MDM Server system. A unique, system generated key that identifies an interaction row in the InfoSphere MDM Server system. A unique, system generated key that identifies an interaction row in the InfoSphere MDM Server system. Describes the types of relationships interactions can have with one another. For example: escalation, follow up, and others. BIGINT
from_interact_id
NOT NULL
No
to_interact_id
BIGINT
NOT NULL
No
interact_rel_tp_cd
BIGINT
NOT NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
251
LOBREL Table
Column Name lob_rel_id Comment A unique, system generated key that identifies a lob relationship with an entity in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
entity_name
Entity Name is the VARCHAR(20) name of the physical business entity that is part of this relationship. Entity Instance primary key is the actual primary key of the row in the logical entity that is part of this relationship. Identifies the unique type code for a specific line of business. Identifies the unique type code for a specific line of business relationship type. The date when this record in takes effect. BIGINT
NOT NULL
No
instance_Pk
NOT NULL
No
lob_tp_cd
BIGINT
NOT NULL
No
lob_rel_tp_cd
BIGINT
NOT NULL
No
TIMESTAMP
No No No
The date when this TIMESTAMP record becomes inactive. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on.
last_update_user
NULL
No
252
LOCATIONGROUP Table
Column Name location_group_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a location group row in the InfoSphere MDM Server system. Identifies the reason for not using a particular address. Some example values are returned mail, change in zip code, and others. BIGINT
undel_reason_tp_cd
NULL
No
cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Indicates that the party CHAR(1) is a member of the household, in this case a simplistic representation, as it is only used in conjunction with common addresses. Indicates that the Party prefers to use this particular location for correspondence. CHAR(1)
NOT NULL
No
member_ind
NULL
No
preferred_ind
NULL
No
solicit_ind
Determines whether this CHAR(1) party be solicited at this specific location group. Determines the type of the location group. The value A indicates an address and the values C indicates contact method. CHAR(1)
NULL
No
loc_group_tp_code
NOT NULL
No
Chapter 2. Tables
253
Licensed Materials Property of IBM Column Name effect_start_mmdd Comment Datatype Null Option NULL Is PK No
The two digit month SMALLINT 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. The two digit month SMALLINT 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. The time of day when a INTEGER party is available at this location group. The time of day when a INTEGER party is no longer available at this location group. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
effect_end_mmdd
NULL
No
effect_start_tm
NULL
No
effect_end_tm
NULL
No
No No No
last_update_user
NULL
No
254
Licensed Materials Property of IBM Column Name last_update_tx_id Comment A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. The date that this data was last used. There is no business logic associated with this field. The date that this data was last verified. There is no business logic associated with this field. Identifies the type for the source identifier. Datatype BIGINT Null Option NULL Is PK No
last_used_dt
TIMESTAMP
NULL
No
last_verified_dt
TIMESTAMP
NULL
No
source_ident_tp_cd
BIGINT
NULL
No
MACROROLEASSOC Table
Column Name macrorole_assoc_id Comment A unique ID to represent the party macro role association in the system. A unique ID to identify a party macro role in the system. Datatype BIGINT Null Option NOT NULL Is PK Yes
cont_macro_role_id
BIGINT
NOT NULL
No
entity_name
The name of the entity VARCHAR(30) 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. The ID of the entity that BIGINT is being associated with the party macro role. This will be the ID of the entity representing party child data. The date when this association becomes active. The date when this association becomes inactive. TIMESTAMP
NOT NULL
No
instance_pk
NULL
No
start_dt
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
Chapter 2. Tables
255
Licensed Materials Property of IBM Column Name end_reason_tp_cd Comment Identifies the cause for why a relationship was ended. For example, a spousal party to party relationship may be ended for a divorce, reason. Datatype BIGINT Null Option NULL Is PK No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
MISCVALUE Table
Column Name miscvalue_Id instance_pk Comment The primary key of Miscellaneous Value. Datatype BIGINT Null Option NOT NULL NOT NULL Is PK Yes No
The actual primary key BIGINT of the row in the logical entity that has the value. The name of the business entity that has the value. For example: contact. VARCHAR(20)
entity_name
NOT NULL
No
256
Licensed Materials Property of IBM Column Name miscvalue_tp_cd Comment Datatype Null Option NOT NULL Is PK No
This is the misc. value BIGINT type that corresponds to a particular misc. value category. Some examples of miscvalue type are number of employees, gold value, credit card risk score, and others. The value content. For example, for a credit risk score record 8. Identifies the priority of a task, a campaign, value and others. Examples include high, medium, low. Identifies the type for the source identifier. Provides extra information. The date that this row of data became valid. The date that this row of data became invalid. VARCHAR(150)
value_string
NULL
No
priority_tp_cd
BIGINT
NULL
No
source_ident_tp_cd description start_dt end_dt last_update_dt
BIGINT VARCHAR(255) TIMESTAMP TIMESTAMP
NULL NULL NOT NULL NULL NOT NULL
No No No No No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
257
Licensed Materials Property of IBM Column Name valueattr_tp_cd_0 Comment Datatype Null Option NULL Is PK No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of the value attribute types are number of employees, gold value, credit card risk score, status, effective date, number of products and others. The Attribute Value field. VARCHAR(150)
attr0_value valueattr_tp_cd_1
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of the value attribute types are number of employees, gold value, credit card risk score, status, effective date, number of products and others. The Attribute Value field. VARCHAR(150)
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of the value attribute type are number of employees, gold value, credit card risk score, customer loyalty, status, credited date and others. The Attribute Value field. VARCHAR(150)
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of value attribute type are number of employees, gold value, credit card risk score, status, customer loyalty and others. The Attribute Value field. VARCHAR(150)
attr3_value
NULL
No
258
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of value attribute type are number of employees, gold value, credit card risk score, status, number of products, customer and others. The Attribute Value field. VARCHAR(150)
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of miscvalue type are number of employees, gold value, credit card risk score, status, customer loyalty, created date and others. The Attribute Value field. VARCHAR(150)
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of value attribute types are number of employees, gold value, credit card risk score, status, created date, customer loyalty and others. The Attribute Value field. VARCHAR(150)
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of value attribute type are number of employees, gold value, credit card risk score, status, effective date, customer loyalty and others. The Attribute Value field. VARCHAR(150)
attr7_value
NULL
No
Chapter 2. Tables
259
The value attribute type BIGINT that corresponds to a particular misc. value type. Some examples of value attribute type are number of employees, gold value, credit card risk score, status, created date, customer loyalty and others. The Attribute Value field. VARCHAR(150)
NULL NULL
No No
The value attribute type BIGINT that corresponds to a particular misc. value type . Some examples of value attribute type are number of employees, gold value, credit card risk score, status, created date, customer loyalty and others. The Attribute Value field. VARCHAR(150)
attr9_value
NULL
No
NATIVEKEY Table
Column Name native_key_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a contract native key row in the InfoSphere MDM Server system. The actual text or number that is used in the administrative source system to identify a contract. VARCHAR(150)
admin_contract_id
NULL
No
contract_id
A unique, system BIGINT generated key that identifies a contract component in the InfoSphere MDM Server system. Identifies the field name BIGINT that the native key refers to, for example, policy number, policy suffix, account number, branch, and others.
NOT NULL
No
admin_fld_nm_tp_cd
NULL
No
260
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. 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). BIGINT
last_update_user
NULL
No
last_update_tx_id
NULL
No
contract_comp_ind
CHAR(1)
NULL
No
NLSENUMANSWER Table
Name nlsenum_ans_id lang_tp_cd Comment Datatype Null Option NOT NULL NOT NULL Is PK Yes Yes The primary key of the BIGINT NLSEnumanswer record Language type code, BIGINT primary key of NLSEnumanswer record Identifies the question that this enumerated answer belongs to. Possible answer text. BIGINT
question_id
NOT NULL
No
answer
VARCHAR(120)
NOT NULL
No
Chapter 2. Tables
261
Description provides VARCHAR(255) extra information, which can be used either as an additional definition or as free form comments used by the user to provide further meaning. Last Update Date is TIMESTAMP used for technical reasons; whenever a record is updated, this field is updated with 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 hasnt 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. Id of user who last VARCHAR(20) updated the data. Either user ID or user group must be passed in the XML header, if security or ROV is turned on. 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
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
NLSQUESTION Table
Name nlsquestion_id lang_tp_cd Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Comment Is PK The primary key of Yes the nlsquestion record Language type, primary key of the NLSQuestion record. Questionnaire id that this question belongs to. Yes
quesnr_id
BIGINT
NOT NULL
No
262
Licensed Materials Property of IBM Name question description Datatype VARCHAR(255) VARCHAR(255) Null Option NOT NULL NULL Comment Question text Description provides extra information, which can be used either as an additional definition or as free form comments used by the user to provide further meaning. Is PK No No
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
NLSQUESTIONNAIRE Table
Name lang_tp_cd Datatype BIGINT Null Option NOT NULL Comment Is PK Language type code, Yes The primary key of the NLSQuestionnaire record.
Chapter 2. Tables
263
Licensed Materials Property of IBM Name nlsquesnr_id Datatype BIGINT Null Option NOT NULL Comment The Primary Key of the nlsquestionnaire record Name is a short, meaningful label. Description provides extra information, which can be used either as an additional definition or as free form comments used by the user to provide further meaning. Is PK Yes
name description
NOT NULL NULL
No No
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
264
ORG Table
Column Name cont_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Identifies the BIGINT classification of the organization. For example: trust, company, charity, estate, etc. The industry type for the organization. For example: SIC. BIGINT
org_tp_cd
NOT NULL
No
industry_tp_cd
NULL
No
established_dt
The date that the TIMESTAMP company or charity was established. For trusts, this is the inception date. An identifier that BIGINT uniquely separates one type of buy-sell agreement from another. Indicates whether the CHAR(1) organization has a Profit or Non-profit status. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. 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
buy_sell_agr_tp_cd
NULL
No
profit_ind
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
265
ORGNAME Table
Column Name org_name_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a organization name row in the InfoSphere MDM Server system. Identifies the type of name for this organization. For example: Legal, Doing Business As, Abbreviated, and others. BIGINT
org_name_tp_cd
NOT NULL
No
cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. 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. A standardized spelling of the organizations name that is used for searching. The phonetic key for Organization Name. Not currently used. The date that this row of data became valid. The date that this row of data became invalid. VARCHAR(255)
NOT NULL
No
org_name
NOT NULL
No
s_org_name
VARCHAR(255)
NULL
No
p_org_name name_search_key start_dt end_dt last_update_dt
VARCHAR(20) VARCHAR(30) TIMESTAMP TIMESTAMP
NULL NULL NOT NULL NULL NOT NULL
No No No No No
266
The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. The date that this data was last used. There is no business logic associated with this field. The date that this data was last verified. There is no business logic associated with this field. Identifies the type for the source identifier. BIGINT
last_update_tx_id
NULL
No
last_used_dt
TIMESTAMP
NULL
No
last_verified_dt
TIMESTAMP
NULL
No
source_ident_tp_cd
BIGINT
NULL
No
PAYMENTSOURCE Table
Column Name payment_source_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a payment source in the InfoSphere MDM Server system. Designates the type of payment source as follows: P - Payroll deduction C - Charge card B - Bank account start_dt The date that the payroll deduction or charge card or bank account record became effective, or was recorded. TIMESTAMP NOT NULL No CHAR(1)
payment_src_code
NOT NULL
No
Chapter 2. Tables
267
Licensed Materials Property of IBM Column Name end_dt Comment The date that the payroll deduction or charge card or bank account record is no longer effective Datatype TIMESTAMP Null Option NULL Is PK No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system.
NOT NULL
No
PAYROLLDEDUCTION Table
Column Name payment_source_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a payment source in the InfoSphere MDM Server system. The full name of the employer when using payroll deduction to pay for a contract or account. VARCHAR(255)
employer_name
NOT NULL
No
268
Licensed Materials Property of IBM Column Name payroll_no Comment The identifier assigned to uniquely identifies the employee when using payroll deduction to pay for a contract or account Datatype VARCHAR(50) Null Option NOT NULL Is PK No
description
Extra information that VARCHAR(255) can be used either as an additional definition of the payroll deduction or as free form comments used by the user to provide further meaning to the payroll deduction. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. 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_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
PERSON Table
Column Name cont_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. The marital status of a person. For example: single, widowed, divorced, and others. BIGINT
marital_st_tp_cd
NULL
No
Chapter 2. Tables
269
Licensed Materials Property of IBM Column Name birthplace_tp_cd Comment A Country Type Code identifying the country of birth. The country where an individual is a citizen. The level of schooling that this person has received. Examples include high school, college, university, and others. An identifier that uniquely separates one type of document being used to verify a clients age from another. Examples include birth certificate, drivers license, and others. Identifies the sex of a Person. The date of birth of the person. Datatype BIGINT Null Option NULL Is PK No
citizenship_tp_cd highest_edu_tp_cd
BIGINT BIGINT
NULL NULL
No No
age_ver_doc_tp_cd
BIGINT
NULL
No
gender_tp_code birth_dt deceased_dt children_ct
CHAR(1) TIMESTAMP
NULL NULL NULL NULL
No No No No
The date of death of the TIMESTAMP person. The total number of SMALLINT children that this person has. The date the person became disabled The date the person ceased being disabled. TIMESTAMP TIMESTAMP
disab_start_dt disab_end_dt user_ind
NULL NULL NULL
No No No
Indicates whether this a CHAR(1) person is a user of the InfoSphere MDM Server system. When a record is added TIMESTAMP 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.
last_update_dt
NOT NULL
No
270
last_update_tx_id
NULL
No
PERSONNAME Table
Column Name person_name_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a person name row in the InfoSphere MDM Server system. Identifies the partys name prefix. Examples include Mr., Mrs., Dr., and others. The actual prefix of name if the Prefix of Name Type Codes value is other. Identifies the type of name for this person. For example: Legal, Nick Name, Maiden Name, and others. The first given name (commonly known as a first name) of the person. The second given name (commonly known as a middle name) of the person. The third given name (commonly known as a middle name) of the person. The fourth given name (commonly known as a middle name) of the person. BIGINT
prefix_name_tp_cd
NULL
No
prefix_desc
VARCHAR(20)
NULL
No
name_usage_tp_cd
BIGINT
NOT NULL
No
given_name_one
VARCHAR(25)
NULL
No
given_name_two
VARCHAR(25)
NULL
No
given_name_three
VARCHAR(25)
NULL
No
given_name_four
VARCHAR(25)
NULL
No
Chapter 2. Tables
271
Licensed Materials Property of IBM Column Name last_name p_last_name p_given_name_one p_given_name_two p_given_name_three p_given_name_four generation_tp_cd Comment Identifies the last name of a person. The phonetic key for Last Name. The phonetic key for Given Name One. The phonetic key for Given Name Two. The phonetic key for Given Name Three. The phonetic key for Given Name Four. Identifies the partys name generation. Examples include the first, the second, and others.. Identifies the name suffix of a person. For example: Jr., MD, Esq, and others. The date that this row of data became valid. The date that this row of data became invalid. Datatype VARCHAR(30) VARCHAR(20) VARCHAR(20) VARCHAR(20) VARCHAR(20) VARCHAR(20) BIGINT Null Option NOT NULL NULL NULL NULL NULL NULL NULL Is PK No No No No No No No
suffix_desc
VARCHAR(20)
NULL
No
start_dt end_dt cont_id
TIMESTAMP TIMESTAMP
No No No
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. Determines whether the CHAR(1) standardized name is used for this party. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on.
use_standard_ind
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
272
Licensed Materials Property of IBM Column Name last_update_tx_id Comment A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. The date that this data was last used. There is no business logic associated with this field. The date that this data was last verified. There is no business logic associated with this field. Identifies the type for the source identifier. Datatype BIGINT Null Option NULL Is PK No
last_used_dt
TIMESTAMP
NULL
No
last_verified_dt
TIMESTAMP
NULL
No
source_ident_tp_cd
BIGINT
NULL
No
PERSONSEARCH Table
Column Name person_search_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a person search record in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a person name row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. The first given name VARCHAR(25) (commonly known as a first name) of the person. If standardization of the name has taken place, the standardized version of the name will be stored here.
person_name_id
NOT NULL
No
cont_id
NOT NULL
No
given_name_one
NULL
No
Chapter 2. Tables
273
Licensed Materials Property of IBM Column Name given_name_two Comment Datatype Null Option NULL Is PK No
The second given name VARCHAR(25) (commonly known as a middle name) of the person. If standardization of the name has taken place, the standardized version of the name will be stored here. The third given name VARCHAR(25) (commonly known as a middle name) of the person. If standardization of the name has taken place, the standardized version of the name will be stored here. The fourth given name VARCHAR(25) (commonly known as a middle name) of the person. If standardization of the name has taken place, the standardized version of the name will be stored here. The last name of a VARCHAR(30) person. If standardization of the name has taken place, the standardized version of the name will be stored here. The date that this row of data became invalid. TIMESTAMP
given_name_three
NULL
No
given_name_four
NULL
No
last_name
NOT NULL
No
end_dt last_update_dt
NULL NOT NULL
No No
last_update_user
NULL
No
274
PHONENUMBER Table
Name phone_number_id Datatype BIGINT Null Option NOT NULL Comment A unique, system generated key that identifies a phone number. Is PK Yes
country_code
VARCHAR(4)
NULL
The part of the phone No number that represents the country. The part of the phone No 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. The part of the phone No 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. The part of the phone No number that represents the local number. In North America, for example, it would be the 1234 portion of (905) 555-1234
area_code
VARCHAR(6)
NULL
exchange
VARCHAR(6)
NULL
ph_number
VARCHAR(20)
NULL
Chapter 2. Tables
275
Licensed Materials Property of IBM Name extension Datatype VARCHAR(8) Null Option NULL Comment Is PK
The part of the phone No 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. When a record is added or updated, this field is 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_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
The ID of user who No 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. A unique, system No generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Contact Method ID is No a unique, system generated key that identifies a contact method in the WCC system.
last_update_tx_id
BIGINT
NULL
contact_method_id
BIGINT
NOT NULL
PPREFACTIONOPT Table
Column Name ppref_act_opt_id Comment Datatype Null Option NOT NULL Is PK Yes The Privacy Preference BIGINT Action Option primary key. Identifies the action type subset available as options for a specific privacy preference type.
276
Licensed Materials Property of IBM Column Name ppref_tp_cd Comment Used to indicate the type of privacy preference being stored, for example: credit worthiness, personal info, and others. Datatype BIGINT Null Option NOT NULL Is PK No
ppref_action_tp_cd
Identifies the action to BIGINT be taken based on the privacy preference set by the customer or by company default setting. For example: Do not call, Do not mail.
NOT NULL
No
The date that this row of data became valid. The date that this row of data became invalid.
TIMESTAMP TIMESTAMP
No No No
last_update_user
NULL
No
last_update_tx_id
NULL
No
PPREFDEF Table
Column Name ppref_id ppref_seg_tp_cd Comment The Privacy Preference Record primary key. The segment associated with the privacy preference record. Datatype BIGINT BIGINT Null Option NOT NULL NULL Is PK Yes No
Chapter 2. Tables
277
Licensed Materials Property of IBM Column Name regulation_value Comment The privacy preference default regulation value which can be the name of the regulation. This is the indicator for the default privacy preference. Datatype VARCHAR(255) Null Option NULL Is PK No
default_ind
CHAR(1)
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
PPREFDEFREL Table
Column Name pprefdefrel_id Comment Identifies a relationship that two privacy preference records can have between one another. Datatype BIGINT Null Option NOT NULL Is PK Yes
parent_ppref_id
The primary key for the BIGINT parent of the relationship. The primary key for the BIGINT child of the relationship.
NOT NULL
No
child_ppref_Id
NOT NULL
No
278
Licensed Materials Property of IBM Column Name rel_desc Comment Datatype Null Option NULL Is PK No
Provides extra VARCHAR(255) information that can be used either as an additional definition of the relationship or as free form comments used by the user to provide further meaning of the relationship. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
No No No
last_update_user
NULL
No
last_update_txn_id
NULL
No
PPREFENTITY Table
Column Name ppref_id Comment A unique, system generated key that identifies a privacy preference object in InfoSphere MDM Server. The name of the business entity that has the privacy preference. Datatype BIGINT Null Option NOT NULL Is PK Yes
ppref_entity
VARCHAR(50)
NULL
No
Chapter 2. Tables
279
Licensed Materials Property of IBM Column Name ppref_instance_pk Comment Datatype Null Option NULL Is PK No
The actual primary key BIGINT of the row in the logical entity that has the privacy preference. Identifies the reason given by customer for making a privacy preference selection. BIGINT
ppref_reason_tp_cd
NOT NULL
No
last_update_dt
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Identifies the type for the source identifier. BIGINT
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
source_ident_tp_cd
BIGINT
NOT NULL
No
PPREFINSTANCE Table
Column Name ppref_inst_Id Comment Uniquely identifies an instance record associated with a privacy preference record. The Privacy Preference Record primary key. The name of the business entity that is associated with the privacy preference values. Datatype BIGINT Null Option NOT NULL Is PK Yes
ppref_id entity_name
BIGINT VARCHAR(20)
NOT NULL NOT NULL
No No
280
Licensed Materials Property of IBM Column Name instance_Pk Comment Datatype Null Option NULL Is PK No
The actual primary key BIGINT of the row in the logical entity that is associated with the privacy preference values. When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_dt
NOT NULL
No
Last_Update_User
NULL
No
last_Update_Tx_Id
NULL
No
PRIVPREF Table
Column Name ppref_id value_string Comment The Privacy Preference Record primary key. Datatype BIGINT Null Option NOT NULL NULL Is PK Yes No
Stores the actual VARCHAR(50) 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
start_dt end_dt
The date that this row of data became valid. The date that this row of data became invalid.
TIMESTAMP TIMESTAMP
NOT NULL NULL
No No
Chapter 2. Tables
281
last_update_user
NULL
No
last_update_tx_id
NULL
No
ppref_act_opt_id
The Privacy Preference BIGINT Action Option primary key. Identifies the action type subset available as options for a specific privacy preference type. Privacy Preference Type Code identifies the particular type of privacy/preference related to the entity. BIGINT
NULL
No
ppref_tp_cd
NOT NULL
No
PRODTPREL Table
Column Name prod_tp_rel_id Comment The Product Type Relationship record primary key. The type of relationship that two products can have between one another. For example: categorize. Datatype BIGINT Null Option NOT NULL Is PK Yes
rel_desc
VARCHAR(255)
NULL
No
282
Licensed Materials Property of IBM Column Name to_prod_tp_cd Comment Datatype Null Option NOT NULL Is PK No
The type of product BIGINT associated with the contract (or at some level within the product family). Examples include Universal Life, Savings, Checking, Term Life, Auto, and others. The type of product BIGINT associated with the contract (or at some level within the product family). Examples include Universal Life, Savings, Checking, Term Life, Auto, and others. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
from_prod_tp_cd
NOT NULL
No
No No No
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Identifies the type of relationship that two products can have between one another. For example: categorize. BIGINT
last_update_user
NULL
No
last_update_txn_id
NULL
No
prodrel_tp_cd
BIGINT
NOT NULL
No
Chapter 2. Tables
283
PRODUCT Table
Name product_id Comment A system generated key that uniquely identifies a product within the system. The identifier that describes what type of product this is. The name of the product. A short description of the product. A long description of the product. The basic structure of the product. Examples: Standalone, Bundle Etc The lifecycle status of the product. Datatype BIGINT Null Option NOT NULL Is PK Yes
product_type_id
BIGINT
NOT NULL
No
name short_description description prod_struc_tp_cd
VARCHAR(120) VARCHAR(255) VARCHAR(500) BIGINT
NOT NULL NULL NULL NOT NULL
No No No No
status_tp_cd status_reason_tp_cd availability_tp_cd
BIGINT
NULL NULL NULL
No No No
Why the product is in BIGINT its current lifecycle state. How widely available the product is to the target market. For example, general availability, restricted availability. A primary market this product targets. When a record is added or 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. BIGINT
primary_target_market_tp_cd last_update_dt
BIGINT TIMESTAMP
NULL NOT NULL
No No
last_update_user
NULL
No
284
Licensed Materials Property of IBM Name last_update_tx_id Comment 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. Datatype BIGINT Null Option NULL Is PK No
PRODUCTCATEGORYASSOC Table
Name product_category_assoc_id Comment A system generated key that uniquely identifies an association between a product and category within the system. The product that is associated to the category. Datatype BIGINT Null Option NOT NULL Is PK Yes
product_id
BIGINT
NOT NULL
No
category_id hierarchy_id start_dt end_dt last_update_dt
The category the BIGINT product is associated to. The hierarchy the category belongs to. BIGINT
NOT NULL NOT NULL NOT NULL NULL NOT NULL
No No No No No
The date the association TIMESTAMP is effective. The date the association TIMESTAMP is not longer effective. When a record is added or 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. TIMESTAMP
last_update_user
NULL
No
Chapter 2. Tables
285
Licensed Materials Property of IBM Name last_update_tx_id Comment 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. Datatype BIGINT Null Option NULL Is PK No
PRODUCTCONTRACTREL Table
Name prod_cont_rel_id Datatype BIGINT Null Option NOT NULL Comment The primary key of the Product Contract Relationship record. A system generated key that uniquely identifies a product within the system. Contract ID is a unique, system generated key that identifies a contract in the WCC system. The Start date from when this relationship is valid The End date till when this relationship is valid The type of the relationship between the product and the contract Is PK Yes
product_id
BIGINT
NOT NULL
No
contract_id
BIGINT
NOT NULL
No
start_dt
TIMESTAMP
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
prod_cont_rel_tp_cd
BIGINT
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
Whenever a record is No 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. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on.
last_update_tx_id
BIGINT
NULL
286
Licensed Materials Property of IBM Name last_update_user Datatype VARCHAR(20) Null Option NULL Comment Is PK
Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
PRODUCTEQUIV Table
Name product_equiv_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a product equivalence record within the system. The product these equivalencies are for. The external system. A representation of the full key concatenated and formatted. First part of the key. Second part of the key. Third part of the key. Fourth part of the key. Fifth part of the key. Is PK Yes
product_id admin_sys_tp_cd product_equiv_key
BIGINT BIGINT VARCHAR(160)
NOT NULL NOT NULL NULL
No No No
key_1 key_2 key_3 key_4 key_5 last_update_dt
VARCHAR(30) VARCHAR(30) VARCHAR(30) VARCHAR(30) VARCHAR(30) TIMESTAMP
NOT NULL NULL NULL NULL NULL NOT NULL
No No No No No
last_update_user
VARCHAR(20)
NULL
Chapter 2. Tables
287
Licensed Materials Property of IBM Name last_update_tx_id Datatype BIGINT Null Option NULL Comment Is PK
PRODUCTIDENTIFIER Table
Name product_identifier_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a product identifier within the system. The product the identifier belongs to. The code that describes the identifier. The identifier value. The date the identifier is effective. Is PK Yes
product_id
BIGINT
NOT NULL NOT NULL
No No
product_identifier_tp_cd BIGINT
ref_num start_dt end_dt
VARCHAR(50) TIMESTAMP TIMESTAMP
NULL NOT NULL NULL
No No
The date the No identifier is no longer effective. Whenever a record is No 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. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on.
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
288
PRODUCTNLS Table
Name product_nls_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a localized product within the system. The product these Product NLS belong to. Is PK Yes
product_id
BIGINT
NOT NULL
No
lang_tp_cd
BIGINT
NOT NULL
Identifies a spoken No language such as English, French, Spanish, German, etc. The localized name of No the product. A localized short description of the product. A localized long description of the product. No
name short_description
NOT NULL NULL
description
VARCHAR(500)
NULL
No
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
Chapter 2. Tables
289
PRODUCTREL Table
Name product_rel_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a relationship between two products within the system. Is PK Yes
from_prod_id to_prod_id product_rel_tp_cd start_dt
BIGINT BIGINT BIGINT TIMESTAMP
NOT NULL NOT NULL NOT NULL NOT NULL
The source product in No the relationship. The target product in the relationship. The type of relationship. The date the relationship becomes effective. The date the relationship is no longer effective. description of the product relationship. No No No
end_dt
TIMESTAMP
NULL
No
rel_desc last_update_dt
VARCHAR(255) TIMESTAMP
NULL NOT NULL
No
last_update_user
VARCHAR(20)
NULL
290
PRODUCTTYPE Table
Name product_type_id Datatype BIGINT Null Option NOT NULL Comment A type of product that (unless is the root product type) is a subtype of another product type. The name of the product type. Is PK Yes
name description parent_prod_type_id metadata_info_tp_cd
VARCHAR(50) VARCHAR(255) BIGINT BIGINT
NOT NULL NULL NULL NOT NULL
No
The description of the No product type. The parent type for this type. The id of the meta-data package this spec belongs to Describes the level of the product type and is required to understand what is hardened in the database model or not. No No
node_tp_cd
BIGINT
NOT NULL
No
start_dt
TIMESTAMP
NOT NULL
When the type No becomes effective and can create products of that type. When the type is no No longer effective and can no longer create products of that type. Note that products of the type will continue to exist.
end_dt
TIMESTAMP
NULL
Chapter 2. Tables
291
Whenever a record is No 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. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on. Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
PRODUCTTYPENLS Table
Name product_type_nls_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a localized product type within the system. The product type these ProductTypeNLS belong to. Is PK Yes
product_type_id
BIGINT
NOT NULL
No
lang_tp_cd
BIGINT
NOT NULL
Identifies a spoken No language such as English, French, Spanish, German, etc.
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
292
Licensed Materials Property of IBM Name description Datatype VARCHAR(500) Null Option NULL Comment Is PK
The description of the No product type for a particular locale. Whenever a record is No 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. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on. Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row.
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
PRODUCTVAL Table
Name product_values_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a product value within the system. The spec that describes the definition of the values. The format (or version) of the spec these values validate to. The product these values belong to. Is PK Yes
spec_id
BIGINT
NOT NULL
No
spec_fmt_id
BIGINT
NOT NULL
No
product_id value_xml
BIGINT CLOB(1G)
NOT NULL NOT NULL
No
The values as defined No by the associated spec format.
Chapter 2. Tables
293
Licensed Materials Property of IBM Name start_dt end_dt Datatype TIMESTAMP TIMESTAMP Null Option NOT NULL NULL Comment The date the values become effective. The date the values are no longer effective. Is PK No No
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
PRODUCTVALNLS Table
Name product_values_nls_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a localized product value within the system. A system generated key that uniquely identifies a source product value within the system. Is PK Yes
product_values_id
BIGINT
NOT NULL
No
lang_tp_cd
BIGINT
NOT NULL
Identifies a spoken No language such as English, French, Spanish, German, etc. The values as defined No by the associated spec format.
value_xml
CLOB(1G)
NOT NULL
294
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
PROPERTY Table
Column Name holding_id address_id Comment The primary key of a party holding record. A unique, system generated key that identifies an address in the InfoSphere MDM Server system. Datatype BIGINT BIGINT Null Option NOT NULL NULL Is PK Yes No
last_update_dt
NOT NULL
No
Chapter 2. Tables
295
last_update_tx_id
NULL
No
QUESTION Table
Name question_id quesnr_id Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Comment The primary key of the question record. Identifies the questionnaire that this question belongs to. Question sequence number. Question type code. The expected answer type code. The answer mandatory indicator. The expected answer cardinality. The id of the parent question. Is PK Yes No
question_sequence question_tp_cd answer_data_tp_cd mandatory answer_cardinality parent_ques_id
INTEGER BIGINT INTEGER CHAR(1) SMALLINT BIGINT
NULL NOT NULL NOT NULL NOT NULL NOT NULL NULL
No No No No No No
296
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
QUESTIONNAIRE Table
Name quesnr_id Datatype BIGINT Null Option NOT NULL Comment The Primary Key of the questionnaire record Questionnaire type code. External reference number Specifies the date when this record is created Specifies the date when this record in takes effect. Is PK Yes
quesnr_tp_cd ref_num created_dt
BIGINT VARCHAR(50) TIMESTAMP
No No No
start_dt
TIMESTAMP
NULL
No
Chapter 2. Tables
297
Licensed Materials Property of IBM Name end_dt Datatype TIMESTAMP Null Option NULL Comment Specifies the date when this record becomes inactive Is PK No
last_update_dt
TIMESTAMP
NOT NULL
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
ROLEIDENTIFIER Table
Column Name role_identifier_id Comment A unique, system generated key that identifies a party contract role identifier row in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
298
Licensed Materials Property of IBM Column Name contract_role_id Comment Datatype Null Option NOT NULL Is PK No
A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party identification row in the InfoSphere MDM Server system. Provides extra VARCHAR(255) information that can be used either as an additional definition of the record or as free form comments used by the user to provide further meaning of the record. The date on which the particular role identification expires. TIMESTAMP
identifier_id
NOT NULL
No
description
NULL
No
expiry_dt
NULL
No
last_update_dt
NOT NULL
No
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
299
ROLELOCATION Table
Column Name role_location_id Comment A unique, system generated key that identifies a party contract role location row in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
location_group_id
A unique, system BIGINT generated key that identifies a location group row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
NOT NULL
No
contract_role_id
NOT NULL
No
No No No
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A reason for not using a BIGINT particular address. Some example values are returned mail, change in zip code, and others. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_user
NULL
No
undel_reason_tp_cd
NULL
No
last_update_tx_id
NULL
No
300
ROLELOCPURPOSE Table
Column Name role_loc_purp_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party contract role location reason row in the InfoSphere MDM Server system. The purpose for the BIGINT location as it relates to a role on a contract. For example, the owners residence address is associated with the contract for the purpose of sending statements Provides extra VARCHAR(255) 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. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
purpose_tp_cd
NOT NULL
No
description
NULL
No
No No No
last_update_user
NULL
No
Chapter 2. Tables
301
Licensed Materials Property of IBM Column Name last_update_tx_id Comment A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. A unique, system generated key that identifies a party contract role location row in the InfoSphere MDM Server system. Datatype BIGINT Null Option NULL Is PK No
role_location_id
BIGINT
NOT NULL
No
ROLESITUATION Table
Column Name role_situation_id Comment Datatype Null Option NOT NULL Is PK Yes A unique, system BIGINT generated key that identifies a party situation role row in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party contract role row in the InfoSphere MDM Server system. Describes the type of BIGINT agreement that the party contract role has with the contract. For example: time delay arrangement such as a common disaster. The date that this row of data became valid. The date that this row of data became invalid. TIMESTAMP TIMESTAMP
contract_role_id
NOT NULL
No
arrangement_tp_cd
NOT NULL
No
start_dt end_dt last_update_user
NOT NULL NULL NULL
No No No
302
When a record is added TIMESTAMP 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. A unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. BIGINT
last_update_tx_id
NULL
No
SEARCHXCLRULE Table
Column Name LAST_NAME Comment The last name value from Person Name or from Person Search. The last name phonetic key from Person Name. The given name one value from Person Name or from Person Search. The given name one phonetic key from Person Name. The city name value from Address. The city name phonetic key from Address. The number of times this exclusion rule combination occurred. Datatype VARCHAR(30) Null Option NOT NULL Is PK No
P_LAST_NAME GIVEN_NAME_ONE
NOT NULL NOT NULL
No No
P_GIVEN_NAME_ONE
VARCHAR(30)
NOT NULL
No
CITY_NAME P_CITY_NAME FREQUENCY
VARCHAR(30) VARCHAR(30) BIGINT
No No No
SERVICEPRODUCT Table
Name product_id Datatype BIGINT Null Option NOT NULL Comment A system generated key that uniquely identifies a product within the system. Is PK Yes
Chapter 2. Tables
303
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
SPEC Table
Name spec_id Datatype BIGINT Null Option NOT NULL Comment Is PK A unique, Yes system-generated key that identifies a spec in the MDM system The id of the meta-data package this spec belongs to. Name given to the spec Namespace this spec belongs to The spec format that is active for this spec The date on which this record becomes active. The date on which this record becomes inactive. No
metadata_info_tp_cd
BIGINT
NOT NULL
spec_name spec_namespace active_format_id
VARCHAR(100) VARCHAR(500) BIGINT
No No No
start_dt
TIMESTAMP
NOT NULL
No
end_dt
TIMESTAMP
NULL
No
304
Whenever a record is No 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. Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on.
last_update_tx_id
BIGINT
NULL
last_update_user
VARCHAR(20)
NULL
SPECFMT Table
Name spec_format_id Datatype BIGINT Null Option NOT NULL Comment Is PK A unique, Yes system-generated key that identifies a spec format in the MDM system. The id of the spec this format is applies to. Client XSD for this format Server XSD for this format It contains the localized xsd information for the mentioned spec format. The version number for this format. No
spec_id
BIGINT
NOT NULL
external_xsd internal_xsd localized_xsd
CLOB(1G) CLOB(1G) CLOB(1G)
NOT NULL NOT NULL NULL
No No No
format_version
BIGINT
NOT NULL
No
Chapter 2. Tables
305
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
SPECFORMATTRANSLATION Table
Name spec_format_translation_id Datatype BIGINT Null Option NOT NULL Comment A unique, system-generated key that identifies a spec format translation in the MDM system The id of the spec format the translation applies to Code for the translations locale language An XML document holding the translations of a given specs attributes for a given locale Is PK Yes
spec_format_id
BIGINT
NOT NULL
No
lang_tp_cd
BIGINT
NOT NULL
No
translation
CLOB(1073741824)
NOT NULL
No
306
Whenever a record No 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 on this field; if it does not, the update fails. 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. 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. No
last_update_user
VARCHAR(20)
NULL
last_update_tx_id
BIGINT
NULL
No
SUSPECT Table
Column Name suspect_id Comment A unique, system generated key that identifies a suspect row in the InfoSphere MDM Server system. Datatype BIGINT Null Option NOT NULL Is PK Yes
cont_id
A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system. A unique, system BIGINT generated key that identifies a party in the InfoSphere MDM Server system.
NOT NULL
No
suspect_cont_id
NOT NULL
No
Chapter 2. Tables
307
Licensed Materials Property of IBM Column Name susp_st_tp_cd Comment Datatype Null Option NOT NULL Is PK No
Indicates the current BIGINT situation for a particular suspect record - suspect duplicate, not duplicate, under investigation, and others. The source of the Suspect Reason Code (system marked or user marked). BIGINT
source_tp_cd
NOT NULL
No
susp_reason_tp_cd match_relev_tp_cd
The field that caused BIGINT the data match to occur. Identifies party match BIGINT relevancies, providing a description of which elements were matched. When a PARTY is CHAR(2) 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. Identifies the business reasons for the action code on the suspect identification being modified. Identifies the current suspect type. The current matching engine. Identifies the matching engine to use for matching parties. The calculated weight used by the matching engine. The ID of the user, system, or other entity that created the data. BIGINT
NULL NULL
No No
adj_action_code
NULL
No
adj_action_tp_cd
NULL
No
cur_suspect_tp_cd cur_mtch_eng_tp_cd match_eng_tp_cd
BIGINT BIGINT BIGINT
NULL NULL NULL
No No No
weight
DECIMAL(17,3)
NULL
No
created_by
VARCHAR(20)
NULL
No
308
last_update_user
NULL
No
last_update_tx_id
NULL
No
SUSPECTAUGMENT
Column Name SUSPECT_AUGMENT_ID Comment The unique Suspect Augmentation ID for this record. The Suspect ID associated with this record. The type code indicating the Adjust Action type. The type code indicating the Suspect type. The calculated weight for this suspect augmentation record. The type code indicating the matching engine to use for matching parties. Datatype BIGINT Null Option NOT NULL Is PK Yes
SUSPECT_ID
BIGINT
NOT NULL
No
ADJ_ACTION_TP_CD
BIGINT
NOT NULL
No
SUSPECT_TP_CD
BIGINT
NOT NULL
No
WEIGHT
DECIMAL(17,3)
NULL
No
MATCH_ENG_TP_CD
BIGINT
NOT NULL
No
Chapter 2. Tables
309
Licensed Materials Property of IBM Column Name LAST_UPDATE_DT Comment Datatype Null Option NOT NULL Is PK No
When a record is added TIMESTAMP 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. The ID of user who last VARCHAR(20) updated the data. Either the user ID or user group must be passed in the XML header if security or RoV is turned on. A unique, system generated key that identifies the specific transaction within the log system that either created, updated, or deleted the data row. BIGINT
LAST_UPDATE_USER
NULL
No
LAST_UPDATE_TX_ID
NULL
No
TERMCONDITION Table
Name condition_id condition_owner_tp_cd Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Comment The primary key of a condition record. 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 Is PK Yes No
BIGINT
NOT NULL
Identifies the usage type of the No condition describing the purpose of the condition. Value is from the code table CDCONDITIONUSAGETP. The name of this condition. The description for this condition. The start date from when a condition is valid. The date till when a condition is valid. No No No No
name description from_date to_date
VARCHAR(120) VARCHAR(3000) TIMESTAMP TIMESTAMP
NULL NULL NOT NULL NULL
310
Licensed Materials Property of IBM Name overrides_condition_id overridable_ind Datatype BIGINT CHAR(1) Null Option NULL NULL Comment The condition Id which is overridden by this Condition. A flag that indicates if the given condition can be overridden. A flag that indicates if this condition is mandatory Is PK No No
mandatory_ind parent_condition_id
CHAR(1) BIGINT
NULL NULL
No
The Term Condition that is the No parent of this condition. Used in hierarchical / nested term conditions Whenever a record is No 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. 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. 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. The column represents associated ruleId if different from the one set in CdConditionUsageTp No
last_update_dt
TIMESTAMP
NOT NULL
last_update_tx_id
BIGINT
NULL
last_update_user
VARCHAR(20)
NULL
No
override_rule_id
VARCHAR(10)
NULL
No
TERMCONDITIONNLS Table
Name condition_nls_id condition_id Datatype BIGINT BIGINT Null Option NOT NULL NOT NULL Comment The primary key of this table. Is PK Yes
The condition id of No the condition record for which localization data is added. The language code on No which data is localized. The localized value of No the name field of this condition.
Chapter 2. Tables
lang_tp_cd
BIGINT
NOT NULL
name
VARCHAR(120)
NULL
311
Licensed Materials Property of IBM Name description Datatype VARCHAR(3000) Null Option NULL Comment Is PK
The localized value of No the description field of this condition. Whenever a record is No 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. Transaction ID is a No unique, system generated key that identifies the specific transaction within the log system that either created, updated or deleted the data row. Id of user who last No updated the data. Either user ID or user group must be passed in the XML header, if security/RoV is turned on.
last_update_dt
TIMESTAMP
NOT NULL
last_update_tx_id
BIGINT
NULL
last_update_user
VARCHAR(20)
NULL
VEHICLE Table
Column Name holding_id vin_num Comment The primary key of a party holding record. The unique 17 digit vehicle identification number. The manufacturer name of the vehicle. The vehicle model as identified by the manufacturer. The vehicle year is the year the vehicle was built. Datatype BIGINT VARCHAR(20) Null Option NOT NULL NULL Is PK Yes No
vehicle_make vehicle_model
NULL NULL
No No
vehicle_year
BIGINT
NULL
No
312
last_update_user
NULL
No
last_update_tx_id
NULL
No
Chapter 2. Tables
313
314
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.
315
316
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 users 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
317
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 IBMs 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:
318
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
320
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.
321
322
Licensed Materials Property of IBM Printed in USA

MDMData Dictionary

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MDMData Dictionary

Uploaded by

Copyright:

Available Formats

IBM InfoSphere Master Data Management Server Version 8.5.

Licensed Materials Property of IBM

InfoSphere Master Data Management Server v8.5.0 Data Dictionary

IBM InfoSphere Master Data Management Server Version 8.5.0

Licensed Materials Property of IBM

InfoSphere Master Data Management Server v8.5.0 Data Dictionary

Licensed Materials Property of IBM

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Copyright IBM Corp. 1996, 2008

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

Chapter 1. Entity report

Licensed Materials Property of IBM

InfoSphere MDM Server v8.5.0: Data Dictionary

Licensed Materials Property of IBM

ANSWER ANSWERSET BANKACCOUNT

CATEGORYNLS CATEQUIV CATHIERARCHY

Copyright IBM Corp. 1996, 2008

CDAGREEMENTSTTP CDAGREEMENTTP CDALERTCAT

InfoSphere MDM Server v8.5.0: Data Dictionary

CDCLAIMROLETP CDCLAIMSTATUSTP CDCLAIMTP CDCLIENTIMPTP

CDCLIENTPOTENTP CDCLIENTSTTP CDCOMPLCATTP CDCOMPLDOCTP

InfoSphere MDM Server v8.5.0: Data Dictionary

InfoSphere MDM Server v8.5.0: Data Dictionary

CDLOBRELTP CDLOBTP CDMARITALSTTP

CDPPREFCAT CDPPREFREASONTP CDPPREFSEGTP CDPPREFTP CDPREFIXNAMETP

CDPRODRELATIONTP CDPRODRELTP CDPRODSTRUCTURETP CDPRODTP CDPRODUCTIDENTIFIERTP CDPRODUCTSTATUSTP

InfoSphere MDM Server v8.5.0: Data Dictionary

CDQUESTIONCATTP CDQUESTIONNAIRETP CDQUESTIONTP CDRELASSIGNTP

InfoSphere MDM Server v8.5.0: Data Dictionary