/purchased_product.PIN_FLD_CYCLE_END_T Changes when Creating a Deferred Action for Closing Service/Account
Last updated on NOVEMBER 27, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
Checked for relevance on 27-Nov-2017.
On an upgraded BRM system (7.0 to 7.5 PS4), the referenced field for all the purchased products related to the closing service has been changed, after the schedule object has been created to match the closing date (/schedule.PIN_FLD_WHEN_T). That is, the /purchased_product.PIN_FLD_CYCLE_END_T changed when creating a deferred action for closing service/account.
Steps to reproduce
1.) An existing customer has active plans and services with cycle_end_t set to 0 (never).
2.) Create a deferred action to close the account.
3.) When you check the cycle_end_t for the products on the account they have been set to the deferred action scheduled execution date.
For example, the query results:
This behaviour is different from 7.0, where the cycle_end_t for the products would be set at EXECUTION of the deferred action, whereas in 7.5 the cycle_end_t for products is set during CREATION of the deferred action.
Is there any major reason for this change, and, is there any chance for BRM 7.5 to behave like BRM 7.0 NOT modifying this field?
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