How to setup Oracle Install Base

How to setup Oracle Install Base

Posted by Apurva Goel at 3:48 AMRead our previous post

Following is the summary of steps to be performed to setup Install Base

1. Set up Inventory attributes for IB trackable items

All items that need to be tracked in Oracle Install Base and Enterprise Install Base are set up as Oracle Install Base trackable, whether they are tangible or non-tangible. An item can be either Oracle Install Base trackable or a service item such as a contract. It cannot be both.

For an item to be set up as trackable in Oracle Install Base, the Install Base Tracking checkbox must be selected on the Service tabbed page of the Item window.

A Serviceable Item from Service Contracts automatically defaults the Install Base trackable flag.

2. Confirm the setup of Service Fulfillment Manager Event Queue

Oracle Install Base is dependent on the SFM Event Manager Queue Service in order to get data from source applications.

The SFM Event Manager Queue Service should have been set up prior to setting up Install Base. Proper operation of the queue service is essential for data to pass from E-Business Suite applications to Install Base. Monitor the status daily, and check it when expected item instances do not appear in Install Base.

3. Set up Order Management menus and workflows

This menu setup is required so that Installation Details and Maintain Systems are set up as part of the Action menu. Without this setup, for example, attempts to access the Transaction Details window produce an error message.

A workflow has to setup using the workflow builder. Once the workflow is defined, assign it to different transaction types in OM

4. Set up installation parameters

Oracle Install Base keeps a set of customer-specific installation parameters defined in a table at setup time. You use the Installed Parameters window to provide them. After you define them and select Freeze, the fields cannot be updated.

5. Set up extended attributes for IB instances

To set up extended attributes, the name and code of the attribute have to be set up in the pool of attributes. This is where users can define an attribute’s name, code, and description to be used in the LOV when the extended attribute is set up.

You can navigate to the Install Base Lookups window from the Oracle Installed Base Admin responsibility:

Type: CSI Lookup

Lookup Type: CSI_EXTEND_ATTRIB_POOL

Access Level: Extensible

Values are not seeded for this code.

6. Set up instance statuses

Instance statuses are used to describe the current state of an item instance. They are user-extendible and are defined through a combination of check boxes.

7. Set up transaction subtypes and use in Transactions Details

Before any source transaction can be used in the LOV for a transaction subtype, you must define the source transaction types. All integration sources and transaction types must be defined here before they can be used to update Oracle Install Base. Values can be seeded or user-defined.

You can navigate to the Source Transaction Types window from the Oracle Installed Base Admin responsibility.

8. Handling errors and using the transaction error processing program

A transaction error occurs when a transaction from an application that integrates with Install Base is not properly processed.

Schedule the Resubmit Interface Process to process the transactions in the Error processing table. This program can be set up to process selected lines or all lines in the table and can be run as needed or set up to run at a regular intervals.

9. Create business users

A Business user can view and perform limited updates to the equipment instances that belong to the business and accounts with which this type of user is associated.

Create business users as needed for Oracle Install Base. To do so, you must create business users and assign them the predefined CSI_END_USER role and the responsibility of an Oracle Install Base customer

10. Create agent users

Agent user is the user type for an enterprise's employees to support all the equipment instances in the application, regardless of its ownership. This user type has access to all the functionalities of the application.

Create agent users as needed for Oracle Install Base. To do so, you must create internal users and assign them the predefined CSI_NORMAL_USER role and the responsibility of an Oracle Install Base user.

11. Set up profile options and concurrent programs

CSI Allow Install Parameter Update	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).
CSI Auto-Generate System Name	Auto-generate System Number at time of system creation (Y or N).
CSI Auto-Split Instances During Instantiation	Auto split instances with multiple quantity to 1 per instance at time of instance creation (Y or N).
CSI BOM Explosion Level	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	Cascade system termination to instances (Y or N).
CSI Configurator Enabled	Default = Network Models Only. Used for integration with the TSO solution and the Oracle Configurator product.
CSI Contracts Enabled	Enable Oracle Install Base integration with Oracle Service Contracts (Y or N).
CSI Counters Enabled	Enable Oracle Install Base integration with Counters (Y or N).
CSI Debug Level	For Debug, set at 9 or 10 for Debug to start.
CSI Default Instance Status	Default Instance Status at time of instance creation. Pick one status from the LOV.
CSI Default Version Label	Default version label at time of instance creation. Pick one from the LOV.
CSI Display HTML UI	Option to use Oracle Install Base HTML for display (Internal). Used by other applications to use the Oracle Install Base HTML UI (Y or N).
CSI Enable Contracts for Open Interfaces	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	For Debug (Y or N). Set to Y to start Debug.
CSI Explode BOM	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	Default = N. If set to Y, the application displays only active contracts.
CSI Forms to SSWA Default Responsibility	Default user for applications to launch HTML from forms. Default Installed Base User or from the LOV.
CSI Instance Termination Status	Default Termination Status. Pick one from the LOV.
CSI Log File Name	The name of the log file for Debug.
CSI Log File Path	For Debug ('utl-file-dir' parameter in init.ora).
CSI OE Line Processing Delay	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	Used to commit Open Interface transactions to the data base. Default = 1000.
CSI Propagate System Changes	Propagate system changes to instances (Y or N).
CSI Propagate Systems Changes - Window Display	Condition of propagating system changes to products when Propagate System Changes is set to 'Y': Always Display: Change only when the system info matches the product information. Always Change: Do not display and always change. Never Change: Do not display and do not change:
CSI Restrict LOV’s on Site Usage.	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	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	Set to Y to start debug (Y or N).
CSI System Name Update Allowed	System name update allowed after system name creation (Y or N)
CSI: UI Default Selection of View Details Dropdown	Defines the default link populated in the ‘speed menu’ for summary results displayed in the Search Products page.
SERVICE Master Inventory Validation Org	Replaces the ASO: Product Organization profile option obsolete 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, this inventory organization is used to validate whether an item is trackable in Oracle Install Base and to derive other item parameters such as serialization when you create new item instances using Oracle Install Base. Oracle strongly recommends that you set this to a master inventory organization.

Concurrent Programs:

The following list describes the Concurrent Programs used for Oracle Install Base.

1. Expire End Dated Instances Program
2. Install Base Open Interface Program
3. Initiate Mass Edit Program
4. Process Mass Edit Program
5. Process Old Order Lines-Fulfillable Only Program
6. Resubmit Interface Process Program
7. Resubmit Waiting Transactions Program

References:

http://apurva-oracleappscrm.blogspot.com/2013/05/how-to-setup-oracle-install-base.html