Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Configurator - EBS (MOSC)

Effectivity range does not match for item XXX with parent XXX in configuration model XXX

Nov 25, 2013 5:40AM edited Nov 26, 2013 5:39AM in Configurator - EBS (MOSC) 2 commentsAnswered ✓

Hi all,

I have the following problem:

I try to migrate a model from one instance to another (both R12.1.3) using the "Migrate Models" concurrent program.

I get the error: Effectivity range does not match for item XXX with parent XXX in configuration model XXX.

But the there was no end date defined for any item on neither instance.

Of course the starting dates were not the same.

After I changed the effectivity start dates of the BOM-components on one instance to exactly match the start dates of BOM-components the on the other it worked.

But this can not be the solution, or? When having complex BOMs it is not possible to manually synchronize the effectivity dates I think....

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month