Installed base oracle

For example, all copier machines on the fifth floor of a building or those belonging to a specific department can be grouped under a system. You can define, view, and invoke specific changes to item instances within the system or grouping. Additionally, you can build hierarchies of systems, and link multiple systems in parent-child hierarchies or relationships. Oracle Installed Base offers the flexibility of multi-level, user definable additional, or extended, attributes associated with an item instance to fit a variety of business requirements.

The application also stores pricing attributes for an item instance and makes them available for subsequent use by Oracle E-Business Suite applications including Oracle Service Contracts.

Oracle Service Contracts uses service programs or extended warranties where pricing is dependent on the attributes of an item. Oracle Trading Community Architecture for querying parties and accounts and building item instance to party relationships. Oracle Work in Process move transactions, assembly completion, configuration support, and others.

When using the TCA merge routines with Oracle Installed Base records, Oracle recommends that the party merge be completed before the account merge. In addition, the internal party that is set up in the Oracle Installed Base parameter cannot be used in the merge. For details, refer to Setting Up Installation Parameters. When entering a quote, you can invoke the transaction detail to enter additional information for Oracle Installed Base. When the quote becomes an order, the transaction detail is copied against an Oracle Order Management order.

This is processed when the order is shipped as described in the Oracle Order Management integration. If an item is set up as trackable in Oracle Installed Base, then an inventory receipt such as miscellaneous receipt or PO receipt causes the creation or update of an Oracle Installed Base instance.

When the inventory transaction occurs, a record is inserted into the Installed Base interface table. The Install Base lines concurrent program processes the lines in the interface table and updates or creates IB instances.

Note: If the Install Base Lines concurrent program is run manually, the User ID will represent the resource who created or modified the transaction. If the concurrent program is run automatically, then the User ID represents the resource who generated the process.

For non-serialized items, if an instance already exists at the same subinventory location, then it is added to the quantity of the instance with the same subinventory location.

If an instance for the same item subinventory location does not exist, then a new instance is created. If an item is serial controlled at receipt or is predefined, then an instance is created for it with quantity of 1 with location in the subinventory location. If an item is serial controlled at order issue, then it is treated as a non-serialized controlled item in inventory.

The item receives a serial number at order-issue creation time only. If an Oracle Installed Base trackable item has been received into inventory and an Oracle Installed Base instance has been created, then any subsequent inventory transactions will be tracked in Oracle Installed Base as well.

For an inventory transfer or move order transaction, the location of an instance is updated to reflect the new location for a serialized item. For a non-serialized item, the quantity of the instance at the From location is subtracted, and the quantity of the instance at the To location is increased by the quantity being moved. If it is issued to an asset, then it reflects the asset number. We recommend that the Interface Install Base Lines Concurrent Manager is running so that the interface lines are processed periodically and users can view the most current inventory transactions.

The integration with Oracle Order Management is the only integration that implements the functionality of the Oracle Installed Base Transaction Details window. This includes RMA receipt, sales order shipment, and sales order fulfillment.

The functionality of the Oracle Installed Base Transaction Details window is not supported for internal sales orders.

An RMA return receipt generates an inventory receipt material transaction in the Inventory application. If a serialized item never existed in Oracle Installed Base, then the RMA receipt creates a new instance with the location in inventory. For non-serialized items, first create the instance with the required quantity using the Oracle Installed Base user interface and then reference it in the RMA.

If the instance exists in Oracle Installed Base, then this return can cause a change of location to inventory and other changes such as status and owner as specified in the transaction type setup used to process the transaction.

In the sales return line, installation detail can be invoked to specify additional details for this instance and other related instances for this update to Oracle Installed Base. Oracle Installed Base supports the Order Management RMA fulfillment process for non-shippable items under specific terms and conditions. Important conditions include the following:. Instance attributes are updated based on the associated transaction types in the transaction details window. Refer to Use of Transaction Details for information on the use of transaction detail.

To use transaction detail, the transaction types being used have to be previously set up. Refer to Set Up Transaction Subtypes for instructions to set up transaction types. For an Oracle Installed Base trackable, shippable item, a shipping transaction generates an inventory issue transaction in the Oracle Inventory application. For a serialized item already in inventory, this transaction causes a change of location and ownership, depending on the transaction type being used.

For items serialized at sales order issue, the first-time shipment transaction causes the creation of a new instance with the serial number. If it has trackable components, then the component instances and component-of configuration for these components are built as well. Refer to Setup Checklist for New Users. Oracle Installed Base requires that the serial control of Oracle Installed Base trackable items is set up in the master organization for Oracle Installed Base to support the continuous tracking through all organizations.

All items that need to be tracked in Oracle Installed Base and Asset Tracking are set up as Oracle Installed Base trackable, whether they are tangible, inventory-transactable, shippable items such as a computer or intangible, noninventory-transactable, non-shippable items such as a license. An item can be either Oracle Installed Base trackable or a service item such as a contract.

It cannot be both. You can additionally set the tracking level of Install Base. The Install Base tracking can be left as set up in the Install parameter by setting "Default from install Parameter" or its tracking can be individually changed to Customer Tracking or Enterprise and Customer Tracking. See Setting Up Installation Parameters for more information. Note: This feature is used at the master item level only. You cannot change this attribute control at an inventory organization level.

To create a warranty for a item instance, the service item of the contract must be part of the BOM of the top assembly item. Instances can be created online and through interfaces such as Inventory receipt and WIP assembly completion.

Refer to Integration with the Oracle E-Business Suite for information about instance creation through integration. For more information about how to set up parties, see the Oracle Accounts Receivable Implementation Guide. For more information about how to set up vendors, see the Oracle Purchasing implementation guides. Employees can be associated with Oracle Installed Base item instances as parties.

To do so, employees must be defined in the HR tables first. The parties associated with item instances in Oracle Installed Base can have a number of accounts associated with them. For more information about how to set up party accounts, consult the Oracle Accounts Receivable Implementation Guide. Oracle Installed Base can maintain the contacts to parties associated with item instances.

For more information about how to set up party contacts, consult the Oracle Accounts Receivable Implementation Guide. This menu setup is required so that Transaction Details and Maintain Systems windows are set up as part of the Action menu. Oracle Installed Base creates instances when tangible items are received into inventory.

It tracks tangible items, for example, as they move between locations in inventory, when they are shipped to customers, and when they are returned to an enterprise. Inventory is a key driver enabling Oracle Installed Base tracking of tangible items. Tracking intangible items, which are non-shippable and non-stockable, requires a separate procedure because Oracle Installed Base has no direct interaction with inventory.

Generally, intangible or fulfillable items are created and tracked commencing with sales order fulfillment. This requires integration with Oracle Order Management. The integration provides Oracle Installed Base with information regarding fulfilled sales order lines.

The integration is achieved by modifying Oracle Order Management order line workflows. The information below provides detailed steps to accomplish the modification. The following two main steps are required to modify order line workflows to enable Oracle Installed Base tracking for non-shippable items:. Delete the line after the Fulfill function. This line is the one going from Fulfill to the node after Fulfill.

Right-click Install Base Interface, and drag it to the node after Fulfill. For option results, choose Any. Note: This customization must be done for fulfill-only order line workflows. Note: The same process must be followed for return lines, which are those without a receipt activity in the order line workflow. After the two main setup steps are complete, sales order lines using newly customized workflows have an interface to Oracle Installed Base.

Use this procedure to process sales orders for non-shippable items. Place an order for a non-shippable item through Oracle Order Management using the customized line type created in the previous section. It enables Oracle Asset Tracking functionality for inventory receipts and other processing required for Oracle Installed Base. This is required only if you have not installed Oracle Asset Tracking.

Confirm that the following profile options were set up:. To set up locations, do the following:. The HZ Locations window appears. Navigate to the Oracle Installed Base Administrator responsibility to access the Setups and Lookups menus to perform most of the setup steps.

Oracle Installed Base includes a set of customer-specific installation parameters defined in a table at setup time. After you define the parameters and select the Freeze check box, the fields cannot be updated. The migration procedure populates the table with default data. After migration, you open the window for update before the freeze takes effect. It is the owner of the item instance when it is owned by your own enterprise. Item transfers from this party are not supported. The organization cannot be changed after it is set.

For new Oracle Installed Base customers, this party can be first set up as an internal party by a responsibility that holds the Contact Center or Customer Create functionality. Such responsibilities may include:. This party does not require an account number.

In the case of upgrades, this setup is done by setting the profile option Service: Migration Organization for Employee Service Requests. This profile option setting is only used during the upgrade process to populate the Party Name field in the Install Parameters window. After the upgrade is complete, all functionality refers to the value in the Party Name field of the Install Parameters window and not to the profile option.

For example: You buy and receive an item in Oracle Receiving. The Oracle Installed Base process that creates the item instance assigns ownership of this new instance based on the Party Name in the Install Parameters window. If you are not using the full Oracle Receivables and are using shared functionality, you must access the Customer setup through different responsibilities that have Customer Create and Update functionality.

Note: Do not use this party as the object of a merge in TCA merge routines. Full Dump Frequency: The number of updates of an Oracle Installed Base record before a full image of the record is dumped into the history table.

For the remaining nine updates, only the changed values are dumped into the history table. Create Unique Asset For: For all transactions that create an asset, this determines if there is a separate asset for each serialized instance or one asset for all serialized instances.

Both Enterprise and Customer Owned Instances: This value indicates that Oracle Installed Base will track the complete lifecycle of an item for both enterprise internal and customer external instances. Only Customer Owned Instances: This value indicates that Installed Base will begin tracking customer owned instances only after order fulfillment and tracks all after-sales transactions such as RMAs and Oracle Field Service returns.

Caution: After the Only Customer Owned Instances option has been enabled by the concurrent program, the option cannot be changed. Default to Install Parameters: This default value enables you to specify the preference for Installed Base tracking at the Master Item level, based on the individual tracking needs for the item. All Parties: If selected, then all parties and locations are made available for transfer and location change.

If it is not selected, then only related parties and locations are made available for transfer and location changes. Some of the general conditions governing multi-quantity WIP assembly completion configurations include:. If genealogy is enabled, configurations are created according to genealogy or from the parent serial number.

Override Ownership: If selected, allows Oracle Installed Base processing of RMA receipts, order shipment, and miscellaneous receipts regardless of ownership. For a miscellaneous receipt serialized at-receipt or predefined of an existing Oracle Installed Base instance, the ownership changes to Internal.

Note: By default, the Override Ownership check box is not selected. After you select it and save one or more transactions, never attempt to change it because doing so results in irrecoverable data corruption. You must specify the directory in which the Oracle Database software is installed, or the location where the product binary files are copied from the installation media.

You must choose a location that has enough disk space to contain the software and is accessible by the operating system user performing the installation. You also specify the location of the Oracle base directory, which is used by all Oracle software products installed on the server.

The first time you install Oracle Database software on a server, you are prompted to specify the location of the inventory directory, called oraInventory. This directory provides a centralized inventory of all Oracle software products installed on the server. You should use the same value for the Oracle inventory directory each time you perform an Oracle software installation on the server.

A database includes several files that store the user data, database metadata, and information required to recover from failures. As an administrator, you decide what kind of storage subsystem to use for these files. You can select from the following options:.

File System —This default option creates database files that are managed by the file system of your operating system. You can specify the directory path where database files are to be stored. Oracle Database can create and manage the actual files. For environments with a large number of disks, this option simplifies database administration and maximizes performance. Oracle ASM performs software striping and mirroring at the file level for maximum storage flexibility, performance, and availability.

A single Oracle ASM instance can provide storage for multiple databases on the same server. These options include your global database name and system identifier SID.

The SID is a unique identifier that is used to distinguish this instance from other Oracle Database instances that you may create later and run concurrently on your system. The global database name is the full name of the database that uniquely distinguishes it from any other database. The database name portion sales is a simple name you call your database. The database domain portion example.

Together, the database name and domain form the global database name. During advanced installations using the Server Class method you are prompted to make the additional choices listed in this section, and the choices for a typical installation. The installation process provides default values for every choice. This guide describes, but does not document, these additional advanced installation choices.

For more information, see Oracle Database Installation Guide for your platform. You choose which language the software should use after it is installed. You can select multiple languages. The default value is English. If you choose a value other than English, it does not change the language used by the installation.

You select a template to use when configuring the database. Database Configuration Options. You can choose how to configure the database created by the installer.

You can select the memory size and management options, the character sets used to store data, the security options for database access, and whether the sample schemas should be installed. To complete the exercises in this guide and related course material, you must install the sample schemas. This data is also used in most examples throughout Oracle Database documentation.

Oracle recommends that you install the sample schemas. This choice is a configuration option only during advanced installation. Sample schemas are installed by default during typical or Desktop class installations.

You specify whether to manage your database centrally or locally using Oracle Enterprise Manager. Central management enables you to manage multiple targets, such as databases and application servers, using a single interface. Using local management you can manage only a single database instance at a time. To use central management, you must have an Oracle Enterprise Management agent on each host , or computer that has Oracle Database software installed on it. These agents are responsible for monitoring all components on that host.

If an agent is not found on the local host, then this option is disabled during installation. If you are setting up a single database for the first time, then it is recommended that you configure local management with Oracle Enterprise Manager, which is the default. You can later install additional databases and configure central management using Enterprise Manager. You specify whether automated backups should be configured for the database. If you choose this option, you must specify whether the recovery area should be stored on the local file system or in an Oracle ASM disk group.

You must also specify the operating system credentials the backup job uses when performing backups. When you create a database, certain administrative user accounts are created automatically. You can use the same password for each account, or specify passwords for each account individually. If you do not enter a secure password, you will receive a warning message during installation.

Administrative access to the database is granted by membership in certain operating system groups. This section briefly describes the steps for a desktop-class installation.

Most steps are common to all platforms and involve running the Oracle Universal Installer. Platform-specific steps are noted. For further assistance, consult the online Help or the Oracle Database Installation Guide for your platform. Log on to your computer as a member of the administrative group that is authorized to install Oracle Database software and to create and run the database.

Refer to your operating system-specific documentation or contact your system administrator to determine whether you have the necessary privileges and permissions to install new software. If you are installing from distribution media, then insert the distribution media for the database into your computer. If you downloaded the installation software from the Oracle Web site, then follow the instructions on the site to run the Oracle Universal Installer. Or, see the Oracle Database Installation Guide for your platform.

The first window that appears is the Configure Security Updates window. To receive notifications about security issues via e-mail, enter your e-mail address in the Email text field. To receive security updates from My Oracle Support, enter the e-mail address registered with My Oracle Support, select the I wish to receive security updates Choose the Create and configure a database option.

Or, you also have the option of choosing to only install the database software, but then you must create a database in an additional step after the software is installed.

If you are currently using a previous version of Oracle Database, choose Upgrade an existing database. After you have chosen an option, click Next. You can choose the Server Class option to customize your installation. For example, you use this method to configure Oracle Automatic Storage Management for your database, install the Sample Schemas, or configure automated backups.

Selecting this option guides you through a series of installation steps that are not documented in this guide. For more information about the advanced choices, see "About Advanced Installation". Also see Oracle Database Installation Guide for your platform. Provide the following configuration details for the database:.

Oracle Base Location— The Oracle base directory helps to facilitate the organization of multiple Oracle software installations. You can click Browse to find the directory you want to act as the Oracle base directory.

Software Location—The software location is the Oracle home for your database. You must specify a new Oracle home directory for each new installation of Oracle Database software. By default, the Oracle home directory is a subdirectory of the Oracle base directory.

You can click Browse to find the directory where you want to install the Oracle Database software. Database File Location—The database file location is the location where Oracle Database files are stored.

You can click Browse to select a different location. See "Installation Type". Character Set—Choose the character set to use to store the data within the database. You can choose between the Default , which is based on the operating system language settings, or Unicode. Host computer users in this group have administrative privileges on the database. This group is typically named dba.

Global Database Name—Enter the fully qualified global database name. See "Installation Type" for more on global database name. If the password you choose is not a secure password, a warning message will be displayed. If Oracle software has not previously been installed on this server, then the Create Inventory window appears. If this is not the first installation attempt on this server, then the Perform Prerequisite Checks window appears.

For first time installations on Linux and UNIX operating systems only , specify a directory for installation files and the name of an operating system group that has write permissions for that directory. If this is the first time you are installing any Oracle software on this computer, then the Create Inventory Directory window appears.

You must specify a local directory for the inventory, which OUI uses to keep track of all Oracle software installed on the computer. This information is used while applying patches or upgrading an existing installation, and while deinstalling Oracle software.

Note that this directory is different from the Oracle home directory. In this window you can also specify the operating system group that has write permissions on the inventory directory.

This prevents other users from writing over the Oracle product installation files. Typically the oinstall group is selected. After you enter a directory path and optionally specify an operating system group, click Next to continue. There are also transactions where Oracle Install Base merges item instances, such as when non-serialized items are returned into inventory.

The Oracle applications that use Oracle Install Base are:. A list of all the Oracle transactions that interface with Oracle Install Base appears in Appendix A, together with the Oracle application that triggers each transaction.

The receipt of the component materials on the purchase order is recorded by Oracle Inventory, and Oracle Install Base starts to track the item instances. The main processing associated with the building and assembly of items occurs in Oracle Work in Process.

When all components have been completed and the item is assembled, this is recorded both in Oracle Inventory and Oracle Install Base. The following diagram shows the high-level flow for shippable and non-shippable items on sales orders.

A sales order shipment generates an Inventory Issue material transaction in Oracle Inventory application. Because Oracle Install Base also tracks the internal inventory for trackable items, the instance already exists in Oracle Install Base.

A shipment can result in a change in instance location and ownership, status, and so on, based on the associated Oracle Install Base transaction subtype. Oracle Install Base tracking of non-shippable items at fulfillment requires workflow customization as defined in the Oracle Install Base Implementation Guide. A sales order return line provides for an Oracle Inventory receipt material transaction in the Oracle Inventory application. Because the Oracle Install Base instance already exists for the item being returned, a receipt can trigger an update of the specified instance, depending on the Oracle Install Base transaction type being used.

Terminology Tangible Items Item instances can be used to track tangible items, that is, physical, real-world objects, that can be assembled and shipped, such as computers, engines, machine parts, and so on.