Massive Product Change in Siebel/AIA & BRM (Doc ID 1282789.1)

Last updated on DECEMBER 01, 2023

Applies to:

Goal

Provide an approach to massively change a product configuration, keeping Billing and Revenue Management (BRM) and the entire Siebel/Application Integration Architecture (AIA) stack is in sync.

How to prevent a cycle forward (CF) event be picked up by prepaid accounts from existing product which is being used for both prepaid and postpaid customers?

There is a product which is a default product for both prepaid and postpaid customers. The product has a CF fee of 0 (zero) amount associated with it. The product is associated with the current 700K subscribers. When running the CF application, all the 700K subscribers are being picked up in the CF application (pin_cycle_forward), out of which, 650K are prepaid and they are getting picked up due to this product.

How to stop prepaid accounts from getting picked up in the CF application? If any update needs to be done in BRM side, it would have been possible. The system is using Siebel, Customer Relationship Management (CRM), AIA and needs to achieve this in End-to-End manner, so that all the components are in sync.

Solution

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