R12 Error 'Function not available to this responsibility' When Trying To Access Custom Form. (Doc ID 553014.1)

Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential. R12 Error 'Function not available to this responsibility' When Trying To Access Custom Form. (Doc ID 553014.1) To Bottom In this Document Symptoms Changes Cause Solution APPLIES TO: Oracle Application Object Library - Version 12.1.3 and later Information in this document applies to any platform. SYMPTOMS When attempting to access custom forms, the following error occurs. "Function not available to this responsibility. Change Responsibilities or contact your System Administrator". The issue can be reproduced at will with the following steps: 1. Register custom application. 2. Register custom form under this application. 3. Add it to the menu 4. Add the new product_top variable to the .env file. 5. Bounce the forms server. 6. Place the .fmx file in PROD_TOP/forms/US. 7. Log in to Oracle applications and try opening the form. 8. Encounter the above error. Due to this issue, users cannot access the form in R12 which was working fine in 11.5.10.2 CHANGES Upgrade from 11i to R12. CAUSE The issue is caused by the following setup: Missing entry for CUSTOM_TOP under default.env file. Ideally in such cases,CUSTOM_TOP should be defined under default.env in $INST_TOP/ora/10.1.2/forms/server directory to have your custom form work with R12. SOLUTION To implement the solution test the following stepsin a development instance and then migrate accordingly: 1. Login to server with APPLMGR manager user access. 2. Go to $INST_TOP/ora/10.1.2/forms/server directory. 3. Ensure that your CUSTOM_TOP 's are registered in the default.env file. This means that, you should create an entry for environment variable CUSTOM_TOP (which contains physical path to your custom directory) like below in default.env file present under location $INST_TOP/ora/10.1.2/forms/server directory. For Example: ..... APPL_TOP=/home/applmgr/PROD/apps/apps_st/appl  CUSTOM_TOP=/home/applmgr/PROD/apps/apps_st/custom ------ Note: Incase of multiple CUSTOM_TOP 's are in use, each must be stated in the default.env file. (Previously in R11i you could have one CUSTOM_TOP in the .env file pointing to other CUSTOM_TOP 's)  Alternatively, you can edit below section of $CONTEXT_FILE and add the CUSTOM_TOP <!-- Environment on this Node --> <oa_environments> <adconfig> This will avoid you to edit the default.env file each time you run the Autoconfig. 4. Restart the middle tier services. 5. Retest the issue.