AIA-BRM: SERVICE_BALGRP_TRANSFER Opcode Call Sent With Create Request For TO_BAL_GRP_OBJ Field
(Doc ID 2663693.1)
Last updated on APRIL 29, 2020
Applies to:Oracle Application Integration Architecture Foundation Pack - Version 188.8.131.52.0 and later
Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In an Oracle Rapid Offer Design & Order (RODOD) setup, when a user places a modified order to for a payee account of a service, Application Integration Architecture (AIA) calls PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode with below input.
In the above input, the PIN_FLD_POID and PIN_FLD_TO_OBJ are the same, which means the service is not transferred to another non-payee account. Instead, the service is getting transferred to another balance group in the same account. Since the PIN_FLD_BAL_GRP_OBJ is passed in as dummy POID, Billing and Revenue Management (BRM) will create a new balance group and transfer the service to this new balance group.
When a service is transferred from one balance group to another balance group in the same account, BRM will not transfer any balances from old balance group to new balance group. When this happens, customers will not be able to consume the balances available in the old balance group.
Either user must customize BRM to transfer the balances from old balance group to new balance group, or AIA should pass the old balance group in the input request to BRM in PIN_FLD_TO_BAL_GRP_OBJ field.
Why is AIA passing dummy POID in the input request? Why does it not pass the existing balance group to ensure that the customer can consume the balances available in the existing balance group?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document