Deal "Package_id" Is Not Unique For Two Separate Deals (Purchased In Same Transaction)

(Doc ID 560513.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 24-Mar-2011***


When two (or more) different deals are purchased within a common database transaction, the
PCM_OP_SUBSCRIPTION_PURCHASE_DEAL opcode is not generating separate package_ids for the two deals.

The logic in PCM_OP_SUBSCRIPTION_PURCHASE_DEAL does not take into account the fact
that multiple deal purchases within a single transaction are not the same thing as a plan-purchase.

Once the deals have the same package_id, cancelling one will automatically cancel the other,
which is not correct.  Each deal should have a separate package_id when it is not purchased as part
of a plan.

-- Steps To Reproduce:
You must purchase the deals using testnap, or some other script. This cannot be reproduced using
Customer Center.

1. Create a file containing the flist for a purchase deal and store it in a file "deal_flist.flp". E.g.

0 PIN_FLD_POID POID [0] /account 358259 0
0 PIN_FLD_PROGRAM_NAME STR [0] "Deal Purchase"
0 PIN_FLD_START_T TSTAMP [0] (1193004000) Mon Oct 22 00:00:00 2007
0 PIN_FLD_END_T TSTAMP [0] (1193004000) Mon Oct 22 00:00:00 2007
0 PIN_FLD_SERVICE_OBJ POID [0] /service/telco/gsm/telephony 356363 0
0 PIN_FLD_DEAL_INFO SUBSTRUCT [0] allocated 20, used 1
1 PIN_FLD_DEAL_OBJ POID [0] /deal 336967 0

2. Start testnap and proceed as follows:

nap(9739)> r deal_flist.flp 1
nap(9739)> open rw 1
nap(9739)> commit

3. Checking the log you can see that the second deal has the same package ID as the first.  This
can also be verified checking in /purchased_product.


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