Implementing Right to be Forgotten by OFSAA

Use the FSI_PARTY_RIGHT_TO_FORGET table to collect the input list of Party IDs for which PII must be removed from the system. The financial institution must source this Party ID list into the FSI_PARTY_RIGHT_TO_FORGET table, and then call the batch (<<INFODOM>>_RightToForget) or schedule it.

Note:

For the sample query, see the Sample Query for the FSI_PARTY_RIGHT_TO_FORGET Table section.
If Redaction is already performed and if you want to implement Right to Forget, you must revert the redaction policy. For more information, see the Disabling Data Redaction section in Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x.

Use the AAI table AAI_DRF_FUNCTION_COLUMN_MAP to store the PII attribute list. During the Right to Forget batch execution, the AAI_DRF_FUNCTION_COLUMN_MAP table is referred to as randomize the PII values. See the Data Redaction section in Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x.

Use the AAI table AAI_DRF_QUERY_METADATA to store the query metadata, which is used during the <<INFODOM>>_RightToForget batch execution. This is the query metadata table that can lead to the following types of queries:

When the table consists of Party Identifier as an attribute, a simple record is required in the metadata query table.

For example: Select v_party_id from Dim_Party where v_party_id='10'

When the table does not consist of Party Identifier as an attribute, an interrelated set of records is required in the metadata query table AAI_DRF_QUERY_METADATA. Compose these set of records in a systematic way such that, for the selected Party Identifier, the table join procedure can be performed and traversed to reach the required PII attribute.

For example: The DIM_CLAIM table does not consist of N_CLAIM_SKEY (N_CLAIM_SKEY is the required Primary Key for the PII Attribute N_DRIVER_SKEY). Therefore, perform a table join procedure similar to the following query:

Dim_driver.n_driver_skey from dim_driver dim_driver, fct_driver_details fct_driver_details,
        Fct_Claim_Driver_Vehicle_Map Fct_Claim_Driver_Vehicle_Map, Dim_Claim Dim_Claim where
        dim_driver.n_driver_skey=fct_driver_details.n_driver_skey and fct_driver_details.n_driver_skey=Fct_Claim_Driver_Vehicle_Map.n_driver_skey and
        Fct_Claim_Driver_Vehicle_Map.n_claim_skey=Dim_Claim.n_claim_skey and
        v_claim_id='GDPR'

In the preceding scenario, DIM_CLAIM.N_CLAIM_SKEY is a Number Datatype.

Note:

For more information about this table, see Table Definition for AAI_DRF_QUERY_METADATA in the OIDF Application Pack Data Protection Implementation Guide.

To arrive at the query above, see Steps to Perform the Table Join Procedure.
For a pictorial representation of this query, see the AAI_DRF_QUERY_METADATA Table section.
For more sample queries generated using the query metadata table, see Sample Queries Using the AAI_DRF_QUERY_METADATA Table.

You must arrive at the SKey or equivalent column in the table, which consists of the required PII attributes. Then the <<INFODOM>>_RightToForget batch uses this key to filter records (For example DIM_DRIVER) and randomize all the PIIs listed in the AAI_DRF_FUNCTION_- COLUMN_MAP for that table.

After completing these steps, PII attributes can be queried and the values are randomized.

I.2 Implementing Right to be Forgotten by OFSAA