This appendix covers the following topics:
The following table describes the profile options for Oracle Installed Base. These profile options are to be set at the site level.
| Profile Option Name | Category | Comments |
|---|---|---|
| FND_ENABLE_LIST_SEARCH | Functional | Enable for List search view in the Transaction Interface Search page. |
| 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 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: Cascade parent status to child for UI transaction | Functional | When enabled, cascades the parent instance status to child when creating the relationship from the UI. Default: No |
| CSI: Check Pending Shipments Before Fulfillment | Functional | When enabled, fulfillment lines are not processed when there are shipment lines pending. This prevents errors on shipment transactions as the later fulfillment transaction is on hold and not interfaced to IB. |
| 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 Installed 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 Installed Base integration with Counters (Y or N). |
| CSI: Customized Mapviewer Class | Deployment | Fully qualified name of the customized mapviewer class. |
| CSI: Debug Level | Debug | For Debug, set at 9 or 10 for Debug to start. |
| CSI: Default Contracts Tab | UI | Displays the Contracts Tab page from the View Customer Products form. |
| 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 Installed Base HTML for display (Internal). Used by other CRM applications to use the Oracle Installed 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 impact 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 Installed Base trackable components at time of shipment/fulfillment (Y or N). |
| CSI: Explode BOM for Phantom ATO Option Item | Functional | Determines whether BOM for Phantom ATO Option item part of internally manufactured configuration needs to be exploded. Default or When Value is Null => Yes. Options => Yes and No. If Yes - Phantom Option Item BOM explosion for internally manufactured item will occur. If No - Phantom Option Item BOM explosion will not happen for internally manufactured Config Item. Eligible WIP issued instance part of config WIP job will come under phantom option item (as per BOM structure). |
| 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 Installed Base User or from the LOV. |
| CSI: Force Cascade Owner from UI and MU | UI | When enabled, this option will force the cascade of ownership for UI and MU transactions. Using the Installed Base Agent User responsibility and the Change Owner UI or Mass Update UI, when the owner of a parent item instance is changed, the owner change and system numbers are cascaded to all the child instances, if this profile option is set to Yes. If the option is set to No, the owner change and system numbers are cascaded to only the child instances which have the same owner. |
| CSI: GOOGLE MAPS API KEY | Deployment | Google API Key for Google Maps |
| CSI: IB Error Correction Program - Auto populate Item instance | Functional | Auto populate option to pick the non-serial instance for RMA case while running error correction program. |
| CSI: IB Tab - Actions Menu | UI | The list of actions allowed to be performed. |
| CSI: IB Tab - Query Only Root Instances | UI | Controls Installed Base tab search behavior in the Contact Center: default value appears in the associated check box in the Find window. |
| CSI: IB Tab - Query Threshold | UI | Controls Installed 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 | Calculates 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: Mapviewer Name | Deployment | Selected mapviewer for GIS integration. This profile checks if customization is defined. Otherwise, default call is used. |
| 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 Installed 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: Operating Unit Restriction | UI | This profile is applicable for the OA framework-based UI through the Oracle Installed Base Agent User responsibility. Used to restrict the CSI agent user to view only the products that belong to a particular operating unit. In addition, the user function name "Restrict Instance Search by Operating Unit” must be enabled at the responsibility's menu. |
| CSI: Override Instance Split for KIT Items | Functional | Used to override splitting (depending upon CSI Auto Split instance profile) of non-serial KIT Item with no IB trackable embedded exploded ATO under it. Default = Y. If 'Y', Splitting is overridden and If 'N', splitting occurs based on CSI Auto Split instance profile. |
| CSI: Process Old Fulfill Lines | Deployment | Enable the processing of old fulfill lines into Oracle Installed Base. If enabled, Oracle Installed Base will attempt to process Oracle Order Management fulfillment line and create and or update item instance. |
| CSI: Pricing Context | Functional | The visible pricing context. Based upon this pricing context, value search can be performed. |
| CSI: Raise Business Event For Customer Owned Instances | Functional | Raise Business Event for Customer Owned Item Instances: CSI_BUSINESS_EVENT_PVT -> UPDATE_INSTANCE_EVENT, CREATE_INSTANCE_EVENT. |
| 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: Sales Facing Quick Search View | Deployment | Sales Facing Quick Search View. Quick Search result view is defined in a profile option CSI_SF_QUICK_SEARCH_VIEW. |
| CSI: Show All Site Usages | UI | Control site usage results based on the profile value: Yes to display All site usages; No to display no site usage. |
| CSI: Switch to 11i Instances Tab in Contact Center form | UI | Switch to 11i Instances tab in Contact Center form. If this profile value is Yes, then the Instances subtab in Install Base tab will be displayed. Otherwise, it will be hidden. |
| CSI: Show Expired Instances | UI | Default = N. Enables users to default the value of the Show Expired Products check box in the Advanced Search page. If the profile option value = Y, then the application shows all instances including expired products in the Oracle Installed 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: Update Net Readings On Reset | Functional | Allows users to specify whether to update the Net reading on reset. |
| CSI: Use Parallel Mode | Functional | When Enabled data is inserted into CSI_BATCH_TXN_LINES and processed by IB Transaction Lines Import, else data is inserted into CSI_TRANSACTIONS_INTERFACE and processed using Interface Install Base Line. |
| CSI: Use Shipping Org for BOM Components Explosion | Functional | When enabled, BOM explosion components will be validated and created against the shipping organization; otherwise, the validation and creation occurs using the item validation organization. If Yes, the shipping/warehouse organization will be used for the BOM child component validation and creation. If No, the item validation organization will be used for BOM child component validation and creation. |
Oracle Installed 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:
Change the value of profile option CSI_DEBUG_LEVEL to either 9 or 10.
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'.
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.
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.