Transfer of Service is Not Working as Expected When There is Promotion Upgrade
Last updated on OCTOBER 03, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Subscription Management
TOS (transfer of service) is not working as expected when there is promotion upgrade in a siebel-brm integrated setup.
Note : 'Promotion' is a Siebel terminology corresponding to a 'Bundle' in BRM
After upgrade to PS17, two issues were observed while calling PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER in two scenarios as below :
Scenario 1) There is a parent account with service 1 and promotion X (products A, B, C, D) and it is upgraded to promotion Y (products A, B, E, F). Promotion X and Y are having 2 common products, so after upgrade the customer will have :
This is because in E2E (end to end) flow there is no specific request to change promotion detail for common products.
As per TOS behavior of PS17, when the request for TOS comes on Service A it will return both promotion X and Y to delete and another promotion gets created internally by PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER. But in AIA there will be a failure as there is no reference for old promotion X in the xref. This is the issue.
Scenario 2) There are two service in same bundle (for example, fixed line and broadband). So for example, both service 1 and service 2 will have same promotion X. When there is a TOS request for these services, there will be call to PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER for every service and BRM will create new promotion for every service and it will have their own promotion. See below table to illustrate the same :
Service - Old Promotion(in BRM) - New promotion(in BRM) - Old XREF- New XREF
Fixedline 111 222 111 222
Broadband 111 333 222 333
So there is an issue with 2nd service transfer when BRM will return old promotion as 111 but XREF does not have any reference for 111 and it will fail while updating XREF (cross reference).
The expectation is to know how to handle the situation from brm side, because in both scenarios above, the old bundle values are being sent in the return flist of TOS opcode to be deleted from xref , but xref will no more contain reference to it (and it will have the value of the new promotion)
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