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.

Demantra Solutions - EBS (MOSC)

Impact Of New R12 Implementation On Demantra CTO Codes

Dec 12, 2013 7:19PM edited Dec 16, 2013 12:10AM in Demantra Solutions - EBS (MOSC) 1 commentAnswered

Hi

We are on Demantra 7.3.1.4 and collecting CTO data from legacy system.

We are also collecting the BOM details from Oracle Ebiz.

While populating the data we are using below template to load the CTO_CODE (t_ep_cto_code)

<Source Instance Id>::<Organization Id>::<Hyphen separated list of Source inventory item ids>

We are currently reimplementing Oracle to a newer version R12.1.3. Due to this change, our organization ids will undergo changes.

As a result we will be fetching whole new list of CTO CODES even though we would be attempting to bring in the same item combinations.

What is the impact and the workaround for such a case?

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