My Oracle Support Banner

After Moving Member to New Billing Hierarchy, Parent Account Has PARENT_FLAGS=0 in /billinfo Object (Doc ID 2997862.1)

Last updated on JANUARY 15, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version 12.0.0.7.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
In Billing and Revenue Management (BRM), after moving member to new billing hierarchy, the parent account has PARENT_FLAGS=0 in /billinfo object. 
PARENT_FLAGS field indicates whether this billinfo object has a subordinate billinfo. This field will be used to see if one needs to walk through the subordinates in the case of triggering of billing, hence it is expected that after moving member account to a new billing hierarchy, the parent account has this flag with a value of 1. It is not happening and then during the bill now execution, only a /bill is generated for a parent account and not for the member accounts.
The user has some wrappers codes that allow to execute the following operations:

Operation 1 - Creating two accounts and creating hierarchy /group/billing with these (one is the parent account PA1, and the other one is the child/member account CA1).

Operation 2 - Creating new account: PA2 and executing CUSTOM_OP_MS_MOVE_ACCT wrapper to create a new /group/billing, set PA2 account as parent and move the account CA1 as member.
→ CUSTOM_OP_MS_MOVE_ACCT: in this wrapper we have 3 important opcodes calls.
  → PCM_OP_CUST_SET_BILLINFO
  op_cust_set_billinfo input flist:
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 2095474 0
0 PIN_FLD_PROGRAM_NAME STR [0] "MANUAL"
0 PIN_FLD_BILLINFO ARRAY [0] allocated 20, used 4
1 PIN_FLD_POID POID [0] 0.0.0.1 /billinfo 2093938 3
1 PIN_FLD_PARENT_BILLINFO_OBJ POID [0] NULL poid pointer
1 PIN_FLD_AR_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 2093938 3
1 PIN_FLD_PAY_TYPE ENUM [0] 0

  → PCM_OP_BILL_GROUP_MOVE_MEMBER
  op_bill_group_move_member input flist
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 2095474 0
0 PIN_FLD_PARENT POID [0] 0.0.0.1 /account 2093651 0

  → PCM_OP_CUST_SET_BILLINFO
  op_cust_set_billinfo input flist:
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 2095474 0
0 PIN_FLD_PROGRAM_NAME STR [0] "MANUAL"
0 PIN_FLD_BILLINFO ARRAY [0] allocated 20, used 4
1 PIN_FLD_POID POID [0] 0.0.0.1 /billinfo 2093938 3
1 PIN_FLD_AR_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 2096723 0
1 PIN_FLD_PARENT_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 2096723 0
1 PIN_FLD_PAY_TYPE ENUM [0] 10007

EXPECTED BEHAVIOR
-----------------------
PIN_FLD_PARENT_FLAGS field in the /billinfo object of the new parent account PA2 should be updated by BRM to 1.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1- Create /account 1
2- Create /account 2
3- Create a billing hierarchy of accounts. Where we have /account 1 as parent, and account 2 as member of the billing hierarchy.
3- Create /account 3
5- Create a new billing hierarchy of accounts, setting /account 3 as parent and moving /account 2 as member of this new hierarchy.
For the parent /account 3, in the /billinfo, we have the pin_fld_parent_flags = 0 instead of 1.


Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.