Why The Product Revision In The deal_products_t Is Not Being Updated To Current Revision? (Doc ID 1467957.1)

Last updated on MARCH 06, 2019

Applies to:

Goal

When adding an event to the 'Event Map' of a product, the revision of the product in the deal_products_t table is not being updated to the most current revision.

For example:
Product A is at revision 1, Deal B contains Product A with Product A being at revision 1

It is decided that Product A should have purchase fees associated with its purchase, so an /event/billing/product/fee/purchase event is added to the event map, through pricing center (Product Purchase Fee Event).

When the change is committed to the database, the product is updated and now Product A is at revision 2.

The problem is that Deal B still contains Product A at revision 1, i.e. in deal_product_t the entry for Product A on Deal B has the product_obj_rev at 1 instead of 2.

This is a problem because we have added 2 custom events to some products and are looking for those events on the products at the purchase and cancellation time of the product. i.e. when a product is cancelled we check to see if the product has this event (using PCM_OP_READ_OBJ with the flag PCM_OPFLG_USE_POID_GIVEN to find the information for the exact revision of the product on the account), and then do some processing. So, if the product was purchased before the event was added to the product, we don't want to do anything at cancellation time.

Moving forward, this is a problem, because despite the fact that a product is purchased after the time when the event was added, it is still 'purchasing' the product at an older revision, and storing in account_product_t that the product on the account is at the older revision, so when we go to cancel that product later on, it will not show the event when we do the read of the product.

Solution

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