http://oracleapps88.blogspot.

com/

Oracle Install Base Implementation

______________________________________________
Process Flow Diagram

.B
8

S
P

A
E

.C

http://oracleapps88.blogspot.com/

Table of Contents

.C

OVERVIEW OF ORACLE INSTALL BASE ...........................................................................4

2.

PRODUCT DEPENDANCIES ................................................................................................5

3.

SETUP REQUIRED ...............................................................................................................6

.B
8

S
P

A
E

3.1 Setup within Other Oracle Applications ........................................................................................... 6

3.1.1 Set Up Oracle Install Base Items in the Item Master .................................................................... 6
3.1.2 Set Up Party Contacts ................................................................................................................... 6
3.1.3 Setup to Ensure the Serializability of transactions processed in Oracle Install Base (One Time) 6
3.2 Setup Steps Within Oracle Install Base ............................................................................................ 7
3.2.1 Setup Installation Parameters ........................................................................................................ 8
3.2.2 Verify Extended Attribute-Level Codes ....................................................................................... 9
3.2.3 Setup Extended Attribute Pools ...................................................................................................10
3.2.4 Setup Extended Attribute Classifications .....................................................................................11
3.2.5 Verify Accounting Classification Codes ......................................................................................12
3.2.6 Setup Instance Type Codes ..........................................................................................................13
3.2.7 Verify Party Sources ....................................................................................................................14
3.2.8 Setup Codes for Instance-Operating Unit Relationship Types.....................................................15
3.2.9 Setup Version Labels ...................................................................................................................16
3.2.10
Setup System Type Codes .......................................................................................................17
3.2.11
Setup Split Process Reasons ....................................................................................................18
3.2.12
Verify Oracle Configurator Enabled Values............................................................................19
3.2.13
Verify Instance Class Values ...................................................................................................20
3.2.14
Verify Values for the Resubmit Interface Process ...................................................................21
3.2.15
Verify Values for CSI: Propogate Systems Changes ...............................................................22
3.2.16
Setup Regions for the Advanced Search Page .........................................................................23
3.2.17
Setup the Results of the Search Products Page ........................................................................24
3.2.18
Setup Instance Statuses ............................................................................................................25
3.2.19
Set Up Source Transaction Types............................................................................................26
3.2.20
Set Up Transaction Subtypes ...................................................................................................27
3.2.21
Verify Transaction Status Codes .............................................................................................28
3.2.22
Verify Transaction Error Source Types ...................................................................................29
3.2.23
Create Business Users .............................................................................................................30
3.2.24 Create Agent Users .........................................................................................................................30
3.2.25
Schedule the Expire End Dated Instances Program .................................................................30
3.2.26
Schedule the Install Base Open Interface Program ..................................................................31
3.2.27
Schedule the Initiate Mass Edit Program .................................................................................32

1.

http://oracleapps88.blogspot.com/

3.2.28
Schedule the Process Mass Edit Program ................................................................................32
3.2.29
Schedule the Resubmit Interface Process ................................................................................32
3.2.30
Schedule the Resubmit Waiting Transactions Program...........................................................32
3.2.31
Schedule the Install Base and Inventory Data Discrepancies Program ...................................32
3.2.32
Schedule the Install Base Error Correction and Synchronization Program .............................33
3.3
Profile Options ................................................................................................................................33

.C

.B
8

S
P

A
E

http://oracleapps88.blogspot.com/

1. OVERVIEW OF ORACLE INSTALL BASE

Oracle Install Base is a separate module for Oracle E-Business Suite which is basically
used to track the complete life cycle of an item. The item can be an inventory item ie
tangible item or intangible item such as License or Service. We can view following details
from the Item Instance through the Oracle Install Base
View and maintain general information about the item instance as system name,
service id number, owner and location
View and update values for additional attributes for an item or instance.
View and define associated asset information such as asset number, date placed in
service and employee.
View and define names, types and effective dates for additional parties that can be
associated with an instance.
View extended pricing attributes that come from Order Management sales order lines at
the sale of an item instance.
Review and update counter readings associated with the instance.
Create and view notes associated with an item instance.
View and create service request associated with the item instance.
View open, closed and hold repair orders for an item instance.
Retrieve and view the history of an item instance based on a data range or a version
label.
Display and maintain operating units associated with the item instance.
Displays the item instance configuration page. There you can view the various
configurations and define children for an instance.

.C

.B
8

S
P

A
E

http://oracleapps88.blogspot.com/

2. PRODUCT DEPENDANCIES
The following modules must be installed and set up Oracle Install Base to work.
Oracle Inventories
Oracle Enterprise Install Base
Oracle Service Fulfillment Manager

Oracle Order Management

.C

Oracle Purchasing (Optional)

Oracle Accounts Receivable

Oracle Work in Process (Optional)

Oracle Bills of Material

.B
8

S
P

A
E

http://oracleapps88.blogspot.com/

3. SETUP REQUIRED
Following setup are required for configuring the Oracle Install Base
3.1 SETUP WITHIN OTHER ORACLE APPLICATIONS
3.1.1

Set Up Oracle Install Base Items in the Item Master

All the items that need to be tracked in Oracle Install Base are set up as
Oracle Install Base track able. For an item to be set up as track able in
Oracle Install Base, the Install Base tracking checkbox must be selected on
the Service tabbed page of the Master Item window.

Go to Service Tab on this page and select the check box for Install Base
Tracking.

.B
8

S
P

A
E

3.1.2 Set Up Party Contacts

Oracle Install Base can maintain the contacts to parties associated with item
instance. These contacts to parties must be defined in the HZ_PARTIES
table using the Contact Center window before referencing them in Oracle
Install Base.

3.1.3 Setup to Ensure the Serializability of transactions processed in Oracle

Install Base (One Time)
1. Log into Oracle Applications
2. Navigate to System Administrator > Concurrent > Manager > Define

.C

Navigation: Inventory > Items > Master Items >

http://oracleapps88.blogspot.com/

3. Query for the Manager SFM Event Manager Queue Service

4. Click Work Shifts
5. Change the processes to 1
6. In the Parameter field, change the value of
XDP_DQ_INIT_NUM_THREADS to 1
7. Stop and restart the SFM Event Manager Queue.
Figure 3.1.3 Setup to Ensure the Serializability of transactions processed in
Oracle Installed Base

.C

.B
8

S
P

A
Ethese steps are performed through navigation to Oracle Install Base Setups
Most of
L
and Lookups.
CLogin to the Oracle application with Oracle Installed Base Admin responsibility.
3.2 SETUP STEPS WITHIN ORACLE INSTALL BASE

http://oracleapps88.blogspot.com/

Figure 3.2 Navigation for Oracle Install Base Setups

.C

3.2.1

Setup Installation Parameters

Login Oracle Application with Oracle Install Base Admin Responsibility
:Setups > Install Parameters

.B
The following list defines the8
Installed Parameters window.
8namefieldsof inyourthe own
1.
Party Name: The
enterprise that you defined in
TCA as anS
internal organization
2.
Full Dump
P Frequency: The number of updates of an Oracle Installed
Base record before a full image of the record is dumped into the
P table.
history
3. AProject Location: The location defined for the use of Instance in
Project
E
4.
WIP Location: The location defined for use of instance in WIP

5.
6.
7.
8.
9.
10.
11.

In-Transit Location: The location defined for use of instances in

transit between organizations.
PO Location: The location defined for use of instances in WIP
outside processing.
Category Set Name: The name of the category set to be used in the
additional attributes setup.
All Parties: If selected, then all parties and locations are made
available for transfer and location change.
Freeze: After this is selected, the parameters cannot be changed.
Allocate a WIP: If selected, conditionally allocates component
quantities when completing a multi-quantity assembly WIP job.
Override Ownership: If selected, allows Oracle Install Base
processing of RMA receipts, order shipment, and miscellaneous
receipts regardless of ownership.

http://oracleapps88.blogspot.com/

12.

SFM Bypass: Replaces the previous CSE: Bypass Event Queue

profile option.

Figure 3.2.1 Installed Parameter Window

.C

3.2.2

.B
8

Verify Extended Attribute-Level Codes

Type: CSI Lookup

Lookup Type: CSI_IEA_LEVEL_CODE
Access Level: System (non-extensible)
Verify that the following values are already seeded for
CSI_IEA_LEVEL_CODE

S
P

A
E

http://oracleapps88.blogspot.com/

Figure 3.2.2 Verify Extended Attribute Level Codes

.C

3.2.3

.B
8

Setup Extended Attribute Pools

Type: CSI Lookup

Lookup Type: CSI_EXTEND_ATTRIB_POOL
Access Level: Extensible

S
P
This is used to define an attributes name, code and description to be used
P
in the LOV when the extended attribute is set up.
A
E

10

http://oracleapps88.blogspot.com/

Figure 3.2.3 Setup Extended Attribute Pools

.C

O
L
3.2.4 Setup Extended Attribute Classifications
.B
Type: CSI Lookup
8
Lookup Type: CSI_IEA_CATEGORY
Access Level: Extensible
8
S
This is used to define the categories by which an attribute can be classified
from a LOV inP
P the extended attribute setup.
A
E
L
C

11

http://oracleapps88.blogspot.com/

Figure 3.2.4 Setup Extended Attribute Classifications

.C

3.2.5

.B
8

Verify Accounting Classification Codes

Type: CSI Lookup

Lookup Type: CSI_ACCOUNTING_CLASS_CODE
Access Level: System

S
P
Verify that the following values are already seeded for
P
CSI_ACCOUNTING_CLASS_CODE
A
E

12

http://oracleapps88.blogspot.com/

Figure 3.2.5 Verify Accounting Classification Codes

.C

3.2.6

.B
8

Setup Instance Type Codes

Type: CSI Lookup

Lookup Type: CSI_INST_LOCATION_SOURCE_CODE
Access Level: System

S
Verify that theP
P following values are already seeded for
CSI_INST_LOCATION_SOURCE_CODE
A
E

13

http://oracleapps88.blogspot.com/

Figure 3.2.6 Setup Instance Type Codes

.C

.B
Type: CSI Lookup
8
Lookup Type: CSI_PARTY_SOURCE_TABLE
8
Access Level: System
S
Verify that theP
following values are already seeded for
CSI_PARTY_SOURCE_TABLE
P
A
E

3.2.7

Verify Party Sources

14

http://oracleapps88.blogspot.com/

Figure 3.2.7 Verify Party Source

.C

O
L
3.2.8 Setup Codes for Instance-Operating Unit Relationship Types
.B
Type: CSI Lookup
8
Lookup Type: CSI_IO_RELATIONSHIP_CODE
8
Access Level: Extensible
S
Verify that theP
following values are already seeded for the
CSI_IO_RELATIONSHIP_TYPE_CODE
P
A
E
L
C

15

http://oracleapps88.blogspot.com/

Figure 3.2.8 Verify Codes for Instance Operating Unit Relationship

Type

.C

3.2.9

.B
8

Setup Version Labels

S
P

Type: CSI Lookup

Lookup Type: CSI_INSTANCE_VERSION_LABELS
Access Level: Extensible

Verify that the following values are already seeded for

CSI_INSTACNE_VERSION_LABELS

A
E

16

http://oracleapps88.blogspot.com/

Figure 3.2.9 Setup Version Labels

.C

Define new version label codes to be used for your organization. This table
of codes is used as a source of the LOV for profile option setup in Default
Version Label.

.B
8
3.2.10 Setup System Type Codes
8
Type: CSI LookupS
Lookup Type:P
CSI_SYSTEM_TYPE
Access Level:
P Extensible
A
E
L
C

17

http://oracleapps88.blogspot.com/

Figure 3.2.10 Setup System Type Codes

.C

This table is used for user-defined system types which can be set up for use
in the LOV. Use this setup window to define types for your organization.
They are used in the Systems page of the application to define systems.

.B
8
3.2.11 Setup Split Process Reasons
8
S
Type: CSI Lookup
Lookup Type:P
P CSI_SPLIT_REASON_CODE
Access Level:
User
A
E
L
C

18

http://oracleapps88.blogspot.com/

Figure 3.2.11 Setup Split Process Reasons

.C

Define split reasons for your organization. When an instance with a quantity
greater than 1 is split, a reason code can be selected for the reason for the
split. This is the window where the reason codes can be set up for use in
an LOV.

.B
8

S
P
Type: CSI
Lookup
P
Lookup Type: CSI_CONFIG_ENABLED_VALUES
ALevel: System
Access
E

3.2.12 Verify Oracle Configurator Enabled Values

19

http://oracleapps88.blogspot.com/

Figure 3.2.12 Verify Oracle Configurator Enables Values

.C

This setup maintains the LOV for the profile option CSI: Configurator
Enabled and is used for integration.

.B
3.2.13 Verify Instance Class Values
8
8
Type: CSI LookupS
Lookup Type: CSI_ITEM_CLASS
Access Level:P
System
P
This
setup maintains the LOV for the Instance class field in the Service tab
A
in the Inventory Item Setup. It is used for integration with Oracle
E
L Telecommunications Service Ordering solution and Oracle Configurator.
C

20

http://oracleapps88.blogspot.com/

Figure 3.2.13 Verify Instance Class Values

.C

3.2.14 Verify Values for the Resubmit Interface Process

.B
8

Type: CSI Lookup

Lookup Type: CSI_RESUBMIT_OPTIONS
Access Level: System

S
P

This setup maintains the LOV for the Oracle Install Base concurrent request
Resubmit Interface process.

A
E

21

http://oracleapps88.blogspot.com/

Figure 3.2.14 Verify Values for the Resubmit Interface Process

.C

O
L
3.2.15 Verify Values for CSI: Propogate Systems Changes
.B
Type: CSI Lookup
8
Lookup Type: CSI_SYSTEM_WINDOW_DISPLAY
Access Level: System 8
S
This setup maintains the LOV for the profile option CSI: Propogate Systems
P Display. The Maintain System window uses these values
Changes- Window
P a confirmation window.
when displaying
A
E
L
C

22

http://oracleapps88.blogspot.com/

Figure 3.2.15 Verify Values for CSI: Propogate Systems Changes

.C

3.2.16 Setup Regions for the Advanced Search Page

.B
8

Type: CSI Lookup

Lookup Type: CSI_ADV_SEARCH_DEF_SHOW
Access Level: System

S
P

Unlike the navigation for the other lookups you must use the application
developer responsibility to navigate to this lookup. This setup lists regions
that are shown by default in the Advanced Search Page.

A
E

23

http://oracleapps88.blogspot.com/

Figure 3.2.16 Regions for Advanced Search Page

.C

.B
8

3.2.17 Setup the Results of the Search Products Page

Type: CSI Lookup

Lookup Type: CSI_PRODUCTS_TABLE_DEF_COLS
Access Level: System
Navigation: Application Developer > Application Object Library

S
P

This setup customizes the display of the search results of the Search
Products page by indicating the display and order of viewable columns.

A
E

24

http://oracleapps88.blogspot.com/

Figure 3.2.17 Set up the Results of the Search Products Page

.C

.B
Instance statuses are user extensible
8 and are defined using a combination
of settable checkboxes.8
There are 16 seeded statuses.
Login with Oracle Installed Base Admin Responsibility > Setups > Instance
S
Statuses
P
The meaning
P of the checkboxes is as follows:
A
Terminated:
Sets the instance to be terminated.
Status
Change
Allowed:
The status can be changed for an instance
E
currently bearing this status.

3.2.18 Setup Instance Statuses

Service Allowed:

Requests Allowed:
Pre-Defined:
Updatable:

Service contract can be active for the instance

with this status. If set to No, then the service
contract will be called to terminate the
contract.
Service request can be created for an
instance with this status.
Seeded
The checkboxes on this status can be
updated.

25

http://oracleapps88.blogspot.com/

Figure 3.2.18 Set up Instance Statuses

.C

.B
8

3.2.19 Set Up Source Transaction Types

Before any source transaction can be used in the LOV for a transaction
subtype, it must be defined in this setup in the Source Transaction Types
window. All integration sources and transaction types must be defined here
before they can be used to update Oracle Installed Base. Values can be
seeded or user defined.
Login in Oracle Installed Base with Oracle Installed Base Admin
Responsibility > Setups > Source Transactions Types

S
P

A
E

Application Name:
Transaction Type:

Transaction Name:
Description:
Source Object:
In Out:

An LOV of Oracle Applications that can be set up to

integrate into Oracle Install Base.
The user-defined name of the kind of transaction that
integrates with Oracle Install Base from the
application named.
The user-defined name of the transaction.
The user-defined description of the transaction.
Reserved is for the future use.
Reserved for future use.

26

http://oracleapps88.blogspot.com/

Figure 3.2.19 Set up Source Transaction Types

.C

.B
8
Transaction types and subtypes are used to specify the kinds of
8
transactions that the interface program can use. The main purpose of the
SSubtypes window is to specify what kind of update can
Source Transactions
be done to anP
Oracle Install Base instance when transactions come from
other applications.
P
A
E

3.2.20 Set Up Transaction Subtypes

27

http://oracleapps88.blogspot.com/

Figure 3.2.20 Set up Transaction Subtypes

.C

.B
8

Transaction subtype region is used to define the name of the transaction

subtype. The name comes from two sources depending whether the
Service Type checkbox is selected or not. If Service Type is selected, then
the LOV comes from Service Transaction Billing Types setup. If the Service
Type is not selected then the LOV comes from Oracle Install Base
Transaction Type code setup.

S
P

A
E
Type: CSI Lookup

3.2.21 Verify Transaction Status Codes

Lookup Type: CSI_TRANSACTION_STATUS_CODE

Access Level: System

28

http://oracleapps88.blogspot.com/

Figure 3.2.21 Verify Transaction Status Codes

.C

O
L
3.2.22 Verify Transaction Error Source Types
B
.
Type: CSI Lookup
8
Lookup Type: CSI_TXN_ERRORS_SOURCE_TYPES
8
Access Level: System Values are seeded for this code
Stransaction is processed with an error, it is posted to
When an integration
the error tableP
with one of these error source types which indicate where an
error comes from.
P
A
E
L
C

29

http://oracleapps88.blogspot.com/

Figure 3.2.22 Verify Transaction Error Source Codes

.C

3.2.23 Create Business Users

.B
8

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

S
P
3.2.24 Create Agent
P Users
A
Create agent users as needed for Oracle Install Base. To do so, you must
E internal users and assign them the predefined CSI_NORMAL_USER
role and the responsibility of an Oracle Install Base user.
L create
C

3.2.25 Schedule the Expire End Dated Instances Program

This program goes through the end dates set up for instances to be expired.
If the end date is past due, then the instances are set to expire. Schedule
this program to run at least once a day. To schedule the program
Steps:
1. Login as Oracle Installed Base Admin in the forms mode.
2. Choose Others > Requests
New Request window appears
3. Select single request and click OK

30

http://oracleapps88.blogspot.com/

The Installed Base Requests window appears.

4. From the name LOV, select Expire End Dated Instances.
5. Click OK
6. In the At these Times region, click Schedule.
The scheduler window appears.
7. Select the desired running schedule.
8. Click OK.
The Installed Base Requests window appears.
9. Click Submit.

Figure 3.2.25 Schedule the Expire End Dated Instance Program

.C

.B
8

S
P

A
E

3.2.26 Schedule the Install Base Open Interface Program

This program imports significant volumes of data into Oracle Installed Base
application tables through its mass load feature. Through its incremental
load feature, it synchronizes Oracle Installed Base with subsystems by
importing item instances from different feeder systems on a frequent, ongoing basis. Through its change functionality, it automates the process of
adding as well as updating changes to the attributes of item instances. It
also validates imported data to ensure data integrity with Oracle
applications. Use the same steps mentioned in 3.2.25 for scheduling the
concurrent program. Modify step 4 as follows:
4. Form the Name LOV, select either Installed Base Open Interface or
Installed Base Open Interface- Parallel Concurrent Workers.

31

http://oracleapps88.blogspot.com/

3.2.27 Schedule the Initiate Mass Edit Program

This program polls the submitted mass edit sessions and calls the Process
Mass Edit program to process eligible sessions. In order to process mass
edit transactions, run the Initiate Mass Edit Concurrent program or schedule
it to run at regular intervals. Oracle recommends that you schedule it to run
at least once a day. Use the same steps mentioned in 3.2.25 for scheduling
the concurrent program. Modify step 4 as follows:
4. Form the Name LOV, select Initiate Mass Edit.

3.2.28 Schedule the Process Mass Edit Program

This is the program that is called automatically to process the mass edit
sessions. Schedule it to run at a regular interval to pick up mass edit
sessions due to be processed. To schedule this program use the same
steps as described in Section 3.2.25. Modify step 4 as follows:

.C

4. From the Name LOV, select Process Mass Edit Transaction.

3.2.29 Schedule the Resubmit Interface Process

This program processes the transactions in the Error processing table. It

can be set up to process selected lines or all lines in the table. This program
can be called to run by user request or can set up to run at a regular
interval. To schedule this program use the same steps as mentioned in
3.2.25. Modify step 4 as follows:

.B
8

8
4. From the NameS
LOV, select Resubmit Interface Process.
P
Pthe Resubmit Waiting Transactions Program
3.2.30 Schedule
A
This program processes the transactions that are set as waiting status in
E Oracle Installed Base update process. The program can be scheduled
L the
to run at a regular interval. To schedule this program use the same steps as
C mentioned in 3.2.25. Modify step 4 as follows:

4. From the Name LOV, select Resubmit Waiting Transactions.

3.2.31 Schedule the Install Base and Inventory Data Discrepancies Program
The Install Base and Inventory Data Discrepancies program picks up the
discrepancy data from the tables of Oracle Installed Base and Oracle
Inventory and displays it on a report. The program can be scheduled to run
at regular interval. To schedule this program use the same steps as
mentioned in 3.2.25. Modify step 4 as follows:

32

http://oracleapps88.blogspot.com/

4. From the Name LOV, select Installed Base and Inventory Data
Discrepancies.
3.2.32 Schedule the Install Base Error Correction and Synchronization
Program
The Install Base Error Correction and Synchronization program is
concurrent program to correct and reprocess the transactions that failed to
update item instances in Oracle Install Base. These are the errored
transactions that you can view through the Transaction Error Summary and
Details window in the application. The program can be scheduled to run at a
regular interval. To schedule this program use the steps as mentioned in
3.2.25. Modify step 4 as follows:
4. From the Name LOV, select Install Base Error Correction and
Synchronization Program.

.C

3.3 PROFILE OPTIONS

The table below shows the profile options are required to setup at Site Level for
using Oracle Installed Base:

S
P

A
E

2.
3.

4.

O
L
Comments

.B The default value=N. Do not alter

setting until instructed to do so
8 this
as a part of patching or by Oracle

SR Name of the Profile Option

No.
1.
CSI: Allow_Install_Parameter_
Update

CSI: Auto-Generate System

Name
CSI: Auto-split Instances
During Instantiation

5.

CSI: Cascade System

Termination
CSI: Configurator Enabled

6.

CSI: Counters Enabled

7.

CSI: Debug Level

33

Customer Support or Development.

Changing the default can cause
irrecoverable data corruption. (The
profile option is set to Y after
migration to allow a one-time
update to install parameters. Then it
is set to N.)
Auto generate system number at a
time of system creation.
Auto split instances with multiple
quantities to 1 per instance at time
of instance creation
Cascade system termination to
instacnces
Default=Network Models Only.
Used for integration with the TSO
solution and the Oracle
Configurator product.
Enables Oracle Install Base
integration with Oracle Counters.
For Debug. Set 9 or 10 to start.

http://oracleapps88.blogspot.com/

8.

CSI: Default Instance Status

9.

CSI: Default Version Label

10.

CSI: Display HTML UI

11.

CSI: Enable SQL Trace

12.

CSI: Forms to SSWA Default

Responsibility

13.
14
15.
16.

CSI: Instance Termination

Status
CSI: Log file Name
CSI: Log file path

17

CSI: Open Interface Commit

Record Limit

18.

CSI: Restrict LOVs on Site

Usage

21.
22

23

CSI: System Name Update

Allowed
CSI: UI Default Selection of
View Details Dropdown

SERVICE: Master Inventory

Validation Organization

34

.B
8

S
PExpired Instances
19. CSI: Show
P
A
E20 CSI: Stop at Errors

The name of the log file for debug

For debug (utl-file-dir parameter in
init.ora)
Delay between OE Line processing.
Time between order line processing
to allow for Oracle Install Base
update completion to avoid record
locking.
Used to commit Open Interface
transactions to the data base.
Default=1000
Default=N. Set at Site Level. For
value=Y, the application restricts
the Installed Locations LOV in the
System page to customer
addresses with locations identified
as Install At.
Default=N. Enables user to default
the value of the Show Expired
Products. Checkbox in the Advance
Search page.
Set to Y to start the debug
System name update allowed after
system name creation.
Defines the default link populated in
the speed menu for summary
results displayed in the Search
Products page.
Replaces the ASO: Product
Organization profile option obsolete
in the prior release.

.C

CSI: OE Line Processing

Delay

Default Instance Status at the time

of instance creation.
Default version label at the time of
instance creation.
Option to use Oracle Installed Base
HTML for display
For debug. Set to Y to start the
debug.
Default user for applications to
launch HTML from forms. Default
Installed base user or from the
LOV.
Default Termination Status