Validation Error On Initial Synch Of Contact: Unable To Transform Contact Type Between CCB And MDM
Last updated on JANUARY 25, 2018
Applies to:Oracle Utilities Customer Care and Billing - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version,
Validation Error on Initial Synch of Contact: Unable to transform Contact Type between CCB and MDM
After Data Conversion in C2M, while running initial synchronization batch jobs for Person - Contact, there is a validation error.
When the inbound request is created, the elements within the data area are being populated with CCB values instead of MDM values. This subsequently causes validation errors to occur.
The first job run in the process is C1-SYNIL. Here are the parameters used to create the Contacts:
This job actually completes okay. The inbound requests are successfully inserted in PENDING status. The problem is, the next job that is run (F1-SYSRQ) fails with validation errors because the elements are not populated correctly.
It was found that X1-TRNCONFLD algorithm is available on D1-OngoingSyncRequestContact whereas no algorithm is plugged-in on D1-InitialSyncRequestContact. As a workaround algorithm on D1-InitialSyncRequestContact was updated and after that synchronization completed successfully.
- Please confirm if this workaround valid;
- Will this be fixed as a permanent solution?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms