1. Customer Hub (UCM) Master Data Management Reference
  2. About Entities

About Entities

Entities are concepts that have attributes. In Oracle Customer Hub (UCM) Privacy Management solution, there are two types of entities:

  • Generated entities from Siebel Object Importer. They come directly from definitions in Siebel business components. The main generated entities are: FINCORP Account, FINCORP Account Contact, UCM FINCORP Account Contact Address, UCM FINCORP Account Contact Garage Address Source Data and History, UCM FINCORP Account Contact Privacy, and UCM FINCORP Account Privacy. For more information about these entities, see Siebel Business Rules Administration Guide, version 8.1.

  • Abstract entities. They are built on other entities or value concepts for convenience when using the Authority. The abstract entities in Oracle Customer Hub (UCM) Privacy Management solution include:

    • Abstract entity-privacy flag. This abstract entity is a named collection of privacy attributes for which an option is selected. The default instances of privacy preferences reflect the standard elections for U.S. financial services companies: affiliate flag, telemarketing flag, nonaffiliate flag, and channel flag for dealer sharing. The privacy preferences can also be mapped to Platform for Privacy Preferences Project (P3P) privacy statements to maintain preferences that are consistent with P3P privacy policies.

    • Abstract entity-privacy flag source. This abstract entity is a choice that indicates whether a privacy flag is allowed, denied, or pending, and whether the privacy flag was elected by default or by request based on customer direction. Typically, this entity has the following values: Opt in default, Opt in request, Opt out default, Opt out request, Pending default, and Pending request.

    • Abstract entity-state code. This abstract entity indicates which state out of all the states that come with all the financial account contacts on the financial account is the most restrictive state for that financial account. Some states such as California, Puerto Rico, and Vermont increase the privacy regulatory requirements set by the Graham-Leach-Bliley Act (GLBA) or FCRA. They are listed as separate instances. The other states are listed as one generic instance. For any state code other than the fifty states or DC or Puerto Rico, this code is set to XX. Note that XX represents invalid states; that is, state codes that do not apply to the 50 U.S. states, DC, or Puerto Rico. This practice is common for managing U.S. state legislation and policy. For example, a customer can have one of the following practices:

      • One state code corresponds to one state.

      • One state code corresponds to all states under the same federal law such as GLBA law.