Same PackageId for Product Purchased in Same Transaction even Though Deals and Plans are Different (Doc ID 2177185.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

On :  7.5.0.15.0 version, Subscription Management

In a single transaction, there are 2 separate calls to 'PCM_OP_SUBSCRIPTION_PURCHASE_DEAL' :

        op_subscription_purchase_deal input flist
# number of field entries allocated 20, used 6
0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 536906 10
0 PIN_FLD_PROGRAM_NAME    STR [0] "MIGRATE-IN"
0 PIN_FLD_END_T        TSTAMP [0] (1752649671) Wed Jul 16 00:07:51 2025
0 PIN_FLD_BILLINFO_OBJ   POID [0] 0.0.0.1 /billinfo 545379 0
0 PIN_FLD_DEAL_INFO    SUBSTRUCT [0] allocated 20, used 2
1     PIN_FLD_PLAN_OBJ       POID [0] 0.0.0.1 /plan 174370 10
1     PIN_FLD_DEAL_OBJ       POID [0] 0.0.0.1 /deal 172322 2
0 PIN_FLD_SERVICE_OBJ    POID [0] 0.0.0.1 /service/xxxxxx/qbop 539601 7

and
        op_subscription_purchase_deal input flist
# number of field entries allocated 20, used 6
0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 536906 10
0 PIN_FLD_PROGRAM_NAME    STR [0] "MIGRATE-IN"
0 PIN_FLD_END_T        TSTAMP [0] (1752649671) Wed Jul 16 00:07:51 2025
0 PIN_FLD_BILLINFO_OBJ   POID [0] 0.0.0.1 /billinfo 545379 0
0 PIN_FLD_DEAL_INFO    SUBSTRUCT [0] allocated 20, used 2
1     PIN_FLD_PLAN_OBJ       POID [0] 0.0.0.1 /plan 175612 10
1     PIN_FLD_DEAL_OBJ       POID [0] 0.0.0.1 /deal 173564 2
0 PIN_FLD_SERVICE_OBJ    POID [0] 0.0.0.1 /service/xxxxxx/qbo 537802 7

As can be seen from above, plans and deals are different. However, the second purchase_deal is using the same package_id generated from the first purchase_deal call.

ACTUAL BEHAVIOR  
------------------
The PackageId is the same for product purchased in same transaction even though deals and plans are different.

EXPECTED BEHAVIOR
--------------------
Ideally, it should use a new package_id.

STEPS
-------
The scenario is that our code is opening a transaction and purchasing these 2 plans, which are being purchased on the same account but different service.
1. Open transaction
2. Purchase Plan 1
3. Purchase Plan 2
4. Close Transaction

Cause

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