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.

This table is used by the following domain: Party Domain

Field Description Data Type Null Option Is PK
CONSENT_ID The primary key of the consent item. BIGINT Not null Yes
TENANT_TP_CD References the line of business that this consent item applies to. It is the TENANT_TP_CD value of the appropriate CDTENANTTP table. BIGINT Null No
CONSENT_OWNER_ID The ID of the individual. It can be one of the following IDs:
  • For physical MDM (InfoSphere® MDM Advanced Edition), the CONT_ID value of the appropriate CONTACT table
  • For virtual MDM ( InfoSphere MDM Standard Edition), a combination of the member record source code value and the member record ID value, in the following format: <member record source code>:<member record ID>. For example, if the member record source code is EDW and the member record ID is 3631060900, then the value CONSENT_OWNER_ID value is EDW:3631060900.
  • For any other system that manages user profiles, the ID that identifies the person.
 VARCHAR(750) Not null No
PROFILE_SYSTEM_TP_CD The unique ID of the system where the personal data of the individual and of the person who gives consent on behalf of an individual, such as a child, is managed. It is the SOURCE_IDENT_TP_CD value of the CDSOURCEIDENTTP table. BIGINT Null No
PROC_PURP_ID References the processing purpose that this consent item applies to. It is the PROC_PURP_ID value of the appropriate PROCESSINGPURPOSE table. BIGINT Not null No
AGREE_IND Indicates whether consent has been given or refused, or to which extent consent has been given. It can be one of the following numbers:
  • 0 to indicate that consent has been refused.
  • 1 to indicate that consent has been given.
  • 2 to indicate that partial consent has been given. In this case, an entry is created in the CONSENTENTITYASSOC table for each entity that is included in, or excluded from consent.
 BIGINT Not null No
CONSENT_GIVER_ID The ID of the person who gives consent on behalf of an individual, such as a child. It can be one of the following IDs:
  • For physical MDM (InfoSphere MDM Advanced Edition), the CONT_ID value of the appropriate CONTACT table
  • For virtual MDM ( InfoSphere MDM Standard Edition), a combination of the member record source code value and the member record ID value, in the following format: <member record source code>:<member record ID>. For example, if the member record source code is EDW and the member record ID is 3631060900, then the value CONSENT_OWNER_ID value is EDW:3631060900.
  • For any other system that manages user profiles, the ID that identifies the person.
 VARCHAR(750) Null No
CONSENT_GIVER_REL_ID The ID of the relationship between the person who gave consent and the individual. It can be one of the following IDs:
  • If you use physical MDM (InfoSphere MDM Advanced Edition), the CONT_REL_ID value of the appropriate CONTACTREL table
  • If you use any other system that manages user profiles, the value that identifies the relationship
 VARCHAR(1024) Null No
ENFORCEMENT_TYPE Indicates where the records of the individual and the person who gives consent are stored. It can be one of the following numbers:
  • 0 to indicate physical MDM (InfoSphere MDM Advanced Edition)
  • 1 to indicate virtual MDM ( InfoSphere MDM Standard Edition)
  • 2 to indicate any other system
 BIGINT Not null No
LANGUAGE_AGREED_IN_TP_CD References the language in which consent was given, refused, or withdrawn. It is the LANG_TP_CD value of the appropriate CDLANGTP table. BIGINT Not null No
SOURCE_IDENT_TP_CD References the system where consent was given, refused, or withdrawn, such as a mobile app. It is the SOURCE_IDENT_TP_CD value of the appropriate CDSOURCEIDENTTP table. BIGINT Null No
CREATE_DATE The date and time when the consent item was created. TIMESTAMP Not null No
START_DT The date and time when the consent setting becomes valid. TIMESTAMP Not null No
END_DT The date and time when the consent setting is no longer valid. TIMESTAMP Null No
END_REASON_TP_CD The reason for why the consent item became inactive. It is the END_REASON_TP_CD value of the CDENDREASONTP table that defines the reason. A reason can be, for example, that the expiration date is reached or that an individual has withdrawn consent. BIGINT Null No
LAST_UPDATE_USER The ID of the user who last updated the consent item. VARCHAR(20) Null No
LAST_UPDATE_DT The time stamp of the last update. TIMESTAMP Not null No
LAST_UPDATE_TX_ID The transaction that updated the consent item. A unique ID is generated. BIGINT Null No