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.
This table is used by the following domain: Party Domain
| Field | Description | Data Type | Null Option | Is PK |
|---|---|---|---|---|
| CONS_PROV_ID | The primary key of the consent provision. | BIGINT | Not null | Yes |
| CONSENT_ID | References the consent item to which the consent provision belongs. It is the CONSENT_ID value of the appropriate CONSENT table. | BIGINT | Not null | No |
| CONTENT | The content of the consent provision. It provides a description of what is included in the consent. | CLOB(10 KB) | Null | No |
| CONS_PROV_TP_CD | References the consent provision type that this consent provision is based on. Examples for consent provision types are lines of business and product types. It is the CONPROV_TP_CD value of the appropriate CDCONSPROVTP table. | BIGINT | Not null | No |
| CREATE_DATE | The date and time when the consent provision was added to the consent item. | TIMESTAMP | Not null | No |
| START_DT | The date and time when the consent provision becomes valid. | TIMESTAMP | Not null | No |
| END_DT | The date and time when the consent provision is no longer valid. | TIMESTAMP | Null | No |
| LAST_UPDATE_USER | The name of the user who last updated the consent provision. | 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 provision. A unique ID is generated. | BIGINT | Null | No |