Demantra Solutions - EBS (MOSC)

MOSC Banner

Impact Of New R12 Implementation On Demantra CTO Codes

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?

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

EBS Demantra Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center