Improvements to Auditability for Voucher Batch Creation
Last updated on APRIL 04, 2018
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 to 18.104.22.168.0 [Release 6.0 to 12.0.0]
Information in this document applies to any platform.
In all versions of Oracle Communications Convergent Charging Controller (OC3C), the architecture of how voucher batches are created resulted in incorrect values being stored in the CHANGE_USER and CHANGE_TERM columns of the CCS_VOUCHER_REFERENCE table.
When creating vouchers through the Service Management Service (SMS) Screens, the ccsVoucher process is invoked which runs on the Service Management Server (SMS) and is responsible for inserting records directly into the CCS_VOUCHER_REFERENCE table.
Database triggers populate the CHANGE_* columns for every insert/update made to the database. The three CHANGE_* columns are:
- CHANGE_TERM - The IP address (or terminal) of the client altering the database record
- CHANGE_USER - The database login altering the database record
- CHANGE_DATE - The timestamp that the database record was last changed
Usually when changes are made through the SMS Screens, the CHANGE_TERM is set to the actual IP address of the host where the client has logged into the SMS Screens from and the CHANGE_USER is set to the SMS screens user who is logged into the SMS Screens. Due to the ccsVoucher binary being called, the CHANGE_TERM ends up being set to the IP of the SMS, and the CHANGE_USER ends up being set to "ccsVoucher".
As a result, it is possible to create voucher batches anonymously.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms