Garbling Customer Information

Oracle Revenue Management and Billing enables you to garble the personal information of a customer, such as the customer name, address, email ID, social security number or any other identifier, birth date, gender, and so on. On receiving the data erasure request from a customer, the data controller will garble the personal information of the customer by masking the data with random characters and then cease the access to the customer records.

To garble the information of one or more persons, you need to do the following:

  1. Define the Garble Data (C1-GRBL) characteristic for each person whose data needs to be garbled and set its value to Y.

  2. Execute the Garble Person Information (C1-GRBPI) batch. For more information about this batch, see Oracle Revenue Management and Billing Batch Guide.

On executing the Garble Person Information (C1-GRBPI) batch, the system identifies the persons where the Garble Data (C1-GRBL) characteristic is set to Y and the Garbling Completed (C1-GBCM) characteristic is either not defined or set to N. Note that the system considers the Garble Data (C1-GRBL) characteristic value which is effective on the batch business date.

Once the persons are identified, the data in the following fields is masked with random characters across all records in the system:

  • ACCOUNT_​NBR

  • ACCT_​NBR

  • ADDRESS1

  • ADDRESS1_​UPR

  • ADDRESS2

  • ADDRESS3

  • ADDRESS4

  • BIRTH_​DT

  • BROKER_​NAME

  • CITY

  • COUNTRY

  • COUNTY

  • CUSTOMER_​NAME

  • EMAILID

  • ENTITY_​NAME

  • ENTITY_​NAME1

  • ENTITY_​NAME2

  • ENTITY_​NAME3

  • GEO_​CODE

  • HOUSE_​TYPE

  • IN_​CITY_​LIMIT

  • NAME1

  • OVRD_​MAIL_​NAME1

  • OVRD_​MAIL_​NAME2

  • OVRD_​MAIL_​NAME3

  • PER_​ID_​NBR

  • PHONE

  • POSTAL

  • POSTAL_​UPR

  • STATE

In other words, the personal and account related information of a customer is garbled across the system. In addition, this batch allows you to garble the required characteristics and identifiers of a person and account.

Note: An account may have one or more persons linked to it. The information of an account is garbled when the data erasure request is received for the main customer of the account.

Once the personal and account related information of a customer is garbled, the access group of the person is changed to C1GB (which does not have any data access role). This ensures that the data of the person and his or her accounts cannot be accessed from any screens in the system. If an approval transaction contains personal and account related information of a customer, you cannot even view the approval transaction in the system.

Note: The access is forbidden for performing any transaction for the person and account only from the user interface and web services and not through the background process.

You can also garble the data of a person using the C1-GRBPI inbound web service. However, you can garble the data of only one person at a time using this inbound web service.

Parent Topic: Oracle Revenue Management and Billing Generic Business Processes