Masking Personally Identifiable Information (PII) in scoped function ID’s are enhanced to display masked or unmask values depending on the user definition. Masking personally identifiable information is based on the policies created in database. In FLEXCUBE Enterprise Limits & Collateral Management System masking can be achieved through following steps:

1. Factory shipped personal identifiable information (PII) of FLEXCUBE Enterprise Limits & Collateral Management provided and by default these are available in data store.
2. Masking Maintenance
   1. Bank User can maintain the Masking details using Masking Maintenance Refer Common Core - Security Management System User Guide → Sec: 2.14 Mask Maintenance in the below link, https://docs.oracle.com/cd/E95372_01/html/CommonCore_SMS/CommonCore_SMS02_SecMgmt.htm#Xaf1078884.
   2. Alternatively, Data controller can execute below given sample script to apply default masking maintenance for factory shipped PII. Bank user can modify / remove masking maintenance using step 2a for PII fields.
      Please refer the below sample script for Mask Maintenance:

      DECLARE
      P_ERRCODE VARCHAR2(200);
      BEGIN
           P_ERRCODE:=NULL;
           SMPKS_MASK_TBLCOL.PR_PROCESS_PII_FIELDS(P_ERRCODE);
      END;
      /

3. Policy Creation
   1. FLEXCUBE Universal Banking Solutions used DBMS_REDACT package to apply masking on PII fields.
   2. Data controller can execute below sample script to create REDACTION policies on PII fields. Please refer the below sample script for Policy Creation.

      DECLARE
      P_ERRCODE VARCHAR2(200);
      P_BRANCH VARCHAR2(10) :='000'; -- Initialize to proper branch
      BEGIN
           GLOBAL.PR_INIT(P_BRANCH);
           P_ERRCODE := NULL; SMPKS_MASK_TBLCOL.PR_PROCESS_JOB
      (P_ERRCODE => P_ERRCODE );
      END;

   Note:

   Masking / Redaction is part of Oracle Advanced Security, which is a separately licensed Enterprise Edition option.