Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
How to add a new customized context variable to the context file ?
Solution:
270519.1 > Section 3: Implementing AutoConfig Customizations 2. Adding a new context variable to the context file
Use the Oracle Applications Manager Context Editor if you want to add a context variable that is not maintained by AutoConfig. Refer to the Help pages available on your Oracle Applications Manager site. The relevant information for adding custom context variables is located in the "System Configuration" -> "AutoConfig" -> "Custom Parameters" section
You can check the existing context file as an example to find the definition of each field/variable on this page
Review section 1, and section 2 as well to ensure the instance has all the pre-requisites mentioned to be able to customize autoconfig
REPORTS_PRINTER_CODE_BEFORE
REPORTS_PRINTER_CODE_AFTER
OA_VAR - This is the name of the variable associated with the parameter
C_REPORTS_PRINTER_CODE_BEFORE
C_REPORTS_PRINTER_CODE_AFTER
Type is NO_TYPE
Default value - The value that was initially assigned to the variable when it
was created.
&5 for REPORTS_PRINTER_CODE_BEFORE
&4 for REPORTS60_PRINTER_CODE_AFTER
Hope that helps
Please note the following
Please note that since the customer variables are not part of any template , adding them to the context file will not be any use.
TO reflect these in the env file , you may additionally need to customize the template $AD_TOP/admin/template/custom/APPLSYS_ux.env
Ex: REPORTS_PRINTER_CODE_BEFORE=%c_reports_printer_code_before%
export REPORTS_PRINTER_CODE_BEFORE
But when a Adconfig TXK templates patch is applied the template file will be overwritten
The correct procedure for pasta setup is described in Note 839520.1 says to set them in the environment file, so if you want to avoid AutoConfig overwriting it, put it in the custom$CONTEXT_NAME.env under the APPL_TOP. custom$CONTEXT_NAME.env is defined as "s_custom_file" in the context file
Reference:
Note 270519.1 “Customizing an AutoConfig Environment“, particularly “Adding a new context variable to the context file”.
Solution:
270519.1 > Section 3: Implementing AutoConfig Customizations 2. Adding a new context variable to the context file
Use the Oracle Applications Manager Context Editor if you want to add a context variable that is not maintained by AutoConfig. Refer to the Help pages available on your Oracle Applications Manager site. The relevant information for adding custom context variables is located in the "System Configuration" -> "AutoConfig" -> "Custom Parameters" section
You can check the existing context file as an example to find the definition of each field/variable on this page
Review section 1, and section 2 as well to ensure the instance has all the pre-requisites mentioned to be able to customize autoconfig
REPORTS_PRINTER_CODE_BEFORE
REPORTS_PRINTER_CODE_AFTER
OA_VAR - This is the name of the variable associated with the parameter
C_REPORTS_PRINTER_CODE_BEFORE
C_REPORTS_PRINTER_CODE_AFTER
Type is NO_TYPE
Default value - The value that was initially assigned to the variable when it
was created.
&5 for REPORTS_PRINTER_CODE_BEFORE
&4 for REPORTS60_PRINTER_CODE_AFTER
Hope that helps
Please note the following
Please note that since the customer variables are not part of any template , adding them to the context file will not be any use.
TO reflect these in the env file , you may additionally need to customize the template $AD_TOP/admin/template/custom/APPLSYS_ux.env
Ex: REPORTS_PRINTER_CODE_BEFORE=%c_reports_printer_code_before%
export REPORTS_PRINTER_CODE_BEFORE
But when a Adconfig TXK templates patch is applied the template file will be overwritten
The correct procedure for pasta setup is described in Note 839520.1 says to set them in the environment file, so if you want to avoid AutoConfig overwriting it, put it in the custom$CONTEXT_NAME.env under the APPL_TOP. custom$CONTEXT_NAME.env is defined as "s_custom_file" in the context file
Reference:
Note 270519.1 “Customizing an AutoConfig Environment“, particularly “Adding a new context variable to the context file”.
No comments:
Post a Comment