Oracle Install Base System Profile Options and Debug Information

Oracle Install Base System Profile Options

The following table describes the profile options for Oracle Install Base. These profile options are to be set at the site level.

Profile Options for Oracle Install Base
Profile Option Name Category Comments
CSI: Allow Install Parameter Update Debug Use this profile option with great caution. The default = N. Do not alter this setting unless instructed to do so as part of patching or by Oracle Customer Support or Development. Changing the default can cause irrecoverable data corruption. (This profile option is set to Y after migration to allow a one-time update to install parameters. Then it is set to N.)
For more information, refer to the discussion of the Override Ownership check box in Section 2.5.1, "Set Up Installation Parameters".
CSI: Archive Block Size Deployment Defines the number of rows that are read and written as a unit during the internal processes of purging transaction history.
CSI: Auto-Generate System Name Deployment Auto-generate System Number at time of system creation (Y or N).
CSI: Auto-split Instances During Instantiation Functional Auto split instances with multiple quantity to 1 per instance at time of instance creation (Y or N).
CSI: BOM Explosion Level Functional Number of BOM levels to explode for creation of component-of configuration from BOM setup (1, 2, 3.). Note that BOM explosion stops at any level where child is at quantity > 1.
CSI: Cascade System Termination Functional Cascade system termination to instances (Y or N).
CSI: Configurator Enabled Deployment Default = Network Models Only. Used for integration with the TSO solution and the Oracle Configurator product.
CSI: Contracts Enabled Deployment Enable Oracle Install Base integration with Oracle Service Contracts (Y or N). If enabled, an instance will be included in the service contracts.
CSI: Counters Enabled Debug Enable Oracle Install Base integration with Counters (Y or N).
CSI: Debug Level Debug For Debug, set at 9 or 10 for Debug to start.
CSI: Default Install Date with Ship or Fulfillment Date Functional Optionally populates installation date from the actual shipment/fulfillment date. Previously, the installation date for an item instance was based on the installation date specified in the Transaction Details window for a sales order line. If the date was not entered, then the installation date was left blank.
CSI: Default Instance Status Functional Default Instance Status at time of instance creation. Pick one status from the LOV.
CSI: Default Party Relationship Type for Party/Account Merge Deployment Provides a default value for party relationship type for party and account merge routines.
CSI: Default Version Label Functional Default version label at time of instance creation. Pick one from the LOV.
CSI: Display HTML UI Ul Option to use Oracle Install Base HTML for display (Internal). Used by other CRM applications to use the Oracle Install Base HTML UI (Y or N).
CSI: Display Impacted Contracts Functional Controls the automatic display of a warning page indicating the impacted contracts, when changes to an item instance imapct existing contracts. Does not affect the behavior of the View Impacted Contracts button.
CSI: Enable Contracts For Open Interface Functional Default = N. A setting of Y means that the Oracle Service Contracts application creates Service Warranties where applicable during an Open Interface run. Setting the profile option to N imports data faster than when it is set to Y.
CSI: Enable SQL Trace Debug For Debug (Y or N). Set to Y to start Debug.
CSI: ESRI Default Service Functional Specifies the default ESRI REST-based map service which will be used to initially launch the map page. This profile displays a list of all functions associated with the FND Form object ESRI_SERVICE_LINKS.
CSI: Explode BOM Functional Enable BOM explosion for top assembly with Oracle Install Base trackable components at time of shipment/fulfillment (Y or N).
CSI: Filter Display of all Contracts UI Default = N. If set to Y, the application displays only active contracts.
CSI: Forms to SSWA Default Responsibility UI Default user for applications to launch HTML from forms. Default Install Base User or from the LOV.
CSI: IB Tab - Query Only Root Instances UI Controls Install Base tab search behavior in the Contact Center: defaults the value to the associated check box in the Find window
CSI: IB Tab - Query Threshold UI Controls Install Base tab auto-query behavior in the Contact Center: shows the result set only if the query count is less than or equal to the profile option value. For other cases, you must use the Find window.
CSI: Ignore Counter time component introduced for Time Base Counter engine Functional Caculates counter reading based on the following statement:
==> runtime - previous_value_timestamp
CSI: Instance Termination Status Functional Default Termination Status. Pick one from the LOV.
CSI: Log file Name Debug The name of the log file for Debug.
CSI: Log File Path Debug For Debug ('utl-file-dir' parameter in init.ora).
CSI: OA Default Selection of the View Dropdown UI Select a value to default the selection of view in the dropdown list of the item instance search summary page. Selecting this option will improve the usability by defaulting the more frequently used view.
CSI: OE Line Processing Delay Deployment Delay between OE line processing. Time between order line processing to allow for Oracle Install Base update completion to avoid record locking. Recommended delay: 60 seconds.
CSI: Open Interface Commit Record Limit Deployment Used to commit Open Interface transactions to the data base. Default = 1000.
CSI: Process Old Fulfill Lines Deployment Enable the processing of old fulfill lines into Oracle Install Base. If enabled, Oracle Install Base will attempt to process Oracle Order Management fulfillment line and create and or update item instance.
CSI: Restrict LOV's on Site Usage. UI Default = N. Set at Site Level. For value = Y, the application restricts the Installed Locations LOV in the Systems page to customer addresses with locations identified as Install At.
CSI: Show Expired Instances UI Default = N. Enables users to default the value of the Show Expired Products checkbox in the Advanced Search page. If the profile option value = Y, then the application shows all instances including expired products in the Oracle Install Base UI.
CSI: Stop At Debug Errors Deployment Set to Y to start debug (Y or N).
CSI: System Name Update Allowed Functional System name update allowed after system name creation (Y or N).
CSI: UI Default Selection of View Details Dropdown UI Defines the default link populated in the ‘speed menu' for summary results displayed in the Search Products page.
CSI: Use Parallel Mode Functional Determines which approach (SFM or Concurrent) to use in order to process order lines in Oracle Install Base. If you set the profile option value to Yes, the IB Transaction Lines Import concurrent program will process the transaction lines.
CSI: Update Net Readings On Reset Functional Allows users to specify whether to update the Net reading on reset.
SERVICE Master Inventory Validation Organization -- Replaces the ASO: Product Organization profile option obsoleted in a prior release.
During the upgrade process, the inventory organization specified in this profile is used to upgrade customer products manually created in Oracle Service.
After upgrade, it is used to default the Organization field value in Oracle Install Base pages.

Setting the Debug Option

Oracle Install Base provides an option to write debug information in a log file. By default, the debug feature is turned off. To turn the debug option off, change the profile option CSI_DEBUG_LEVEL value to 0.

To enable the debug option, perform the following steps:

Steps

  1. Change the value of profile option CSI_DEBUG_LEVEL to either 9 or 10.

  2. Specify the value of the profile option CSI_LOGFILE_PATH to be the path of the directory on the server side where the log file should be written.

    You must choose the log file path from the list of paths defined for the parameter utl_file_dir in the init.ora file. Alternatively, you can run the SQL statement:

    • SELECT value FROM v$parameter WHERE name = 'utl_file_dir'.

  3. Specify the value of profile option CSI_LOGFILE_NAME to be the name you want to give to the log file.

    The specified log file will be written in the CSI_LOGFILE_PATH directory on the server side, and all debug messages will be written to this file. Each message in the log file will have the session ID and username attached to it.

  4. Use these settings as required:

    • CSI Stop At Debug Errors: Set to Y to start Debug.

    • CSI Enable SQL Trace: Set to Y to start Trace.