C2M - Billing Issue Occurs When US Override "Stop" and/or "Start" Date/Time Does Not Reflect The Respective IMD Date/Time (Doc ID 2587563.1)

Last updated on SEPTEMBER 13, 2019

Applies to:

Symptoms

C2M - billing issue occurs when US Override "Stop" and/or "Start" date/Time does not reflect the respective IMD date/Time.

Back-to-Back
1.Premise has one Service Point
- Usage Subscription's Override Stop date/time reflects Activity's completion date/time and not the IMD Date/Time

2.Premise has multiple Service Points and each SP is linked to one SA
- Usage Subscription's Override "Stop" date/time (i.e. US/SP record) reflects Activity's completion date/time and not the respective IMD Date/Time
- Usage Subscription's Override "Start" date/time (i.e. US/SP record) reflects one IMD date/time (looks like the latest processed) and not the respective IMD Date/time

Stop
1.Premise has multiple Service Points and each SP is linked to one SA
- Usage Subscription's Override "Stop" date/time (i.e. US/SP record) reflects one IMD date/time (looks like the latest processed) and not the respective IMD Date/time



STEPS-
The issue can be reproduced at will with the following steps:
1. In C2M initiate a Back to Back to stop one acct/Service Agreement on a Premise and start another on the same Premise.
2. Initiate an Inbound Communication for the Activity that was generated such that the Completion Date/Time of the IBComm is different than the Reading Date/Time provided in the same COMM
3. Notice Activity will use the Completion Date/Time as its own Completion Date/Time and will have a IMD Completion Event with the date fo the Reading Date/Time.
4. Notice the Activity Completion Date/Time is used as the Override Stop Date/Time on the Usage Subscription that is ending.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.