My Oracle Support Banner

PCM_OP_BILL_GROUP_MOVE_MEMBER Does Not Allow Moving Subordinate Account Even If AR Account Is Same (Doc ID 1487765.1)

Last updated on JUNE 05, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.
*** Checked for relevance on 09-19-2016 ***

Symptoms

Scenario:

1. Account A is the root/paying account and has non paying (subord) childs B and C.
2. Under B we have a subord child account "B-Child" and under C we have a subord child account "C-child".
3. Move subordinate account "B-Child" from B to C.

Problem: PCM_OP_BILL_GROUP_MOVE_MEMBER opcode does not allow moving B-child as it is a subordinate account.

Question:

We understand that this restriction might be required in order to avoid moving accounts across AR accounts as the moving account might have pending/open unsettled items.
But, Why is it a restriction to move subordinate from one parent to other parent when the source and destination parents have the same AR account and also the AR of moving child remains same before and after move?

Changes

 

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!


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