CCB Premise Address Updates Not Cascading To MDM SP Address Via Batch Run
(Doc ID 2481595.1)
Last updated on MARCH 04, 2019
Applies to:Oracle Utilities Customer to Meter Base - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.6]
Information in this document applies to any platform.
On :C2M 126.96.36.199.0 version, Sync Request
CCB Premise Address updates not cascading to MDM SP Address via Batch Run
$$C2M_SP_UPDATE global variable does not initialize to FALSE before every MDM SP update triggered by update on CCB Premise.
When CCB Premise is updated via Batch Job, only the first CCB Premise Address update is cascaded to its corresponding MDM SP Address. Succeeding CCB Premise Address update (e.g. 2nd, 3rd record) no longer update the MDM SP to sync up.
Upon checking, in Base Algorithm/Script X1-UPSPFRPR, the $$C2M_SP_UPDATE variable is initially set to false and is set to TRUE when the MDM SP is successfully updated. The base scripts responsible for maintaining MDM SP terminates when $$C2M_SP_UPDATE variable is TRUE. This is not a problem when updating CCB Premise online where CCB Premises are updated one at a time. However, the problem occurs when the CCB Premise is updated via Batch process where update of multiple Premises is possible. Since the global variable is not initialize to false for every update, CCB Premise’s corresponding MDM SPs after the first record are not updated.
We are requesting to always enable the cascading of CCB Premise Address update to its corresponding MDM SP Address.
The issue can be reproduced at will with the following steps:
1. Run CM Batch.
The issue has the following business impact:
Due to this issue, expected result is not met for maintenance of Premise/SP. C2M Data for CCB Premise and MDM SP is out of sync. Transactional Data stored in C2M database is not accurate..
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