Incorrect Effective_t on /ordered_balgrp
Last updated on JULY 25, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Subscription Management
BRM set incorrect effective_t on /ordered_balgrp after sharing group creation/modification.
1. Create account with two services (two numbers)
2. Create sharing group: call PCM_OP_SUBSCRIPTION_SHARING_GROUP_CREATE opcode and call opcode from event_notify
3. Add numbers
from 1: to sharing group
from 2: call PCM_OP_SUBSCRIPTION_SHARING_GROUP_MODIFY opcode and call opcode from event_notify
This resulted /ordered_balgrp objects created with effective_t set to regular time (Ex: Mar 1 12:07:34 2016) despite the fact that all dates in sharing group creation and modification were aligned to midnight (Ex:Mar 1 00:00:00 2016).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms