My Oracle Support Banner

CMA - Error Comparing When Importing Tender Sources (Doc ID 2315900.1)

Last updated on AUGUST 05, 2022

Applies to:

Oracle Utilities Customer Care and Billing - Version and later
Information in this document applies to any platform.


**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

CCB - Oracle Utilities Customer Care and Billing
CMA - Configuration Migration Assistant
BO - Business Object
MO - Maintenance Object


On CCB v2.

CMA - Error Comparing when importing Tender Sources

While running a large configuration import containing several tender sources, it was discovered they all transitioned into the "Error Comparing" status by the object import monitor batch. It is worth noting the target environment is using empty initial install database, making the error listed the impacted object logs rather confounding:

"There already exists an entity with ID SURE in the current system which is a different entity than the one provided in the migration. Migration cannot occur."
(ID changed according to the TNDR_SOURCE_CD for each respective import object)

To test this specific issue, one created a migration request with just the C1-TenderSource plan targeting a single tender source. This produced the same results, using different environments as sources & targets, this might be a bug.

Followed the CMA process as per the administration manual as follows:
Created a migration request with C1-TenderSource migration plan, with a specific key selection type.
Created a migration export data set using the request described above.
Ran F1-MGDPR with trace to create an export file.
Create a migration import data set targeting the described export file.
Ran F1-MGDIM to populate the impacted objects & migration transactions, and update the data set status.
Ran F1-MGOPR to compare the impacted objects & update their status. (First indication of an error.)
Ran F1-MGTPR update the transaction statuses.
Ran F1-MGDIM to update the data set status.

The last two steps were just executed for thoroughness, leading to a generic error for both:
"Error parsing requested import file. See system log for details."


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.