X1-MIGAD DM Batch Not Stamping Valid Service Providers On The US Type
(Doc ID 2882386.1)
Last updated on JULY 22, 2022
Applies to:Oracle Utilities Customer Cloud Service - Version 22A and later
Oracle Utilities Customer to Meter Base - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 2.9]
Information in this document applies to any platform.
On : NA version, Environment Related
X1-MIGAD DM batch not stamping valid service providers on the US type. This is impacting X1-MIGSA.
X1-MIGSA DM batch cannot create the Usage Subscription for the SA Types that pivoted to Bill Determinants Required due to batch error "If populated, the Service Provider on the Usage Subscription must be valid for the Usage Subscription Type".
It appears this was due to a hard-coded value mapped into an MDM field. The batch’s Plug-in Script X1ProcSAIds always pass "OUC2M" in Service Provider, but in all the Usage Subscription Types created by MIGAD, the list of valid service providers is empty.
This is a defect on Migrate Admin job (X1MigSAType.class) – it is creating the service provider (OUC2M) as well as the US type, so it is responsible for stamping the valid service providers on the US type.
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