|
During our upgrade we consolidated many custom tops into a single custom top. As you know there are many references to the fnd_application table through the application_id (examples, concurrent_programs, functions, etc..). We did NOT make any changes to try and resolve these references. Instead we registered a single new custom top using Adsplice. Then using the custom<CONTEXT_NAME>.env file. Then we set the many retired custom top environment variables XX01, XX02, etc.. to point at the path of the new custom top XXNEW_PATH. That has been working fine in production. The problem is that the custom<CONTEXT_NAME>.env does not get cloned and we are looking for a solution that is more clone friendly. I am considering the option of updating he basepath column in the FND_APPLICATION table to point to the XXOCNEW environment variable. The question is do you see any problems? Also, can you think of other alternatives?
|