This section provides information about the Notice and Consent feature used in the OFSAA Data Foundation applications.
Topics:
· Introduction to Notice and Consent
· Populate Consent Purpose Dimension and Fact Party Consent Tables
According to the Data Protection guidelines, a clear, legal-based, and accessible Notice must be provided to the Party regarding the Personally Identifiable Information (PII), which is collected from the Party during the onboarding process or during any stage of the workflow where PII of the Data Subject is captured.
After providing a Notice, clear Consent must be obtained from the Party regarding the usage and handling of PII by the financial institutions. This Consent must be given by the Party and must be presented to them as their choice with the option of withdrawal from providing Consent at any time. After the Party gives their Consent, their PII can be used in the workflow.
OFSAA is a back-office product and does not have direct interaction with the end-user of the financial institution. Therefore, Notice, and Consent User Interfaces are not applicable. However, the Data Model of Data Foundation is enhanced to hold Notice and Consent information as a download from source systems. The financial institution may further use this feature for the task of processing or reporting.
This section provides information about the Consent Purpose Dimension Population and Party Consent Population processes in the Oracle Financial Services Data Foundation application.
Topics:
· Overview of the Consent Purpose Dimension and Fact Party Consent Tables
· Execute the Consent Purpose Dimension and Party Consent T2T
· Check the Execution Status of the Party Consent Table
· Retrieve T2T Definition as an Excel File
This section provides information about the overview of the Consent Purpose Dimension and Fact Party Consent tables.
Topics:
· Overview of Consent Purpose Dimension Table
· Overview of Fact Party Consent Table
In the Consent Purpose Dimension table (DIM_CONSENT_PURPOSE), Consent content is stored. This table can be populated from Stage Consent Purpose Master Entity (STG_CONSENT_PURPOSE_MASTER) using the SCD-468 packaged in OFSDF.
Fact Party Consent is the table where the Consent of the Party is stored. Table to Table seeded definitions are provided for loading data into the target table Fact Party Consent (FCT_PARTY_CONSENT):
|
SourceTableName |
TargetTableName |
T2TName |
|---|---|---|
|
STG_PARTY_CONSENT |
FCT_PARTY_CONSENT |
T2T_FCT_PARTY_CONSENT |
This section provides information about the execution of the Consent Purpose Dimension and Party Consent T2T.
· Execute the Consent Purpose Dimension through Batch
· Execute the Party Consent T2T Process in PMF
From Consent Party Master, execute the Consent Purpose Dimension SCD by executing tasks present in the SCD batch <INFODOM>_DATA_FOUNDATION_SCD.
Follow these steps to execute the batch:
1. Navigate to the Batch Execution page.
2. Select the seeded batch <INFODOM>_DATA_FOUNDATION_SCD for Consent Purpose Dimension.
3. Select the AS_OF_DATE for which source customer information is required to be loaded into the table.
4. Click Execute Batch.
5. Monitor the status of the batch in the Batch Monitor page of OFSAAI.
For information about the SCD batch execution, see the Slowly Changing Dimension (SCD) Process section in the required 8.1.x.x.x release version of the Oracle Financial Services Data Foundation Application Pack User Guide.
Execute the T2T_FCT_PARTY_CONSENT using the Process Modelling Framework (PMF). For information about how to execute the T2T process, see the Table to Table (T2T) Loading Process section in the required 8.1.x.x.x release version of the Oracle Financial Services Data Foundation Application Pack User Guide.
You can check the log file in the following directories to check the error messages, if any:
· ftpshare/logs/<Run_Date>/<infodom>/RUN EXECUTABLE directory forDIM_CONSENT_PURPOSE.
· ftpshare/logs/<Run_Date>/<infodom>/LOAD DATA directory for T2T_FCT_PARTY_CONSENT.
The most common error message is as follows:
Unique Constraint Violation
This occurs when attempting to re-load or when loading existing records for the already executed AS_OF_DATE.
For SCD, monitor the execution status in the Batch Monitor page.
NOTE:
For more comprehensive coverage of the configuration and execution of a batch, see the required 8.1.x.x.x release version of the Oracle Financial Services Advanced Analytical Applications Infrastructure User Guide.
For T2T, check the status of the Run execution in the Process Monitor page of the Process Modelling Framework (PMF).
T2T definition can be retrieved as an excel document for reference from the metadata browser of the Unified Metadata Manager (UMM) component of OFSAAI.