This appendix describes the profile options that are used by Oracle Configurator and Oracle Configurator Developer.
This appendix covers the following topics:
To utilize some Oracle Configurator Developer functionality or run the runtime Oracle Configurator within other Oracle Applications such as Order Management, you must set some profile options and decide whether default values for others are appropriate for your installation. The System Administrator responsibility has access to all Oracle Applications profile options.
The profile options that are used by the runtime Oracle Configurator are listed in Runtime Oracle Configurator Profile Options. Only the System Administrator can view and update these profile options.
The profile options that are used by Oracle Configurator Developer are listed in Oracle Configurator Developer Profile Options.
For information about setting profile options, see the Oracle E-Business Suite User’s Guide.
| Profile Option | User | User | Resp | Apps | Site | Required? | Default Value |
|---|---|---|---|---|---|---|---|
| BOM: Configurator URL of UI Manager | - | X | X | X | X | Required with Order Management, iStore, TeleSales, and SalesOnLine | (none) |
| CZ: Add Model Routing Cookie | - | 0 | 0 | 0 | X | Optional | False |
| CZ: Auto-Expire Discontinued IB Trackable Items | - | X | X | X | X | Optional | Yes |
| CZ: Configurator Install Base | - | X | X | X | X | Optional | oracle.apps. cz.dio.config.OracleInstalledBase |
| CZ: Create Item Type Name Method | - | 0 | 0 | 0 | X | Required with Oracle Bills of Material | Item Catalog Description |
| CZ: BOM Tree Expansion State | - | X | 0 | 0 | X | Optional | One level |
| CZ: Disable Configurator Extensions | - | 0 | 0 | 0 | X | Optional | No |
| CZ: Enable List Prices | - | 0 | 0 | 0 | X | Optional | No |
| CZ: Enable ATP | - | 0 | 0 | 0 | X | Optional | No |
| CZ: Enable Selling Prices | - | 0 | 0 | 0 | X | Optional | No |
| CZ: BOM Tree Expansion State | - | X | 0 | 0 | X | Optional | One level |
| CZ: Fail BV if Configuration Changed | - | X | X | X | X | Required with Order Management | No |
| CZ: Fail BV if Input Quantities Not Maintained | - | 0 | X | X | X | Required with Order Management | Yes |
| CZ: Generic Configurator UI Max Child Rows | - | 0 | 0 | 0 | X | Required | 50 |
| CZ: Generic Configurator UI Type | - | X | 0 | 0 | 0 | Optional | Java Applet |
| CZ: Include Unchanged Install Base Items | - | 0 | 0 | 0 | X | Optional | Yes |
| CZ: Only Create CZ Config Items for Selected Nodes | - | 0 | 0 | 0 | X | Optional | No |
| CZ: Populate Decimal Quantity Flags | - | 0 | 0 | 0 | X | Optional | No |
| CZ: Publication Lookup Mode | - | X | X | X | X | Optional | Production |
| CZ: Publication Usage | - | X | X | X | X | Optional | Any Usage |
| CZ: Report All Baseline Conflicts | - | X | X | X | X | Required with Oracle Install Base | No |
| CZ: Skip Validation Procedure | - | 0 | 0 | 0 | X | Optional | (none) |
| CZ: Suppress Baseline Errors | - | X | X | X | X | Required with Oracle Install Base | No |
| CZ: Use Alternate Retraction Algorithm Before Structure Changes | - | 0 | 0 | 0 | X | Optional | No |
| CZ: Use Generic Configurator UI | - | - | X | - | X | Required with iStore or Quoting | Yes |
Note: Following is a description of the symbols used in the previous table:
X: You can update the profile option.
- (dash): You can view the profile value but you cannot change it.
Null/no value: You cannot view or change the profile option value.
The first User column refers to options that can be set indirectly through the Oracle Configurator Developer user responsibility. The other User column (and the Resp, App, and Site columns) refer to the System Administrator responsibility.
Oracle Configurator Developer Profile Options lists the profile options that are used by Oracle Configurator Developer. The System Administrator can specify a value for these profile options at various levels. A Configurator Developer user can modify the default User-level value for each option by changing various settings in Oracle Configurator Developer. In other words, changing one of these settings does not affect any other Configurator Developer users.
For example, to change the User-level setting for CZ: BOM Node Display Name, a Configurator Developer user modifies the BOM Node Display Names setting. This setting appears in the General area of the Workbench. Other settings that a Configurator Developer user can modify appear in the Preferences page.
For more information about updating settings in Configurator Developer, see the Oracle Configurator Developer User’s Guide.
| Profile Option | User | User | Resp | Apps | Site | Required? | Default Value |
|---|---|---|---|---|---|---|---|
| CZ: BOM Node Display Name | + | X | X | X | X | Required | Description |
| CZ: BOM Structure Display Method | + | X | X | X | X | Required | Description |
| CZ: Custom Initialization Parameters | + | X | X | X | X | Optional | (none) |
| CZ: Effectivity Date Filter | + | X | X | X | X | Optional | All |
| CZ: Enable Creation of Functional Companions | 0 | 0 | 0 | 0 | X | Optional | No |
| CZ: Non-BOM Node Display Name | + | X | X | X | X | Required | Name |
| CZ: Non-BOM Structure Display Method | + | X | X | X | X | Required | Name |
| CZ: Number of Table Rows Displayed | + | X | X | X | X | Required | 25 |
| CZ: Number of Rows Displayed in Hierarchical Tables | - | 0 | 0 | 0 | X | Optional | 50 |
| CZ: Require Locking | - | 0 | 0 | 0 | X | Required | Yes |
| GMA: Default Language | - | X | X | X | X | Required | US |
| Help System Root | - | X | X | X | X | Required to display online help | CZ:CONTENTS (at Application level) |
Note: Following is a description of the symbols used in the previous table:
X: You can update the profile option.
- (dash): You can view the profile value but you cannot change it.
+: A Configurator Developer user can view and change the value of this profile option.
Null/no value: You cannot view or change the profile option value.
The first User column refers to options that can be set indirectly through the Oracle Configurator Developer user responsibility. The other User column (and the Resp, App, and Site columns) refer to the System Administrator responsibility.
You must set a value for profile options followed by the word "required," no default is supplied. Ordinary users can see profile options followed by the word "exposed," only system administrators can see the rest. Further details follow the list, click an item to find them.
BOM: Configurator URL of UI Manager
This profile option indicates the Oracle Configurator Servlet URL, which is where the Oracle Configurator Servlet resides. This profile option must be set correctly for the host application to locate the Oracle Configurator Servlet.
The person installing Oracle Applications supplies this URL when running Oracle Rapid Install. Oracle Rapid Install uses this information as the default value for BOM: Configurator URL of UI Manager.
If you recently upgraded to a new version of Oracle Configurator, verify that this profile option is set correctly.
Note: Setting this profile option is not required if you are installing a runtime Oracle Configurator running in a custom Web application. In this case, the person setting up the application that will be hosting the runtime Oracle Configurator must specify the URL of the Oracle Configurator Servlet, and then post the initialization message to that URL.
All URLs in your profile options should be specified with the URL format: machine_name.domain:port_number; where machine_name is the name of the server machine, domain is your domain name, and port_number is the port where your service is running. The Apache server port is typically 880n. For example:
http://appsmachine.appsdomain:8800/OA_HTML/configurator/UiServlet
This profile option enables Oracle Configurator to add the cookie named czPoolToken to HTTP response messages. This cookie is used by the Web server at runtime to route specified Models to specified JVM pools.
The default value is False, which disables adding the cookie. Setting the value to True enables adding the cookie.
This profile can be set only at Site level.
For more information about routing Models to JVMs, see the Oracle Configurator Implementation Guide.
CZ: Auto-Expire Discontinued IB Trackable Items
This profile option controls whether an item’s status automatically changes to Expired in Oracle Installed Base when an Oracle Configurator end user is reconfiguring an installed instance and deselects the item.
The default value is Yes, which means items are automatically set to Expired in Oracle Installed Base when they are removed from a configuration. This profile option can be set at the Site, Application, Responsibility, and User levels.
For more information about the integration between Oracle Installed Base and Oracle Configurator, see the Oracle Telecommunications Service Ordering Process Guide. For more information about Oracle Installed Base, refer to Oracle Installed Base documentation.
This profile option stores the value of the BOM Node Display Names setting. This setting appears in the General area of the Workbench in Oracle Configurator Developer. The default value is Description.
For more information, see the Oracle Configurator Developer User’s Guide.
CZ: BOM Structure Display Method
This profile option stores the value of the BOM Structure Nodes setting, which appears in the Oracle Configurator Developer Preferences page.
For more information, see the Oracle Configurator Developer User’s Guide.
This profile option controls the initial expansion level of the Model tree when the Generic Configurator UI that appears as a hierarchical table is launched from a host application.
If this profile option is not defined or is set to One Level (this is the default), only the root node and its children are displayed. In this case, all other branches are initially collapsed. Any node that contains children is a branch; therefore Model References, Components, and BOM Option Classes are usually branches that can be expanded and collapsed.
Set this profile option to Full to expand all branches of the Model tree when the configuration session begins.
You can set this profile option at the Site level only. For more information about Generic Configurator UIs, see the Oracle Configurator Implementation Guide.
This profile option enables Oracle Configurator to interact with an installed base repository by specifying the Java class to call when an end user configures trackable components.
The default value is oracle.apps.cz.dio.config.OracleInstalledBase which allows Oracle Configurator to integrate with Oracle Installed Base. Oracle Installed Base is the only repository currently supported for integration with Oracle Configurator.
This option can be set at the Site, Application, Responsibility, and User levels.
For more information about trackable components and integration with Oracle Installed Base, see the Oracle Telecommunications Service Ordering Process Guide.
CZ: Create Item Type Name Method
When you import a BOM Model, Item Catalog Groups appear as Item Types in Configurator Developer (that is, in the CZ schema’s Item Master). This profile option determines the default Item Type Name for each imported Item Catalog Group. You can create Item Type names using either Item Catalog Group descriptions (defined in Oracle Inventory) or Item Catalog Group concatenated flexfield segments. The default is Item Catalog Description.
This profile option can be set at the Site level only.
CZ: Custom Initialization Parameters
This profile option stores the value of the Custom Initialization Parameters setting in the Oracle Configurator Developer Preferences page.
For more information, see the Oracle Configurator Developer User’s Guide.
CZ: Disable Configurator Extensions
Set this profile option to Yes if you want to disable all Configurator Extensions in a runtime User Interface (and all Functional Companions in legacy UIs). Disabling all Configurator Extensions can be a useful way of debugging unexpected runtime behavior or performance issues.
See the Oracle Configurator Developer User’s Guide for more information about Configurator Extensions.
This profile option can be set only at the Site level.
The default value is No, which means all Configurator Extensions are enabled.
This profile option stores the value of the Effectivity Date Filter setting in the Oracle Configurator Developer Preferences page.
For more information, see the Oracle Configurator Developer User’s Guide.
This profile option controls whether available to promise (ATP) information for selected items is displayed at runtime. To display ATP information in a UI, set this profile option to Yes. Also refer to the Oracle Configurator Developer User's Guidefor details about settings that control whether ATP information appears in a generated UI.
For more information about integrating ATP with Oracle Configurator, see the Oracle Configurator Implementation Guide.
This profile option can be set only at the Site level.
The default value is No.
CZ: Enable Creation of Functional Companions
Set this profile option to Yes if you want to be able to create new Functional Companions and edit them in Configurator Developer. This profile option is set to No by default.
You would enable this feature only if you need to create or modify Functional Companions in a DHTML User Interface that was created in a previous release of Configurator Developer. However, as of Release 12.1, DHTML UIs are no longer supported. If you are using a User Interface generated with the HTML-based version of Oracle Configurator Developer, use Configurator Extensions, not Functional Companions. See Maintaining or Migrating Functional Companions.
See the Oracle Configurator Developer User’s Guide for more information about Configurator Extensions.
This profile option can be set only at the Site level.
This profile option controls whether list prices for selected items are displayed at runtime. To display list prices in a UI, set this profile option to Yes. Also refer to the Oracle Configurator Developer User's Guidefor details about settings that control whether list prices appear in a generated UI.
For more information about integrating pricing with Oracle Configurator, see the Oracle Configurator Implementation Guide.
This profile option controls whether selling prices for selected items are displayed at runtime. To display selling prices in a UI, set this profile option to Yes. Also refer to the Oracle Configurator Developer User's Guide for details about settings that control whether selling prices appear in a generated UI.
For more information about integrating pricing with Oracle Configurator, see the Oracle Configurator Implementation Guide.
The default value is No.
CZ: Fail BV if Configuration Changed
Use this profile option to determine whether the Batch Validation process fails when validating a saved configuration that has changed. The default value is No. Batch Validation occurs when booking an order in Oracle Order Management.
Set this option to Yes if you want Batch Validate to notify the end user when a previously saved quote or order has changed. In this case, the message that appears contains the item name, description, current quantity, and new quantity.
This profile option can be set at the Site, Application, Responsibility, and User Levels.
CZ: Fail BV if Input Quantities Not Maintained
This profile option determines whether the Batch Validation (BV) process fails if any input quantities change during the BV session. For example, Oracle Order Management passes a quantity of 2 for item A and 3 for item B. Item A is successfully selected first in the BV session and has a quantity of 2. Item B's quantity of 3 is then asserted. A Numeric rule propagates and subtracts 1 from the quantity of A. Item A now has a quantity of 1, which does not match the input value. If this profile option is set to Yes, Batch Validation fails and return a validation status of false.
The default value is Yes, which means quantities are checked against the input quantities during Batch Validation. This profile option can be set at the Site level only.
CZ: Generic Configurator UI Max Child Rows
This profile option controls the maximum number of rows that are displayed at a time in the Generic Configurator User Interface. For example, this profile option is set to 50 (this is the default value). At runtime, an end user expands a BOM Option Class that has 200 Standard Items. The Generic Configurator UI displays 50 of the Items, and provides navigation controls that enable the user to display the next 50 Items.
Customizing the value of this profile option may improve performance of the Generic Configurator UI when the Model has many child Items.
This profile option can be set at the Site level only.
For details about the Generic Configurator UI, see the Oracle Configurator Implementation Guide.
CZ: Generic Configurator UI Type
This profile option specifies the type of Generic Configurator User Interface to display when configuring a BOM Model item for which no matching publication exists. If your host application is Forms-based (such as Oracle Order Management), use this profile option to control whether to use the Java Applet UI or the HTML Hierarchical Table UI. HTML-based host applications such as iStore use the HTML Hierarchical Table UI, regardless of how this profile option is set.
Valid values for this profile option are Java Applet and HTML Hierarchical Table. The default is Java Applet.
For details about the available Generic Configurator UI types and when they are used, see the Oracle Configurator Implementation Guide.
This profile option can be set at the User level only.
CZ: Hide Focus in Generic Configurator UI
This profile option controls whether the Focus column appears in the Generic Configurator User Interface. The Focus column displays an icon that enables an end user to view only a specific part of the Model structure. By default, this profile option is set to No, which means the Focus column does appear.
This profile option can be set at the Site level only.
For details about the Generic Configurator UI, see the Oracle Configurator Implementation Guide.
CZ: Include Unchanged Install Base Items
When an Oracle Installed Base user makes a request to reconfigure an installed instance, this profile option controls what items are returned as lines on the Quote (in Oracle Quoting) or Sales Order (in Oracle Order Management).
Accept the default value of Yes if you want all items to appear in the Quote or Sales Order, regardless of whether they have changed in Installed Base. Set this profile option to No if you want only items that have changed to appear in the Quote or Sales Order. Setting this profile option to No may improve runtime performance because a smaller set of items is returned to the host application.
This profile option can be set at the Site level only.
Note: When the value of this profile option changes, you must restart the Oracle Configurator Servlet for configurations to use the new setting.
For more information about the integration between Oracle Installed Base and Oracle Configurator, see the Oracle Telecommunications Service Ordering Process Guide.
This profile option stores the value of the Non-BOM Node Display Names setting, which appears in the General area of the Workbench. The default is Name.
For more information, see the Oracle Configurator Developer User’s Guide.
CZ: Non-BOM Structure Display Method
This profile option stores the value of the Non-BOM Structure Nodes setting, which appears in the Oracle Configurator Developer Preferences page.
For more information, see the Oracle Configurator Developer User’s Guide.
CZ: Number of Rows Displayed in Hierarchical Tables
This profile option controls the maximum number of rows that are displayed by default in Configurator Developer pages that display data in a hierarchy. These pages include all areas of the Repository and the Workbench. The default value is 50.
If a page contains more rows than the number specified here, Configurator Developer provides links at the top and bottom of the page so users can view the additional rows.
CZ: Number of Table Rows Displayed
This profile option stores the value specified for the Number of Table Rows Displayed setting, which appears in the Oracle Configurator Developer Preferences page. The default is 25.
For more information, see the Oracle Configurator Developer User’s Guide.
CZ: Only Create CZ Config Items for Selected Nodes
This profile option controls whether the runtime Oracle Configurator creates CZ Config Items for options that are included in a saved configuration.
The default value of this profile option is No, which means CZ Config Items are created for all:
BOM Models, regardless of whether they are selected
Integer Features, Decimal Features and Text Features, regardless of whether they have any user input value
Instantiable Components, even if they have no descendants that are selected or have user inputs
Totals and Resources
If the value of this profile option is Yes, CZ Config Items are created for:
BOM Models, but only when any of the following are true:
They are selected
They have descendants that are selected
They are the target of a Connector
Integer Features, Decimal Features and Text Features, only if they have user input values
Instantiable Components, only if they have descendants that are selected or have user inputs, or are the target of a Connector
CZ Config Items are never created for Totals or Resources when this profile option is set to Yes.
Setting this option to Yes may improve performance when saving large configuration models, or a configuration that has many initial BOM Model instances.
This profile option can be set at the Site level only.
Note: When the value of this profile option changes, you must restart the Oracle Configurator Servlet for configurations to use the new setting.
CZ: Populate Decimal Quantity Flags
In Oracle Inventory, an Item can be defined as accepting a decimal quantity. This profile option controls whether BOM Standard Items that accept decimal quantities are imported into the CZ schema as allowing end users to enter a decimal quantity in a generated User Interface. For details about how the Generic Configurator User Interface uses this profile option, see the Oracle Configurator Implementation Guide.
This option can be set at the Site level only.
CZ: Populate Decimal Quantity Flags Profile Option describes the effect of setting this profile option.
| Value | Effect |
|---|---|
| No | This is the default value. All items are imported as allowing only integer input, regardless of how they were defined in Oracle Inventory. |
| Yes | All items are imported as allowing either decimal or integer input, depending on how they were defined in Oracle Inventory. |
If your host application does not support input of decimal quantities, it is recommended that you set the value of this profile option to No and import all BOM Standard Items as allowing only integer values.
If your sales order system does support input of decimal quantities, set the value of this profile option to Yes and then import new BOM Models or refresh and republish existing models to use the new setting.
When the value of this profile option changes, you must perform the following for existing publications to use the new setting:
Refresh all imported BOM Models
Republish existing Model publications
Restart the Oracle Configurator Servlet
This profile option affects the behavior of the Import and Import Refresh concurrent programs. The internal name of this profile option is CZ_IMP_DECIMAL_QTY_FLAG. See the Oracle Configurator Implementation Guide for details.
When publishing a configuration model, an Oracle Configurator Developer user specifies a publication mode to control its availability to hosting applications. Oracle Applications products such as Order Management and iStore use this profile option to determine the publication mode to use when selecting a publication.
You can set this profile option to either Production or Test at the User, Responsibility, Application, and Site levels. The default value at the Site level is Production.
Note: The value of this profile option is cached at runtime. Therefore, when the profile option’s value changes, you must log out of Oracle Applications before starting another configuration session if you want the new value to be used at runtime.
When publishing a configuration model, an Oracle Configurator Developer user specifies one or more Usages to control the publication’s availability to hosting applications. Oracle Applications products such as Order Management and iStore use this profile option to determine the Usage name to use when selecting a publication.
Valid values for this profile option include any Usage names defined in Oracle Configurator Developer. The default value of this profile option is Any Usage, which does not limit the availability of publications based on Usages.
For more information about Publishing, see the Oracle Configurator Developer User’s Guide.
CZ: Report All Baseline Conflicts
If your Oracle Configurator end users can reconfigure installed instances, this profile option determines what Oracle Configurator considers to be a conflict between the instance the end user wants to reconfigure and the baseline configuration that exists in Oracle Installed Base. (In other words, when the differences between the two are significant.)
If this option is set to Yes, Oracle Configurator displays a message when the baseline has changed, even if the changes are minor and compatible with the instance that the end user wants to reconfigure. The message that appears lists the differences between the baseline and the selected instance’s configuration.
If this option is set to No, Oracle Configurator displays a message only when the baseline has changed and the changes are not compatible with the instance that the end user wants to reconfigure. This is the default value.
You can set this profile option at the Site, Application, Responsibility, and User levels.
See also CZ: Suppress Baseline Errors.
For more information about the integration between Oracle Installed Base and Oracle Configurator, see the Oracle Telecommunications Service Ordering Process Guide.
This profile option controls whether Models and UI Content Templates must be locked before you can edit them or perform certain global operations in Configurator Developer. Global operations include publishing and refreshing a Model, and generating logic. The default value is Yes. It is recommended that you require locking in Configurator Developer to ensure the integrity of your configuration model data.
This profile option can be set at the Site level only.
For more information, see the Oracle Configurator Developer User’s Guide.
This profile option allows the Oracle Order Management batch validation process to complete more quickly by allowing parts of the process to be skipped. You may want to do this if, for example, your configuration model is large or has many complex rules, and batch validation takes a considerable amount of time to run.
To use this profile option, you must define a PL/SQL callback function that checks specific criteria of your configuration. When this function returns a value of True, the Batch Validation process does not perform all of its typical tasks, such as restoring the configuration and validating any input values.
Enable this profile option only if one of the following conditions applies:
None of your configuration models include Configurator Extensions (formerly called Functional Companions) that cause the validity of a configuration to depend on data external to the published Configurator model. In this case the value of the profile option should be the name of a PL/SQL function that always returns true.
External data dependencies such as the one described above exist, but you are able to detect programmatically whether that external data has changed since a given configuration was last validated. In this case, the value of the profile option should be the name of a PL/SQL function that returns true only if the external data is known to be unchanged.
If neither of these conditions apply, you should not provide a value for this profile option. In this case, the batch validation process always performs a complete validation.
To enable this profile option, specify the name of your PL/SQL callback function, using the following format:
package_name.procedure_name
This profile option can be set at the Site level only.
For more information about skipping batch validation, and the PL/SQL callback function you must define to do this, see the Oracle Configurator Implementation Guide.
If your Oracle Configurator end users can reconfigure installed instances, this profile option determines whether Oracle Configurator displays a message when the baseline configuration of the instance that exists in Oracle Installed Base has changed, even though the changes are compatible with the configuration that the end user wants to reconfigure. (In other words, the baseline’s Instance Revision Number has changed in Oracle Installed Base.)
When an end user reconfigures an instance of a configuration, Oracle Configurator compares it to the baseline configuration in Oracle Installed Base. The baseline is specified by the Instance Revision Number of the component’s installed instance. If the Instance Revision Number of the component being reconfigured does not match the installed component’s Instance Revision Number, validation errors are generated, because the installed and the new instances do not have the same baseline. This can happen if you are restoring a saved configuration after another configuration based on the same baseline has been accepted into the Installed Base data repository.
If this option is set to Yes, Oracle Configurator does not display a message when the installed instance’s Instance Revision Number has changed.
The default value is No, which means Oracle Configurator displays a message when the component’s Instance Revision Number has changed. This message lists the differences between the baseline configuration and the instance the end user wants to reconfigure.
If the baseline configuration and the instance that the end user wants to reconfigure are not compatible (that is, the changes are significant), Oracle Configurator displays a message regardless of how you set this profile option.
You can set this profile option at the Site, Application, Responsibility, and User levels.
Note: Regardless of how you set this profile option or CZ: Report All Baseline Conflicts, the configuration always contains the latest baseline information when the Oracle Configurator session begins.
See also CZ: Report All Baseline Conflicts.
For more information about the integration between Oracle Installed Base and Oracle Configurator, see the Oracle Telecommunications Service Ordering Process Guide.
CZ: Use Alternate Retraction Algorithm Before Structure Changes
This profile option controls whether Oracle Configurator uses an internal retraction method when an end user changes the configuration by:
Adding or deleting a component
Creating or clearing a connection
If this profile option is set to Yes, Oracle Configurator retracts all end user selections at the same time before updating the configuration. Enabling this profile option may improve performance in large Models when a user performs one of the operations listed above. By default, this profile option is set to No and Oracle Configurator retracts each selection separately before updating the configuration. For more information, see the section on user requests in the Oracle Configurator Extensions and Interface Object Developer’s Guide.
This profile option can be set at the Site level only.
Note: When the value of this profile option changes, you must restart the Oracle Configurator Servlet for configurations to use the new setting.
CZ: Use Generic Configurator UI
This profile option is used only by Oracle iStore and Oracle Quoting. It controls whether these applications consider the Generic Configurator User Interface a valid user interface.
This profile option is used by some Oracle Configurator APIs, like cz_cf_api.ui_for_item. Oracle iStore and Oracle Quoting call this API to decide whether or not an item is configurable and, if it is, which UI to display when an end user makes a request to configure it.
The default value of this profile option is Yes. In this case, if there is a published UI, cz_cf_api.ui_for_item returns the published UI. If the profile option is set to Yes but no published UI exists, cz_cf_api.ui_for_item returns the Generic Configurator UI. If the item is not a Model, the API returns null, which tells the calling application that the item is not configurable.
If this profile option is set to No and a published UI is found for the item, cz_cf_api.ui_for_item returns the published UI. If this profile option is set to No and there is no published UI, cz_cf_api.ui_for_item returns null. In this case, the item will not be configurable from the host application (for example, the Configure button or action will not be available for the item).
The default value of this profile option is Yes and it can be set at the Site and Responsibility levels.
For information about the available types of Generic Configurator UIs, see CZ: Generic Configurator UI Type.
For details about the Generic Configurator UI, see the Oracle Configurator Implementation Guide.
The default value for this profile option is set at the Site level by Oracle Rapid Install and is the base language of your Oracle Applications instance. This profile option is relevant if you are using Multiple Language Support (MLS). See Configuring Oracle Configurator Developer for Multiple Language Support.
This profile option determines which product's context sensitive help content is displayed when a user clicks the global Help link in Oracle Applications. When you install Oracle Configurator (which includes Oracle Configurator Developer), this profile option is set to "CZ:CONTENTS" at the Application level by default.