Update Required In Existing OC3C Voucher Server To Keep Track Of Voucher Old States, Supplier/Agents (Doc ID 3068577.1)

Last updated on JANUARY 22, 2025

Applies to:

Goal

On Oracle Communications Convergent Charging Controller (OC3C), 15.0.0.0.0 version, Chg Ctrl Svcs

Update required in existing OC3C voucher server to keep track of voucher old states, supplier/agents

Customer has an existing voucher management system which is getting replaced by oracle Voucher Management System. In existing customer system, below voucher specific attributes are supported in their database/functionality.

1. Old voucher state: This old state of voucher when we modify a voucher state. In oracle DB, voucher's old-states are not recorded. Here old-state means single old state per voucher is required. i.e. when voucher state modifies then what is previous state, this need to be kept in DB.

2. Supplier ID: This is like sub customers of customer owning the voucher management system. Here customer will own the VWS and will distribute the voucher functionality to different vendors in market. So vouchers for all vendors are maintained by VWS owner but in market they are launched with vendor's name. This vendor/supplier id attribute information is required per voucher/batch.

3. Agent Id: This is a specific id for an application/module/store who is creating the vouchers. This can be understood as a records of voucher creators.

All these attributes are managed/recorded by customer in their voucher reports.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.