CIM On Demand Read: Completion Event Creating IMDs In Seeder Error Status
(Doc ID 2581495.1)
Last updated on SEPTEMBER 22, 2022
Applies to:Oracle Utilities Meter Data Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.2 to 2.3]
Information in this document applies to any platform.
Completion event status of Inbound comm BO D3-CIMMeterReadingsResponse creating IMDs in seeder error when head system reporting 5 interval readings for 1 hour window.
Example - Head end system sent 5 interval readings between 4 AM to 5 AM (4:00AM, 4:15AM, 4:30AM, 4:45 AM and 5:00 AM), but MDM Activity Completion event on its inbound comm BO created IMDs in seeder error message "Overcount is Detected"
The expected behavior should be MDM completion event should create IMD successfully by adjusting start/end dates.
In the above example of head end 15 min interval readings, It is expected to create IMDs starting 3:45 AM to avoid Overcount IMD seeder error.
The issue can be reproduced at will with the following steps:
1. Create on demand read request for D3 CIM
2. D3-CIMMeterReadingsResponse comes back with 5 readings in an hour time span.
3. Seeder subsequently fails with overcount because times are not converted to avoid it.
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