Update basepath in fnd_application table to consolidate custom tops

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Update basepath in fnd_application table to consolidate custom tops

dlongmore
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?
Reply | Threaded
Open this post in threaded view
|

Re: Update basepath in fnd_application table to consolidate custom tops

ErmanArslansOracleBlog
Administrator
How did you create your new custom top?
EBS In 12.2 , custom tops should be added using "adsplice" utility.

Refer to this document for the details:
Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)
Reply | Threaded
Open this post in threaded view
|

Re: Update basepath in fnd_application table to consolidate custom tops

dlongmore
We used adsplice and everything is working fine in production and has been for some time now. Our challenge is the extra work involved in cloning because the custom<CONTEXT_NAME>.env file is not automatically handled (copying of file and updating paths). I am looking for a better solution than our current custom<CONTEXT_NAME>.env file.
Reply | Threaded
Open this post in threaded view
|

Re: Update basepath in fnd_application table to consolidate custom tops

ErmanArslansOracleBlog
Administrator
Custom tops (the environment variables) are set from the CONTEXT_FILE.

For example, if you have an custom top named XXEFA, you will have the following in your apps context file;

<XXEFA_TOP oa_var="s_xxefatop" oa_type="PROD_TOP" oa_enabled="FALSE">/u01/install/fs2/EBSapps/appl/xxefa/12.0.0</XXEFA_TOP>


So when you set the run filesystem using EBSapps.env run , EBSapps.env script calls,
<context_name>_hostname.env file (not the Custom env !)
for example: /u01/install/fs2/EBSapps/appl/CLONE_demoorcl.env, which in turns parses the context file and set these custom environment variables using the following ;

if test -f $CONTEXT_FILE; then
  allprods=`grep 'oa_type="PROD_TOP"' $CONTEXT_FILE |
     sed 's/^.*<\([A-Z_a-z0-9]*\).*oa_var[^>]*>[ ]*\([^<]*\)<.*$/\1=\2; export \1;/g'`


So , please revise your custom tops accordingly.
Reply | Threaded
Open this post in threaded view
|

Re: Update basepath in fnd_application table to consolidate custom tops

ErmanArslansOracleBlog
Administrator
so no need for custom env file for defining them.
If you add your custom applications using adsplice properly, this will not be an issue.