Sensus Data Quality Code Mapping With MDM Condition Codes
(Doc ID 2289066.1)
Last updated on SEPTEMBER 25, 2022
Applies to:
Oracle Utilities Meter Data Management - Version 2.2.0.1.0 to 2.2.0.1.0 [Release 2.2]Oracle Utilities Smart Grid Gateway Adapter for Sensus RNI - Version 2.2.0.1.0 to 2.2.0.1.0 [Release 2.2]
Information in this document applies to any platform.
Symptoms
When trying to map Sensus data quality code to MDM condition codes via D6-IntStsCodeToCondMapLookup, the customer directory maps the Sensus Data quality code to the MDM Condition Code via this Extendable Lookup.
However, it appears OSB transforms the data quality codes into bit positions before loading into MDM.
For eg, N39 is tranformed into following bits - 5, 2, 1, 0
These bit positions are mapped in the D6-IntStsCodeToCondMapLookup extended lookup with the condition code in MDM but then only the highest condition code are considered when mapping to the Condition Code.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |