My Oracle Support Banner

Why Account Inactivation Changes Service close_when_t ? (Doc ID 408051.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: to
Solaris Operating System (SPARC 32-bit)
Solaris Operating System (SPARC)


When a deferred closure is programmed at service level, /service close_when_t date is set to chosen date. However, if an account inactivation occurs before service closure is actually realized, the close_when_t date changes.

Service closure deffer date is overwritten with inactivation date.

Is there any coherent reason for this behavior ?

This seems to be a bug and this leads to important dysfunction because changing status implies :

- customer communication to inform him on the status change.

- provisioning triggering (for instance to close or inactivate a given service)

- non needed autobilling is sometimes triggered.


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.