CMT: Issue With Multiple Purchase Bundles Using 'PurBun' Tag
(Doc ID 1571681.1)
Last updated on AUGUST 07, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.5.0]
Information in this document applies to any platform.
On BRM 7.5 PS1 and Patch 16833242 on Linux, there is an issue with purchased bundle 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 fails to update purchased_bundle_t with three records.
The issue happens when there are multiple bundles attached, the purchased_bundle_t.dat file which was created contains information related to all bundles. However, all 3 records are present in a single row rather than a single row. The 3 records should be separated by a new line so that there will be 3 separate row,s 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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!