Oracle Revenue Management and Billing Garbling Customer Information
Oracle Revenue Management and Billing Garbling Customer Information
Oracle Revenue Management and Billing Garbling Customer Information
Version 2.4.0.1.0
E95976-01
April, 2018
Oracle Revenue Management and Billing Garbling Customer Information
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. iii
Oracle Revenue Management and Billing Garbling Customer Information
Preface
About This Document
This document provides detail information on how to garble the customer information in Oracle
Revenue Management and Billing.
Intended Audience
This document is intended for the following audience:
End-users
Implementation Team
Consulting Team
Related Documents
You can refer to the following documents for more information:
Document Description
Oracle Revenue Management and Billing Lists and describes various banking features in Oracle
Banking User Guide Revenue Management and Billing. It also describes all
screens related to these features and explains how to
perform various tasks in the application.
Contents
1. Garbling Customer Information............................................................................................................. 1
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
only 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.
At present, the system does not restrict you from uploading non-financial and financial data (such as
billable charges, adjustments, payments, refund requests, write off requests, and so on) of a person for
whom the Garbling Completed (C1-GBCM) characteristic is set to Y. Therefore, you need to ensure that
the non-financial and financial data of such person is not uploaded in the system.
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.