Question

We need to remove a cycle forward event from existing product which is being used for both the prepaid and postpaid customers. We don't want the pin_cycle_forward to pick up prepaid accounts.

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

We need to stop the 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, but in our stack we are using the Siebel CRM, AIA also. So, we need to achieve this in a End-to-End manner, so that all the components are in sync.

Answer

The following is a list of a few possible suggestions, to address the above business requirement.

Option #1 - Siebel is on driver seat for managing the products, and there must be a way to submit a batch process from Siebel to AIA. I assume this is one time effort and will require AIA configuration enhancement to handle the load and recovery. This option will maintain integrity between Siebel, BRM and AIA xref tables.

Option#2 - Run batch process on BRM and then on Siebel and then update cross reference table, in theory this should work but is not documented.

Option#3 - Create your own workflow and let Siebel send data to it, on the other end of your workflow call OOB O2B PIP.

Option#4 - Explore if any ODI KM is available for Siebel batch process which you can use to call O2B process.