Tables

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

ACCESSDATEVAL
The ACCESSDATEVAL table captures the last used date and last verified date around various entities and attributes.
ADDACTIONTYPE
The ADDACTIONTYPE table identifies an action taken as a result of suspect duplicate identification.
ADDRESS
The ADDRESS table records the location used for mailing and other street addresses. Only one address per CDADDRUSAGETP is allowed. For example, there can only be one "Mailing" address for a contact.
ADDRESSGROUP
The ADDRESSGROUP table links a contact to an address and contains rules specific for using that address.
AGREEMENTSPECVAL
The AGREEMENTSPECVAL table contains spec values that are related to business agreements.
BANKACCOUNT
The BANKACCOUNT table is a subtype of the PAYMENTSOURCE table, describing the bank account information used to pay one or more contracts or accounts.
BILLINGSUMMARY
The BILLINGSUMMARY table represents a summary bill for a CONTRACT or a CONTRACTCOMPONENT.
CAMPAIGN
The CAMPAIGN table contains the details of a campaign for customer solicitation, including the priority order for customer presentation.
CAMPAIGNASSOCIAT
The CAMPAIGNASSOCIAT table lists the association between a campaign and any associated entities.
CATEGORY
The CATEGORY table contains common platform attributes for categories. A CATEGORY can participate in only one hierarchy at a time.
CATEGORYNLS
The CATEGORYNLS table contains the language sensitive fields for the CATEGORY table.
CATEQUIV
The CATEQUIV table contains information about a category equivalency.
CATHIERARCHY
The CATHIERARCHY table contains information about a category hierarchy.
CATHIERARCHYNLS
The CATHIERARCHYNLS table contains the language sensitive fields for the CATHIERARCHY table.
CATNODEREL
The CATNODEREL table contains the definition of relationships between category nodes in a category hierarchy.
CDACCETOCOMPTP
The CDACCETOCOMPTP table describes the type of access a CONTACT has to a computer and to current and future related technologies. For example, computers or videophones.
CDACCOUNTREQUIREDTP
The CDACCOUNTREQUIREDTP table contains information about the account requirement type codes for the FINANCIALPRODUCT table.
CDACCOUNTTP
The CDACCOUNTTP table contains values for the account type code and its descriptions. For example, "Savings" and "Checking".
CDACTIONADJREASTP
The CDACTIONADJREASTP table identifies the reason that an action, taken as a result of suspect duplicate identification, was adjusted.
CDADDRUSAGETP
The CDADDRUSAGETP table contains information about the address usage type code values, such as primary residence, secondary address, or business address.
CDADMINFLDNMTP
The CDADMINFLDNMTP table contains the valid values for the native key field name type code and its descriptions.
CDADMINSYSTP
CDAGEVERDOCTP
The CDAGEVERDOCTP table contains the age verification type code values and their descriptions.
CDAGREEMENTSTTP
The CDAGREEMENTSTTP table stores the valid status of an agreement. For example, Draft, Normal, or Suspended.
CDAGREEMENTTP
The CDAGREEMENTTP table stores the agreement type. For example, ValuePackage.
CDARRANGEMENTTP
The CDARRANGEMENTTP table contains the values and descriptions of the arrangement type code, describing the role that the CONTACT plays on an AGREEMENT. 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 contact can only receive the benefit if the contact happens to die in the same accident as the insured person, but only if that contact survived the insured person by a certain length of time; otherwise, if both die at the same time, the proceeds will go to the insured's contingent beneficiary.
CDAVAILABILITYTP
The CDAVAILABILITYTP table contains information about how widely available a PRODUCT is to its target market.
CDBILLINGSTTP
The CDBILLINGSTTP table contains the status values and descriptions for a billing type. For example, "Closed", "Paid", "Pending" and "Disputed".
CDBILLTP
The CDBILLTP table contains the values for the bill type code and its descriptions.
CDBUYSELLAGREETP
The CDBUYSELLAGREETP table contains the buy sell agreement type code values and their descriptions. For example, Cross purchase, or Hybrid.
CDCAMPAIGNTP
The CDCAMPAIGNTP table identifies the type of campaign.
CDCDCREJREASONTP
The CDCDCREJREASONTP table stores the reason type detailing why a critical data change is rejected. For example, Created in error, or Withdrawn by customer.
CDCDCSTTP
The CDCDCSTTP table stores the status type of a critical data change request. For example, Change rejected, or Change accepted.
CDCHARGECARDTP
The CDCHARGECARDTP table contains the charge card type code values and their descriptions. For example, Visa, MasterCard, or American Express.
CDCLAIMROLETP
The CDCLAIMROLETP table contains the claim role type code values and their descriptions. For example, "Claimant", "Third Party", "Witness", and "Adjuster".
CDCLAIMSTATUSTP
The CDCLAIMSTATUSTP table contains the claim status type code values and their descriptions. For example, "Pending", "Closed", "Open" and "Rejected".
CDCLAIMTP
The CDCLAIMTP table contains the claim type code values and their descriptions.
CDCLIENTIMPTP
The CDCLIENTIMPTP contains the client importance type code values and their descriptions. The importance type can be used to indicated VIP situations or other special services that can be applied to this contact.
CDCLIENTPOTENTP
The CDCLIENTPOTENTP table represents the party potential type code and its descriptions.
CDCLIENTSTTP
The CDCLIENTSTTP table represents the party status type code value and its description.
CDCONDITIONATTRIBUTETP
The CDCONDITIONATTRIBUTETP table serves as a means to group condition attributes, allowing a second level of granularity. For example, Core Account Type, Annual Interest rate, and Minimum Charge.
CDCONDITIONOWNERTP
The CDCONDITIONOWNERTP table describes the Terms and Conditions component owner type. For example, PRODUCT or CONTRACT.
CDCONDITIONUSAGETP
The CDCONDITIONUSAGETP table serves as a means to group condition types. For example: ValuePackage Integrity, Rate Fee.
CDCONSPROVCATTP
The CDCONSPROVCATTP table defines the consent provision categories. A consent provision category determines the format of the content provision content.
CDCONSPROVTP
The CDCONSPROVTP table defines the consent provision types. Examples for consent provision types are lines of business or product types.
CDCONTMETHCAT
The CDCONTMETHCAT table contains information on the contact method category type code values and their descriptions. For example, phone, e-mail, or PDA.
CDCONTMETHTP
The CDCONTMETHTP table contains information on the valid values for the contact method type code. For example, primary phone number and cell phone number.
CDCONTRACTRELSTTP
The CDCONTRACTRELSTTP table contains the values and descriptions for the contract relationship status code, which identifies the status of a relationship. For example, "pending," "active," and "terminated".
CDCONTRACTRELTP
The CDCONTRACTRELTP table contains the values and descriptions for the contract relationship type code, which identifies the purpose for a relationship.
CDCONTRACTROLETP
The CDCONTRACTROLETP table represents the contract role type code values and their descriptions. For example, Owner, Beneficiary, Insured, or Payer.
CDCONTRACTSTTP
The CDCONTRACTSTTP table contains the contract status type code values and their descriptions.
CDCONTRCOMPTP
The CDCONTRCOMPTP table contains the values and descriptions for the contract component type codes that describe the type of component. For example, base, rider, or base increase.
CDCOUNTRYTP
The CDCOUNTRYTP table contains the country type code value and its descriptions. For example, "USA", "Canada", or "England".
CDCURRENCYTP
The CDCURRENCYTP table contains the currency type code and its descriptions. For example, Euro, US Dollar, Japanese Yen, British Pound.
CDDEMOGRAPHICSTP
The CDDEMOGRAPHICSTP table defines demographics types.
CDDOMAINTP
The CDDOMAINTP table contains values and descriptions for the domain type code that defines the business area of the agreement component values.
CDDOMAINVALUETP
The CDDOMAINVALUETP table contains the values and descriptions for the Value Type Code, which, in a given domain, identifies the values that are captured. For example, within banking, values captured can be "account balance" and "account deposit".
CDEMEMATCHFUNCTIONTP
This table represent the IBM InfoSphere MDM Probabilistic Matching Engine match function details. A match function is a component of a larger algorithm that compares 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 a street number, a phone number, a first name, a last name, and so forth) are the same, different, or similar (that is, a partial match), and so forth.
CDEMEMATCHWORDTP
This table contains the codes and values for the word-by-word comparisons that each InfoSphere MDM Probabilistic Matching Engine match function code performs (see the CDEMEMATCHFUNCTIONTP table). Some examples of word comparisons that are done are Nickname (for example, Nick or Nicholas) and acronym (for example, IBM or International Business Machines).
CDENDREASONTP
The CDENDREASONTP table defines the reason for why a relationship ended or consent item becomes inactive.
CDENTITYLINKSTTP
This table lists the entity link status types associated with parties that are persisted from virtual MDM. This table is used by the Hybrid MDM functional feature.
CDENTITYNAMETP
The CDENTITYNAMETP table defines the entities that can be associated with consent items.
CDENTITYSTATUSTP
This table lists the entity status types associated with entities that are persisted in MDM.
CDFREQMODETP
The CDFREQMODETP contains the frequency mode type code values and their descriptions. For example, "Weekly", "Monthly", "Quarterly", or "Annual".
CDGENERATIONTP
The CDGENERATIONTP table contains familial generational information in the form of a generation name type code. For example, The First, The Second, Junior or Senior.
CDHIGHESTEDUTP
The CDHIGHESTEDUTP table contains the highest education type code values and their descriptions.
CDHOLDINGTP
The CDHOLDINGTP table contains the holding type code values and their descriptions. For example, "Vehicle" or "Property".
CDIDSTATUSTP
The CDIDSTATUSTP table represents the identification status type code values and their descriptions. For example, Applied For, Certified, or Expired.
CDIDTP
The CDIDTP table represents the identification type code values and their descriptions. For example, social insurance number, social security number, driver's license, passport number, or tax registration number.
CDINACTREASONTP
The CDINACTREASONTP table contains information on the valid values for the inactivated reason type code. For example, "collapsed", "split", or "deceased".
CDINCOMESRCTP
The CDINCOMESRCTP table contains information on the valid values for the income source type code. For example, annual salary and net worth.
CDINDUSTRYTP
The CDINDUSTRYTP table contains the industry type code values and their descriptions. For example, farming, industrial, insurance.
CDLANGTP
The CDLANGTP table contains the values for the Language Type Code and its descriptions. For example, "English", "French", or "Spanish".
CDLINKREASONTP
The CDLINKREASONTP table identifies the reason why two parties are linked together. For example, collapsed, or split.
CDLOBRELTP
The CDLOBRELTP table defines various LOB relationship types. For example, "owner".
CDLOBTP
The CDLOBTP table contains the values and descriptions for all of the lines of business set up in the system.
CDMARITALSTTP
The CDMARITALSTTP table contains the marital status type code values and their descriptions. For example: "married", "separated", or "widowed".
CDMATCHENGINETP
The CDMATCHENGINETP table contains the type information and description of the matching engine use for matching contacts.
CDMATCHRELEVTP
The CDMATCHRELEVTP table contains the match relevancy type code value and its description. For example, LNAME, SSN and ADDRESS LINE 1.
CDMETADATAINFOTP
The CDMETADATAINFOTP table stores information used to identify metadata. For example, task definition, or spec.
CDMETADATAPACKAGETP
The CDMETADATAPACKAGETP table stores a list of meta data package names used to identify the location of metadata in the system. For example, task definition, or spec. Stores a list of meta data package names, which are used to identify the location of the metadata in system, such as task definition and spec.
CDMETHODSTATUSTP
The CDMETHODSTATUSTP table contains the values and descriptions for the contact method status type code. For example, "disconnected", "unlisted", or "no longer available".
CDMISCVALUEATTRTP
The CDMISCVALUEATTRTP table contains miscellaneous value attributes types that are captured.
CDMISCVALUECAT
The CDMISCVALUECAT table categorizes types of miscellaneous values. For example, demographic category, risk category, or standard industry codes.
CDMISCVALUETP
The CDMISCVALUETP table identifies miscellaneous value types that are captured. These attributes can be different value attribute types for a miscellaneous value type, or they can be additional information about a particular miscellaneous type such as status, effective date, created date, or indicator.
CDNAMEUSAGETP
The CDNAMEUSAGETP table contains the name usage type code value and its description. For example, legal name, nickname, or maiden name.
CDNODETP
The CDNODETP table captures metadata regarding how the subtype is represented within the product type hierarchy.
CDORGNAMETP
The CDORGNAMETP table contains the organization name type code values and their descriptions. For example, "doing business as", "abbreviated name", or "legal name".
CDORGTP
The CDORGTP table contains information on organization type code values. For example, charity, trust, estate, or corporation.
CDPAYMENTMETHODTP
The CDPAYMENTMETHODTP table contains various payment method type values and their descriptions. For example, "cash", "cheque", or "payroll deduction".
CDPPREFACTIONTP
The CDPPREFACTIONTP table contains the values of the privacy preference action type code and its descriptions. For example, "Call", "Do not call", "Opt In", or "Opt Out".
CDPPREFCAT
The CDPPREFCAT table contains a high level categorization of privacy preferences types.
CDPPREFREASONTP
The CDPPREFREASONTP identifies the reason for a privacy preference element.
CDPPREFSEGTP
The CDPPREFSEGTP table stores the segment that a privacy preference regulation applies to. This can be based on geography or a particular segment.
CDPPREFTP
The CDPPREFTP table contains the various types of privacy preference information.
CDPREFIXNAMETP
The CDPREFIXNAMETP table contains information on a person's name prefix type code. For example, Mr., Mrs., Dr., or others.
CDPRIMARYTARGETMARKETTP
The CDPRIMARYTARGETMARKETTP table captures information about the primary market that a product targets.
CDPRIORITYCATTP
The CDPRIORITYCATTP table contains the various priority categories that a priority type can belong to. "Task" is a typical priority category that is specifically used by Task Management services.
CDPRIORITYTP
The CDPRIORITYTP table contains the various priorities for campaigns and the like, and includes values such as high, medium, low.
CDPROCACTTP
The CDPROCACTTP table defines the processing activity types. Examples for a processing activity type are collection and storage. If Consent Management is integrated with Information Governance Catalog, this table is filled with the processing activity types that are defined in Information Governance Catalog.
CDPROCPURPTP
The CDPROCPURPTP table defines the processing purpose types. Examples for a processing purpose type are marketing and analysis. If Consent Management is integrated with Information Governance Catalog, this table is filled with the processing purpose types that are defined in Information Governance Catalog.
CDPRODCONTRACTRELTP
The CDPRODCONTRACTRELTP table holds information on the type of relationship a product has with a contract.
CDPRODRELATIONTP
The CDPRODRELATIONTP table holds information about the type of relationship held between two products.
CDPRODRELTP
The CDPRODRELTP table identifies all the relationship types that can exist between products.
CDPRODSTRUCTURETP
The CDPRODSTRUCTURETP table captures information concerning how a product is structured.
CDPRODTP
The CDPRODTP table contains the product type code values and their descriptions.
CDPRODUCTIDENTIFIERTP
The CDPRODUCTIDENTIFIERTP table captures information about the product identifier type code.
CDPRODUCTPARTYROLETP
The CDPRODUCTPARTYROLETP contains the product party role type code and its descriptions.
CDPRODUCTSTATUSTP
The CDPRODUCTSTATUSTP table captures information about the lifecycle status of a product.
CDPROVSTATETP
The CDPROVSTATETP table contains province or state type code values. For example, WA, NJ, ON, or BC.
CDPURPOSETP
The CDPURPOSETP table identifies the purpose for a location as it relates to a role on a contract. For example, statements are sent to the location for the owner of a contract.
CDREGULATIONTP
The CDREGULATIONTP table defines the regulations that can apply to the processing purposes, such as the EU General Data Protection Regulation (GDPR).
CDRELASSIGNTP
The CDRELASSIGNTP table contains the relationship assignment type code values and its descriptions. Party-to-party relationships can be assigned by a court order or judgment, or by another party.
CDRELTP
The CDRELTP table contains trackable information about relationships that contacts 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 which contact is made the "to" contact.
CDREPOSITORYTP
The CDREPOSITORYTP table stores information about the content management systems and its related repositories for an organization.
CDRESIDENCETP
The CDRESIDENCETP table contains the residence type code values and their descriptions. For example, "suite", "apartment", or "building".
CDRESOLUTIONTP
This table contains the values of the entity resolution types and their descriptions. For example, collapsing, merging, or splitting a product record.
CDROLECATTP
The CDROLECATTP table contains a high-level categorization of types for roles. For example, grouping roles, hierarchy roles, relationship roles, and party macro roles.
CDROLETP
The CDROLETP table identifies various role types in the system. For example, "head of household" or "prospect".
CDRPTINGFREQTP
The CDRPTINGFREQTP table contains the reporting frequency type code values and their descriptions.
CDSERVICELEVELTP
The CDSERVICELEVELTP stores the service level agreements for an agreement. For example, "Service during business hours only" or "Service 24/7 through a call center".
CDSHAREDISTTP
The CDSHAREDISTTP table contains the values and descriptions of the share distribution type code that defines how the proceeds of the contract are distributed among the party contract roles.
CDSOURCEIDENTTP
The CDSOURCEIDENTTP table contains the type codes describing what the source identifier values represent in the default source value table.
CDSPECCASCADETP
The CDSPECCASCADETP table captures information about the type of cascade action a spec will have in a hierarchy.
CDSPECUSETP
The CDSPECUSETP table captures information about the usage types a spec will be used for.
CDSTATISTICSAGGREGATIONTP
The CDSTATISTICSAGGREGATIONTP table stores a list of statistics aggregation types to determine the increments by which system statistics data is aggregated. For example: Daily, Monthly, and Yearly.
CDSTATISTICSENTITYTP
The CDSTATISTICSENTITYTP table stores a list of entity types that can be included in system statistics collection. For example: Person and Product.
CDSTATUSREASONTP
The CDSTATUSREASONTP table captures information about the reason a product is in its current state.
CDSUSPECTREASONTP
The CDSUSPECTREASONTP table describes the relevancy of a potential suspect duplicate for a particular party. For example, all elements for the party and the suspect matched.
CDSUSPECTSOURCETP
The CDSUSPECTSOURCETP table indicates how a potential suspect duplicate was identified. For example, system-marked, or user-marked.
CDSUSPECTSTATUSTP
The CDSUSPECTSTATUSTP describes the current status of the investigation into a potential suspect duplicate. For example, "parties not duplicate", or "critical change resolved".
CDSUSPECTTP
The CDSUSPECTTP table enables the replacement of default suspect duplicate processing logic with custom implementation. It also provides hooks to integrate with third party software to perform suspect search and matching.
CDTAXPOSITIONTP
The CDTAXPOSITIONTP table captures information about the relative tax position offered by a product.
CDTENANTTP
The CDTENANTTP table defines the lines of business that can be associated with consent items and processing purposes.
CDTRANSACTIONCATEGORYTP
The CDTRANSACTIONCATEGORYTP table stores a list of transaction category types. For example: Get, Update, and Add.
CDTERMINATIONREASONTP
The CDTERMINATIONREASONTP table stores termination reasons for an agreement. For example, "Agreement terms & conditions violation" in the case of a value package breakage.
CDUNDELREASONTP
The CDUNDELREASONTP table contains information on the valid values for the undeliverable reason type code. For example, bad addresses, incorrect zip code, and so on.
CDUSERROLETP
Code Table for storing User Role Types. Each Type specific functions/data that a user can use within the application
CHARGECARD
The CHARGECARD table is a subtype of the PAYMENTSOURCE table, describing the bank account information used to pay one or more contracts or accounts.
CLAIM
The CLAIM table contains claim information for coverage types that can be insured in a contract. For example: "Auto Claim", or "break-in".
CLAIMCONTRACT
The CLAIMCONTRACT table contains a record of claims against a contract. For example, Automobile, Homeowners and Whole Life insurance policies.
CLAIMROLE
The CLAIMROLE table contains information on the role a party plays on a claim record. For example, Party 1 reported the broken windshield, Party 2 is at fault.
CONDITIONATTRIBUTE
The CONDITIONATTRIBUTE table records attributes that are added to the TermCondition Entity. The attribues are functionally "executable" and are used by business rules to enforce the condition or to perform a calculation described by the condition.
CONSENT
The CONSENT table defines the consent items. A consent item describes to which extent the personal data of an individual is allowed to be processed for a specific purpose. A consent item is associated with one processing purpose and one individual.
CONSENTCONFIGURATION
The CONSENTCONFIGURATION table defines the consent configuration.
CONSENTENTITYASSOC
The CONSENTENTITYASSOC table provides more details about each partial consent, where the consent given or refused does not apply to all personal data of an individual. An entry is created for each entity that is included in, or excluded from consent. It defines the relationship between an entity and a consent item.
CONSENTPROVISION
The CONSENTPROVISION table defines the consent provisions. A consent provision describes a restriction with regard to the consent given or refused for a processing purpose. For example, an individual might agree to receive marketing material but only with regard to TVs. A consent item can have more than one consent provision. A table entry is created for each relationship between a consent provision and a consent item.
CONSENTREGULATION
An entry in the CONSENTREGULATION table defines the relationship between a consent regulation and a processing purpose. A processing purpose can be associated with more than one regulation.
CONTACT
A CONTACT is a legal entity that is tracked in the system, and can be further refined by one of two subtypes: PERSON or ORG. CONTACT can include clients, suspect duplicates, prospects, CSRs, agents, competitors, contact persons, and any other entity whose name, address, telephone number, and relationship to another contact is relevant.
CONTACTCDC
The CONTACTCDC table records information about critical data changes on a CONTACT.
CONTACTDEMOGRAPHICS
The CONTACTDEMOGRAPHICS table contains various demographic data for a contact.
CONTACTMETHOD
The CONTACTMETHOD table stores the ways that a CONTACT can be reached. For example, this can include e-mail address, phone number, fax number, web sites, or others.
CONTACTMETHODGROUP
The CONTACTMETHODGROUP table, a subtype of the LOCATIONGROUP table, links contacts with addresses and specifies rules for reaching those contacts.
CONTACTREL
The CONTACTREL records the relationship between two parties. For example: FROM CONTACT: Sue Smith; RELATIONSHIP: child of; TO CONTACT: Greg Smith.
CONTEQUIV
The CONTEQUIV table provides the link between the system Party ID and the external administrative system Party ID.
CONTMACROROLE
The CONTMACROROLE table represents a high-level role a contact plays in the system. For instance, the contact can be captured in the context of a prospect and, as such, its macro role is recorded as "prospect".
CONTRACT
The CONTRACT table contains information representing the purchase of a PRODUCT. For example, this purchase can include various scenarios including a disability insurance plan, a savings account, a GIC, and so forth.
CONTRACTCOMPONENT
The CONTRACTCOMPONENT table contains information on contract components, such as base, riders, or others. A contract component represents a part of a contract. Every contract must have at least one base component.
CONTRACTCOMPVAL
The CONTRACTCOMPVAL table allows you to model numeric values on the Contract Component, presenting you with a mechanism to extend information associated with a contract component that is only available through back-end systems. Certain contract features such as Balances in accounts, limits, terms and rates are typically what can be modeled using the Value entity. A contract component value has the following characteristics: (i) Allows extending the information 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 a specific type; (vi) Has a specific value; (vii) Has a status; (viii) Has a validity period or is indefinite.
CONTRACTREL
The CONTRACTREL table represents the relationship that an agreement can have with another agreement.
CONTRACTROLE
The CONTRACTROLE table represents an association that links contacts to the various roles they can have on a contract.
CONTRACTROLEREL
The CONTRACTROLEREL table represents an association that links a contact's contract roles together. For example, a role relationship is used to determine the custodian role for a minor on a given contract.
CONTSUMMARY
The CONTSUMMARY table contains a summary view of a contact record and contains indicators that track what information is stored about a particular party.
DEFAULTSOURCEVAL
The DEFAULTSOURCEVAL table identifies a business data element that was defaulted during data collection or migration. For example, a date may be incomplete in the source system and as a result must be defaulted in order to provide the system an accurate and complete date.
EME_RECBKTD
eme_recbktd stores the derived data information for a record that is used for first-pass determination of records for comparison. All records having the same bucket hash (bkthash) belong in the same bucket, and compare to each other.
EME_RECCHKD
EME_RECCMPD
This derived data table stores the comparison data information for a record that is used for scoring records that met the bucketing pass. The purpose of storing information in eme_reccmpd, rather than spreading the information among the various record data tables, is to provide a performance enhancement.
EME_RECHEAD
The eme_rechead table is used to store one row for each record presented to the Embedded Matching Engine.
ENTITYCONDITIONREL
The ENTITYCONDITIONREL table stores the association between the TermCondition the entity (PRODUCT or CONTRACT) to which it applies.
ENTITYCONTENTREFERENCE
The ENTITYCONTENTREFERENCE table stores the content references of the content assets stored in external CMS.
ENTITYROLE
The ENTITYROLE table stores information about the role or roles that a particular entity can play on a particular collection. For example, grouping, hierarchy, or party-to-party relationships.
ENTITYSOURCEASSOC
An entry in the ENTITYSOURCEASSOC table defines the relationship between an entity and the source where the entity managed.
ENTITYSPECUSE
The ENTITYSPECUSE table defines the way a spec will be used to define an entity such as a product.
ENTITYSTATISTICS
The ENTITYSTATISTICS table stores hourly aggregated statistics data about entities stored in the system.
FINANCIALPRODUCT
The FINANCIALPRODUCT table contains information about products that are a hardened subtype of PRODUCT.
GOODSPRODUCT
The GOODSPRODUCT table contains information on a product that is a hardened subtype of product.
HOLDING
The HOLDING table contains records of personal holdings. For example, a list of assets and liabilities such as Vehicles, Dwellings and Mortgage.
IDENTIFIER
The IDENTIFIER table provides an additional way of distinguishing a contact that is natural to them. For example: social security number, driver's license number, or passport number.
INACTIVATEDCONT
The INACTIVATEDCONT table records when a CONTACT is no longer considered active in a company. When an entity becomes inactive, modifications to the INACTIVATEDCONT records are ended.
INACTIVECONTLINK
The INACTIVECONTLINK table maintains the linkage from the CONTACT (target) to an INACTIVATEDCONT (source) entity, tracking a collapsed or split CONTACT that is now an INACTIVATEDCONT, as well as tracking the link that it has with the newly created CONTACT (as a result of a collapse or split).
INACTIVEPRODLINK
This table maintains the linkage between active and inactive entities. Its function is to track entities that have been collapsed or split and are now inactive.
INITIALSTATISTICS
The INITIALSTATISTICS table stores initial statistics data for existing entities in the system. This table is populated by the initializeStatistics transaction after the system statistics collection feature has been enabled.
INCOMESOURCE
The INCOMESOURCE table contains information, provided and attested-to by the party, detailing the CONTACT's investment experience and financial standing. This information is used to determine a CONTACT's suitability in purchasing a new investment.
INSURANCEPRODUCT
The INSURANCEPRODUCT table contains information on products that are a hardened subtype of PRODUCT.
LOBREL
The LOBREL table represents the party ownership by a line of business. For example, John Smith owned by Home Insurance, or Jane Doe owned by Retail banking.
LOCATIONGROUP
The LOCATIONGROUP table links locations, such as addresses and telephone numbers, to contacts and contains rules for use.
MACROROLEASSOC
The MACROROLEASSOC table represents an association between a contact's macro role and its child data. For instance, as "prospect" (macro role), the system can capture that party's email address (associated party child data), "jsmith@example.com". Child data must exist before it can be associated with a macro role.
MISCVALUE
The MISCVALUE table records miscellaneous values that don't fit into other parts of the data model, such as data generated from other systems in the enterprise or other specific details an institution would like to record about its customer base.
NATIVEKEY
The NATIVEKEY table provides the link between the system Contract ID and the external administrative system Contract ID.
ORG
The 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.
ORGNAME
The ORGNAME table contains the different names that an organization uses.
PAYMENTSOURCE
The PAYMENTSOURCE table is the abstract supertype for the various payment source subtypes in the system: BANKACCOUNT, CHARGECARD, and PAYROLLDEDUCTION.
PAYROLLDEDUCTION
The PAYROLLDEDUCTION table represents a contact's payroll deduction payment source information that is used to pay one or more contracts or accounts.
PERSON
The PERSON table is a subtype of CONTACT and represents a human being as a legal entity.
PERSONNAME
The PERSONNAME table contains the names that are used by a person.
PERSONSEARCH
The PERSONSEARCH table contains the standardized or non-standardized versions of the PERSON NAME table to facilitate searching.
PHONENUMBER
The PHONENUMBER table contains a contact's phone number.
PPREFACTIONOPT
The PPREFACTIONOPT table stores the action types that are possible options for each privacy preference type.
PPREFDEF
The PPREFDEF table captures the default privacy preference regulations for an institution. The privacy preference default settings apply to all parties within the system.
PPREFDEFREL
The PPREFDEFREL table defines the parent child relationship between two default privacy preference records, allowing for different privacy preference regulations to supersede other regulations that are based on different criteria.
PPREFENTITY
The PPREFENTITY table stores customized privacy and preference information for a contact, address, contact method, and contract role location.
PPREFINSTANCE
The PPREFINSTANCE table identifies the entity instance that is associated with a privacy preference record. For example, a party has a preference for a new product.
PRIVPREF
The PRIVPREF table stores all privacy and preference records for a contact.
PROCESSINGACTIVITY
An entry in the PROCESSINGACTIVITY table defines the relationship between a processing activity and a processing purpose. A processing purpose can be associated with several processing activities.
PROCESSINGPURPOSE
The PROCESSINGPURPOSE table defines the purposes that the personal data of an individual can be processed for.
PROCPURPCOMPLREQASSOC
An entry in the PROCPURPCOMPLREQASSOC table defines the relationship between a compliance entity and a processing purpose. A processing purpose can be associated with more than one compliance entity.
PROCPURPTENANTASSOC
An entry in the PROCPURPTENANTASSOC table defines the relationship between a line of business and a processing purpose.
PROCPURPQUESTIONNAIREASSOC
An entry in the PROCPURPQUESTIONNAIREASSOC table defines the relationship between a questionnaire and a processing purpose. There can be more than one questionnaire for a processing purpose.
PRODTPREL
The PRODTPREL table stores the relationship type between two product records. These relationships can be used in combinations to provide a hierarchy of products.
PRODUCT
The PRODUCT table contains information on items that are of interest to a business.
PRODUCTCATEGORYASSOC
The PRODUCTCATEGORYASSOC table contains information on a product's association with a category.
PRODUCTCONTRACTREL
The PRODUCTCONTRACTREL table holds the relationship between a product and a contract.
PRODUCTEQUIV
The PRODUCTEQUIV table stores information about how a product is identified in a different system.
PRODUCTIDENTIFIER
The PRODUCTIDENTIFIER table contains a client-defined identifier for the product such as a part number or product code.
PRODUCTMATCHRESULT
This table contains the match result details of the suspect records. Each record is produced by a suspect match engine described by its code type.
PRODUCTNLS
The PRODUCTNLS table is the localization table for the Product table, containing any localization data for fields that must be localized.
PRODUCTPARTYROLE
The PRODUCTPARTYROLE table represents an association that links contacts to the various roles they can have on a product.
PRODUCTREL
The PRODUCTREL table holds information about the relationship between two products. Relationships can be used to determine product substitutes, up-sells, cross-sells, and they can also be used to form bundles and coarser-grain products made up of product components.
PRODUCTSUSPECT
This table contains records of pairs of products which are marked as suspect either by user or system.
PRODUCTTYPE
The PRODUCTTYPE table is a type of product that, unless it is the root product type, is a subtype of another product type.
PRODUCTTYPENLS
The PRODUCTTYPENLS table is the localization table for the ProductType table, containing any localization data for fields that must be localized.
PRODUCTVAL
The PRODUCTVAL table contains a set of values based on a spec format, representing the product's association to some other entity such as the product type. Values are based on spec formats associated to the product type are maintained in this table.
PRODUCTVALINDEX
PRODUCT VALUE INDEX TABLE records all searchable attribute values for a specific product value (indicated by the PRODUCTVAL_ID). For databases with limited or no native XML support, it is this table that is queried when spec value attributes are provided as search criteria (rather than the PRODUCTVAL table).
PRODUCTVALNLS
The PRODUCTVALNLS table is the localization table for the PRODUCTVAL table, containing any localization data for fields that must be localized.
PRODUCTVALNLSINDEX
The PRODUCTVALNLSINDEX table records all searchable attribute values for a specific product value nls record associated with the PRODUCTVAL. For databases with limited or no native XML support, it is this table that is queried when localized spec value attributes are provided as search criteria in the context of a localized search.
PROPERTY
The PROPERTY table contains all HOLDING records that are locations. For example, cottage, private residence, or condominium.
ROLEIDENTIFIER
The ROLEIDENTIFIER table provides an identifier for a contact's specific role on a contract.
ROLELOCATION
The ROLELOCATION table represents an association between a contact's role on a contract to a particular location group.
ROLELOCPURPOSE
The ROLELOCPURPOSE table describes why contract information for a particular role is addressed to a defined location. The location can either be an address or a contact method.
ROLESITUATION
The ROLESITUATION table defines the different arrangements that can be defined by a given party contract role. For example, time delay, or common disaster arrangements on life insurance policies.
SEARCHEXCLRULE
The SEARCHEXCLRULE table provides the initial search exclusion criteria for each search transaction. For example, last name only, last and given name only, or last name and city only.
SERVICEPRODUCT
The SERVICEPRODUCT table contains information about non-physical products that are a hardened subtype of Product.
SPEC
The SPEC table holds information about specs available in the system.
SPECFMT
The SPECFMT contains all the various formats or versions for a system's specs.
SPECFORMATTRANSLATION
The SPECFORMATTRANSLATION table contains locale specific translations for a spec's attribute names.
SPECSRCHATTR
SPEC SEARCHABLE ATTRIBUTE records all spec attributes that are marked as 'searchable' within the system. It assists with both validating that a spec attribute provided in the context of search is in fact searchable and with the dynamic construction of the required SQL to perform the search.
SUSPECT
The SUSPECT table contains suspect duplicates (contacts that are possible duplicates of each other) that a particular contact has in the database.
SUSPECTAUGMENT
The SUSPECTAUGMENT table contains the augmented suspect duplicate processing results preformed by additional matching engines.
TERMCONDITION
The TERMCONDITION table represents a logical condition, containing conditions for entities such as Product and Agreement. TermCondition can be static or executable.
TERMCONDITIONNLS
The TERMCONDITIONNLS table is the localization table for the TERMCONDITION table, containing anylocalization data for fields that must be be localized.
TRANSACTIONSTATISTICS
The TRANSACTIONSTATISTICS table stores hourly aggregated statistics data about transactions that have been run on the system.
USERTABLE
A type of PERSON that is allowed to use the application. The specific functions/data that they can use within the application are determined by the role (CODE USER ROLE) that they are assigned to.
VEHICLE
The VEHICLE table contains all HOLDING records that are vehicles. For example, Mazda M3, Subaru Outback, or Honda Civic.

Parent topic: Physical data dictionary

Last updated: 22 May 2023