Rerate Backout Events Do Not Have PIN_FLD_USERID Populated Correctly
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 18.104.22.168.1
HP 9000 HP-UX 11.0 (32 bit)
Checked for relevance on 23-Feb-2012.
The adjustment events created during the backout step of rerating are not being created with valid PIN_FLD_USERID's. This causes downstream opcodes to fail.
- Created an account with some cycle forwarded charges.
- Rated few events.
- Changed the pin_virtual_time a ahead of 3 days.
- Executed pin_rerate (syntax pin_rerate -t <time_stamp> -a <account_poid>)
- The cm log shows the PIN_FLD_USERID's field having a NULL value.
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 hundreds of Community platforms