InfoSphere MDM 11.0: MDM Physical Data Dictionary - IBM · 2002-01-31 · IBM InfoSphere Master...

IBM InfoSphere Master Data Management

InfoSphere Master Data ManagementVersion 11.0MDM Physical Data Dictionary

GI13-2668-00

��

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

Edition Notice

This edition applies to version 11.0 of IBM InfoSphere Master Data Management and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 1996, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Tables. . . . . . . . . . . 1ACCESSDATEVAL . . . . . . . . . . . . 1ADDACTIONTYPE . . . . . . . . . . . . 2ADDRESS . . . . . . . . . . . . . . . 2ADDRESSGROUP . . . . . . . . . . . . 5AGREEMENTSPECVAL . . . . . . . . . . 5BANKACCOUNT . . . . . . . . . . . . 6BILLINGSUMMARY. . . . . . . . . . . . 7CAMPAIGN . . . . . . . . . . . . . . 9CAMPAIGNASSOCIAT . . . . . . . . . . 10CATEGORY . . . . . . . . . . . . . . 11CATEGORYNLS . . . . . . . . . . . . . 12CATEQUIV . . . . . . . . . . . . . . 13CATHIERARCHY . . . . . . . . . . . . 14CATHIERARCHYNLS . . . . . . . . . . . 15CATNODEREL . . . . . . . . . . . . . 15CDACCETOCOMPTP . . . . . . . . . . . 16CDACCOUNTREQUIREDTP . . . . . . . . 17CDACCOUNTTP . . . . . . . . . . . . 17CDACTIONADJREASTP . . . . . . . . . . 18CDADDRUSAGETP . . . . . . . . . . . 19CDADMINFLDNMTP . . . . . . . . . . . 19CDADMINSYSTP . . . . . . . . . . . . 20CDAGEVERDOCTP . . . . . . . . . . . 21CDAGREEMENTSTTP . . . . . . . . . . 21CDAGREEMENTTP . . . . . . . . . . . 22CDARRANGEMENTTP . . . . . . . . . . 23CDAVAILABILITYTP . . . . . . . . . . . 24CDBILLINGSTTP . . . . . . . . . . . . 25CDBILLTP. . . . . . . . . . . . . . . 25CDBUYSELLAGREETP . . . . . . . . . . 26CDCAMPAIGNTP . . . . . . . . . . . . 27CDCDCREJREASONTP . . . . . . . . . . 27CDCDCSTTP . . . . . . . . . . . . . . 28CDCHARGECARDTP . . . . . . . . . . . 29CDCLAIMROLETP . . . . . . . . . . . . 30CDCLAIMSTATUSTP . . . . . . . . . . . 30CDCLAIMTP . . . . . . . . . . . . . . 31CDCLIENTIMPTP . . . . . . . . . . . . 32CDCLIENTPOTENTP . . . . . . . . . . . 32CDCLIENTSTTP. . . . . . . . . . . . . 33CDCONDITIONATTRIBUTETP. . . . . . . . 34CDCONDITIONOWNERTP . . . . . . . . . 35CDCONDITIONUSAGETP . . . . . . . . . 35CDCONTMETHCAT . . . . . . . . . . . 36CDCONTMETHTP . . . . . . . . . . . . 37CDCONTRACTRELSTTP . . . . . . . . . . 38CDCONTRACTRELTP. . . . . . . . . . . 38CDCONTRACTROLETP . . . . . . . . . . 39CDCONTRACTSTTP . . . . . . . . . . . 40CDCONTRCOMPTP . . . . . . . . . . . 41CDCOUNTRYTP . . . . . . . . . . . . 41CDCURRENCYTP . . . . . . . . . . . . 42CDDEMOGRAPHICSTP . . . . . . . . . . 43CDDOMAINTP . . . . . . . . . . . . . 44CDDOMAINVALUETP . . . . . . . . . . 44

CDEMEMATCHFUNCTIONTP . . . . . . . . 45CDEMEMATCHWORDTP . . . . . . . . . 46CDENDREASONTP . . . . . . . . . . . 47CDENTITYLINKSTTP . . . . . . . . . . . 48CDFREQMODETP . . . . . . . . . . . . 49CDGENERATIONTP . . . . . . . . . . . 50CDHIGHESTEDUTP . . . . . . . . . . . 50CDHOLDINGTP . . . . . . . . . . . . 51CDIDSTATUSTP. . . . . . . . . . . . . 52CDIDTP . . . . . . . . . . . . . . . 52CDINACTREASONTP. . . . . . . . . . . 53CDINCOMESRCTP. . . . . . . . . . . . 54CDINDUSTRYTP . . . . . . . . . . . . 55CDLANGTP . . . . . . . . . . . . . . 55CDLINKREASONTP . . . . . . . . . . . 56CDLOBRELTP . . . . . . . . . . . . . 57CDLOBTP . . . . . . . . . . . . . . . 57CDMARITALSTTP . . . . . . . . . . . . 58CDMATCHENGINETP . . . . . . . . . . 59CDMATCHRELEVTP . . . . . . . . . . . 60CDMETADATAINFOTP . . . . . . . . . . 60CDMETADATAPACKAGETP . . . . . . . . 61CDMETHODSTATUSTP . . . . . . . . . . 61CDMISCVALUEATTRTP . . . . . . . . . . 62CDMISCVALUECAT . . . . . . . . . . . 63CDMISCVALUETP . . . . . . . . . . . . 64CDNAMEUSAGETP . . . . . . . . . . . 65CDNODETP . . . . . . . . . . . . . . 66CDORGNAMETP . . . . . . . . . . . . 66CDORGTP. . . . . . . . . . . . . . . 67CDPAYMENTMETHODTP . . . . . . . . . 68CDPPREFACTIONTP . . . . . . . . . . . 69CDPPREFCAT . . . . . . . . . . . . . 69CDPPREFREASONTP . . . . . . . . . . . 70CDPPREFSEGTP . . . . . . . . . . . . 71CDPPREFTP . . . . . . . . . . . . . . 72CDPREFIXNAMETP . . . . . . . . . . . 72CDPRIMARYTARGETMARKETTP . . . . . . 73CDPRIORITYCATTP . . . . . . . . . . . 74CDPRIORITYTP . . . . . . . . . . . . . 75CDPRODCONTRACTRELTP . . . . . . . . 75CDPRODRELATIONTP . . . . . . . . . . 76CDPRODRELTP . . . . . . . . . . . . . 77CDPRODSTRUCTURETP. . . . . . . . . . 78CDPRODTP . . . . . . . . . . . . . . 78CDPRODUCTIDENTIFIERTP . . . . . . . . 79CDPRODUCTPARTYROLETP . . . . . . . . 80CDPRODUCTSTATUSTP . . . . . . . . . . 81CDPROVSTATETP . . . . . . . . . . . . 82CDPURPOSETP . . . . . . . . . . . . . 82CDRELASSIGNTP . . . . . . . . . . . . 83CDRELTP . . . . . . . . . . . . . . . 84CDREPOSITORYTP. . . . . . . . . . . . 85CDRESIDENCETP . . . . . . . . . . . . 85CDRESOLUTIONTP . . . . . . . . . . . 86CDROLECATTP . . . . . . . . . . . . . 87

© Copyright IBM Corp. 1996, 2013 iii

CDROLETP . . . . . . . . . . . . . . 88CDRPTINGFREQTP . . . . . . . . . . . 88CDSERVICELEVELTP . . . . . . . . . . . 89CDSHAREDISTTP . . . . . . . . . . . . 90CDSOURCEIDENTTP . . . . . . . . . . . 91CDSPECCASCADETP . . . . . . . . . . . 91CDSPECUSETP . . . . . . . . . . . . . 92CDSTATUSREASONTP . . . . . . . . . . 93CDSUSPECTREASONTP . . . . . . . . . . 94CDSUSPECTSOURCETP . . . . . . . . . . 94CDSUSPECTSTATUSTP . . . . . . . . . . 95CDSUSPECTTP . . . . . . . . . . . . . 96CDTAXPOSITIONTP . . . . . . . . . . . 97CDTERMINATIONREASONTP. . . . . . . . 98CDUNDELREASONTP . . . . . . . . . . 98CDUSERROLETP . . . . . . . . . . . . 99CHARGECARD . . . . . . . . . . . . 100CLAIM . . . . . . . . . . . . . . . 100CLAIMCONTRACT . . . . . . . . . . . 102CLAIMROLE . . . . . . . . . . . . . 103CONDITIONATTRIBUTE . . . . . . . . . 103CONTACT . . . . . . . . . . . . . . 104CONTACTCDC . . . . . . . . . . . . 107CONTACTDEMOGRAPHICS . . . . . . . . 108CONTACTMETHOD . . . . . . . . . . . 108CONTACTMETHODGROUP . . . . . . . . 109CONTACTREL . . . . . . . . . . . . . 110CONTEQUIV . . . . . . . . . . . . . 111CONTMACROROLE . . . . . . . . . . . 112CONTRACT. . . . . . . . . . . . . . 113CONTRACTCOMPONENT. . . . . . . . . 116CONTRACTCOMPVAL . . . . . . . . . . 118CONTRACTREL . . . . . . . . . . . . 119CONTRACTROLE. . . . . . . . . . . . 120CONTRACTROLEREL . . . . . . . . . . 121CONTSUMMARY . . . . . . . . . . . . 122DEFAULTSOURCEVAL . . . . . . . . . . 124EME_RECBKTD . . . . . . . . . . . . 125EME_RECCHKD . . . . . . . . . . . . 126EME_RECCMPD . . . . . . . . . . . . 126EME_RECHEAD . . . . . . . . . . . . 126ENTITYCONDITIONREL . . . . . . . . . 127ENTITYCONTENTREFERENCE . . . . . . . 128ENTITYROLE . . . . . . . . . . . . . 129ENTITYSPECUSE . . . . . . . . . . . . 130FINANCIALPRODUCT . . . . . . . . . . 131GOODSPRODUCT . . . . . . . . . . . 131HOLDING . . . . . . . . . . . . . . 132IDENTIFIER. . . . . . . . . . . . . . 133INACTIVATEDCONT . . . . . . . . . . 134INACTIVECONTLINK . . . . . . . . . . 135INACTIVEPRODLINK . . . . . . . . . . 136INCOMESOURCE. . . . . . . . . . . . 136INSURANCEPRODUCT. . . . . . . . . . 137LOBREL . . . . . . . . . . . . . . . 138LOCATIONGROUP . . . . . . . . . . . 139MACROROLEASSOC . . . . . . . . . . 141MISCVALUE . . . . . . . . . . . . . 142NATIVEKEY . . . . . . . . . . . . . 144

ORG . . . . . . . . . . . . . . . . 145ORGNAME . . . . . . . . . . . . . . 146PAYMENTSOURCE . . . . . . . . . . . 147PAYROLLDEDUCTION . . . . . . . . . . 148PERSON . . . . . . . . . . . . . . . 149PERSONNAME . . . . . . . . . . . . 150PERSONSEARCH . . . . . . . . . . . . 152PHONENUMBER . . . . . . . . . . . . 153PPREFACTIONOPT . . . . . . . . . . . 154PPREFDEF . . . . . . . . . . . . . . 155PPREFDEFREL . . . . . . . . . . . . . 155PPREFENTITY . . . . . . . . . . . . . 156PPREFINSTANCE . . . . . . . . . . . . 157PRIVPREF . . . . . . . . . . . . . . 158PRODTPREL . . . . . . . . . . . . . 158PRODUCT . . . . . . . . . . . . . . 159PRODUCTCATEGORYASSOC. . . . . . . . 161PRODUCTCONTRACTREL . . . . . . . . 161PRODUCTEQUIV . . . . . . . . . . . . 162PRODUCTIDENTIFIER . . . . . . . . . . 163PRODUCTMATCHRESULT . . . . . . . . 164PRODUCTNLS . . . . . . . . . . . . . 164PRODUCTPARTYROLE . . . . . . . . . . 165PRODUCTREL . . . . . . . . . . . . . 166PRODUCTSUSPECT . . . . . . . . . . . 167PRODUCTTYPE . . . . . . . . . . . . 168PRODUCTTYPENLS . . . . . . . . . . . 169PRODUCTVAL . . . . . . . . . . . . . 170PRODUCTVALINDEX . . . . . . . . . . 170PRODUCTVALNLS . . . . . . . . . . . 172PRODUCTVALNLSINDEX . . . . . . . . . 172PROPERTY . . . . . . . . . . . . . . 173ROLEIDENTIFIER. . . . . . . . . . . . 174ROLELOCATION . . . . . . . . . . . . 175ROLELOCPURPOSE . . . . . . . . . . . 176ROLESITUATION . . . . . . . . . . . . 176SEARCHEXCLRULE . . . . . . . . . . . 177SERVICEPRODUCT . . . . . . . . . . . 178SPEC . . . . . . . . . . . . . . . . 178SPECFMT . . . . . . . . . . . . . . 179SPECFORMATTRANSLATION . . . . . . . 180SPECSRCHATTR . . . . . . . . . . . . 180SUSPECT. . . . . . . . . . . . . . . 181SUSPECTAUGMENT . . . . . . . . . . . 183TERMCONDITION . . . . . . . . . . . 183TERMCONDITIONNLS . . . . . . . . . . 185USERTABLE. . . . . . . . . . . . . . 185VEHICLE . . . . . . . . . . . . . . 186

Chapter 2. Tables by Features . . . . 187Account Domain . . . . . . . . . . . . 187Party Domain . . . . . . . . . . . . . 188Product Domain . . . . . . . . . . . . 191

Notices . . . . . . . . . . . . . . 193

Trademarks . . . . . . . . . . . . 197

iv InfoSphere MDM 11.0: MDM Physical Data Dictionary

Chapter 1. Tables

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

ACCESSDATEVALThe ACCESSDATEVAL table captures the last used date and last verified datearound various entities and attributes.

This table is used by the following domain.v Party Domain

Name Comment Datatype Null Option Is PK

ACC_DATE_VAL_ID A unique, system-generated key thatidentifies a default object in thesystem.

BIGINT Not Null Yes

INSTANCE_PK The actual primary key of the row inthe logical entity.

BIGINT Not Null No

ENTITY_NAME The name of the business entity. VARCHAR(20) Not Null No

COL_NAME The actual name of the column wherethe default occurred.

VARCHAR(20) Null No

DESCRIPTION A description of the record. VARCHAR(1000) Null No

LAST_USED_DT The date that this data was last used.There is no business logic associatedwith this field.

TIMESTAMP Null No

LAST_VERIFIED_DT The date that this data was lastverified. There is no business logicassociated with this field.

TIMESTAMP Null No

LAST_UPDATE_DT When a record is added or updated,this field is updated with the dateand time. On subsequent updates, thesystem uses this information toensure that the update requestincludes a matching date and time onthis field; if it does not, the updatefails.

TIMESTAMP Not Null No

LAST_UPDATE_USER The ID of the user who last updatedthe data.

VARCHAR(20) Null No

LAST_UPDATE_TX_ID A unique, system-generated key thatidentifies the specific transactionwithin the log system that eithercreated, updated, or deleted the datarow.

BIGINT Null No

© Copyright IBM Corp. 1996, 2013 1

ADDACTIONTYPEThe ADDACTIONTYPE table identifies an action taken as a result of suspectduplicate identification.



ADD_ACTION_ID A unique, system-generated key thatidentifies an add action in the system.

BIGINT Not Null Yes

MATCH_RELEV_TP_CD Identifies the CONTACT matchrelevancies - scores and descriptions.

BIGINT Not Null No

SUSP_REASON_TP_CD Describes the critical data that wasconsidered "matched" between twoparticular CONTACT records duringsuspect processing. Examples includeall elements matched (first name, lastname, and so forth).

BIGINT Not Null No

ORG_TP_CD Identifies the classification of theorganization. For example, trust,company, charity, estate, and so forth.

BIGINT Null No

PERSON_ORG_CODE Indicates the type of CONTACT -person or organization.

CHAR(1) Not Null No

ADD_ACTION_CODE Identifies the action taken as a resultof suspect duplicate identification.

CHAR(2) Not Null No




VARCHAR(20) Null No


BIGINT Null No

SUSPECT_TP_CD Suspect Type code captures varioussuspect types. One record exists foreach unique add_action_code in theaddactiontype table.

BIGINT Null No

ADDRESSThe ADDRESS table records the location used for mailing and other streetaddresses. Only one address per CDADDRUSAGETP is allowed. For example,there can only be one "Mailing" address for a contact.

This table is used by the following domains.

2 InfoSphere MDM 11.0: MDM Physical Data Dictionary

v Account Domainv Party Domain


ADDRESS_ID A unique, system-generated key thatidentifies an address in the system.

BIGINT Not Null Yes

COUNTRY_TP_CD Identifies a country. BIGINT Null No

RESIDENCE_TP_CD A type of residence for a givenaddress. Some examples includeHome, Apartment and Suite.

BIGINT Null No

PROV_STATE_TP_CD Identifies US States, Possessions,overseas military locations, as well asnon-US country provinces. Foroverseas military locations, APO orFPO designations are used along witha "state" abbreviation, AE, AP, or AA,and the ZIP code.

BIGINT Null No

ADDR_LINE_ONE The first line of an address. VARCHAR(100) Not Null No

P_ADDR_LINE_ONE The phonetic representation of thefirst line of an address. Not currentlyused.

CHAR(8) Null No

ADDR_LINE_TWO The second line of an address. VARCHAR(100) Null No

P_ADDR_LINE_TWO The phonetic representation of thesecond line of an address. Notcurrently used.

CHAR(8) Null No

ADDR_LINE_THREE The third line of an address. VARCHAR(100) Null No

P_ADDR_LINE_THREE The phonetic representation of thethird line of an address. Not currentlyused.

CHAR(8) Null No

CITY_NAME The city of an address. VARCHAR(50) Not Null No

POSTAL_CODE Postal Codes, and ZIP Codes, areused by the postal system to uniquelyidentify an address location.

VARCHAR(20) Null No

ADDR_STANDARD_IND

Indicates whether this address isstandardized.

CHAR(1) Null No

OVERRIDE_IND Indicates whether the addressstandardization process should beoverridden.

CHAR(1) Null No

RESIDENCE_NUM The apartment, suite, or unit numberof the address.

VARCHAR(10) Null No

COUNTY_CODE A three-digit postal code used toidentify the county of the post office.

CHAR(3) Null No

LATITUDE_DEGREES Latitude of Measure in Degreesidentifies an angular distance north orsouth. Latitude Degrees is useful forMapping Software (for example, toidentify the nearest doctors office).

VARCHAR(10) Null No

LONGITUDE_DEGREES Longitude of Measure in Degreesidentifies an angular distance east orwest. Longitude Degrees is useful forMapping Software (for example, toidentify the nearest doctors office).

VARCHAR(10) Null No

Chapter 1. Tables 3





VARCHAR(20) Null No


BIGINT Null No

POSTAL_BARCODE The structure of the 12 digits postalbar code is as follows: 5 digits for theZIP code; 4 digits for the ZIP+4 code;2 digits representing the last 2 digitsof the street address; 1 digit checksumcalculated as the sum of the otherdigits modulo 10.

VARCHAR(30) Null No

P_CITY The phonetic key for City. VARCHAR(20) Null No

BUILDING_NAME The name of the building. VARCHAR(64) Null No

STREET_NUMBER The street number of the building.For example: "55" in the address "55Main Road East".

VARCHAR(16) Null No

STREET_NAME The name of the street. For example:"Main" in the address "55 Main RoadEast".

VARCHAR(64) Null No

STREET_SUFFIX The type of street. For example:"Road" in the address "55 Main RoadEast".

VARCHAR(16) Null No

PRE_DIRECTIONAL A directional element of the address. VARCHAR(16) Null No

POST_DIRECTIONAL A directional element of the address.For example: "East" in the address "55Main Road East".

VARCHAR(16) Null No

BOX_DESIGNATOR Box designator. VARCHAR(16) Null No

BOX_ID Box identifier. VARCHAR(16) Null No

STN_INFO Station information. VARCHAR(16) Null No

STN_ID Station identifier. VARCHAR(16) Null No

REGION Further qualification of area, inaddition to City.

VARCHAR(32) Null No

DEL_DESIGNATOR Delivery designator. VARCHAR(16) Null No

DEL_ID Delivery identifier. VARCHAR(16) Null No

DEL_INFO Additional delivery information. VARCHAR(50) Null No

P_STREET_NAME The phonetic representation of thename of the street.

VARCHAR(30) Null No

STREET_PREFIX VARCHAR(16) Null No


ADDRESSGROUPThe ADDRESSGROUP table links a contact to an address and contains rulesspecific for using that address.



LOCATION_GROUP_ID A unique, system-generated key thatidentifies a location group in thesystem.

BIGINT Not Null Yes


BIGINT Not Null No

CARE_OF_DESC In Care of Description is placed abovethe recipient line. It containsinformation such as a specific personor department to provide additionalinformation, facilitating delivery.

VARCHAR(50) Null No

ADDR_USAGE_TP_CD Identifies the usage of an addressprovided by a party. Examplesinclude residence address, businessaddress, and so forth.

BIGINT Not Null No




VARCHAR(20) Null No


BIGINT Null No

AGREEMENTSPECVALThe AGREEMENTSPECVAL table contains spec values that are related to businessagreements.

This table is used by the following domain.v Account Domain


AGREEMENT_SPEC_VAL_ID

A unique, system-generated key thatidentifies a set of contract related specvalues in the system.

BIGINT Not Null Yes

SPEC_ID The spec that describes the definitionof the spec values.

BIGINT Not Null No

Chapter 1. Tables 5


SPEC_FMT_ID The spec format, or version, used tovalidate these spec values.

BIGINT Not Null No

ENTITY_NAME The type of entity with which thespec values are associated. The typesof entities are expected to becontract-related.

VARCHAR(250) Not Null No

INSTANCE_PK The primary key of the related entity. BIGINT Not Null No

VALUE_XML The spec values as defined by theassociated spec format.

XML Not Null No

START_DT The date when this record becomesactive.


END_DT The date when this record becomesinactive.

TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

BANKACCOUNTThe BANKACCOUNT table is a subtype of the PAYMENTSOURCE table,describing the bank account information used to pay one or more contracts oraccounts.



PAYMENT_SOURCE_ID A unique, system-generated key thatidentifies a payment source in thesystem.

BIGINT Not Null Yes

ACCT_TP_CD The type of bank account provided bythe party. Some examples arechecking, savings, etc.

BIGINT Not Null No

ACCT_NUM The alphanumeric identifier assignedto the bank account that uniquelyidentifies it for that given institution.


RECORDED_OPEN_DT The date on which the bank accountwas actually opened, or recorded asopened.

TIMESTAMP Null No



RECORDED_CLOSED_DT

The date on which the bank accountwas actually closed, or recorded asclosed.

TIMESTAMP Null No

BRANCH_NUM The local office, or branch, identifierused by the bank to identify thatlocation of the account.


BANK_NUM A unique identifier for the bank,assigned outside of the system.


DEPOSITOR_NAME The Party's name as printed on acheck (the account registration name).

VARCHAR(255) Null No




VARCHAR(20) Null No


BIGINT Null No

BILLINGSUMMARYThe BILLINGSUMMARY table represents a summary bill for a CONTRACT or aCONTRACTCOMPONENT.

This table is used by the following domains.v Account Domainv Party Domain


BILLING_SUMMARY_ID A unique, system-generated key thatidentifies a billing summary in thesystem.

BIGINT Not Null Yes

BILLING_ST_TP_CD A unique type code which uniquelydefines a billing status value. Forexample, closed, paid, and so forth.

BIGINT Not Null No

PYMT_MTHD_TP_CD A type code which uniquely identifiesa payment method value in thesystem. This represents the nextpayment method type. Someexamples are bank account, chargecard, cash, and so forth.

BIGINT Null No

Chapter 1. Tables 7


LAST_PY_MD_TP_CD A type code which uniquely identifiesa payment method value in thesystem. This represents the lastpayment method type. Someexamples are bank account, chargecard, cash, and so forth.

BIGINT Null No

EFFECTIVE_DATE The date from which this billingsummary is effective.

TIMESTAMP Null No

DUE_DATE The due date for this billingsummary.

TIMESTAMP Null No

ACCOUNT_BALANCE The total outstanding balance. DECIMAL(17,3) Not Null No

MIN_PAYMENT The minimum payment required forthis billing summary.

DECIMAL(17,3) Null No

MAX_PAYMENT The maximum payment allowed forthis billing summary.


PAID_TO_DATE The date up to which the account orcontract has been paid.

TIMESTAMP Null No

INVOICE_ID Links this billing summary to aninvoice; external to the system.

VARCHAR(50) Null No

BILL_FROM_DATE The start date of the billing period ofthis billing summary.

TIMESTAMP Null No

BILL_TO_DATE The end date of the billing period ofthis billing summary.

TIMESTAMP Null No

ACCOUNT_ID An account ID is a free form specificmeans by which the account can bedistinguished from all other accounts.

VARCHAR(50) Null No


BIGINT Null No

WITHDRAWAL_DATE The date on which payment will bewithdrawn from a payment source forthis billing summary.

TIMESTAMP Null No

LAST_PAYMENT_AMT The amount paid or withdrawnagainst the last billing summary.


LAST_PAYMENT_DT The date when payment was lastreceived.

TIMESTAMP Null No

PAYMENTS_REMAINING

The number of payments remaining. INTEGER Null No




VARCHAR(20) Null No




BIGINT Null No

FREQ_MODE_TP_CD The frequency of the payments madeon the contract. For example, monthlyor annual.

BIGINT Null No

CONTRACT_ID A unique, system-generated key thatidentifies a contract in the system.

BIGINT Null No

CONTR_COMPONENT_ID

A unique, system-generated key thatidentifies a contract component in thesystem.

BIGINT Null No

ACCBALA_CUR_TP The currency type for the accountbalance.

BIGINT Null No

MINPAYM_CUR_TP The currency type for the minimumpayment.

BIGINT Null No

MAXPAYM_CUR_TP The currency type for the maximumpayment.

BIGINT Null No

LASTPAY_CUR_TP The currency type for the lastpayment.

BIGINT Null No

CAMPAIGNThe CAMPAIGN table contains the details of a campaign for customer solicitation,including the priority order for customer presentation.



CAMPAIGN_ID A unique, system-generated key thatidentifies a campaign in the system.

BIGINT Not Null Yes

PRIORITY_TP_CD The priority of a task, a campaign, avalue, and so on. Examples includehigh, medium, low.

BIGINT Null No

CAMPAIGN_TP_CD A numeric representation of thecampaign for customer.

BIGINT Null No

CAMPAIGN_SOURCE The source of the campaign record. VARCHAR(100) Null No

NAME A short, meaningful label for thecampaign.


DESCRIPTION Provides extra space for informationthat can be used for an additionaldefinition or as free form commentsto provide further meaning.


CREATED_DT The date when this record wascreated.



TIMESTAMP Null No

Chapter 1. Tables 9



TIMESTAMP Null No


VARCHAR(20) Null No




BIGINT Null No

CAMPAIGNASSOCIATThe CAMPAIGNASSOCIAT table lists the association between a campaign and anyassociated entities.



CAMPAIGNASSOC_ID A unique, system-generated key thatidentifies a Campaign Group in thesystem.

BIGINT Not Null Yes

ENTITY_NAME The name of the business entity thatis associated with the Campaign.


INSTANCE_PK The actual primary key of the row inthe logical entity that is associatedwith the Campaign.

BIGINT Not Null No

CAMPAIGN_ID The primary key of a campaignrecord.

BIGINT Not Null No

ASSOCIATE_IND Identifies whether this is a targetassociation or regarding association.

CHAR(1) Null No




TIMESTAMP Null No


VARCHAR(20) Null No






BIGINT Null No

CATEGORYThe CATEGORY table contains common platform attributes for categories. ACATEGORY can participate in only one hierarchy at a time.

This table is used by the following domain.v Product Domain


CATEGORY_ID A unique, system-generated key thatidentifies a category in the system.

BIGINT Not Null Yes

CAT_HIERARCHY_ID A unique, system-generated key thatidentifies a category hierarchy in thesystem.

BIGINT Not Null No

CATEGORY_CODE An identifier for a category within aparticular hierarchy.


NAME VARCHAR(120) Not Null No



IS_ROOT Indicates that the category is root inthe hierarchy (ultimate parent).

CHAR(1) Not Null No

IS_LEAF Indicates if the category can havesubcategories or not.

CHAR(1) Not Null No

ASSOC_IND Indicates if the category permitsassociations to be made with it (i.e.,product-category).

CHAR(1) Not Null No




TIMESTAMP Null No

Chapter 1. Tables 11





VARCHAR(20) Null No


BIGINT Null No

CATEGORYNLSThe CATEGORYNLS table contains the language sensitive fields for theCATEGORY table.



CATEGORY_NLS_ID A unique, system-generated key thatidentifies a localized category in thesystem.

BIGINT Not Null Yes

CATEGORY_ID The primary key of the categoryrecord.

BIGINT Not Null No

LANG_TP_CD Language type code. BIGINT Not Null No

NAME Localized name for the categoryname.


DESCRIPTION Localized description for the categorydescription.





VARCHAR(20) Null No


BIGINT Null No


CATEQUIVThe CATEQUIV table contains information about a category equivalency.



CAT_EQUIV_ID A unique, system-generated key thatidentifies a category equivalency inthe system.

BIGINT Not Null Yes

CATEGORY_ID A unique, system-generated key thatidentifies a category in the system.

BIGINT Not Null No

ADMIN_SYS_TP_CD Administration System Code uniquelyidentifies the administrative sourcesystem for a contract. Examplesinclude Ingenium, Alltel, Huon, etc.

BIGINT Not Null No

CAT_EQUIV_KEY A key, or ID, that uniquely identifiesthe category in the administrativesource system.


KEY_1 A partial key, which in conjunctionwith other keys, identifies thecategory in the administrative sourcesystem.



VARCHAR(30) Null No


VARCHAR(30) Null No


VARCHAR(30) Null No


VARCHAR(30) Null No




VARCHAR(20) Null No




BIGINT Null No

CATHIERARCHYThe CATHIERARCHY table contains information about a category hierarchy.



CAT_HIERARCHY_ID A unique, system-generated key thatidentifies a category hierarchy in thesystem.

BIGINT Not Null Yes

NAME A short, meaningful label for thecategory hierarchy.




HIERARCHY_TP_CD Code indicating the categoryhierarchy type.

BIGINT Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


CATHIERARCHYNLSThe CATHIERARCHYNLS table contains the language sensitive fields for theCATHIERARCHY table.



CAT_HIERARCHY_NLS_ID

A unique, system-generated key thatidentifies a category hierarchy NLSrecord in the system.

BIGINT Not Null Yes

CAT_HIERARCHY_ID The primary key of the NLS categoryhierarchy record.

BIGINT Not Null No

LANG_TP_CD Language type code. BIGINT Not Null No

NAME Localized name for the categoryhierarchy name.


DESCRIPTION Localized description for the categoryhierarchy description.





VARCHAR(20) Null No


BIGINT Null No

CATNODERELThe CATNODEREL table contains the definition of relationships between categorynodes in a category hierarchy.



CAT_NODE_REL_ID A unique, system-generated key thatidentifies a category node relationshipin the system.

BIGINT Not Null Yes

PARENT_NODE_ID The primary key (category_id) of theparent hierarchy node record.

BIGINT Not Null No

CHILD_NODE_ID The primary key (category_id) of thechild hierarchy node record.

BIGINT Not Null No






TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

CDACCETOCOMPTPThe CDACCETOCOMPTP table describes the type of access a CONTACT has to acomputer and to current and future related technologies. For example, computersor videophones.



LANG_TP_CD Identifies a spoken language, such asEnglish, French, Spanish, or German.When used as part of the primary keyof a code value lookup table, theLanguage Type Code also representsthe language of the code name.

BIGINT Not Null Yes

ACCE_COMP_TP_CD Represents one of the various types ofaccess a party can have to a computerand related technologies.

BIGINT Not Null Yes

NAME A short, meaningful label for thevalue of the type code.


DESCRIPTION Provides extra information either asan additional definition of the typecode value or as free form usercomments to provide further meaningto the type code.


EXPIRY_DT The date that the type code is nolonger valid.

TIMESTAMP Null No





CDACCOUNTREQUIREDTPThe CDACCOUNTREQUIREDTP table contains information about the accountrequirement type codes for the FINANCIALPRODUCT table.



LANG_TP_CD Identifies a spoken language, such as English,French, Spanish, or German. When used as partof the primary key of a code value lookup table,the Language Type Code also represents thelanguage of the code name.

BIGINT Not Null Yes

ACCOUNT_REQUIRED_TP_CD Indicates whether the product requires anaccount or not.

BIGINT Not Null Yes

NAME A short, meaningful label for the value of thetype code.


DESCRIPTION Provides extra information either as anadditional definition of the type code value or asfree form user comments to provide furthermeaning to the type code.


EXPIRY_DT The date that the type code is no longer valid. TIMESTAMP Null No

LAST_UPDATE_DT When a record is added or updated, this field isupdated with the date and time. On subsequentupdates, the system uses this information toensure that the update request includes amatching date and time on this field; if it doesnot, the update fails.


LAST_UPDATE_USER The ID of the user who last updated the data. VARCHAR(20) Null No

CDACCOUNTTPThe CDACCOUNTTP table contains values for the account type code and itsdescriptions. For example, "Savings" and "Checking".




BIGINT Not Null Yes



ACCT_TP_CD Identifies the type of bank accountprovided by the party. Someexamples are checking, savings, andso forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDACTIONADJREASTPThe CDACTIONADJREASTP table identifies the reason that an action, taken as aresult of suspect duplicate identification, was adjusted.




BIGINT Not Null Yes

ADJ_ACTION_TP_CD Identifies the business reasons for theaction code on the suspectidentification being modified.

BIGINT Not Null Yes






TIMESTAMP Null No





CDADDRUSAGETPThe CDADDRUSAGETP table contains information about the address usage typecode values, such as primary residence, secondary address, or business address.




BIGINT Not Null Yes

ADDR_USAGE_TP_CD Identifies the usage of an addressprovided by a party.

BIGINT Not Null Yes






TIMESTAMP Null No



CDADMINFLDNMTPThe CDADMINFLDNMTP table contains the valid values for the native key fieldname type code and its descriptions.





BIGINT Not Null Yes

ADMIN_FLD_NM_TP_CD

Identifies the field name that thenative key refers to, for example,policy number, policy suffix, accountnumber, branch, and so forth.

BIGINT Not Null Yes



DESCRIPTION Description provides extrainformation, which can be used eitheras an additional definition of the typecode value or as free form commentsused by the user to provide furthermeaning to the type code.


ADMIN_SYS_TP_CD Uniquely identifies the administrativesource system for a contract.Examples include Ingenium, Alltel,Huon, and so forth.

BIGINT Not Null No

SIZE_NUM The length or number of digits usedby the native key field.


DATATYPE_NAME The name of the datatype for thenative key field.

VARCHAR(40) Null No

DISPLAYED_IND Indicates whether this is the nativekey field to be displayed to the user.

CHAR(1) Null No

PRESENT_SEQ_NUM The order by which the contract'sadministrative source systemunderstands the native key fields.

SMALLINT Null No


TIMESTAMP Null No



CDADMINSYSTP



LANG_TP_CD BIGINT Not Null Yes

ADMIN_SYS_TP_CD BIGINT Not Null Yes

NATIVE_KEY_TOT SMALLINT Null No



NAME VARCHAR(120) Null No

DESCRIPTION VARCHAR(255) Null No

EXPIRY_DT TIMESTAMP Null No

LAST_UPDATE_DT TIMESTAMP Not Null No

CDAGEVERDOCTPThe CDAGEVERDOCTP table contains the age verification type code values andtheir descriptions.




BIGINT Not Null Yes

AGE_VER_DOC_TP_CD An identifier that uniquely separatesone type of document being used toverify a client's age from another.Examples include birth certificate,driver's license, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDAGREEMENTSTTPThe CDAGREEMENTSTTP table stores the valid status of an agreement. Forexample, Draft, Normal, or Suspended.





BIGINT Not Null Yes

AGREEMENT_ST_TP_CD

Identifies the status of the contract asprovided by the administrative sourcesystems. For example, a bank mighthave the contract status types "active","pending", "lapse pending", and"cancelled".

BIGINT Not Null Yes






TIMESTAMP Null No



CDAGREEMENTTPThe CDAGREEMENTTP table stores the agreement type. For example,ValuePackage.




BIGINT Not Null Yes

AGREEMENT_TP_CD Describes the type of the contract.Some examples include ValuePackage, or Supplier Agreement.

BIGINT Not Null Yes








TIMESTAMP Null No



CDARRANGEMENTTPThe CDARRANGEMENTTP table contains the values and descriptions of thearrangement type code, describing the role that the CONTACT plays on anAGREEMENT. For examples, a time delay arrangement can be active on the role.For example, if a contact is the beneficiary on an insurance contract, that contactcan only receive the benefit if the contact happens to die in the same accident asthe insured person, but only if that contact survived the insured person by acertain length of time; otherwise, if both die at the same time, the proceeds will goto the insured's contingent beneficiary.




BIGINT Not Null Yes

ARRANGEMENT_TP_CD

Describes the type of agreement thatthe party contract role has with thecontract. For example: time delayarrangement such as a commondisaster.

BIGINT Not Null Yes






TIMESTAMP Null No





CDAVAILABILITYTPThe CDAVAILABILITYTP table contains information about how widely available aPRODUCT is to its target market.




BIGINT Not Null Yes

AVAILABILITY_TP_CD The availability status of the productwith respect to its target market.Determines whether the product isgenerally available, or has restrictedavailability.

BIGINT Not Null Yes






TIMESTAMP Null No




VARCHAR(20) Null No


CDBILLINGSTTPThe CDBILLINGSTTP table contains the status values and descriptions for a billingtype. For example, "Closed", "Paid", "Pending" and "Disputed".




BIGINT Not Null Yes

BILLING_ST_TP_CD A unique type code which uniquelydefines a billing status value. Someexamples are closed, paid, and soforth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDBILLTPThe CDBILLTP table contains the values for the bill type code and its descriptions.




BIGINT Not Null Yes



BILL_TP_CD An identifier that uniquely separatesone billing type from another.Examples include Regular, Direct,Payroll deduction, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDBUYSELLAGREETPThe CDBUYSELLAGREETP table contains the buy sell agreement type code valuesand their descriptions. For example, Cross purchase, or Hybrid.




BIGINT Not Null Yes

BUY_SELL_AGR_TP_CD An identifier that uniquely separatesone type of buy-sell agreement fromanother.

BIGINT Not Null Yes






TIMESTAMP Null No





CDCAMPAIGNTPThe CDCAMPAIGNTP table identifies the type of campaign.




BIGINT Not Null Yes

CAMPAIGN_TP_CD A numeric representation of thecampaign for customer.

BIGINT Not Null Yes






TIMESTAMP Null No



CDCDCREJREASONTPThe CDCDCREJREASONTP table stores the reason type detailing why a criticaldata change is rejected. For example, Created in error, or Withdrawn by customer.





BIGINT Not Null Yes

REJ_REASON_TP_CD The reason for which a critical datachange has been rejected.

BIGINT Not Null Yes






TIMESTAMP Null No



CDCDCSTTPThe CDCDCSTTP table stores the status type of a critical data change request. Forexample, Change rejected, or Change accepted.




BIGINT Not Null Yes

CDC_ST_TP_CD The type code indicating the status ofthe critical data change request.

BIGINT Not Null Yes






TIMESTAMP Null No





CDCHARGECARDTPThe CDCHARGECARDTP table contains the charge card type code values andtheir descriptions. For example, Visa, MasterCard, or American Express.




BIGINT Not Null Yes

CHARGE_CARD_TP_CD Identifies one type of charge cardfrom another. Some examples areVisa, MasterCard, or AmericanExpress.

BIGINT Not Null Yes






TIMESTAMP Null No




CDCLAIMROLETPThe CDCLAIMROLETP table contains the claim role type code values and theirdescriptions. For example, "Claimant", "Third Party", "Witness", and "Adjuster".




BIGINT Not Null Yes

CLAIM_ROLE_TP_CD A type of role a party plays on aclaim. Some examples includeClaimant, Witness and Third Party.

BIGINT Not Null Yes






TIMESTAMP Null No



CDCLAIMSTATUSTPThe CDCLAIMSTATUSTP table contains the claim status type code values andtheir descriptions. For example, "Pending", "Closed", "Open" and "Rejected".




BIGINT Not Null Yes

CLAIM_STATUS_TP_CD Identifies the status of a claim. Someexamples include Pending, Closedand Rejected.

BIGINT Not Null Yes








TIMESTAMP Null No



CDCLAIMTPThe CDCLAIMTP table contains the claim type code values and their descriptions.




BIGINT Not Null Yes

CLAIM_TP_CD The type of claim that is recorded.For example, Fire, Theft, Automobile,Collision, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No




CDCLIENTIMPTPThe CDCLIENTIMPTP contains the client importance type code values and theirdescriptions. The importance type can be used to indicated VIP situations or otherspecial services that can be applied to this contact.




BIGINT Not Null Yes

CLIENT_IMP_TP_CD An identifier that uniquely separatesone client importance type fromanother. Examples include high,medium, and low.

BIGINT Not Null Yes






TIMESTAMP Null No



CDCLIENTPOTENTPThe CDCLIENTPOTENTP table represents the party potential type code and itsdescriptions.




BIGINT Not Null Yes



CLIENT_POTEN_TP_CD An identifier that uniquely separatesone client potential type from another.For example, an insurance providermight have the potential types"client", "prospect" and"non-potential".

BIGINT Not Null Yes






TIMESTAMP Null No



CDCLIENTSTTPThe CDCLIENTSTTP table represents the party status type code value and itsdescription.




BIGINT Not Null Yes

CLIENT_ST_TP_CD An identifier that uniquely separatesone client status type from another.For example, a telecommunicationscompany might have the client statustypes "active", "inactive", and"pending".

BIGINT Not Null Yes








TIMESTAMP Null No



CDCONDITIONATTRIBUTETPThe CDCONDITIONATTRIBUTETP table serves as a means to group conditionattributes, allowing a second level of granularity. For example, Core Account Type,Annual Interest rate, and Minimum Charge.




BIGINT Not Null Yes

CONDITION_ATTR_TP_CD

Describes the attribute type of thecondition. For example, "CoreAccount Type", "Status", and "InterestRate".

BIGINT Not Null Yes

CONDITION_USAGE_TP_CD

Describes the usage types for acondition. For example, "ValuePackage Integrity", "Rate", "Fee", or"Balance".

BIGINT Not Null No






TIMESTAMP Null No




CDCONDITIONOWNERTPThe CDCONDITIONOWNERTP table describes the Terms and Conditionscomponent owner type. For example, PRODUCT or CONTRACT.




BIGINT Not Null Yes

CONDITION_OWNER_TP_CD

Identifies the owner of the condition. BIGINT Not Null Yes






TIMESTAMP Null No



CDCONDITIONUSAGETPThe CDCONDITIONUSAGETP table serves as a means to group condition types.For example: ValuePackage Integrity, Rate Fee.




BIGINT Not Null Yes


Describes the usage types for a termand condition. For example, "ValuePackage Integrity", "Rate", "Fee", or"Balance".

BIGINT Not Null Yes








TIMESTAMP Null No



RULE_ID The associated business rule ID. VARCHAR(10) Null No

CDCONTMETHCATThe CDCONTMETHCAT table contains information on the contact methodcategory type code values and their descriptions. For example, phone, e-mail, orPDA.




BIGINT Not Null Yes

CONT_METH_CAT_CD Identifies the type of contact method.For example: telephone, e-mail, PDA,and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No





CDCONTMETHTPThe CDCONTMETHTP table contains information on the valid values for thecontact method type code. For example, primary phone number and cell phonenumber.




BIGINT Not Null Yes

CONT_METH_TP_CD Identifies the subtypes of a ContactMethod Category Type Code. Forexample, if the category type istelephone, then the values of thesubtype code are home, business, cellphone, and so forth.

BIGINT Not Null Yes

CONT_METH_CAT_CD Identifies the type of contact method.For example: telephone, e-mail, PDA,and so forth.

BIGINT Not Null No






TIMESTAMP Null No




CDCONTRACTRELSTTPThe CDCONTRACTRELSTTP table contains the values and descriptions for thecontract relationship status code, which identifies the status of a relationship. Forexample, "pending," "active," and "terminated".




BIGINT Not Null Yes

CONTR_REL_ST_TP_CD Identifies the status of therelationship between two contracts,for example, "pending", "active", and"terminated."

BIGINT Not Null Yes






TIMESTAMP Null No



CDCONTRACTRELTPThe CDCONTRACTRELTP table contains the values and descriptions for thecontract relationship type code, which identifies the purpose for a relationship.




BIGINT Not Null Yes



CONTR_REL_TP_CD Describes the type of a relationship.Reciprocal in nature, examplesinclude child and parent, andsupports and supported-by.

BIGINT Not Null Yes

TO_FROM_NAME A short, meaningful label for the "to"value of the relationship.


FROM_TO_NAME A short, meaningful label for the"from" value of the relationship.





TIMESTAMP Null No



CDCONTRACTROLETPThe CDCONTRACTROLETP table represents the contract role type code valuesand their descriptions. For example, Owner, Beneficiary, Insured, or Payer.




BIGINT Not Null Yes

CONTR_ROLE_TP_CD Identifies the type of role that a partycan have on a contract. For example,an insurance provider might have thecontract role types "beneficiary,""owner," "insured," and "payer".

BIGINT Not Null Yes








TIMESTAMP Null No



CDCONTRACTSTTPThe CDCONTRACTSTTP table contains the contract status type code values andtheir descriptions.




BIGINT Not Null Yes

CONTRACT_ST_TP_CD Identifies the status of the contract.These values are provided by theadministrative source systems of thecontract. For example, a bank mighthave the contract status types "active,""pending," lapse pending," and"cancelled".

BIGINT Not Null Yes






TIMESTAMP Null No




CDCONTRCOMPTPThe CDCONTRCOMPTP table contains the values and descriptions for the contractcomponent type codes that describe the type of component. For example, base,rider, or base increase.




BIGINT Not Null Yes

CONTR_COMP_TP_CD A numeric representation of the typeof coverage for the product. Forexample, Base, Rider, Base Increase,or Integrated.

BIGINT Not Null Yes






TIMESTAMP Null No



CDCOUNTRYTPThe CDCOUNTRYTP table contains the country type code value and itsdescriptions. For example, "USA", "Canada", or "England".




BIGINT Not Null Yes

COUNTRY_TP_CD Identifies a country. BIGINT Not Null Yes








TIMESTAMP Null No



ISO_CODE CHAR(2) Null No

CDCURRENCYTPThe CDCURRENCYTP table contains the currency type code and its descriptions.For example, Euro, US Dollar, Japanese Yen, British Pound.

This table is used by the following domains.v Party Domainv Product Domain



BIGINT Not Null Yes

CURRENCY_TP_CD Identifies the currency of the amountcolumns.

BIGINT Not Null Yes






TIMESTAMP Null No





CURRENCY_CODE The standard currency code for thecurrency.

CHAR(3) Null No

CDDEMOGRAPHICSTPThe CDDEMOGRAPHICSTP table defines demographics types.




BIGINT Not Null Yes

DEMOGRAPHICS_TP_CD

The Demographics ID identifies thetype of the demographics record.

BIGINT Not Null Yes



SPEC_ID The ID of the Spec used for thedemographics type.

BIGINT Null No




TIMESTAMP Null No




VARCHAR(20) Null No


CDDOMAINTPThe CDDOMAINTP table contains values and descriptions for the domain typecode that defines the business area of the agreement component values.




BIGINT Not Null Yes

DOMAIN_TP_CD Defines the types of values can bestored. For example, Integer, String,Decimal, Date, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDDOMAINVALUETPThe CDDOMAINVALUETP table contains the values and descriptions for theValue Type Code, which, in a given domain, identifies the values that are captured.For example, within banking, values captured can be "account balance" and"account deposit".




BIGINT Not Null Yes



DOMAIN_VALUE_TP_CD

Domain Value Type Code, in a givendomain, identifies the specific valuesthat are captured. For example:Integer value, Date value, and soforth.

BIGINT Not Null Yes

PROD_TP_CD Identifies the type of productassociated with the contract (or atsome level within the product family).For example, a manufacturingcompany might have the producttypes "precision tools", "switches","defence", "electronics", and"automotive".

BIGINT Null No





DOMAIN_TP_CD Defines the types of values can bestored. Examples include Integer,String, Decimal, Date, and so forth.

BIGINT Not Null No

PRECISION_VALUE Defines the Value String attribute inthe Contract Component Value byidentifying the number of digits to beexpected for that given Value TypeCode.

SMALLINT Null No


TIMESTAMP Null No



CDEMEMATCHFUNCTIONTPThis table represent the IBM InfoSphere MDM Probabilistic Matching Enginematch function details. A match function is a component of a larger algorithm thatcompares the data for two entities and derives a score based on their likenesses.The match function determines if a subset of the data in an entity (for example astreet number, a phone number, a first name, a last name, and so forth) are thesame, different, or similar (that is, a partial match), and so forth.





BIGINT Not Null Yes

MATCH_FUNCTION_TP_CD

The match function type code is anumerical value returned from eMEengine that represents the results of amatching function that was used on aportion of the data. The values can beone of 68, 69, 70, 77, 80, 84, 42.

VARCHAR(5) Not Null Yes

NAME A short, meaningful label for thevalue of the type code. The currentnames for the corresponding typecodes can be: Different, Equal, False,Missing, Partial, True, Unknown.





TIMESTAMP Null No




VARCHAR(20) Null No

CDEMEMATCHWORDTPThis table contains the codes and values for the word-by-word comparisons thateach InfoSphere MDM Probabilistic Matching Engine match function codeperforms (see the CDEMEMATCHFUNCTIONTP table). Some examples of wordcomparisons that are done are Nickname (for example, Nick or Nicholas) andacronym (for example, IBM or International Business Machines).




BIGINT Not Null Yes



MATCH_WORD_TP_CD The match word type code is thenumerical value that represents thethe outcome of a comparison of twoindividual words carried out by amatching function. These values canbe : 65, 67, 68, 69, 89, 88, 73, 49, 77,78, 80, 79, 50, 42.


NAME A short, meaningful label for thevalue of the type code. The currentnames of the codes are: Acronym,Compound Word Match, Different,Edit Distance, Equal Initials, EqualWord, Initials match word firstcharacter, Left prefix of right, Missing,Nickname, Phonetic, PhoneticNickname Equal, Right prefix of left,Unknown.





TIMESTAMP Null No




VARCHAR(20) Null No

CDENDREASONTPThe CDENDREASONTP table contains the values and descriptions of the endreason type code that identifies why a relationship was ended.




BIGINT Not Null Yes

END_REASON_TP_CD Identifies the cause for why arelationship was ended. For example,a spousal party to party relationshipcan be ended for a "divorce," reason.

BIGINT Not Null Yes








TIMESTAMP Null No



CDENTITYLINKSTTPThis table lists the entity link status types associated with parties that are persistedfrom virtual MDM. This table is used by the Hybrid MDM functional feature.




BIGINT Not Null Yes

ENTITYLINK_ST_TP_CD Identifies the status of a party that ispersisted from virtual MDM. Forexample, 'Virtual-Owned Entity' or'Persisted View'.

BIGINT Not Null Yes






TIMESTAMP Null No






VARCHAR(20) Null No

CDFREQMODETPThe CDFREQMODETP contains the frequency mode type code values and theirdescriptions. For example, "Weekly", "Monthly", "Quarterly", or "Annual".




BIGINT Not Null Yes

FREQ_MODE_TP_CD Identifies the frequency of thepayments made on the contract. Forexample, monthly, annual, weekly,daily, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No




CDGENERATIONTPThe CDGENERATIONTP table contains familial generational information in theform of a generation name type code. For example, The First, The Second, Junioror Senior.




BIGINT Not Null Yes

GENERATION_TP_CD Identifies familial generationalinformation in the form of ageneration name type code. Forexample, The First, The Second,Junior or Senior.

BIGINT Not Null Yes






TIMESTAMP Null No



CDHIGHESTEDUTPThe CDHIGHESTEDUTP table contains the highest education type code valuesand their descriptions.




BIGINT Not Null Yes



HIGHEST_EDU_TP_CD Identifies the highest level ofschooling that this person hasreceived. For example, high school,college, university, or postgraduate.

BIGINT Not Null Yes






TIMESTAMP Null No



CDHOLDINGTPThe CDHOLDINGTP table contains the holding type code values and theirdescriptions. For example, "Vehicle" or "Property".




BIGINT Not Null Yes

HOLD_TP_CD Identifies a type of party holding. Forexample: Vehicles, Property, Stocks, orothers.

BIGINT Not Null Yes






TIMESTAMP Null No





CDIDSTATUSTPThe CDIDSTATUSTP table represents the identification status type code values andtheir descriptions. For example, Applied For, Certified, or Expired.




BIGINT Not Null Yes

ID_STATUS_TP_CD Identifies the status of the identifierprovided by the party. For example,"applied for", "expired", "certified",and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDIDTPThe CDIDTP table represents the identification type code values and theirdescriptions. For example, social insurance number, social security number, driver'slicense, passport number, or tax registration number.

This table is used by the following domain.


v Party Domain



BIGINT Not Null Yes

ID_TP_CD Identifies the type of identifierprovided by the party. For example,"social security number," "passport,""driver's license number," and soforth.

BIGINT Not Null Yes






TIMESTAMP Null No



MAX_ALLOWED_NUM Maximum allowed number. SMALLINT Null No

CDINACTREASONTPThe CDINACTREASONTP table contains information on the valid values for theinactivated reason type code. For example, "collapsed", "split", or "deceased".




BIGINT Not Null Yes

INACT_REASON_TP_CD

Identifies the reason for the partyinformation being inactivated. Forexample, splitting or collapsing ofparty records.

BIGINT Not Null Yes








TIMESTAMP Null No



CDINCOMESRCTPThe CDINCOMESRCTP table contains information on the valid values for theincome source type code. For example, annual salary and net worth.




BIGINT Not Null Yes

INCOME_SRC_TP_CD Identifies the type of income sourcethat the party provided. For example,"annual salary", "estimated networth", "Ownership of Bonds", and soforth.

BIGINT Not Null Yes






TIMESTAMP Null No




CDINDUSTRYTPThe CDINDUSTRYTP table contains the industry type code values and theirdescriptions. For example, farming, industrial, insurance.




BIGINT Not Null Yes

INDUSTRY_TP_CD Represents the industry type for theorganization. Examples include SIC,and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDLANGTPThe CDLANGTP table contains the values for the Language Type Code and itsdescriptions. For example, "English", "French", or "Spanish".




BIGINT Not Null Yes








TIMESTAMP Null No



LOCALE The locale string for the languagerecord.

VARCHAR(20) Null No

CODE_TABLE_TRANSLATION

Indicates whether the systemprovides the code table translation forthe given language and locale.

CHAR(1) Null No

CDLINKREASONTPThe CDLINKREASONTP table identifies the reason why two parties are linkedtogether. For example, collapsed, or split.

This table is used by the following domains.v Party Domainv Product Domain



BIGINT Not Null Yes

LINK_REASON_TP_CD Describes the reason why two partiesare linked. For example, "Sourcecollapsed into target", "Sourceduplicated as target", and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No





CDLOBRELTPThe CDLOBRELTP table defines various LOB relationship types. For example,"owner".




BIGINT Not Null Yes

LOB_REL_TP_CD Identifies the unique type code for aspecific line of business relationshiptype.

BIGINT Not Null Yes






TIMESTAMP Null No



CDLOBTPThe CDLOBTP table contains the values and descriptions for all of the lines ofbusiness set up in the system.





BIGINT Not Null Yes

LOB_TP_CD Identifies the unique type code for aspecific line of business.

BIGINT Not Null Yes






TIMESTAMP Null No



CDMARITALSTTPThe CDMARITALSTTP table contains the marital status type code values and theirdescriptions. For example: "married", "separated", or "widowed".




BIGINT Not Null Yes

MARITAL_ST_TP_CD Identifies a person's marital status.For example, single, widowed, ordivorced.

BIGINT Not Null Yes








TIMESTAMP Null No



CDMATCHENGINETPThe CDMATCHENGINETP table contains the type information and description ofthe matching engine use for matching contacts.




BIGINT Not Null Yes

MATCH_ENG_TP_CD The Matching Engine to use formatching parties.

BIGINT Not Null Yes






TIMESTAMP Null No




CDMATCHRELEVTPThe CDMATCHRELEVTP table contains the match relevancy type code value andits description. For example, LNAME, SSN and ADDRESS LINE 1.




BIGINT Not Null Yes

MATCH_RELEV_TP_CD Identifies party match relevancies,providing a description of whichelements were matched.

BIGINT Not Null Yes





RELEVENCY_SCORE The score associated with a matchrelevancy type. For example: LNAMEscore = 30.

SMALLINT Null No


TIMESTAMP Null No



MATCH_ENG_TP_CD The matching engine used formatching parties.

BIGINT Null No

CDMETADATAINFOTPThe CDMETADATAINFOTP table stores information used to identify metadata.For example, task definition, or spec.



METADATA_INFO_TP_CD

A code that identifies the metadatainformation.

BIGINT Not Null Yes



METADATA_KEY Data that defines the value of themetadata information type code. Anexample is: "928749ae-f19c-41b6-babf-380467cea769".


METADATA_PACKAGE_TP_CD

A code that identifies the metadatapackage.

BIGINT Null No


TIMESTAMP Null No



CDMETADATAPACKAGETPThe CDMETADATAPACKAGETP table stores a list of meta data package namesused to identify the location of metadata in the system. For example, taskdefinition, or spec. Stores a list of meta data package names, which are used toidentify the location of the metadata in system, such as task definition and spec.



METADATA_PACKAGE_TP_CD

A code that identifies the metadatapackage.

BIGINT Not Null Yes

METADATA_PACKAGE_NAME

Data that defines the value of ametadata package type code. Forexample, "com.ibm.mdm.System".



TIMESTAMP Null No



CDMETHODSTATUSTPThe CDMETHODSTATUSTP table contains the values and descriptions for thecontact method status type code. For example, "disconnected", "unlisted", or "nolonger available".





BIGINT Not Null Yes

METHOD_ST_TP_CD Identifies the status of a contactmethod. For example, disconnected orcancelled.

BIGINT Not Null Yes






TIMESTAMP Null No



CDMISCVALUEATTRTPThe CDMISCVALUEATTRTP table contains miscellaneous value attributes typesthat are captured.




BIGINT Not Null Yes

VALUEATTR_TP_CD The miscvalue attribute can be usedto provide more informationregarding a miscellaneous value typesuch as status, effective date, createddate and so forth, or the miscvalueattribute type can be used to populatemultiple values for a party.

BIGINT Not Null Yes








TIMESTAMP Null No



CDMISCVALUECATThe CDMISCVALUECAT table categorizes types of miscellaneous values. Forexample, demographic category, risk category, or standard industry codes.




BIGINT Not Null Yes

MISCVALUE_CAT_CD The category allows institutions toclassify the different types of values.Some examples are DemographicCategory, Risk Category, StandardIndustry Codes,Party, Billing, Addressand so forth.

BIGINT Not Null Yes






TIMESTAMP Null No





CDMISCVALUETPThe CDMISCVALUETP table identifies miscellaneous value types that arecaptured. These attributes can be different value attribute types for a miscellaneousvalue type, or they can be additional information about a particular miscellaneoustype such as status, effective date, created date, or indicator.




BIGINT Not Null Yes

MISCVALUE_TP_CD This is the miscellaneous value typethat corresponds to a particularmiscellaneous value category. Someexamples of miscvalue type arenumber of employees, gold value,credit card risk score, loyalty,profitability and so forth.

BIGINT Not Null Yes

MISCVALUE_CAT_CD The category allows institutions toclassify the different types of values.Some examples are DemographicCategory, Risk Category, StandardIndustry Codes, Party, Billing,Address and so forth.

BIGINT Null No






TIMESTAMP Null No





CDNAMEUSAGETPThe CDNAMEUSAGETP table contains the name usage type code value and itsdescription. For example, legal name, nickname, or maiden name.




BIGINT Not Null Yes

NAME_USAGE_TP_CD Identifies the type of name for thisperson. For example, "Legal," "NickName," "Maiden Name," and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



MAX_ALLOWED_NUM The greatest number of times a givenPerson Name Usage Type Code canbe used.

SMALLINT Null No


CDNODETPThe CDNODETP table captures metadata regarding how the subtype isrepresented within the product type hierarchy.




BIGINT Not Null Yes

NODE_TP_CD Identifies whether the product type isthe root type, a hardened type (i.e. asub-type defined through physicaltables), or a soft type (i.e. a sub-typedefined through specs).

BIGINT Not Null Yes






TIMESTAMP Null No



CDORGNAMETPThe CDORGNAMETP table contains the organization name type code values andtheir descriptions. For example, "doing business as", "abbreviated name", or "legalname".




BIGINT Not Null Yes



ORG_NAME_TP_CD Identifies the type of name for thisorganization. For example, "Legal","Doing Business As", "Abbreviated",and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



MAX_ALLOWED_NUM The maximum number of activeorganization name types allowed.Null means an unlimited number isallowed.

SMALLINT Null No

CDORGTPThe CDORGTP table contains information on organization type code values. Forexample, charity, trust, estate, or corporation.




BIGINT Not Null Yes

ORG_TP_CD Identifies the classification of theorganization. For example, trust,company, charity, estate, and so forth.

BIGINT Not Null Yes








TIMESTAMP Null No



CDPAYMENTMETHODTPThe CDPAYMENTMETHODTP table contains various payment method type valuesand their descriptions. For example, "cash", "cheque", or "payroll deduction".




BIGINT Not Null Yes

PYMT_MTHD_TP_CD A type code which uniquely identifiesa payment method value in thesystem. For example, bank account,charge card, cash, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No




CDPPREFACTIONTPThe CDPPREFACTIONTP table contains the values of the privacy preference actiontype code and its descriptions. For example, "Call", "Do not call", "Opt In", or "OptOut".




BIGINT Not Null Yes

PPREF_ACTION_TP_CD Identifies the action to be taken basedon the privacy preference set by thecustomer or by company defaultsetting. For example, Call only, Mailonly, Do not call, Do not mail.

BIGINT Not Null Yes






TIMESTAMP Null No



CDPPREFCATThe CDPPREFCAT table contains a high level categorization of privacy preferencestypes.




BIGINT Not Null Yes



PPREF_CAT_CD Identifies the high level category ofthe privacy preference for thecustomer. For example, Sharing ofData, Solicitation, and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDPPREFREASONTPThe CDPPREFREASONTP identifies the reason for a privacy preference element.




BIGINT Not Null Yes

PPREF_REASON_TP_CD Identifies the reason given bycustomer for making a privacypreference selection.

BIGINT Not Null Yes






TIMESTAMP Null No





CDPPREFSEGTPThe CDPPREFSEGTP table stores the segment that a privacy preference regulationapplies to. This can be based on geography or a particular segment.




BIGINT Not Null Yes

PPREF_SEG_TP_CD Identifies the segment associated withthe privacy preference record. Forexample, FCRA, FCC, and so forth.

BIGINT Not Null Yes


BIGINT Null No






TIMESTAMP Null No




CDPPREFTPThe CDPPREFTP table contains the various types of privacy preferenceinformation.




BIGINT Not Null Yes

PPREF_TP_CD The specific privacy preference typewithin a particular category. Forexample: Credit Info, Personal Info,and so forth.

BIGINT Not Null Yes

PPREF_CAT_CD Privacy Preference Category Codeidentifies the high level category ofthe privacy preference for thecustomer. For example: Sharing ofData, Solicitation, and so forth.

BIGINT Null No






TIMESTAMP Null No



CDPREFIXNAMETPThe CDPREFIXNAMETP table contains information on a person's name prefix typecode. For example, Mr., Mrs., Dr., or others.





BIGINT Not Null Yes

PREFIX_NAME_TP_CD Identifies the party's name prefix. Forexample, Mr., Mrs., Dr., and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDPRIMARYTARGETMARKETTPThe CDPRIMARYTARGETMARKETTP table captures information about theprimary market that a product targets.




BIGINT Not Null Yes

PRIMARY_TARGET_MARKET_TP_CD

A primary market this producttargets. For example, "RetailCustomer", "SMB", or "LargeCorporate".

BIGINT Not Null Yes








TIMESTAMP Null No




VARCHAR(20) Null No

CDPRIORITYCATTPThe CDPRIORITYCATTP table contains the various priority categories that apriority type can belong to. "Task" is a typical priority category that is specificallyused by Task Management services.




BIGINT Not Null Yes

PRIORITY_CAT_TP_CD A code that classifies the varioustypes of priority. An example of it is"Task".

BIGINT Not Null Yes






TIMESTAMP Null No




CDPRIORITYTPThe CDPRIORITYTP table contains the various priorities for campaigns and thelike, and includes values such as high, medium, low.




BIGINT Not Null Yes

PRIORITY_TP_CD Identifies the priority of a task, acampaign, value and so forth.Examples include high, medium, low.

BIGINT Not Null Yes






TIMESTAMP Null No



PRIORITY_CAT_TP_CD A code that classifies the varioustypes of priority. An example of apriority category type code is "Task".

BIGINT Null No

CDPRODCONTRACTRELTPThe CDPRODCONTRACTRELTP table holds information on the type ofrelationship a product has with a contract.




BIGINT Not Null Yes



PROD_CONTR_REL_TP_CD

Identifies the type of the ProductContract Relationship. For example,"Party Selection".

BIGINT Not Null Yes






TIMESTAMP Null No



CDPRODRELATIONTPThe CDPRODRELATIONTP table holds information about the type of relationshipheld between two products.




BIGINT Not Null Yes

PRODUCT_REL_TP_CD Identifies the type of relationship thattwo products can have between oneanother.

BIGINT Not Null Yes

FROM_TO_NAME A short, meaningful description forthe "FROM" value of the relationship.For example, "Product 1 is the bundlefor Product 2". This value determinesthe relative direction for therelationship.


TO_FROM_NAME A short, meaningful description forthe "TO" value of the relationship. Forexample, "Product 2 is the bundlemember for Product 1". This valuedetermines the relative direction forthe relationship.







TIMESTAMP Null No



CDPRODRELTPThe CDPRODRELTP table identifies all the relationship types that can existbetween products.




BIGINT Not Null Yes

PRODREL_TP_CD Identifies the type of relationship thattwo products can have between oneanother.

BIGINT Not Null Yes

FROM_TO_NAME A short, meaningful label for the"from" value of the type code.


TO_FROM_NAME A short, meaningful label for the "to"value of the type code.





TIMESTAMP Null No




CDPRODSTRUCTURETPThe CDPRODSTRUCTURETP table captures information concerning how aproduct is structured.




BIGINT Not Null Yes

PROD_STRUC_TP_CD Identifies whether the product is astandalone product or represents abundling of other componentproducts.

BIGINT Not Null Yes






TIMESTAMP Null No



STRATEGY_RULE_ID The rule ID of the correspondingproduct structure. For example, abundled product can have a defaultstrategy_rule_id of 192 because thisID corresponds to the BundleStrategyrule.

VARCHAR(10) Null No

CDPRODTPThe CDPRODTP table contains the product type code values and theirdescriptions.





BIGINT Not Null Yes

PROD_TP_CD Identifies the type of productassociated with the contract (or atsome level within the product family).For example, a manufacturingcompany might have the producttypes "precision tools", "switches","defence", "electronics", and"automotive".

BIGINT Not Null Yes






TIMESTAMP Null No



PROD_SOURCE Identifies the source of the code. VARCHAR(100) Null No

CDPRODUCTIDENTIFIERTPThe CDPRODUCTIDENTIFIERTP table captures information about the productidentifier type code.




BIGINT Not Null Yes



PRODUCT_IDENTIFIER_TP_CD

Identifies the type of identifier for theproduct. For financial products,examples include an "InternationalSecurities Identification Number","National Securities IdentificationNumber", etc.

BIGINT Not Null Yes





MAX_ALLOWED_NUM Represents the maximum number ofactive identifiers that can be added tothe same product for the sameidentifier type.

SMALLINT Null No


TIMESTAMP Null No



CDPRODUCTPARTYROLETPThe CDPRODUCTPARTYROLETP contains the product party role type code andits descriptions.




BIGINT Not Null Yes

PRODUCT_PARTY_ROLE_TP_CD

A unique, system-generated key thatidentifies a product party role in thesystem. It identifies the type of rolethat a party can have on a product.For example "Supplier", "Vendor","Retailer", "Item Analyst", or"Consumer".

BIGINT Not Null Yes








TIMESTAMP Null No




VARCHAR(20) Null No

CDPRODUCTSTATUSTPThe CDPRODUCTSTATUSTP table captures information about the lifecycle statusof a product.




BIGINT Not Null Yes

STATUS_TP_CD The lifecycle status of the product.For example, "Available","Unavailable", "Obsolete", etc.

BIGINT Not Null Yes






TIMESTAMP Null No






VARCHAR(20) Null No

CDPROVSTATETPThe CDPROVSTATETP table contains province or state type code values. Forexample, WA, NJ, ON, or BC.




BIGINT Not Null Yes


BIGINT Not Null Yes






TIMESTAMP Null No



CDPURPOSETPThe CDPURPOSETP table identifies the purpose for a location as it relates to a roleon a contract. For example, statements are sent to the location for the owner of acontract.





BIGINT Not Null Yes

PURPOSE_TP_CD Identifies the purpose for the locationas it relates to a role on a contract.For example, the owner's residenceaddress is associated with the contractfor the purpose of sendingstatements.

BIGINT Not Null Yes






TIMESTAMP Null No



CDRELASSIGNTPThe CDRELASSIGNTP table contains the relationship assignment type code valuesand its descriptions. Party-to-party relationships can be assigned by a court orderor judgment, or by another party.




BIGINT Not Null Yes

REL_ASSIGN_TP_CD Identifies how the relationshipbetween the parties has beenassigned. For example, a custodialrelationship between a minor and anadult can be created by a court order.

BIGINT Not Null Yes








TIMESTAMP Null No



CDRELTPThe CDRELTP table contains trackable information about relationships thatcontacts can have among one another. For each relationship, there is a "from" and a"to" contact, and the relationship is usually named differently depending on whichcontact is made the "to" contact.




BIGINT Not Null Yes

REL_TP_CD Identifies the type of relationship thattwo parties can have between oneanother. For example: "is parent of" or"is employer of".

BIGINT Not Null Yes

FROM_TO_NAME A short, meaningful label for the"from" value of the relationship.


TO_FROM_NAME A short, meaningful label for the "to"value of the relationship.





TIMESTAMP Null No





CDREPOSITORYTPThe CDREPOSITORYTP table stores information about the content managementsystems and its related repositories for an organization.

This table is used by the following domains.v Account Domainv Product Domain


REPOSITORY_TP_CD Uniquely identifies the CMSRepository.

BIGINT Not Null Yes

NAME Name of the repository, can point tothe jndi name, connector name of theIICE etc.




CONTENT_SYSTEM The name of the CMS system. VARCHAR(250) Null No

NO_OF_KEYS Number of parameters defined by theCMS System, to uniquely identify acontent.

BIGINT Not Null No


TIMESTAMP Null No



CDRESIDENCETPThe CDRESIDENCETP table contains the residence type code values and theirdescriptions. For example, "suite", "apartment", or "building".





BIGINT Not Null Yes

RESIDENCE_TP_CD Identifies a type of residence for agiven address. Some examplesinclude Home, Apartment, and Suite.

BIGINT Not Null Yes






TIMESTAMP Null No



CDRESOLUTIONTPThis table contains the values of the entity resolution types and their descriptions.For example, collapsing, merging, or splitting a product record.




BIGINT Not Null Yes

RESOLUTION_TP_CD Identifies the current resolution for aparticular entity record. For example,collapsing, merging, or splitting aproduct record.

BIGINT Not Null Yes








TIMESTAMP Null No




VARCHAR(20) Null No

CDROLECATTPThe CDROLECATTP table contains a high-level categorization of types for roles.For example, grouping roles, hierarchy roles, relationship roles, and party macroroles.




BIGINT Not Null Yes

ROLE_CAT_TP_CD This is the role category type code. BIGINT Not Null Yes






TIMESTAMP Null No




CDROLETPThe CDROLETP table identifies various role types in the system. For example,"head of household" or "prospect".




BIGINT Not Null Yes

ROLE_TP_CD This is the role type, whichcorresponds to a particular rolecategory. Some examples include"head of household", "OnlineCustomer", "Prospect" etc.

BIGINT Not Null Yes

ROLE_CAT_TP_CD The category allows institutions toclassify the different types of roles.Some examples are Party RelationshipRoles, Hierarchy Roles, GroupingRoles, and so forth.

BIGINT Null No






TIMESTAMP Null No



CDRPTINGFREQTPThe CDRPTINGFREQTP table contains the reporting frequency type code valuesand their descriptions.





BIGINT Not Null Yes

RPTING_FREQ_TP_CD Describes the frequency that aparticular Party (CONTACT) wouldlike to receive consolidatedstatements. Sample values includeannually, semi-annually, monthly, andso forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDSERVICELEVELTPThe CDSERVICELEVELTP stores the service level agreements for an agreement.For example, "Service during business hours only" or "Service 24/7 through a callcenter".




BIGINT Not Null Yes

SERVICE_LEVEL_TP_CD Identifies the Service level associatedwith the contract. Some examplesinclude 24/7 call centre service orService during business hours only.

BIGINT Not Null Yes








TIMESTAMP Null No



CDSHAREDISTTPThe CDSHAREDISTTP table contains the values and descriptions of the sharedistribution type code that defines how the proceeds of the contract are distributedamong the party contract roles.




BIGINT Not Null Yes

SHARE_DIST_TP_CD Identifies how the proceeds of thecontract component get distributedamong the associated party contractroles. Examples include equal shares,50% share, and so on.

BIGINT Not Null Yes






TIMESTAMP Null No





CDSOURCEIDENTTPThe CDSOURCEIDENTTP table contains the type codes describing what the sourceidentifier values represent in the default source value table.




BIGINT Not Null Yes

SOURCE_IDENT_TP_CD Identifies the type for the sourceidentifier.

BIGINT Not Null Yes






TIMESTAMP Null No



CDSPECCASCADETPThe CDSPECCASCADETP table captures information about the type of cascadeaction a spec will have in a hierarchy.





BIGINT Not Null Yes

SPEC_CASCADE_TP_CD The cascade action the spec will havein a hierarchy. For example,"Cascaded to descendents", "Notcascaded to descendents", and soforth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDSPECUSETPThe CDSPECUSETP table captures information about the usage types a spec willbe used for.




BIGINT Not Null Yes

SPEC_USE_TP_CD The usage type that dictates how thespec will be used. For example, thespec could be used to govern productcommon attribute values.

BIGINT Not Null Yes








TIMESTAMP Null No



CDSTATUSREASONTPThe CDSTATUSREASONTP table captures information about the reason a productis in its current state.




BIGINT Not Null Yes

STATUS_REASON_TP_CD

Identifies the reason why the productis in its current state.

BIGINT Not Null Yes






TIMESTAMP Null No




VARCHAR(20) Null No


CDSUSPECTREASONTPThe CDSUSPECTREASONTP table describes the relevancy of a potential suspectduplicate for a particular party. For example, all elements for the party and thesuspect matched.




BIGINT Not Null Yes

SUSP_REASON_TP_CD Identifies the field that caused thedata match to occur.

BIGINT Not Null Yes





REASON_SCORE Reason Score is the numeric scoreassociated with the suspect reasoncode.

SMALLINT Null No


TIMESTAMP Null No



MATCH_ENG_TP_CD The matching engine used formatching parties.

BIGINT Null No

CDSUSPECTSOURCETPThe CDSUSPECTSOURCETP table indicates how a potential suspect duplicate wasidentified. For example, system-marked, or user-marked.





BIGINT Not Null Yes

SUSP_SOURCE_TP_CD Identifies the source of the SuspectReason Code: system-marked oruser-marked.

BIGINT Not Null Yes






TIMESTAMP Null No



CDSUSPECTSTATUSTPThe CDSUSPECTSTATUSTP describes the current status of the investigation into apotential suspect duplicate. For example, "parties not duplicate", or "critical changeresolved".




BIGINT Not Null Yes

SUSP_ST_TP_CD Indicates the current situation for aparticular suspect record. Forexample, suspect duplicate, notduplicate, under investigation, and soforth.

BIGINT Not Null Yes








TIMESTAMP Null No



CDSUSPECTTPThe CDSUSPECTTP table enables the replacement of default suspect duplicateprocessing logic with custom implementation. It also provides hooks to integratewith third party software to perform suspect search and matching.




BIGINT Not Null Yes

SUSPECT_TP_CD Captures various suspect types. Onerecord exists for each uniqueadd_action_code in theADDACTIONTYPE table.

BIGINT Not Null Yes





RULE_ID Primary key of the External RuleRecord.



TIMESTAMP Null No





CDTAXPOSITIONTPThe CDTAXPOSITIONTP table captures information about the relative tax positionoffered by a product.




BIGINT Not Null Yes

TAX_POSITION_TP_CD The relative tax position offered bythe product. Determines whether theproduct is tax neutral, provides thecustomer a tax advantage, or providesthe FI with a tax advantage.

BIGINT Not Null Yes






TIMESTAMP Null No




VARCHAR(20) Null No


CDTERMINATIONREASONTPThe CDTERMINATIONREASONTP table stores termination reasons for anagreement. For example, "Agreement terms & conditions violation" in the case of avalue package breakage.




BIGINT Not Null Yes

TERMINATION_REASON_TP_CD

Describes the reason why the contractis terminated. For example : "Terms &Conditions violated", "Core accountclosed by owner"

BIGINT Not Null Yes






TIMESTAMP Null No



CDUNDELREASONTPThe CDUNDELREASONTP table contains information on the valid values for theundeliverable reason type code. For example, bad addresses, incorrect zip code,and so on.




BIGINT Not Null Yes



UNDEL_REASON_TP_CD

Identifies the reason for not using aparticular address. Some examplevalues are "returned mail", "change inZIP code", and so forth.

BIGINT Not Null Yes






TIMESTAMP Null No



CDUSERROLETPCode Table for storing User Role Types. Each Type specific functions/data that auser can use within the application



BIGINT Not Null Yes

USER_ROLE_TP_CD The type code uniquely identifyingthe user role.

BIGINT Not Null Yes






TIMESTAMP Null No




CHARGECARDThe CHARGECARD table is a subtype of the PAYMENTSOURCE table, describingthe bank account information used to pay one or more contracts or accounts.




BIGINT Not Null Yes

CHARGE_CARD_TP_CD Identifies one type of charge cardfrom another. Some examples areVisa, MasterCard, or AmericanExpress.

BIGINT Not Null No

CHARGE_CARD_NUM The number that uniquely identifies acharge card.


EXPIRY_DT The date that the charge card willexpire.


ON_CARD_NAME The account name of the charge cardexactly as it appears on the chargecard.


BANK_NUM A unique identifier for the bank thatissued the chargecard, assignedoutside of the system.

VARCHAR(10) Null No




VARCHAR(20) Null No


BIGINT Null No

CLAIMThe CLAIM table contains claim information for coverage types that can beinsured in a contract. For example: "Auto Claim", or "break-in".




CLAIM_ID A unique, system-generated key thatidentifies a claim in the system.

BIGINT Not Null Yes

ADMIN_REF_NUM The reference identification numberfor the claim record.


CLAIM_NUMBER The Claim Number, a unique,assigned number, distinguishes oneclaim from all other claims.

VARCHAR(20) Null No

CLAIM_DETAIL_AMT The value of the claim detail. DECIMAL(17,3) Null No

CLAIM_PAID_AMT The amount paid on the claim. DECIMAL(17,3) Null No

OUTSTANDING_AMT The amount that is to be paid on theclaim.


BENEFIT_CLAIM_AMT The maximum amount that can bepaid on a claim.


CLAIM_TP_CD Identifies the type of claim that isrecorded. Some examples includeFire, Theft, Automobile, Collision, andso forth.

BIGINT Not Null No

LOB_TP_CD Identifies the unique type code for aspecific line of business. Someexamples are Life, Annuity, Disability,or Auto and Home.

BIGINT Null No

CLAIM_STATUS_TP_CD Identifies the status of a claim. Someexamples include Pending, Closed,and Rejected.

BIGINT Null No

CLAIM_CODE A code that identifies the procedureor claim service. For example,Orthodontics procedure code isD8000.

VARCHAR(20) Null No

STATUS_DT The date that the claim status wasupdated.

TIMESTAMP Null No

CLAIM_INCURRED_DT The date that the claim was incurred. TIMESTAMP Null No

REPORTED_DT The date that the claim was reported. TIMESTAMP Null No

DESCRIPTION Description provides extrainformation about the claim.





VARCHAR(20) Null No


BIGINT Null No

DETLAMT_CUR_TP The currency type for the claim detailamount.

BIGINT Null No



PAIDAMT_CUR_TP The currency type for the total claimbenefit amount.

BIGINT Null No

OUTSAMT_CUR_TP The currency type for the outstandingamount.

BIGINT Null No

BENEAMT_CUR_TP The currency type for the BenefitClaim amount.

BIGINT Null No

CLAIMCONTRACTThe CLAIMCONTRACT table contains a record of claims against a contract. Forexample, Automobile, Homeowners and Whole Life insurance policies.



CLAIM_CONTR_ID A unique, system-generated key thatidentifies a claim agreement in thesystem.

BIGINT Not Null Yes


BIGINT Not Null No


BIGINT Not Null No






TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


CLAIMROLEThe CLAIMROLE table contains information on the role a party plays on a claimrecord. For example, Party 1 reported the broken windshield, Party 2 is at fault.



CLAIM_ROLE_ID A unique, system-generated key thatidentifies a claim detail role in thesystem.

BIGINT Not Null Yes

CLAIM_ROLE_TP_CD Identifies a type of role a party playson a claim. Some examples includeClaimant, Witness and Third Party.

BIGINT Not Null No

CONT_ID A unique, system-generated key thatidentifies a party in the system.

BIGINT Not Null No


BIGINT Not Null No

DESCRIPTION Provides extra information. VARCHAR(255) Null No

START_DT The date that the claim role recordbecame effective, or was recorded.


END_DT The date that the claim role record isno longer effective.

TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

CONDITIONATTRIBUTEThe CONDITIONATTRIBUTE table records attributes that are added to theTermCondition Entity. The attribues are functionally "executable" and are used bybusiness rules to enforce the condition or to perform a calculation described by thecondition.




CONDITION_ATTRIBUTE_ID

A unique, system-generated key thatidentifies a Condition Attribute in thesystem.

BIGINT Not Null Yes

CONDITION_ATTR_TP_CD

Serves to group condition attributesand allows another level of detail.

BIGINT Not Null No

VALUE The value associated with thisCondition Attribute.


CONDITION_ID The ID of the term conditionassociated with this conditionattribute

BIGINT Not Null No




BIGINT Null No


VARCHAR(20) Null No

CONTACTA CONTACT is a legal entity that is tracked in the system, and can be furtherrefined by one of two subtypes: PERSON or ORG. CONTACT can include clients,suspect duplicates, prospects, CSRs, agents, competitors, contact persons, and anyother entity whose name, address, telephone number, and relationship to anothercontact is relevant.




BIGINT Not Null Yes

ACCE_COMP_TP_CD Represents one of the various types ofaccess a party can have to a computerand related technologies.

BIGINT Null No

PREF_LANG_TP_CD Identifies a preferred spokenlanguage. For example, English,French, Spanish, and so forth.

BIGINT Null No

CREATED_DT The date that the party was created. TIMESTAMP Not Null No



INACTIVATED_DT The date which the party row wasconsidered inactive through businessprocesses such as collapsing andsplitting, resulting in a new partyrecord created, and so forth.

TIMESTAMP Null No

CONTACT_NAME Identifies the full name of the personto be contacted within thecorporation. For trusts, this identifiesthe trustee.


PERSON_ORG_CODE A pointer to the type of party: personor organization.

CHAR(1) Not Null No

SOLICIT_IND Determines whether this party can besolicited at any location group.

CHAR(1) Null No

CONFIDENTIAL_IND Indicates whether this party'sinformation must be keptconfidential.

CHAR(1) Null No

CLIENT_IMP_TP_CD An identifier that uniquely separatesone client importance type fromanother. Examples include high,medium, or low.

BIGINT Null No

CLIENT_ST_TP_CD An identifier that uniquely separatesone client status type from another.Examples include prospect, active, orsuspended.

BIGINT Null No

CLIENT_POTEN_TP_CD An identifier that uniquely separatesone client potential type from another.Examples include high, medium, orlow.

BIGINT Null No

RPTING_FREQ_TP_CD Describes the frequency that aparticular Party (CONTACT) wouldlike to receive consolidatedstatements. Sample values includeannually, semi-annually, monthly, andothers. No business logic is currentlybeing invoked on this field.

BIGINT Null No

LAST_STATEMENT_DT The last time a consolidated statementwas sent to the Party. No businesslogic is currently being invoked onthis field.

TIMESTAMP Null No

PROVIDED_BY_CONT The ID of the party that referred thisparty to the organization.

BIGINT Null No

ALERT_IND Indicates whether there is any kind ofalert or restriction on this party. Thisfield is set by the system when anactive alert is associated with theParty record.

CHAR(1) Null No






VARCHAR(20) Null No


BIGINT Null No

DO_NOT_DELETE_IND Indicates whether the record can orcannot be deleted. A blank value or avalue of '0' means neither operationalor history data can be deleted. Avalue of '1' means both operationaland history data can be deleted. Avalue of '2' means only history datacan be deleted. A value of '3' meansonly operational data can be deleted.

CHAR(1) Null No


TIMESTAMP Null No


TIMESTAMP Null No

SOURCE_IDENT_TP_CD The type for the source identifier. BIGINT Null No

SINCE_DT Identifies the date that the contactbecame a customer.

TIMESTAMP Null No

LEFT_DT Identifies the date that the contactstopped being a customer.

TIMESTAMP Null No

ACCESS_TOKEN_VALUE

An access token is a means to protecta resource from unauthorized user orgroup access. When an access tokenvalue is associated with a resourcesuch as a database record, only usersor groups that are assigned that tokencan have access to that resource.

VARCHAR(50) Null No

PENDING_CDC_IND Indicates the presence of a pendingcritical data change for a party.

CHAR(1) Null No

ENTITYLINK_ST_TP_CD BIGINT Null No

ENTITY_ID The entity ID from virtual MDMwhen a party is persisted to thephysical MDM.

BIGINT Null No

ENTITY_TYPE The associated entity type of theentity ID from virtual MDM.

VARCHAR(25) Null No


CONTACTCDCThe CONTACTCDC table records information about critical data changes on aCONTACT.



CDC_ID A unique, system-generated key thatidentifies a critical data change in thesystem.

BIGINT Not Null Yes


BIGINT Not Null No

ENTITY_NAME The class name of the entity holdingthe critical data that was requestedfor update.


INSTANCE_PK The primary key of the entity holdingcritical data that was requested forupdate.

BIGINT Null No

CRITDATA An XML representation of the entitythat was requested for update.

CLOB(200K) Not Null No

CDC_ST_TP_CD The status of the critical data changerequest.

BIGINT Not Null No

REJ_REASON_TP_CD The reason for which a critical datachange is rejected.

BIGINT Null No

CREATED_DT The date when the pending criticaldata change is created.


EXPIRY_DT The date when the pending criticaldata change was resolved (eitheraccepted or rejected).

TIMESTAMP Null No


BIGINT Null No


VARCHAR(20) Null No




CONTACTDEMOGRAPHICSThe CONTACTDEMOGRAPHICS table contains various demographic data for acontact.



DEMOGRAPHICS_ID A unique, system-generated key thatidentifies a party demographicsrecord in the system.

BIGINT Not Null Yes

CONT_ID The ID of the party to whom thedemographics record belongs.

BIGINT Not Null No

DEMOGRAPHICS_TP_CD

Type of the demographics informationdefined in code tableCDDEMOGRAPHICSTP.

BIGINT Not Null No

SPEC_FMT_ID The ID of the spec format. BIGINT Not Null No

VALUE The demographics XML. XML Not Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

CONTACTMETHODThe CONTACTMETHOD table stores the ways that a CONTACT can be reached.For example, this can include e-mail address, phone number, fax number, websites, or others.



CONTACT_METHOD_ID

A unique, system-generated key thatidentifies a contact method in thesystem.

BIGINT Not Null Yes



ADDRESS_ID A unique, system-generated key thatidentifies an address in the system.There is no implementation for thisattribute in the object model. Youhave the option to create your ownimplementation.

BIGINT Null No

CONT_METH_CAT_CD Identifies the main category of contactmethod. For example: telephone,e-mail, PDA, and so forth.

BIGINT Not Null No

REF_NUM The actual text provided for thecontact method. For example, if thecontact method category type istelephone, then this column containsthe actual 10 digits for the phonenumber.





VARCHAR(20) Null No


BIGINT Null No

CONT_METH_STD_IND Indicates if this contact method hasbeen standardized.

CHAR(1) Null No

CONTACTMETHODGROUPThe CONTACTMETHODGROUP table, a subtype of the LOCATIONGROUP table,links contacts with addresses and specifies rules for reaching those contacts.




BIGINT Not Null Yes

CONTACT_METHOD_ID


BIGINT Not Null No



CONT_METH_TP_CD Identifies the subtypes of a ContactMethod Category Type Code. Forexample, if the category type istelephone, then the values of thesubtype code are home, business, cellphone, and so forth.

BIGINT Not Null No

METHOD_ST_TP_CD Identifies the status of a contactmethod. For example: disconnected orcancelled.

BIGINT Null No

ATTACH_ALLOW_IND Indicates whether attachments areallowed to be sent with this contactmethod. This indicator should only beused when the contact method refersto an e-mail.

CHAR(1) Null No

TEXT_ONLY_IND Indicates whether this can be sent astext only. This indicator should onlybe used when the contact methodrefers to an e-mail.

CHAR(1) Null No

MESSAGE_SIZE Represents the maximum size ofelectronic message that can be sent tothis contact method. This indicatorshould only be used when the contactmethod refers to an e-mail.

VARCHAR(20) Null No

COMMENT_DESC A comment or description. VARCHAR(100) Null No




VARCHAR(20) Null No


BIGINT Null No

CONTACTRELThe CONTACTREL records the relationship between two parties. For example:FROM CONTACT: Sue Smith; RELATIONSHIP: child of; TO CONTACT: GregSmith.



CONT_REL_ID A unique, system-generated key thatidentifies a party relationship in thesystem.

BIGINT Not Null Yes



REL_TP_CD Identifies the type of relationship thattwo parties can have between oneanother. For example, "is parent of,""is employer of," and so forth.

BIGINT Not Null No

REL_DESC Refers to comments that a user mighthave concerning the partyrelationship.





TIMESTAMP Null No

TO_CONT_ID A unique, system-generated key thatidentifies a party in the system.

BIGINT Not Null No

FROM_CONT_ID A unique, system-generated key thatidentifies a party in the system.

BIGINT Not Null No




VARCHAR(20) Null No

REL_ASSIGN_TP_CD Identifies how the relationshipbetween the parties has beenassigned. For example, a custodialrelationship between a minor and anadult can be created by a court order.

BIGINT Null No


BIGINT Null No

END_REASON_TP_CD Identifies the cause for a party toparty relationship being ended. Forexample, "divorce" can be used as anend reason.

BIGINT Null No

CONTEQUIVThe CONTEQUIV table provides the link between the system Party ID and theexternal administrative system Party ID.



CONT_EQUIV_ID A unique, system-generated key thatidentifies a party equivalency in thesystem.

BIGINT Not Null Yes




BIGINT Not Null No


BIGINT Not Null No

ADMIN_CLIENT_ID Uniquely identifies the primary keyfor the administrative source system.

VARCHAR(20) Null No






VARCHAR(20) Null No


BIGINT Null No

CONTMACROROLEThe CONTMACROROLE table represents a high-level role a contact plays in thesystem. For instance, the contact can be captured in the context of a prospect and,as such, its macro role is recorded as "prospect".



CONT_MACRO_ROLE_ID

A unique, system-generated key thatidentifies a party macro role in thesystem.

BIGINT Not Null Yes


BIGINT Not Null No

ROLE_TP_CD This is the role type, whichcorresponds to a particular rolecategory. Some examples include"head of household", "OnlineCustomer", "Prospect", and so forth.

BIGINT Not Null No

START_DT The date when this role becomesactive


END_DT The date when this role becomesinactive

TIMESTAMP Null No



DESCRIPTION A free form description for this role. VARCHAR(255) Null No

END_REASON_TP_CD Identifies the cause for why arelationship was ended. For example,a spousal party to party relationshipcan be ended for a "divorce," reason.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No

CONTRACTThe CONTRACT table contains information representing the purchase of aPRODUCT. For example, this purchase can include various scenarios including adisability insurance plan, a savings account, a GIC, and so forth.




BIGINT Not Null Yes

CONTR_LANG_TP_CD Identifies a spoken language, such asEnglish, French, Spanish, or German.When used as part of the primary keyof a code value lookup table, theLanguage Type Code also representsthe language of the code name.

BIGINT Null No


BIGINT Null No

FREQ_MODE_TP_CD Identifies the frequency of thepayments made on the contract. Forexample, monthly or annual.

BIGINT Null No

BILL_TP_CD An identifier that uniquely separatesone billing type from another. Forexamples, Regular, Direct, or Payrolldeduction.

BIGINT Null No



REPL_BY_CONTRACT A unique, system-generated key thatidentifies a contract in the system,that is replacing this particularcontract.

BIGINT Null No

PREMIUM_AMT The premium payment due at theintervals identified by the frequencymode type code.


NEXT_BILL_DT The date of the next bill for thecontract.

TIMESTAMP Null No

CURR_CASH_VAL_AMT The cash value of the contract. DECIMAL(17,3) Null No

LINE_OF_BUSINESS Represents a high-level productgrouping (Life, Annuity, Disability, orAuto and Home.)

VARCHAR(30) Null No

BRAND_NAME The title of the subsidiary that soldthis contract.

VARCHAR(30) Null No

SERVICE_ORG_NAME The organization that services thecontract.

VARCHAR(70) Null No

BUS_ORGUNIT_ID The lowest level of identificationwithin the servicing organization ofthis contract.

VARCHAR(30) Null No

SERVICE_PROV_ID The unique identifier that identifiesthe servicing agent or broker for thiscontract.

VARCHAR(30) Null No




VARCHAR(20) Null No


BIGINT Null No

ISSUE_LOCATION Describes the location where thecontract was issued.

VARCHAR(30) Null No

ADMIN_CONTRACT_ID The actual text or number that is usedin the administrative source system toidentify a contract.



BIGINT Null No

PREMAMT_CUR_TP The currency type for the premiumamount.

BIGINT Null No

CASHVAL_CUR_TP The currency type for the current cashvalue amount.

BIGINT Null No



ACCESS_TOKEN_VALUE


VARCHAR(50) Null No

MANAGED_ACCOUNT_IND

Indicates whether or not this contractis a managed account. A managedaccount is a contract that is managedby this system. The opposite of amanaged account is a referenceaccount. A reference account is acontract that is managed by anexternal system.

CHAR(1) Null No

AGREEMENT_NAME The name of the contract oragreement.


AGREEMENT_NICKNAME

The alternate name of the contract. VARCHAR(120) Null No

SIGNED_DT The date on which the contract issigned.

TIMESTAMP Null No

EXECUTED_DT The date on which the contractbecomes active.

TIMESTAMP Null No

END_DT The date on which the contract isconsidered ended.

TIMESTAMP Null No

REPLACES_CONTRACT The identifier of the contract that thiscontract replaces (if applicable).

BIGINT Null No

ACCOUNT_LAST_TRANSACTION_DT

The date on which a transaction waslast executed against this contract.

TIMESTAMP Null No

TERMINATION_DT The date on which the contract isterminated.

TIMESTAMP Null No

TERMINATION_REASON_TP_CD

The reason for which the contract isterminated.

BIGINT Null No

AGREEMENT_DESCRIPTION

The description of the contract. VARCHAR(250) Null No

AGREEMENT_ST_TP_CD

The status of the contract. BIGINT Null No

AGREEMENT_TP_CD

The type of the contract. BIGINT Null No

SERVICE_LEVEL_TP_CD The service level provided for thiscontract. For example: "24/7 CallCenter service" or "Service duringbusiness hours only".

BIGINT Null No

LAST_VERIFIED_DT The date on which the contract waslast verified.

TIMESTAMP Null No

LAST_REVIEWED_DT The date on which the contract waslast reviewed.

TIMESTAMP Null No

PRODUCT_ID The Product identifier on which thecontract is based.

BIGINT Null No



CLUSTER_KEY This column can optionally be usedas a clustering index. A clusteringindex is an index that determineshow rows are physically ordered(clustered) in a table space. If notspecified, the default value for thiscolumn is NOT NULL.

BIGINT Null No

CONTRACTCOMPONENTThe CONTRACTCOMPONENT table contains information on contractcomponents, such as base, riders, or others. A contract component represents a partof a contract. Every contract must have at least one base component.



CONTR_COMPONENT_ID


BIGINT Not Null Yes

CONTRACT_ST_TP_CD Identifies the status of the contract.For example, "active", "pending","lapse pending", or "cancelled". Thesevalues are provided by theadministrative source systems of thecontract.

BIGINT Not Null No

PROD_TP_CD Identifies the type of productassociated with the contract (or atsome level within the product family).Examples include Universal Life,Savings, Checking, Term Life, Auto,and so forth.

BIGINT Null No


BIGINT Not Null No

CURR_CASH_VAL_AMT

The cash value of the contractcomponent.


PREMIUM_AMT The premium payment due at theintervals identified by the frequencymode type code for this contractcomponent.


ISSUE_DT The date when the contractcomponent was issued.

TIMESTAMP Null No



VIATICAL_IND Determines whether this contract isunder a viatical arrangement. Aviatical settlement is a transaction thatoccurs when a person with a terminalor chronic illness sells a life insurancepolicy in return for a discountedamount of the death benefit. Theviator, the individual who sells thepolicy, sells his or her interest in apolicy to a viatical settlementcompany. The beneficial interest inthe policy is then purchased by thirdparty investors. A viaticated policy isa life insurance policy that has beensold.

CHAR(1) Null No

BASE_IND Used to identify the base componentof the contract. Every contract has atleast one component, the basecomponent.

CHAR(1) Null No




VARCHAR(20) Null No

CONTR_COMP_TP_CD A numeric representation of the typeof coverage for the product. Forexample: Base, Rider, Base Increase,Integrated.

BIGINT Null No


BIGINT Null No

SERV_ARRANGE_TP_CD

Indicates whether this contract isadministered by the organization or athird party.

BIGINT Null No

HOLDING_ID The primary key of a party holdingrecord.

BIGINT Null No

EXPIRY_DT The date when this record becomesinactive.

TIMESTAMP Null No

PREMAMT_CUR_TP The currency type for the premiumamount.

BIGINT Null No

CASHVAL_CUR_TP The currency type for the current cashvalue amount.

BIGINT Null No



CLUSTER_KEY This column can optionally be usedas a clustering index. A clusteringindex is an index that determineshow rows are physically ordered(clustered) in a table space. If notspecified, the default value for thiscolumn is null.

BIGINT Null No

CONTRACTCOMPVALThe CONTRACTCOMPVAL table allows you to model numeric values on theContract Component, presenting you with a mechanism to extend informationassociated with a contract component that is only available through back-endsystems. Certain contract features such as Balances in accounts, limits, terms andrates are typically what can be modeled using the Value entity. A contractcomponent value has the following characteristics: (i) Allows extending theinformation that is held within an contract component or contract component row;(ii) Any number of values can be associated with an contract component; (iii)Allow values are defined through Code Tables; (iv) Has a description; (v) Has aspecific type; (vi) Has a specific value; (vii) Has a status; (viii) Has a validityperiod or is indefinite.



CONTR_COMP_VAL_ID

A unique, system-generated key thatidentifies a contract component valuein the system.

BIGINT Not Null Yes

DOMAIN_VALUE_TP_CD

Domain Value Type Code, in a givendomain, identifies the specific valuesthat are captured. For example,Integer value, Date value, etc.

BIGINT Not Null No

VALUE_STRING The numeric value associated withthe Value Type Code.


CONTR_COMPONENT_ID


BIGINT Not Null No




TIMESTAMP Null No


BIGINT Null No






VARCHAR(20) Null No

CONTRACTRELThe CONTRACTREL table represents the relationship that an agreement can havewith another agreement.



CONTRACT_REL_ID A unique, system-generated key thatidentifies a contract relationship inthe system.

BIGINT Not Null Yes

TO_CONTRACT_ID A unique, system-generated key thatidentifies a contract in the system.

BIGINT Not Null No

FROM_CONTRACT_ID A unique, system-generated key thatidentifies a contract in the system.

BIGINT Not Null No

CONTR_REL_TP_CD Describes the type of relationship.Examples include master contract andcontract term.

BIGINT Not Null No

CONTR_REL_ST_TP_CD Identifies the status of therelationship between two contracts,such as "pending", "active", and"terminated".

BIGINT Null No




TIMESTAMP Null No

REL_DESCRIPTION Provides for comments that a usermight have concerning the contractrelationship.



BIGINT Null No






VARCHAR(20) Null No

CONTRACTROLEThe CONTRACTROLE table represents an association that links contacts to thevarious roles they can have on a contract.



CONTRACT_ROLE_ID A unique, system-generated key thatidentifies a party contract role in thesystem.

BIGINT Not Null Yes


BIGINT Not Null No

CONTR_COMPONENT_ID


BIGINT Not Null No

CONTR_ROLE_TP_CD Identifies the type of role that a partycan have on a contract. For example"beneficiary", "owner", "insured", or"payer".

BIGINT Not Null No

REGISTERED_NAME The party contract role name as itappears on the contract.


DISTRIB_PCT Used for beneficiary type, it indicatesthe share that this party has interestin regarding this contract component.


IRREVOC_IND Indicates whether this role can bechanged without consent.

CHAR(1) Null No




TIMESTAMP Null No

RECORDED_START_DT The date when the party'srelationship to the contract becamelegally effective. This is commonly thedate which the party signed thecontract.

TIMESTAMP Null No

RECORDED_END_DT The date that the party's relationshipto the contract is no longer effective.

TIMESTAMP Null No






VARCHAR(20) Null No

SHARE_DIST_TP_CD The values and descriptions defininghow the proceeds of the contract aredistributed among the party contractroles.

BIGINT Null No

ARRANGEMENT_TP_CD

The type of agreement that the partycontract role has with the contract.For example: time delay arrangementsuch as a common disaster.

BIGINT Null No

ARRANGEMENT_DESC Provides extra information that can beused either as an additional definitionof the arrangement or as free formcomments used by the user toprovide further meaning to thearrangement.



BIGINT Null No

END_REASON_TP_CD Identifies the cause for why a rolewas ended. For example, a beneficiaryrelationship can be ended for a deathreason.

BIGINT Null No

CONTRACTROLERELThe CONTRACTROLEREL table represents an association that links a contact'scontract roles together. For example, a role relationship is used to determine thecustodian role for a minor on a given contract.



CONTR_ROLE_REL_ID A unique, system-generated key thatidentifies a party contract rolerelationship in the system.

BIGINT Not Null Yes

REL_TP_CD Identifies the type of relationship thattwo parties can have between oneanother, within the context of thecontract. For example: "is custodianof", "is minor for", and so forth.

BIGINT Not Null No



ROLE_REL_DESC Provides a space to store usercomments of the party rolesrelationship.


CONTR_ROLE_FROM_ID

A unique, system-generated key thatidentifies a party contract role in thesystem.

BIGINT Not Null No

CONTR_ROLE_TO_ID A unique, system-generated key thatidentifies a party contract role in thesystem.

BIGINT Not Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

END_REASON_TP_CD Identifies the cause for why a rolerelationship was ended. For example,a custodial relationship can be endedfor a "coming of age" reason.

BIGINT Null No

CONTSUMMARYThe CONTSUMMARY table contains a summary view of a contact record andcontains indicators that track what information is stored about a particular party.




BIGINT Not Null Yes

PRIVPREF_IND Determines whether there is anyparty privacy preference on this party.This field is set by the system when aparty privacy preference is associatedwith the Party record.

SMALLINT Not Null No



MISCVALUE_IND Determines whether there is anyparty miscellaneous value on thisparty. This field is set by the systemwhen a party miscellaneous value isassociated with the Party record.


CONTACTREL_IND Determines whether there is anyparty relationship on this party. Thisfield is set by the system when aparty relationship is associated withthe Party record.


BANKACCOUNT_IND Determines whether there is anyparty bank account on this party. Thisfield is set by the system when aparty financial profile is associatedwith the Party record.


CHARGECARD_IND Determines whether there is anyparty charge card on this party. Thisfield is set by the system when aparty financial profile is associatedwith the Party record.


PAYROLLDEDUCT_IND Determines whether there is anyparty payroll deduction on this party.This field is set by the system when aparty financial profile is associatedwith the Party record.


INCOMESOURCE_IND Determines whether there is anyparty income source on this party.This field is set by the system when aparty financial profile is associatedwith the Party record.


IDENTIFIER_IND Determines whether there is anyparty identifier on this party. Thisfield is set by the system when aparty identifier is associated with theParty record.


ALERT_IND Indicates whether there is any kind ofalert or restriction on this party. Thisfield is set by the system when anactive alert is associated with theParty record.


CONTEQUIV_IND Indicates whether there is any contactequivalent on this party. This field isset by the system when a contactequivalent is associated with theParty record.


INTERACTION_IND Indicates whether there is anyinteraction on this party. This field isset by the system when an interactionis associated with the Party record.


ADDRESSGROUP_IND Indicates whether there is any partyaddress group on this party. This fieldis set by the system when a partyaddress group is associated with theParty record.




CONTMETHGROUP_IND

Indicates whether there is any partycontact method group on this party.This field is set by the system when aparty contact method group isassociated with the Party record.


LOBREL_IND Indicates whether there is any partyline of business relationship on thisparty. This field is set by the systemwhen a party line of businessrelationship is associated with theParty record.





BIGINT Null No


VARCHAR(20) Null No

DEFAULTSOURCEVALThe DEFAULTSOURCEVAL table identifies a business data element that wasdefaulted during data collection or migration. For example, a date may beincomplete in the source system and as a result must be defaulted in order toprovide the system an accurate and complete date.



DEFAULT_SRC_VAL_ID A unique, system-generated key thatidentifies an default object in thesystem.

BIGINT Not Null Yes

ENTITY_NAME The name of the business entity thathas the defaulted values.


INSTANCE_PK The actual primary key of the row inthe logical entity that has thedefaulted values.

BIGINT Null No

COLUMN_NAME The actual name of the column wherethe default occurred.


SOURCE_VALUE The value of the Logical ColumnName prior to defaulted to thesystem database column value. Forexample: established date - Jan 31,2002; Source Value is: Jan 2002.




DEFAULT_VALUE The value of the Logical ColumnName after it is defaulted to thesystem database column value. Forexample: established date - Jan 2002.Default Value is: Jan 31, 2002.







VARCHAR(20) Null No


BIGINT Null No


BIGINT Null No

SOURCE_IDENTIFIER Identifies the source of the value. VARCHAR(100) Null No

EME_RECBKTDeme_recbktd stores the derived data information for a record that is used forfirst-pass determination of records for comparison. All records having the samebucket hash (bkthash) belong in the same bucket, and compare to each other. Arecord can belong



RECNO Unique record number fromeme_rechead.

BIGINT Not Null Yes

SRCRECNO Source record, from the EmbeddedMatching Engine configuration.

SMALLINT Not Null Yes

BKTHASH Hash value of the derived data. BIGINT Not Null Yes


EME_RECCHKD



RECNO BIGINT Not Null Yes

SRCRECNO SMALLINT Not Null No

CHKSUM BIGINT Not Null No

EME_RECCMPDThis derived data table stores the comparison data information for a record that isused for scoring records that met the bucketing pass. The purpose of storinginformation in eme_reccmpd, rather than spreading the information among thevarious record data tables, is to provide a performance enhancement.



RECNO Unique record number fromeme_rechead.

BIGINT Not Null Yes

SRCRECNO Source record, from the EmbeddedMatching Engine configuration.


CMPSEQNO Comparison sequence number. SMALLINT Not Null Yes

CMPVAL The comparison data. The comparisondata itself is a derived copy of thesource record from which it wasobtains, altered to provide high-speedcomparisons.


EME_RECHEADThe eme_rechead table is used to store one row for each record presented to theEmbedded Matching Engine.



RECNO Automatically assigned internalidentification number.

BIGINT Not Null No

SRCRECNO Source system identification in theEmbedded Matching Engineconfiguration.

SMALLINT Not Null Yes

SRCID Source system primary identifier forthe record.




TXNID User specified transaction identifier,not managed by the EmbeddedMatching Engine.

BIGINT Not Null No

ENTITYCONDITIONRELThe ENTITYCONDITIONREL table stores the association between theTermCondition the entity (PRODUCT or CONTRACT) to which it applies.



ENTITY_CONDITION_REL_ID

A unique, system-generated key thatidentifies a Entity ConditionRelationship in the system.

BIGINT Not Null Yes

INSTANCE_PK The Primary key of the entity towhich the term and condition isrelated. It can be the primary key ofeither PRODUCT or CONTRACT.

BIGINT Not Null No

ENTITY_NAME The type of entity that the term andcondition is related to. It can be eitherPRODUCT or CONTRACT.


CONDITION_ID The identifier of the term andcondition attached to the entity.

BIGINT Not Null No




TIMESTAMP Null No




BIGINT Null No


VARCHAR(20) Null No


ENTITYCONTENTREFERENCEThe ENTITYCONTENTREFERENCE table stores the content references of thecontent assets stored in external CMS.



CONTENT_REF_ID A unique, system-generated key thatidentifies a Content Reference in thesystem.

BIGINT Not Null Yes

CONTENT_REF_1 Parameter defined in the CMS systemto identify the Content Reference.








INSTANCE_PK The actual primary key of the row inthe logical entity that is associatedwith the content reference.

BIGINT Null No

ENTITY_NAME The name of the business entity. VARCHAR(250) Null No

CONTENT_VERSION The version of the content referencein the CMS system.


START_DATE The date when this record becomesactive.


END_DATE The date when this record becomesinactive.

TIMESTAMP Null No

REPOSITORY_TP_CD Identifies the Repository within theCMS System.

BIGINT Null No




BIGINT Null No


VARCHAR(20) Null No

DOCUMENT_NAME The name of the document in theCMS system.


AUTHOR The document author name in theCMS system.



ENTITYROLEThe ENTITYROLE table stores information about the role or roles that a particularentity can play on a particular collection. For example, grouping, hierarchy, orparty-to-party relationships.



ENTITY_ROLE_ID A unique, system-generated key thatidentifies an entity role in the system.

BIGINT Not Null Yes

ROLE_TP_CD This is the role type, whichcorresponds to a particular rolecategory. Some examples include"head of household", "OnlineCustomer", "Prospect", and so forth.

BIGINT Not Null No

CONTXT_ENTITY_NAME

The name of the entity that a role isbeing provided for.


CONTXT_INSTANCE_PK

The primary key of the entity. BIGINT Not Null No

ROLE_ENTITY_NAME The entity name of the role player. VARCHAR(30) Null No

ROLE_INSTANCE_PK The primary key of the role player. BIGINT Null No

START_DT The date when this role becomesactive.


END_DT The date when this role becomesinactive.

TIMESTAMP Null No

DESCRIPTION A freeform description for this role. VARCHAR(255) Null No

END_REASON_TP_CD The reason why a relationship ended.For example, a spousal party-to-partyrelationship can be ended by a"divorce" reason.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No


ENTITYSPECUSEThe ENTITYSPECUSE table defines the way a spec will be used to define an entitysuch as a product.



SPEC_USE_ID A unique, system-generated key thatidentifies the usage of a spec by anentity in the system.

BIGINT Not Null Yes

ENTITY_NAME The type of entity this spec use isrelated to.


INSTANCE_PK The primary key of the related entity. BIGINT Not Null No

SPEC_ID A unique, system-generated key thatidentifies a spec in the system.

BIGINT Not Null No

SPEC_USE_TP_CD The code assigned to the spec usetype.

BIGINT Not Null No

SPEC_CASCADE_TP_CD

The code assigned to the cascadeaction type for a spec. For example, ifthis spec is cascaded to descendentsin the entity's hierarchy.

BIGINT Not Null No

EXPLICIT_DEF_IND Indicates that the spec has beendefined for the first time on thisentity.

CHAR(1) Not Null No

METADATA_INFO_TP_CD

The code assigned to the metadatainfo type.

BIGINT Not Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

DESTINATION_ENTITY_NAME

The destination entity this spec use isrelated to.


SEARCHABLE_IND This is an indicator ("Y" or "N") whichindicates whether the associated specis to be searchable in the context ofthe destination entity.

CHAR(1) Null No


FINANCIALPRODUCTThe FINANCIALPRODUCT table contains information about products that are ahardened subtype of PRODUCT.



PRODUCT_ID A unique, system-generated key thatidentifies a product in the system.

BIGINT Not Null Yes

TAX_POSITION_TP_CD The relative tax position offered bythe product. Determines whether theproduct is tax neutral, provides thecustomer a tax advantage, or providesthe FI with a tax advantage.

BIGINT Null No

ACCOUNT_REQUIRED_TP_CD

Indicates whether the productrequires an account or not.

BIGINT Null No

CURRENCY_TP_CD Identifies the currency the product istraded in.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No

GOODSPRODUCTThe GOODSPRODUCT table contains information on a product that is a hardenedsubtype of product.




BIGINT Not Null Yes






VARCHAR(20) Null No


BIGINT Null No

HOLDINGThe HOLDING table contains records of personal holdings. For example, a list ofassets and liabilities such as Vehicles, Dwellings and Mortgage.



HOLDING_ID A unique, system-generated key thatidentifies a party holding in thesystem.

BIGINT Not Null Yes

HOLD_TP_CD Identifies a type of party holding.Some examples include Vehicles,Property, or Stocks.

BIGINT Not Null No

HOLDING_CODE Identifies the holding code: V -vehicle; P - property.

CHAR(1) Not Null No

HOLDING_VALUE_AMT

The value of the specific holding. DECIMAL(17,3) Null No





TIMESTAMP Null No




VARCHAR(20) Null No




BIGINT Null No

VALUAMT_CUR_TP The currency type for the holdingvalue amount.

BIGINT Null No

IDENTIFIERThe IDENTIFIER table provides an additional way of distinguishing a contact thatis natural to them. For example: social security number, driver's license number, orpassport number.



IDENTIFIER_ID A unique, system-generated key thatidentifies a party identification in thesystem.

BIGINT Not Null Yes

ID_STATUS_TP_CD Identifies the status of the identifierprovided by the party. For example:"applied for," "expired," "certified,"and so forth.

BIGINT Null No


BIGINT Not Null No

ID_TP_CD Identifies the type of identifierprovided by the party. For example:"social security number," "passport,""driver's license number," and soforth.

BIGINT Not Null No

REF_NUM The actual identifier text provided bya party. For example, if theIdentification Type Code indicates asocial security number was provided,then this column contains the actual 9characters.

VARCHAR(50) Null No




TIMESTAMP Null No

EXPIRY_DT The date on which the particularidentification expires, such as aPassport expiry date.

TIMESTAMP Null No






VARCHAR(20) Null No


BIGINT Null No

ASSIGNED_BY Used to associate a particular contractrole to a particular identifier. Forexample: an employee number can beused as an identifier on a groupcontract.

BIGINT Null No

IDENTIFIER_DESC Provides extra space for informationthat can be used for an additionaldefinition or as free form commentsto provide further meaning.


ISSUE_LOCATION The issue location of the identificationitem.

VARCHAR(30) Null No


TIMESTAMP Null No


TIMESTAMP Null No

SOURCE_IDENT_TP_CD

Identifies the type for the sourceidentifier.

BIGINT Null No

INACTIVATEDCONTThe INACTIVATEDCONT table records when a CONTACT is no longer consideredactive in a company. When an entity becomes inactive, modifications to theINACTIVATEDCONT records are ended.




BIGINT Not Null Yes

INACT_BY_USER The ID of the user who inactivatedthe associated party.

VARCHAR(20) Null No

INACT_REASON_TP_CD

Contains the valid values forinactivating a party record, such as'collapsed', 'split' and 'deceased'.

BIGINT Not Null No



COMMENTS A free form text field used forentering additional informationconcerning the inactivated party.





VARCHAR(20) Null No


BIGINT Null No

INACTIVECONTLINKThe INACTIVECONTLINK table maintains the linkage from the CONTACT(target) to an INACTIVATEDCONT (source) entity, tracking a collapsed or splitCONTACT that is now an INACTIVATEDCONT, as well as tracking the link that ithas with the newly created CONTACT (as a result of a collapse or split).



INACT_CONT_LINK_ID A unique, system-generated key thatidentifies an inactivated party link inthe system.

BIGINT Not Null Yes

TARGET_CONT_ID A unique, system-generated key thatidentifies a party in the system.

BIGINT Not Null No

SOURCE_CONT_ID A unique, system-generated key thatidentifies a party in the system.

BIGINT Not Null No

LINK_REASON_TP_CD Describes the reason why two partiesare linked. For example, "Sourcecollapsed into target", "Sourceduplicated as target", etc.

BIGINT Not Null No




VARCHAR(20) Null No




BIGINT Null No

INACTIVEPRODLINKThis table maintains the linkage between active and inactive entities. Its function isto track entities that have been collapsed or split and are now inactive.



INACT_ENTITY_LINK_ID

A unique, system-generated key thatidentifies an inactivated entity linkrow in the system.

BIGINT Not Null Yes

TARGET_ENTITY_ID A unique, system generated key thatidentifies an entity in the system.

BIGINT Not Null No

SOURCE_ENTITY_ID A unique, system generated key thatidentifies an entity in the system.

BIGINT Not Null No

LINK_REASON_TP_CD Describes the reason why two partiesare linked. For example, "Sourcecollapsed into target", "Sourceduplicated as target", and so forth.

BIGINT Not Null No




VARCHAR(20) Null No


BIGINT Null No

INCOMESOURCEThe INCOMESOURCE table contains information, provided and attested-to by theparty, detailing the CONTACT's investment experience and financial standing. Thisinformation is used to determine a CONTACT's suitability in purchasing a newinvestment.




INCOME_SOURCE_ID A unique, system-generated key thatidentifies an income source in thesystem.

BIGINT Not Null Yes


BIGINT Null No


BIGINT Not Null No

INCOME_SRC_TP_CD Identifies the type of income sourcethat the party provided. For example,"annual salary," "estimated net worth,""Ownership of Bonds," and so forth.

BIGINT Null No

INCOME_SOURCE_DESC

Stores comments provided by theuser concerning the income sourceprovided by the party.


ANNUAL_AMT Annual Amount is used when theIncome Source Type Code requires anamount provided by the party.

DECIMAL(17,3) Not Null No

INVEST_EXPER_YRS Investment Experience in Years isused when the Income Source TypeCode requires a length of ownershipin years to be provided by the party.

SMALLINT Null No

INFO_OBTAINED_DT The date that the information wasobtained from the party.





VARCHAR(20) Null No


BIGINT Null No

INSURANCEPRODUCTThe INSURANCEPRODUCT table contains information on products that are ahardened subtype of PRODUCT.




BIGINT Not Null Yes






VARCHAR(20) Null No


BIGINT Null No

LOBRELThe LOBREL table represents the party ownership by a line of business. Forexample, John Smith owned by Home Insurance, or Jane Doe owned by Retailbanking.



LOB_REL_ID A unique, system-generated key thatidentifies a lob relationship with anentity in the system.

BIGINT Not Null Yes

ENTITY_NAME Entity Name is the name of thebusiness entity that is part of thisrelationship.


INSTANCE_PK Entity Instance primary key is theactual primary key of the row in thelogical entity that is part of thisrelationship.

BIGINT Not Null No

LOB_TP_CD Identifies the unique type code for aspecific line of business.

BIGINT Not Null No

LOB_REL_TP_CD Identifies the unique type code for aspecific line of business relationshiptype.

BIGINT Not Null No




TIMESTAMP Null No






VARCHAR(20) Null No


BIGINT Null No

LOCATIONGROUPThe LOCATIONGROUP table links locations, such as addresses and telephonenumbers, to contacts and contains rules for use.




BIGINT Not Null Yes

UNDEL_REASON_TP_CD

Identifies the reason for not using aparticular address. Some examplevalues are "returned mail," "change inzip code," and so forth.

BIGINT Null No


BIGINT Not Null No

MEMBER_IND Indicates that the party is a memberof the "household", in this case asimplistic representation, as it is onlyused in conjunction with commonaddresses.

CHAR(1) Null No

PREFERRED_IND Indicates that the Party "prefers" touse this particular location forcorrespondence.

CHAR(1) Null No

SOLICIT_IND Determines whether this party besolicited at this specific locationgroup.

CHAR(1) Null No

LOC_GROUP_TP_CODE Determines the type of the locationgroup. The value "A" indicates anaddress, and the values "C" indicatescontact method.

CHAR(1) Not Null No



EFFECT_START_MMDD The two-digit month and two-digitday which the Party wishes thiscontact point to be used. It is usedwith the Effective End Month Day toidentify a date range of when thisparty contact point relationshipshould be used.

SMALLINT Null No

EFFECT_END_MMDD The two digit month and two digitday which the Party wishes thiscontact point to be used. It is usedwith the Effective Start Month Day toidentify a date range of when thisparty contact point relationshipshould be used.

SMALLINT Null No

EFFECT_START_TM The time of day when a party isavailable at this location group.

INTEGER Null No

EFFECT_END_TM The time of day when a party is nolonger available at this locationgroup.

INTEGER Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


TIMESTAMP Null No


TIMESTAMP Null No


BIGINT Null No


MACROROLEASSOCThe MACROROLEASSOC table represents an association between a contact'smacro role and its child data. For instance, as "prospect" (macro role), the systemcan capture that party's email address (associated party child data),"[email protected]". Child data must exist before it can be associated with amacro role.



MACROROLE_ASSOC_ID

A unique, system-generated key thatidentifies a party macro roleassociation in the system.

BIGINT Not Null Yes

CONT_MACRO_ROLE_ID

A unique, system-generated key thatidentifies a party macro role in thesystem.

BIGINT Not Null No

ENTITY_NAME The name of the entity which is beingassociated with the party macro role.This will be the name of the entityrepresenting party child data.Examples includes "PERSONNAME","ADDRESSGROUP" and so forth.


INSTANCE_PK The ID of the entity that is beingassociated with the party macro role.This will be the ID of the entityrepresenting party child data.

BIGINT Null No




TIMESTAMP Null No

END_REASON_TP_CD Identifies the cause for why arelationship was ended. For example,a spousal party-to-party relationshipcan be ended for a "divorce" reason.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No


MISCVALUEThe MISCVALUE table records miscellaneous values that can be generated fromother systems in the enterprise or can specific details an institution would like torecord about its customer base.



MISCVALUE_ID The primary key of MiscellaneousValue.

BIGINT Not Null Yes

INSTANCE_PK The actual primary key of the row inthe logical entity that has the value.

BIGINT Not Null No

ENTITY_NAME The name of the business entity thathas the value. For example:CONTACT.


MISCVALUE_TP_CD This is the miscellaneous value typethat corresponds to a particularmiscellaneous value category. Someexamples of miscellaneous value typeare number of employees, gold value,credit card risk score, and so forth.

BIGINT Not Null No

VALUE_STRING The value content. For example, for acredit risk score record 8.


PRIORITY_TP_CD Identifies the priority of a task, acampaign, value and so forth.Examples include high, medium, low.

BIGINT Null No


BIGINT Null No





TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No



VALUEATTR_TP_CD_0 The value attribute type thatcorresponds to a particularmiscellaneous value type. Someexamples of the value attribute typesare number of employees, gold value,credit card risk score, status, effectivedate, number of products and soforth.

BIGINT Null No

ATTR0_VALUE The Attribute Value field. VARCHAR(150) Null No


BIGINT Null No



BIGINT Null No



BIGINT Null No



BIGINT Null No



BIGINT Null No





BIGINT Null No



BIGINT Null No



BIGINT Null No



BIGINT Null No


NATIVEKEYThe NATIVEKEY table provides the link between the system Contract ID and theexternal administrative system Contract ID.



NATIVE_KEY_ID A unique, system-generated key thatidentifies a contract native key in thesystem.

BIGINT Not Null Yes



ADMIN_CONTRACT_ID The actual text or number that is usedin the administrative source system toidentify a contract.


CONTRACT_ID A unique, system-generated key thatidentifies a contract component in thesystem.

BIGINT Not Null No

ADMIN_FLD_NM_TP_CD

Identifies the field name that thenative key refers to, for example,policy number, policy suffix, accountnumber, branch, and so forth.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No

CONTRACT_COMP_IND

Describes which table the native keyapplies to. If the contract componentindicator is 'Y', the native key appliesto the Contract Component. If thecontract indicator is not 'Y', the nativekey applies to the Contract. Thecontract ID is the value from theContract Component (the contractcomponent ID).

CHAR(1) Null No

ORGThe ORG table is a subtype of CONTACT and represents a non-human legal entity.For example, incorporated companies, nonprofit organizations,sole-proprietorships, partnerships, trusts, and so forth.




BIGINT Not Null Yes

ORG_TP_CD Identifies the classification of theorganization. For example: trust,company, charity, estate, etc.

BIGINT Not Null No

INDUSTRY_TP_CD The industry type for theorganization. For example: SIC.

BIGINT Null No



ESTABLISHED_DT The date that the company or charitywas established. For trusts, this is theinception date.

TIMESTAMP Null No

BUY_SELL_AGR_TP_CD An identifier that uniquely separatesone type of buy-sell agreement fromanother.

BIGINT Null No

PROFIT_IND Indicates whether the organizationhas a Profit or Non-profit status.

CHAR(1) Null No




VARCHAR(20) Null No


BIGINT Null No

ORGNAMEThe ORGNAME table contains the different names that an organization uses.



ORG_NAME_ID A unique, system-generated key thatidentifies a organization name in thesystem.

BIGINT Not Null Yes

ORG_NAME_TP_CD Identifies the type of name for thisorganization. For example: "Legal","Doing Business As", "Abbreviated",and so forth.

BIGINT Not Null No


BIGINT Not Null No

ORG_NAME The actual text of the organizationname. The text should correspond toone of the types of names identifiedin the Organization Name Type Code.


S_ORG_NAME A standardized spelling of theorganization's name that is used forsearching.


NAME_SEARCH_KEY Not currently used. VARCHAR(30) Null No






TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


TIMESTAMP Null No


TIMESTAMP Null No


BIGINT Null No

P_ORG_NAME The phonetic key for OrganizationName.

VARCHAR(20) Null No

STANDARD_IND Indicates whether the ORGNAMErecord contains standardized content.

CHAR(1) Null No

PAYMENTSOURCEThe PAYMENTSOURCE table is the abstract supertype for the various paymentsource subtypes in the system: BANKACCOUNT, CHARGECARD, andPAYROLLDEDUCTION.




BIGINT Not Null Yes

PAYMENT_SRC_CODE Designates the type of paymentsource as follows: P - Payrolldeduction; C - Charge card; B - Bankaccount.

CHAR(1) Not Null No

START_DT The date that the payroll deduction,charge card, or bank account recordbecame effective or was recorded.




END_DT The date that the payroll deduction,charge card, or bank account record isno longer effective.

TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


BIGINT Not Null No

PAYROLLDEDUCTIONThe PAYROLLDEDUCTION table represents a contact's payroll deduction paymentsource information that is used to pay one or more contracts or accounts.




BIGINT Not Null Yes

EMPLOYER_NAME The full name of the employer whenusing payroll deduction to pay for acontract or account.


PAYROLL_NO The identifier assigned to uniquelyidentifies the employee when usingpayroll deduction to pay for acontract or account









VARCHAR(20) Null No


BIGINT Null No

PERSONThe PERSON table is a subtype of CONTACT and represents a human being as alegal entity.




BIGINT Not Null Yes

MARITAL_ST_TP_CD The marital status of a person. Forexample, single, widowed, divorced,and so forth.

BIGINT Null No

BIRTHPLACE_TP_CD A Country Type Code identifying thecountry of birth.

BIGINT Null No

CITIZENSHIP_TP_CD The country where an individual is acitizen.

BIGINT Null No

HIGHEST_EDU_TP_CD The level of schooling that this personhas received. For examples, highschool, college, university, and soforth.

BIGINT Null No

AGE_VER_DOC_TP_CD An identifier that uniquely separatesone type of document being used toverify a client's age from another. Forexample, birth certificate, or driver'slicense.

BIGINT Null No

GENDER_TP_CODE Identifies the sex of a person. CHAR(1) Null No

BIRTH_DT The date of birth of the person. TIMESTAMP Null No

DECEASED_DT The date of death of the person. TIMESTAMP Null No

CHILDREN_CT The total number of children that aperson has.

SMALLINT Null No

DISAB_START_DT The date the person became disabled. TIMESTAMP Null No

DISAB_END_DT The date the person ceased beingdisabled.

TIMESTAMP Null No

USER_IND Indicates whether this a person is auser of the system.

CHAR(1) Null No






VARCHAR(20) Null No


BIGINT Null No

PERSONNAMEThe PERSONNAME table contains the names that are used by a person.



PERSON_NAME_ID A unique, system-generated key thatidentifies a person name in thesystem.

BIGINT Not Null Yes

PREFIX_NAME_TP_CD Identifies the party's name prefix. Forexample, Mr., Mrs., Dr., and so forth.

BIGINT Null No

PREFIX_DESC The actual prefix of name if the Prefixof Name Type Code's value is "other."

VARCHAR(20) Null No

NAME_USAGE_TP_CD Identifies the type of name for thisperson. For example, "Legal", "NickName", or "Maiden Name".

BIGINT Not Null No

GIVEN_NAME_ONE The first given name (commonlyknown as the first name) of a person.

VARCHAR(25) Null No

GIVEN_NAME_TWO The second given name (commonlyknown as the middle name) of aperson.

VARCHAR(25) Null No

GIVEN_NAME_THREE

The third given name (commonlyknown as the middle name) of aperson.

VARCHAR(25) Null No

GIVEN_NAME_FOUR The fourth given name (commonlyknown as the middle name) of aperson.

VARCHAR(25) Null No

LAST_NAME Identifies the surname or family name(commonly known as the last name)of a person.




GENERATION_TP_CD Identifies familial generationalinformation in the form of ageneration name type code. Forexample, The First, The Second,Junior or Senior.

BIGINT Null No

SUFFIX_DESC Identifies the name suffix of a person.For example: "Jr.", "MD", "Esq", andso forth.

VARCHAR(20) Null No




TIMESTAMP Null No


BIGINT Not Null No

USE_STANDARD_IND Determines whether the standardizedname is used for this party.

CHAR(1) Null No




VARCHAR(20) Null No


BIGINT Null No


TIMESTAMP Null No


TIMESTAMP Null No


BIGINT Null No

P_LAST_NAME The phonetic key for Last Name. VARCHAR(20) Null No

P_GIVEN_NAME_ONE The phonetic key for Given NameOne.

VARCHAR(20) Null No

P_GIVEN_NAME_TWO The phonetic key for Given NameTwo.

VARCHAR(20) Null No

P_GIVEN_NAME_THREE

The phonetic key for Given NameThree.

VARCHAR(20) Null No

P_GIVEN_NAME_FOUR The phonetic key for Given NameFour.

VARCHAR(20) Null No


PERSONSEARCHThe PERSONSEARCH table contains the standardized or non-standardizedversions of the PERSON NAME table to facilitate searching.



PERSON_SEARCH_ID A unique, system-generated key thatidentifies a person search record inthe system.

BIGINT Not Null Yes

PERSON_NAME_ID A unique, system-generated key thatidentifies a person name record in thesystem.

BIGINT Not Null No


BIGINT Not Null No

GIVEN_NAME_ONE The first given name (commonlyknown as a first name) of the person.If standardization of the name hastaken place, the standardized versionof the name will be stored here.

VARCHAR(25) Null No

GIVEN_NAME_TWO The second given name (commonlyknown as a middle name) of theperson. If standardization of the namehas taken place, the standardizedversion of the name will be storedhere.

VARCHAR(25) Null No

GIVEN_NAME_THREE The third given name (commonlyknown as a middle name) of theperson. If standardization of the namehas taken place, the standardizedversion of the name will be storedhere.

VARCHAR(25) Null No

GIVEN_NAME_FOUR The fourth given name (commonlyknown as a middle name) of theperson. If standardization of the namehas taken place, the standardizedversion of the name will be storedhere.

VARCHAR(25) Null No

LAST_NAME The last name of a person. Ifstandardization of the name has takenplace, the standardized version of thename will be stored here.



TIMESTAMP Null No






VARCHAR(20) Null No


BIGINT Null No

STANDARD_IND Indicates whether thePERSONSEARCH record containsstandardized content.

CHAR(1) Null No

PHONENUMBERThe PHONENUMBER table contains a contact's phone number.



PHONE_NUMBER_ID A unique, system-generated key thatidentifies a phone number in thesystem.

BIGINT Not Null Yes

COUNTRY_CODE The part of the phone number thatrepresents the country.

VARCHAR(4) Null No

AREA_CODE The part of the phone number thatrepresents the area (finer grained thancountry). In North America, forexample, it would be the '905' portionof (905) 555-1234. Germany can have2 to 5 digits in their area code.

VARCHAR(6) Null No

EXCHANGE The part of the phone number thatrepresents the exchange (finer grainedarea than the area code). In NorthAmerica, for example, it would be the'555' portion of (905) 555-1234.

VARCHAR(6) Null No

PH_NUMBER The part of the phone number thatrepresents the local number. In NorthAmerica, for example, it would be the'1234' portion of (905) 555-1234.

VARCHAR(20) Null No

EXTENSION The part of the phone number thatrepresents the extension (typicallyapplicable for business phonenumbers). It would be the '56789'portion of (905) 555-1234 ext. 56789.

VARCHAR(8) Null No






VARCHAR(20) Null No


BIGINT Null No

CONTACT_METHOD_ID


BIGINT Not Null No

PPREFACTIONOPTThe PPREFACTIONOPT table stores the action types that are possible options foreach privacy preference type.



PPREF_ACT_OPT_ID The Privacy Preference Action Optionprimary key. Identifies the action typesubset available as options for aspecific privacy preference type.

BIGINT Not Null Yes

PPREF_TP_CD Used to indicate the type of privacypreference being stored, for example:credit worthiness, personal info, andso forth.

BIGINT Not Null No

PPREF_ACTION_TP_CD Identifies the action to be taken basedon the privacy preference set by thecustomer or by company defaultsetting. For example: Do not call, Donot mail.

BIGINT Not Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


PPREFDEFThe PPREFDEF table captures the default privacy preference regulations for aninstitution. The privacy preference default settings apply to all parties within thesystem.



PPREF_ID The Privacy Preference Recordprimary key.

BIGINT Not Null Yes

PPREF_SEG_TP_CD The segment associated with theprivacy preference record.

BIGINT Null No

REGULATION_VALUE The privacy preference defaultregulation value which can be thename of the regulation.


DEFAULT_IND This is the indicator for the defaultprivacy preference.

CHAR(1) Null No




VARCHAR(20) Null No


BIGINT Null No

PPREFDEFRELThe PPREFDEFREL table defines the parent child relationship between two defaultprivacy preference records, allowing for different privacy preference regulations tosupersede other regulations that are based on different criteria.



PPREFDEFREL_ID A unique, system-generated key thatidentifies a relationship that twoprivacy preference records can havebetween one another in the system.

BIGINT Not Null Yes

PARENT_PPREF_ID The primary key for the parent of therelationship.

BIGINT Not Null No

CHILD_PPREF_ID The primary key for the child of therelationship.

BIGINT Not Null No



REL_DESC Provides extra space for informationthat can be used for an additionaldefinition or as free form commentsto provide further meaning.





TIMESTAMP Null No




VARCHAR(20) Null No

LAST_UPDATE_TXN_ID A unique, system-generated key thatidentifies the specific transactionwithin the log system that eithercreated, updated, or deleted the datarow.

BIGINT Null No

PPREFENTITYThe PPREFENTITY table stores customized privacy and preference information fora contact, address, contact method, and contract role location.



PPREF_ID A unique, system-generated key thatidentifies a privacy preference objectin the system.

BIGINT Not Null Yes

PPREF_ENTITY The name of the business entity thathas the privacy preference.

VARCHAR(50) Null No

PPREF_INSTANCE_PK The actual primary key of the row inthe logical entity that has the privacypreference.

BIGINT Null No

PPREF_REASON_TP_CD Identifies the reason given bycustomer for making a privacypreference selection.

BIGINT Not Null No


BIGINT Not Null No






VARCHAR(20) Null No


BIGINT Null No

PPREFINSTANCEThe PPREFINSTANCE table identifies the entity instance that is associated with aprivacy preference record. For example, a party has a preference for a newproduct.



PPREF_INST_ID A unique, system-generated key thatidentifies a privacy preferenceinstance in the system.

BIGINT Not Null Yes

PPREF_ID The Privacy Preference Recordprimary key.

BIGINT Not Null No

ENTITY_NAME The name of the business entity thatis associated with the privacypreference values.


INSTANCE_PK The actual primary key of the row inthe logical entity that is associatedwith the privacy preference values.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No


PRIVPREFThe PRIVPREF table stores all privacy and preference records for a contact.



PPREF_ID A unique, system-generated key thatidentifies a privacy preference in thesystem.

BIGINT Not Null Yes

PPREF_ACT_OPT_ID The Privacy Preference Action Optionprimary key. Identifies the action typesubset available as options for aspecific privacy preference type.

BIGINT Null No

PPREF_TP_CD Privacy Preference Type Codeidentifies the particular type ofprivacy preference related to theentity.

BIGINT Not Null No

VALUE_STRING Stores the actual privacy preferencevalue for the type identified and theentity or instance pk identified. Forexample, entity "Contact" instance"10001" has a preference type"Preferred Salutation" with a value of"Mike".

VARCHAR(50) Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

PRODTPRELThe PRODTPREL table stores the relationship type between two product records.These relationships can be used in combinations to provide a hierarchy ofproducts.




PROD_TP_REL_ID A unique, system-generated key thatidentifies a product type relationshipin the system.

BIGINT Not Null Yes

FROM_PROD_TP_CD The type of product associated withthe contract (or at some level withinthe product family). Examples includeUniversal Life, Savings, Checking,Term Life, Auto, and so forth.

BIGINT Not Null No

TO_PROD_TP_CD The type of product associated withthe contract (or at some level withinthe product family). Examples includeUniversal Life, Savings, Checking,Term Life, Auto, and so forth.

BIGINT Not Null No

PRODREL_TP_CD Identifies the type of relationship thattwo products can have between oneanother. For example: "categorize".

BIGINT Not Null No

REL_DESC Provides extra space for informationthat can be used for an additionaldefinition or as free form commentsto provide further meaning.





TIMESTAMP Null No




VARCHAR(20) Null No

LAST_UPDATE_TXN_ID A unique, system-generated key thatidentifies the specific transactionwithin the log system that eithercreated, updated, or deleted the datarow.

BIGINT Null No

PRODUCTThe PRODUCT table contains information on items that are of interest to abusiness.




BIGINT Not Null Yes



PRODUCT_TYPE_ID The identifier that describes whattype of product this is.

BIGINT Not Null No

NAME The name of the product. VARCHAR(120) Not Null No

SHORT_DESCRIPTION A short description of the product. VARCHAR(255) Null No

DESCRIPTION A long description of the product. VARCHAR(500) Null No

PROD_STRUC_TP_CD The basic structure of the product.Examples include Standalone, Bundle,and so forth.

BIGINT Not Null No

STATUS_TP_CD The lifecycle status of the product. BIGINT Null No

STATUS_REASON_TP_CD

Why the product is in its currentlifecycle state.

BIGINT Null No

AVAILABILITY_TP_CD How widely available the product isto the target market. For example,general availability, restrictedavailability.

BIGINT Null No

PRIMARY_TARGET_MARKET_TP_CD

A primary market this producttargets.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No

VARIANT_ALLOWED_IND

This indicates whether or not aProduct can have variant products.

CHAR(1) Null No

VARIANT_OF_PRODUCT_ID

This column stores the Product ID ofthe Root Product.

BIGINT Null No

RESOLUTION_IND Indicates whether the product recordhas been resolved through either acollapse or split operation. A value of'Y' means the product has beenresolved and is inactive. A value of'N' or blank means the product is stillactive.

CHAR(1) Null No

RESOLUTION_TP_CD Identifies the current resolution for aparticular entity record. For example,collapsing, merging, or splitting aproduct record.

BIGINT Null No


PRODUCTCATEGORYASSOCThe PRODUCTCATEGORYASSOC table contains information on a product'sassociation with a category.



PRODUCT_CATEGORY_ASSOC_ID

A unique, system-generated key thatidentifies an association between aproduct and category in the system.

BIGINT Not Null Yes

PRODUCT_ID The product that is associated to thecategory.

BIGINT Not Null No

CATEGORY_ID The category the product is associatedwith.

BIGINT Not Null No

HIERARCHY_ID The hierarchy the category belongs to. BIGINT Not Null No

START_DT The date when the associationbecomes active.


END_DT The date when the associationbecomes inactive.

TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

PRODUCTCONTRACTRELThe PRODUCTCONTRACTREL table holds the relationship between a productand a contract.



PROD_CONT_REL_ID A unique, system-generated key thatidentifies a Product ContractRelationship in the system.

BIGINT Not Null Yes

PRODUCT_ID A unique, system-generated key thatidentifies a Product in the system.

BIGINT Not Null No



CONTRACT_ID A unique, system-generated key thatidentifies a Contract in the system.

BIGINT Not Null No




TIMESTAMP Null No

PROD_CONT_REL_TP_CD

The type of the relationship betweenthe product and the contract.

BIGINT Null No




BIGINT Null No


VARCHAR(20) Null No

PRODUCTEQUIVThe PRODUCTEQUIV table stores information about how a product is identifiedin a different system.



PRODUCT_EQUIV_ID A unique, system-generated key thatidentifies a product equivalence in thesystem.

BIGINT Not Null Yes

PRODUCT_ID The product represented by theproduct equivalence.

BIGINT Not Null No


BIGINT Not Null No

PRODUCT_EQUIV_KEY A representation of the full keyconcatenated and formatted.


KEY_1 First part of the key. VARCHAR(30) Not Null No

KEY_2 Second part of the key. VARCHAR(30) Null No

KEY_3 Third part of the key. VARCHAR(30) Null No

KEY_4 Fourth part of the key. VARCHAR(30) Null No

KEY_5 Fifth part of the key. VARCHAR(30) Null No






VARCHAR(20) Null No


BIGINT Null No

PRODUCTIDENTIFIERThe PRODUCTIDENTIFIER table contains a client-defined identifier for theproduct such as a part number or product code.



PRODUCT_IDENTIFIER_ID

A unique, system-generated key thatidentifies a product identifier in thesystem.

BIGINT Not Null Yes

PRODUCT_ID The product to which the identifierbelongs.

BIGINT Not Null No

PRODUCT_IDENTIFIER_TP_CD

The code that describes the identifier. BIGINT Not Null No

REF_NUM The identifier value. VARCHAR(50) Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No


PRODUCTMATCHRESULTThis table contains the match result details of the suspect records. Each record isproduced by a suspect match engine described by its code type.



MATCH_RESULT_ID A system-generated key that uniquelyidentifies a product suspect duplicatematch result record.

BIGINT Not Null Yes

SUSPECT_ID The ID of the suspect duplicate recordthat this match result belongs to.

BIGINT Not Null No

MATCH_RESULT The match result of the suspectduplicate record.


MATCH_DETAIL The match detail of the suspectduplicate record.

XML Null No

MATCH_ENGINE_TP_CD

Suspect duplicate match engine codetype.

BIGINT Not Null No

SPEC_ID The spec that describes the definitionof the spec values.

BIGINT Null No

SPEC_FMT_ID The format, or version, of the specthat these spec values validate to.

BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No

PRODUCTNLSThe PRODUCTNLS table is the localization table for the Product table, containingany localization data for fields that must be localized.




PRODUCT_NLS_ID A unique, system-generated key thatidentifies a localized product in thesystem.

BIGINT Not Null Yes

PRODUCT_ID The product the Product NLS belongsto.

BIGINT Not Null No

LANG_TP_CD Identifies a spoken language such asEnglish, French, Spanish, German, etc.

BIGINT Not Null No

NAME The localized name of the product. VARCHAR(120) Not Null No

SHORT_DESCRIPTION A localized short description of theproduct.


DESCRIPTION A localized long description of theproduct.





VARCHAR(20) Null No


BIGINT Null No

PRODUCTPARTYROLEThe PRODUCTPARTYROLE table represents an association that links contacts tothe various roles they can have on a product.



PRODUCT_PARTY_ROLE_ID

A unique, system-generated key thatidentifies a product party role in thesystem.

BIGINT Not Null Yes

PRODUCT_ID A unique, system-generated key thatidentifies a product instance in thesystem.

BIGINT Null No


BIGINT Null No

ADMIN_CLIENT_ID Uniquely identifies the primary keyfor a party in the administrativesource system.


ADMIN_PRODUCT_ID Uniquely identifies the primary keyfor a product in the administrativesource system.




ADDITIONAL_DETAILS Any additional details to be capturedabout the role.





TIMESTAMP Null No

END_REASON_TP_CD Identifies the cause for why a rolewas ended.

BIGINT Null No

PRODUCT_PARTY_ROLE_TP_CD

Identifies the type of role that a partycan have on a product. For example"Supplier", "Vendor", "Retailer", "ItemAnalyst", or "Consumer".

BIGINT Not Null No

ADMIN_SYS_TP_CD Uniquely identifies the administrativesource system for a party or product.

BIGINT Null No




BIGINT Null No


VARCHAR(20) Null No

PRODUCTRELThe PRODUCTREL table holds information about the relationship between twoproducts. Relationships can be used to determine product substitutes, up-sells,cross-sells, and they can also be used to form bundles and coarser-grain productsmade up of product components.



PRODUCT_REL_ID A unique, system-generated key thatidentifies a relationship between twoproducts in the system.

BIGINT Not Null Yes

FROM_PROD_ID The source product in therelationship.

BIGINT Not Null No

TO_PROD_ID The target product in the relationship. BIGINT Not Null No

PRODUCT_REL_TP_CD The type of relationship. BIGINT Not Null No

START_DT The date when the relationshipbecomes active.




END_DT The date when the relationshipbecomes inactive.

TIMESTAMP Null No

REL_DESC Description of the productrelationship.





VARCHAR(20) Null No


BIGINT Null No

MIN_QUANTITY Indicates the minimum quantity. BIGINT Null No

MAX_QUANTITY Indicates the maximum quantity. BIGINT Null No

PRODUCTSUSPECTThis table contains records of pairs of products which are marked as suspect eitherby user or system.



SUSPECT_ID A system-generated key that uniquelyidentifies a product suspect duplicaterecord.

BIGINT Not Null Yes

SOURCE_ENTITY_ID The ID of the source product. BIGINT Not Null No

SUSPECT_ENTITY_ID The ID of the suspect duplicateproduct.

BIGINT Not Null No

SUSP_ST_TP_CD The status code type of the suspectduplicate record.

BIGINT Not Null No

SOURCE_TP_CD The source code type of the suspectduplicate record.

BIGINT Not Null No

SUSPECT_TP_CD The suspect code type of the suspectduplicate record.

BIGINT Null No

CREATED_BY The user who created the record. VARCHAR(20) Null No






VARCHAR(20) Null No


BIGINT Null No

PRODUCTTYPEThe PRODUCTTYPE table is a type of product that, unless it is the root producttype, is a subtype of another product type.



PRODUCT_TYPE_ID A unique, system-generated key thatidentifies a type of product that(unless is the root product type) is asubtype of another product type, inthe system.

BIGINT Not Null Yes

NAME The name of the product type. VARCHAR(50) Not Null No

DESCRIPTION The description of the product type. VARCHAR(255) Null No

PARENT_PROD_TYPE_ID

The parent type for this type. BIGINT Null No

NODE_TP_CD Describes the level of the producttype and is required to understandwhat is hardened in the databasemodel or not.

BIGINT Not Null No

METADATA_INFO_TP_CD

The ID of the metadata package thisspec belongs to.

BIGINT Not Null No

START_DT The date when the type becomeseffective and can create products ofthat type.


END_DT The date when the type is no longereffective and can no longer createproducts of that type. Note thatproducts of the type will continue toexist.

TIMESTAMP Null No






VARCHAR(20) Null No


BIGINT Null No

PRODUCTTYPENLSThe PRODUCTTYPENLS table is the localization table for the ProductType table,containing any localization data for fields that must be localized.



PRODUCT_TYPE_NLS_ID

A unique, system-generated key thatidentifies a localized product type inthe system.

BIGINT Not Null Yes

PRODUCT_TYPE_ID The product type the localizedproduct type belongs to.

BIGINT Not Null No

LANG_TP_CD Identifies the language for which theproduct type has been localized.

BIGINT Not Null No

NAME The name of the product type for aparticular locale.


DESCRIPTION The description of the product typefor a particular locale.





VARCHAR(20) Null No


BIGINT Null No


PRODUCTVALThe PRODUCTVAL table contains a set of values based on a spec format,representing the product's association to some other entity such as the producttype. Values are based on spec formats associated to the product type aremaintained in this table.



PRODUCT_VALUES_ID A unique, system-generated key thatidentifies a product value in thesystem.

BIGINT Not Null Yes

SPEC_ID The spec that describes the definitionof the values.

BIGINT Not Null No

SPEC_FMT_ID The format (or version) of the specthese values validate to.

BIGINT Not Null No

PRODUCT_ID The product these values belong to. BIGINT Not Null No

VALUE_XML The values as defined by theassociated spec format.

XML Not Null No




TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

PRODUCTVALINDEXPRODUCT VALUE INDEX TABLE records all searchable attribute values for aspecific product value (indicated by the PRODUCTVAL_ID). For databases withlimited or no native XML support, it is this table that is queried when spec valueattributes are provided as search criteria (rather than the PRODUCTVAL table).




PRODUCTVAL_INDEX_ID

A unique, system-generated key thatidentifies a value index in the system.

BIGINT Not Null Yes

SPEC_SRCH_ATTR_ID The ID of the associated specsearchable attribute.

BIGINT Not Null No

PRODUCT_ID The ID of the associated entity. BIGINT Not Null No

PRODUCTVAL_ID The ID of the associated spec value. BIGINT Not Null No

BOOLEAN_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:boolean.

CHAR(1) Null No

STRING_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:string ormdmspec:localizedString.


DECIMAL_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:decimal.


LONG_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:long.

BIGINT Null No

DATETIME_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:dateTime.

TIMESTAMP Null No

DATE_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:date.

TIMESTAMP Null No

TIME_VALUE Contains the value retrieved from theassociated spec value document usingthe associated searchable attribute'path'. It remains null if the data typeof this element is not xsd:time.

TIMESTAMP Null No




VARCHAR(20) Null No




BIGINT Null No

STRING_VALUE_UPPER This column stores upper case ofstring_value column to improve noncase sensitive search performance.


PRODUCTVALNLSThe PRODUCTVALNLS table is the localization table for the PRODUCTVAL table,containing any localization data for fields that must be localized.



PRODUCT_VALUES_NLS_ID

A unique, system-generated key thatidentifies a localized product value inthe system.

BIGINT Not Null Yes

PRODUCT_VALUES_ID A unique, system-generated key thatidentifies a source product value inthe system.

BIGINT Not Null No

LANG_TP_CD Identifies a spoken language, such asEnglish, French, Spanish, or German.

BIGINT Not Null No

VALUE_XML The values as defined by theassociated spec format.

XML Not Null No




VARCHAR(20) Null No


BIGINT Null No

PRODUCTVALNLSINDEXThe PRODUCTVALNLSINDEX table records all searchable attribute values for aspecific product value nls record associated with the PRODUCTVAL. For databaseswith limited or no native XML support, it is this table that is queried whenlocalized spec value attributes are provided as search criteria in the context of alocalized search.




PRODUCTVALNLS_INDEX_ID

A unique, system-generated key thatidentifies the localized value index inthe system.

BIGINT Not Null Yes

SPEC_SRCH_ATTR_ID The ID of the associated specsearchable attribute.

BIGINT Not Null No

PRODUCT_ID The ID of the associated entity. BIGINT Not Null No

PRODUCTVAL_ID The ID of the associated spec value. BIGINT Not Null No

LANG_TP_CD Identifies a spoken language, such asEnglish, French, Spanish, or German.

BIGINT Not Null No

STRING_VALUE This field contains the value retrievedfrom the associated spec valuedocument using the associatedsearchable attribute 'path'. It shouldremain null if the data type of thiselement is notmdmspec:localizedString.





VARCHAR(20) Null No


BIGINT Null No

STRING_VALUE_UPPER This column stores upper case ofstring_value column to improve noncase sensitive search performance.


PROPERTYThe PROPERTY table contains all HOLDING records that are locations. Forexample, cottage, private residence, or condominium.




BIGINT Not Null Yes




BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No

ROLEIDENTIFIERThe ROLEIDENTIFIER table provides an identifier for a contact's specific role on acontract.



ROLE_IDENTIFIER_ID A unique, system-generated key thatidentifies a party contract roleidentifier in the system.

BIGINT Not Null Yes


BIGINT Not Null No

IDENTIFIER_ID A unique, system-generated key thatidentifies a party identification in thesystem.

BIGINT Not Null No



EXPIRY_DT The date on which the particular roleidentification expires.

TIMESTAMP Null No






VARCHAR(20) Null No


BIGINT Null No

ROLELOCATIONThe ROLELOCATION table represents an association between a contact's role on acontract to a particular location group.



ROLE_LOCATION_ID A unique, system-generated key thatidentifies a party contract rolelocation in the system.

BIGINT Not Null Yes

LOCATION_GROUP_ID Location Group ID is a unique,system-generated key that identifies alocation group in the system.

BIGINT Not Null No


BIGINT Not Null No




TIMESTAMP Null No




VARCHAR(20) Null No

UNDEL_REASON_TP_CD

A reason for not using a particularaddress. Some example values are"returned mail", "change in ZIP code"and so forth.

BIGINT Null No


BIGINT Null No


ROLELOCPURPOSEThe ROLELOCPURPOSE table describes why contract information for a particularrole is addressed to a defined location. The location can either be an address or acontact method.



ROLE_LOC_PURP_ID A unique, system-generated key thatidentifies a party contract rolelocation reason in the system.

BIGINT Not Null Yes

ROLE_LOCATION_ID A unique, system-generated key thatidentifies a party contract rolelocation in the system.

BIGINT Not Null No

PURPOSE_TP_CD The purpose for the location as itrelates to a role on a contract. Forexample, the owner's residenceaddress is associated with the contractfor the purpose of sendingstatements.

BIGINT Not Null No

DESCRIPTION Free form comments to provideadditional information.





TIMESTAMP Null No




VARCHAR(20) Null No


BIGINT Null No

ROLESITUATIONThe ROLESITUATION table defines the different arrangements that can be definedby a given party contract role. For example, time delay, or common disasterarrangements on life insurance policies.

This table is used by the following domains.v Account Domain


v Party Domain


ROLE_SITUATION_ID A unique, system-generated key thatidentifies a party situation role in thesystem.

BIGINT Not Null Yes


BIGINT Not Null No

ARRANGEMENT_TP_CD

Describes the type of agreement thatthe party contract role has with thecontract. For example: time delayarrangement such as a commondisaster.

BIGINT Not Null No




TIMESTAMP Null No


VARCHAR(20) Null No




BIGINT Null No

SEARCHEXCLRULEThe SEARCHEXCLRULE table provides the initial search exclusion criteria for eachsearch transaction. For example, last name only, last and given name only, or lastname and city only.



LAST_NAME The last name value from PersonName or from Person Search.


P_LAST_NAME The last name phonetic key fromPerson Name.


GIVEN_NAME_ONE The "given name one" value fromPerson Name or from Person Search.


P_GIVEN_NAME_ONE The "given name one" phonetic keyfrom Person Name.


CITY_NAME The city name value from Address. VARCHAR(30) Not Null Yes



P_CITY_NAME The city name phonetic key fromAddress.


FREQUENCY The number of times this exclusionrule combination occurred.

BIGINT Not Null No

SERVICEPRODUCTThe SERVICEPRODUCT table contains information about non-physical productsthat are a hardened subtype of Product.




BIGINT Not Null Yes




VARCHAR(20) Null No


BIGINT Null No

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



SPEC_ID A unique, system-generated key thatidentifies a spec in the system.

BIGINT Not Null Yes

METADATA_INFO_TP_CD

The ID of the metadata package thisspec belongs to.

BIGINT Not Null No

SPEC_NAME Name given to the spec. VARCHAR(100) Not Null No

SPEC_NAMESPACE Namespace this spec belongs to. VARCHAR(500) Not Null No

ACTIVE_FORMAT_ID The spec format that is "active" forthis spec.

BIGINT Not Null No






TIMESTAMP Null No




BIGINT Null No


VARCHAR(20) Null No

SPECFMTThe SPECFMT contains all the various formats or versions for a system's specs.



SPEC_FORMAT_ID A unique, system-generated key thatidentifies a spec format in the system.

BIGINT Not Null Yes

SPEC_ID The ID of the spec this format isapplied to.

BIGINT Not Null No

EXTERNAL_XSD Client XSD for this format. CLOB(1G) Not Null No

INTERNAL_XSD Server XSD for this format. CLOB(1G) Not Null No

LOCALIZED_XSD The localized XSD information for thementioned spec format.

CLOB(1G) Null No

FORMAT_VERSION The version number for this format. BIGINT Not Null No




BIGINT Null No


VARCHAR(20) Null No


SPECFORMATTRANSLATIONThe SPECFORMATTRANSLATION table contains locale specific translations for aspec's attribute names.



SPEC_FORMAT_TRANSLATION_ID

A unique, system-generated key thatidentifies a spec format translation inthe system.

BIGINT Not Null Yes

SPEC_FORMAT_ID The ID of the spec format thetranslation applies to.

BIGINT Not Null No

LANG_TP_CD Code for the translation's localelanguage.

BIGINT Not Null No

TRANSLATION An XML document holding thetranslations of a given spec'sattributes for a given locale.

CLOB(1G) Not Null No




BIGINT Null No


VARCHAR(20) Null No

SPECSRCHATTRSPEC SEARCHABLE ATTRIBUTE records all spec attributes that are marked as'searchable' within the system. It assists with both validating that a spec attributeprovided in the context of search is in fact searchable and with the dynamicconstruction of the required SQL to perform the search.



SPEC_SRCH_ATTR_ID A unique, system-generated key thatidentifies a spec searchable attributein the system.

BIGINT Not Null Yes

SPEC_ID The ID of the spec associated withthis searchable attribute.

BIGINT Not Null No



PATH The path that identifies a searchableelement within a spec valuedocument.


DATA_TYPE The data type of the elementidentified by the path.


DESTINATION_ENTITY_NAME

The destination entity this spec use isrelated to.


END_DT The date when this attribute is nolonger searchable.

TIMESTAMP Null No

INDEX_STATUS The current index state of thesearchable attribute.

BIGINT Not Null No




VARCHAR(20) Null No


BIGINT Null No

SUSPECTThe SUSPECT table contains suspect duplicates (contacts that are possibleduplicates of each other) that a particular contact has in the database.



SUSPECT_ID A unique, system-generated key thatidentifies a suspect in the system.

BIGINT Not Null Yes


BIGINT Not Null No

SUSPECT_CONT_ID A unique, system-generated key thatidentifies a party in the system.

BIGINT Not Null No

SUSP_ST_TP_CD Suspect Status Type code indicates thecurrent situation for a particularsuspect record. For example, suspectduplicate, not duplicate, underinvestigation, etc.

BIGINT Not Null No

SOURCE_TP_CD The source of the Suspect ReasonCode (system-marked oruser-marked).

BIGINT Not Null No



SUSP_REASON_TP_CD The field that caused the data matchto occur.

BIGINT Null No

MATCH_RELEV_TP_CD Identifies party match relevancies,providing a description of whichelements were matched.

BIGINT Null No

ADJ_ACTION_CODE When a PARTY is identified as aSUSPECT, the SUSPECT(party ID) canhave relevancy scores dictating a 'B'action type. The client might take intoaccount relationships or roles on apolicy that can adjust the SUSPECT toan 'A' type action or alternatively a'C' type SUSPECT.

CHAR(2) Null No

ADJ_ACTION_TP_CD Identifies the business reasons for theaction code on the suspectidentification being modified.

BIGINT Null No

CREATED_BY The ID of the user, system, or otherentity that created the data.

VARCHAR(20) Null No




VARCHAR(20) Null No


BIGINT Null No

MATCH_ENG_TP_CD Identifies the matching engine to usefor matching parties.

BIGINT Null No

WEIGHT The calculated weight used by thematching engine.


CUR_SUSPECT_TP_CD Identifies the current suspect type. BIGINT Null No

CUR_MTCH_ENG_TP_CD

The current matching engine. BIGINT Null No

PERSON_ORG_CODE Indicates the Party type of the suspectduplicates.

CHAR(1) Null No

INACTIVATED_DT Indicates the earliest inactivated dateof the two suspect duplicate parties.

TIMESTAMP Null No

ACCESS_TOKEN_VALUE


VARCHAR(50) Null No


SUSPECTAUGMENTThe SUSPECTAUGMENT table contains the augmented suspect duplicateprocessing results preformed by additional matching engines.



SUSPECT_AUGMENT_ID

A unique, system-generated key thatidentifies a suspect augment record inthe system.

BIGINT Not Null Yes

SUSPECT_ID The Suspect ID associated with thisrecord.

BIGINT Not Null No

ADJ_ACTION_TP_CD The type code indicating the AdjustAction type.

BIGINT Not Null No

SUSPECT_TP_CD The type code indicating the Suspecttype.

BIGINT Not Null No

WEIGHT The calculated weight for this suspectaugmentation record.


MATCH_ENG_TP_CD The type code indicating thematching engine to use for matchingparties.

BIGINT Not Null No




VARCHAR(20) Null No


BIGINT Null No

TERMCONDITIONThe TERMCONDITION table represents a logical condition, containing conditionsfor entities such as Product and Agreement. TermCondition can be static orexecutable.



CONDITION_ID A unique, system-generated key thatidentifies a term and condition recordin the system.

BIGINT Not Null Yes



CONDITION_OWNER_TP_CD

Identifies the owner of the term andcondition. The Condition Attributeentity is common to both Accountand Product Domain. The value isfrom the code tableCDCONDITIONOWNERTP.

BIGINT Not Null No


This value, pulled from theCDCONDITIONUSAGETP table,identifies the term and conditionusage type that describes the purposeof the term and condition.

BIGINT Not Null No

NAME The name of the term and condition. VARCHAR(120) Null No

DESCRIPTION The description for the term andcondition.


FROM_DATE The date from which a term andcondition is valid.


TO_DATE The date till which a term andcondition is valid.

TIMESTAMP Null No

OVERRIDES_CONDITION_ID

The term and condition ID that isoverridden by this term andcondition.

BIGINT Null No

OVERRIDABLE_IND A flag that indicates if the term andcondition can be overridden.

CHAR(1) Null No

MANDATORY_IND A flag that indicates if the term andcondition is mandatory.

CHAR(1) Null No

PARENT_CONDITION_ID

The term and condition that is theparent of this term and condition. It isused in hierarchical and nested termsand conditions.

BIGINT Null No




BIGINT Null No


VARCHAR(20) Null No

OVERRIDE_RULE_ID An associated rule ID if it is differentfrom the one set inCDCONDITIONUSAGETP.

VARCHAR(10) Null No


TERMCONDITIONNLSThe TERMCONDITIONNLS table is the localization table for theTERMCONDITION table, containing anylocalization data for fields that must be belocalized.



CONDITION_NLS_ID A unique, system-generated key thatidentifies a localized term andcondition in the system.

BIGINT Not Null Yes

CONDITION_ID The condition ID of the term andcondition record for whichlocalization data is added.

BIGINT Not Null No

LANG_TP_CD The language code on which data islocalized.

BIGINT Not Null No

NAME The localized value of the name fieldof the term and condition.


DESCRIPTION The localized value of the descriptionfield of the term and condition.





BIGINT Null No


VARCHAR(20) Null No

USERTABLEA type of PERSON that is allowed to use the application. The specificfunctions/data that they can use within the application are determined by the role(CODE USER ROLE) that they are assigned to.



BIGINT Not Null Yes

USER_ROLE_TP_CD The type code identifying the userrole.

BIGINT Null No

USER_ID The unique user ID to identify thesystem user.




PASSWORD The password used by the user toauthenticate against the system.

VARCHAR(20) Null No

EXPIRY_DT The date that the user is no longervalid.

TIMESTAMP Null No



VEHICLEThe VEHICLE table contains all HOLDING records that are vehicles. For example,Mazda M3, Subaru Outback, or Honda Civic.




BIGINT Not Null Yes

VIN_NUM The unique 17-digit vehicleidentification number.

VARCHAR(20) Null No

VEHICLE_MAKE The manufacturer name of thevehicle.

VARCHAR(20) Null No

VEHICLE_MODEL The vehicle model as identified by themanufacturer.

VARCHAR(20) Null No

VEHICLE_YEAR The year the vehicle was built. BIGINT Null No




VARCHAR(20) Null No


BIGINT Null No


Chapter 2. Tables by Features

This section lists the domains in InfoSphere MDM and the database tables that areused by each of the domains.

Account DomainThe Account Domain uses the following tables:v ADDRESSv AGREEMENTSPECVALv BILLINGSUMMARYv CDAGREEMENTSTTPv CDAGREEMENTTPv CDPRODCONTRACTRELTPv CDREPOSITORYTPv CDSERVICELEVELTPv CDTERMINATIONREASONTPv CLAIMCONTRACTv CLAIMv CLAIMROLEv CONDITIONATTRIBUTEv CONTACTv CONTRACTCOMPONENTv CONTRACTCOMPVALv CONTRACTv CONTRACTRELv CONTRACTROLEv CONTRACTROLERELv ENTITYCONDITIONRELv ENTITYCONTENTREFERENCEv HOLDINGv IDENTIFIERv LOBRELv LOCATIONGROUPv NATIVEKEYv PRODUCTCONTRACTRELv PRODUCTv PROPERTYv ROLEIDENTIFIERv ROLELOCATIONv ROLELOCPURPOSEv ROLESITUATIONv TERMCONDITIONNLSv TERMCONDITION


v VEHICLE

Party DomainThe Party Domain uses the following tables:v ACCESSDATEVALv ADDACTIONTYPEv ADDRESSGROUPv ADDRESSv BANKACCOUNTv BILLINGSUMMARYv CAMPAIGNASSOCIATv CAMPAIGNv CDACCETOCOMPTPv CDACCOUNTTPv CDACTIONADJREASTPv CDADDRUSAGETPv CDADMINFLDNMTPv CDADMINSYSTPv CDAGEVERDOCTPv CDARRANGEMENTTPv CDBILLINGSTTPv CDBILLTPv CDBUYSELLAGREETPv CDCAMPAIGNTPv CDCDCREJREASONTPv CDCDCSTTPv CDCHARGECARDTPv CDCLAIMROLETPv CDCLAIMSTATUSTPv CDCLAIMTPv CDCLIENTIMPTPv CDCLIENTPOTENTPv CDCLIENTSTTPv CDCONTMETHCATv CDCONTMETHTPv CDCONTRACTRELSTTPv CDCONTRACTRELTPv CDCONTRACTROLETPv CDCONTRACTSTTPv CDCONTRCOMPTPv CDCOUNTRYTPv CDCURRENCYTPv CDDEMOGRAPHICSTPv CDDOMAINTPv CDDOMAINVALUETP


v CDEMEMATCHFUNCTIONTPv CDEMEMATCHWORDTPv CDENDREASONTPv CDENTITYLINKSTTPv CDFREQMODETPv CDGENERATIONTPv CDHIGHESTEDUTPv CDHOLDINGTPv CDIDSTATUSTPv CDIDTPv CDINACTREASONTPv CDINCOMESRCTPv CDINDUSTRYTPv CDLANGTPv CDLINKREASONTPv CDLOBRELTPv CDLOBTPv CDMARITALSTTPv CDMATCHENGINETPv CDMATCHRELEVTPv CDMETHODSTATUSTPv CDMISCVALUEATTRTPv CDMISCVALUECATv CDMISCVALUETPv CDNAMEUSAGETPv CDORGNAMETPv CDORGTPv CDPAYMENTMETHODTPv CDPPREFACTIONTPv CDPPREFCATv CDPPREFREASONTPv CDPPREFSEGTPv CDPPREFTPv CDPREFIXNAMETPv CDPRIORITYCATTPv CDPRIORITYTPv CDPRODRELTPv CDPRODTPv CDPROVSTATETPv CDPURPOSETPv CDRELASSIGNTPv CDRELTPv CDRESIDENCETPv CDROLECATTPv CDROLETP

Chapter 2. Tables by Features 189

v CDRPTINGFREQTPv CDSHAREDISTTPv CDSOURCEIDENTTPv CDSUSPECTREASONTPv CDSUSPECTSOURCETPv CDSUSPECTSTATUSTPv CDSUSPECTTPv CDUNDELREASONTPv CHARGECARDv CLAIMCONTRACTv CLAIMv CLAIMROLEv CONTACTCDCv CONTACTDEMOGRAPHICSv CONTACTMETHODGROUPv CONTACTMETHODv CONTACTv CONTACTRELv CONTEQUIVv CONTMACROROLEv CONTRACTCOMPONENTv CONTRACTCOMPVALv CONTRACTv CONTRACTRELv CONTRACTROLEv CONTRACTROLERELv CONTSUMMARYv DEFAULTSOURCEVALv EME_RECBKTDv EME_RECCHKDv EME_RECCMPDv EME_RECHEADv ENTITYROLEv HOLDINGv IDENTIFIERv INACTIVATEDCONTv INACTIVECONTLINKv INCOMESOURCEv LOBRELv LOCATIONGROUPv MACROROLEASSOCv MISCVALUEv NATIVEKEYv ORGNAMEv ORG


v PAYMENTSOURCEv PAYROLLDEDUCTIONv PERSONNAMEv PERSONv PERSONSEARCHv PHONENUMBERv PPREFACTIONOPTv PPREFDEFv PPREFDEFRELv PPREFENTITYv PPREFINSTANCEv PRIVPREFv PRODTPRELv PROPERTYv ROLEIDENTIFIERv ROLELOCATIONv ROLELOCPURPOSEv ROLESITUATIONv SEARCHEXCLRULEv SUSPECTAUGMENTv SUSPECTv VEHICLE

Product DomainThe Product Domain uses the following tables:v CATEGORYNLSv CATEGORYv CATEQUIVv CATHIERARCHYNLSv CATHIERARCHYv CATNODERELv CDACCOUNTREQUIREDTPv CDAVAILABILITYTPv CDCONDITIONATTRIBUTETPv CDCONDITIONOWNERTPv CDCONDITIONUSAGETPv CDCURRENCYTPv CDLINKREASONTPv CDMETADATAINFOTPv CDMETADATAPACKAGETPv CDNODETPv CDPRIMARYTARGETMARKETTPv CDPRODRELATIONTPv CDPRODSTRUCTURETPv CDPRODUCTIDENTIFIERTP

Chapter 2. Tables by Features 191

v CDPRODUCTPARTYROLETPv CDPRODUCTSTATUSTPv CDREPOSITORYTPv CDRESOLUTIONTPv CDSPECCASCADETPv CDSPECUSETPv CDSTATUSREASONTPv CDTAXPOSITIONTPv CONDITIONATTRIBUTEv ENTITYCONDITIONRELv ENTITYCONTENTREFERENCEv ENTITYSPECUSEv FINANCIALPRODUCTv GOODSPRODUCTv INACTIVEPRODLINKv INSURANCEPRODUCTv PRODUCTCATEGORYASSOCv PRODUCTEQUIVv PRODUCTIDENTIFIERv PRODUCTMATCHRESULTv PRODUCTNLSv PRODUCTPARTYROLEv PRODUCTv PRODUCTRELv PRODUCTSUSPECTv PRODUCTTYPENLSv PRODUCTTYPEv PRODUCTVALINDEXv PRODUCTVALNLSINDEXv PRODUCTVALNLSv PRODUCTVALv SERVICEPRODUCTv SPECFMTv SPECFORMATTRANSLATIONv SPECv SPECSRCHATTRv TERMCONDITIONNLSv TERMCONDITION


Notices

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

IBM® may not offer the products, services, or features discussed in this documentin other countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country/region or send inquiries, inwriting, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry/region where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions; therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

This document may provide links or references to non-IBM Web sites andresources. IBM makes no representations, warranties, or other commitmentswhatsoever 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-IBMWeb site does not mean that IBM endorses the content or use of such Web site orits owner. In addition, IBM is not a party to or responsible for any transactions youmay enter into with third parties, even if you learn of such parties (or use a link tosuch parties) from an IBM site. Accordingly, you acknowledge and agree that IBMis not responsible for the availability of such external sites or resources, and is notresponsible or liable for any content, services, products, or other materials on oravailable from those sites or resources. Any software provided by third parties issubject 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 itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation that has been exchanged, should contact:

IBM Canada LimitedOffice of the Lab Director8200 Warden AvenueMarkham, OntarioL6G 1C7CANADA

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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems, and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements, or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility, or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information may contain examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious, and any similarity to the names and addresses used by an actualbusiness enterprise is entirely coincidental.


COPYRIGHT LICENSE:

This information may contain sample application programs, in source language,which illustrate programming techniques on various operating platforms. You maycopy, modify, and distribute these sample programs in any form without paymentto IBM for the purposes of developing, using, marketing, or distributingapplication programs conforming to the application programming interface for theoperating platform for which the sample programs are written. These exampleshave not been thoroughly tested under all conditions. IBM, therefore, cannotguarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work mustinclude 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 rightsreserved.

Notices 195

Trademarks

Company, product, or service names identified in the documents of the text maybe trademarks or service marks of International Business Machines Corporation orother companies. Information on the trademarks of IBM Corporation in the UnitedStates, other countries, or both is located at http://www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Windows is a trademark of Microsoft Corporation in the United States, othercountries, or both.

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

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

Other company, product, or service names may be trademarks or service marks ofothers.


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

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

��

Printed in USA

GI13-2668-00

InfoSphere MDM 11.0: MDM Physical Data Dictionary - IBM · 2002-01-31 · IBM InfoSphere Master...

Documents

Transcript of InfoSphere MDM 11.0: MDM Physical Data Dictionary - IBM · 2002-01-31 · IBM InfoSphere Master...