Failures When Importing CMT Files For New Timeperiod (Doc ID 2728161.1)

Last updated on JUNE 21, 2021

Applies to:

Goal

On : 3.20.2.0.0 version, Integration Points

Failures when importing CMT files for new timeperiod.

We are importing new time period into UAT and received failures which is preventing the correct data/config to be loaded in the UAT environment. The UUIDs from source to target environment were misaligned.  We had refreshed our UAT environment to see if the issue would be resolved which it was not, therefore, we know that the issue also exists in production.

As we were needing to migrate our config to UAT , we had to resolve this issue.  Knowing that the issue exists in production as well, we opted to update the UUID instead of purging the affected policies as a POC for the fix that will be required for production.  

We would like product team to confirm if the same approach we took in UAT can be done in production, or alternatively please advise on another solution.  

 In addition to the data fix we ask that the mechanism to create and import CMT files be explored a further to prevent the reliance solely on the UUID in the event that the user has done something incorrect.

Solution

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