CMT: Issue With Multiple Purchase Bundles Using 'PurBun' Tag
Last updated on AUGUST 16, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
On BRM 75 PS1, plus the patch 16833242 on Linux, to support /purchased_bundle class, there is an issue in the below mentioned case:
1) One Purchase bundles having 3 products, 2 discounts : This case works ok.
2) Three Purchase bundles having 1 product, 1 discount each : This case failes to update purchased_bundle_t with three records.
The issue is that, when there are multiple bundles attached, the purchased_bundle_t.dat file that is created has information related to all bundles. But all the 3 records are present in a single row (rather single line). The three records should be separated by a new line so that there will be 3 separate rows which will then create three records in purchased_bundle_t table in database.
See below example about the results fetched from the database:
select plan_obj_id0 from purchased_product_t where account_obj_id0=148115174;
select poid_id0 from purchased_bundle_t where account_obj_id0=148115174;
select plan_obj_id0 from purchased_discount_t where account_obj_id0=148115174;
Notice above that the plan_obj_id0 is correctly populated for each purchased_product and purchased_discount. But the purchased_bundle_t has only one record while it should have three records.
Additional information :
Below is the relevant snippet from the input xml :
See that the dat file contains a single line, while it is expected to contain 3 separate rows for each <PurBun> in the input xml.
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