Incorrect Cycle Info Flags in First Cycle Forward Event
(Doc ID 2017542.1)
Last updated on MARCH 31, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On : 7.5.0.11.0 version, Subscription Management
After upgraded from 7.5 PS4 to PS11 patch level, the purchase time cycle forward event did not indicate a first cycle, which meant PIN_RATE_FLG_PRO_FIRST was not set in PIN_FLD_CYCLE_INFO->PIN_FLD_FLAGS.
ACTUAL BEHAVIOR
----------------------------
In PS11, the value was coming as 1280 (which is binary "10100000000").
i.e. When bitwise ANDED with PIN_RATE_FLG_PRO_FIRST (0x08 from pin_rate.h or binary "1000"), it results in 0 (false).
EXPECTED BEHAVIOR
--------------------------------
As in the PS4, the value was 1032 (which is binary "10000001000").
i.e. When bitwise ANDED with PIN_RATE_FLG_PRO_FIRST (0x08 from pin_rate.h or binary "1000"), it results in 1 (true).
STEPS
-----------------------
The scenario can be simplified by creating account with monthly cycle forward fee and verify the constructed flist on the value of PIN_FLD_FLAGS of PIN_FLD_CYCLE_INFO SUBSTRUCT.
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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |