My Oracle Support Banner

When Transfer Service Getting Failed During ECE Publish The Transaction Is Not Rolled Back In In ECE (Doc ID 2944509.1)

Last updated on APRIL 26, 2023

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


On Oracle Communications Elastic Charging Engine (ECE) when a service transfer transaction getting failed during ECE publish due to some reasons, the transaction is rolled back in Billing And Revenue Management (BRM) successfully but not in ECE (i.e. new balance group created in Balance cache pointing to target account and also the Service is transferred under Target Account which is not correct). Since the transaction is not rolled back, the subscription details exists under both the source account cache and target account cache. But the PublicUserIdentity still pointing to Source account id.

This cause inconsistent rating (happens randomly) behavior as the rated event Call Data Record (CDR) for these subscription points to target account & new balance group which does not exist in BRM, so it fails in Rated Event Loader (REL) loading.

Steps to reproduce:

1.Disable publish in CM & Restart CM

2.Create a (source) account (A1) & subscription (S1). this account will not exists in ECE cache

3.Enable publish in CM & Restart CM

4.Create another (target) account (A2) & subscription (S2). this account should exists in ECE cache

5. Now do service transfer S1 (from A1) to A2 using “PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER”

The service transfer will fail while publishing to ECE with below error:




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

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