Results for “sizing_factor”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_PRODUCT_INSTALLATIONS is a core Oracle E-Business Suite registration table owned by the APPLSYS schema. It records the Oracle Applications products that are installed and licensed at a given site, together with the Oracle database user (schema) each product owns and the version or patch level associated with that installation. In release 12.1.1 and 12.2.2 this table serves as the authoritative registry that the AD (Applications DBA) utilities, the Oracle Applications Manager (OAM), and various diagnostic and patching components consult to determine which products are present, which database schemas implement them, and what dependencies exist between them.

The unique index FND_PRODUCT_INSTALLATIONS_PK is defined on the composite column set (APPLICATION_ID, ORACLE_ID). Because FND_PRODUCT_INSTALLATIONS holds the durable identity of each installed product instance and is referenced by satellite-style tables such as FND_PRODUCT_DEPENDENCIES and ALR_ACTION_SET_CHECKS, the metadata heuristic classifies it as hub-leaning within a Data Vault model. In that interpretation, (APPLICATION_ID, ORACLE_ID) constitutes the natural business key of the hub.

Key Information Stored

The table contains seventeen documented columns. The most operationally significant are listed below.

• APPLICATION_ID — Foreign key to FND_APPLICATION; identifies the installed Oracle Applications product (for example, GL, AP, AR). Part of the composite primary key.
• ORACLE_ID — Foreign key to FND_ORACLE_USERID; identifies the Oracle database schema that owns the product's objects. Part of the composite primary key.
• PRODUCT_VERSION — The installed version of the product, used during patching and upgrade validation.
• STATUS — Indicates whether the product installation is active, shared, or otherwise flagged.
• PATCH_LEVEL — The current patch set level applied to the product, consulted by AD utilities and OAM.
• DB_STATUS — Database-side status of the product schema.
• INDUSTRY — Industry classification associated with the product installation.
• INSTALL_GROUP_NUM — Grouping value used to sequence products during installation and upgrade operations.
• SIZING_FACTOR — Relative sizing weight applied during database capacity planning.
• TABLESPACE — Default tablespace assigned to the product's schema.
• INDEX_TABLESPACE — Default index tablespace for the product's schema.
• TEMPORARY_TABLESPACE — Temporary tablespace used by the product schema.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns providing the audit trail for each row.

The composite primary key (APPLICATION_ID, ORACLE_ID) is the surrogate identity of the row, while the pair also serves as the business-key candidate enforced by the unique index. There is no separate single-column surrogate; identity is expressed through the two foreign keys together.

Common Use Cases and Queries

The most frequent scenario is verifying which products are installed and which schema owns each one. A typical query joins the table to FND_APPLICATION and FND_ORACLE_USERID to produce a readable inventory:

• List all installed products with their application short name, Oracle schema, version, and patch level.
• Identify the database schema (ORACLE_ID) responsible for a given product before running product-specific DDL, SQL, or data fix scripts.
• Report the installed version and patch level per product to support upgrade planning and compliance checks.
• Drive dependency analysis by joining to FND_PRODUCT_DEPENDENCIES to confirm that required products are present at the correct level.
• Validate tablespace and sizing configuration (TABLESPACE, INDEX_TABLESPACE, TEMPORARY_TABLESPACE, SIZING_FACTOR) for capacity reviews.
• Support OAM and AD utility troubleshooting by confirming the STATUS and DB_STATUS flags recorded for each product.

A representative pattern joins FND_PRODUCT_INSTALLATIONS to FND_APPLICATION on APPLICATION_ID and to FND_ORACLE_USERID on ORACLE_ID, filtering on STATUS to return only active installations.

Related Objects

FND_PRODUCT_INSTALLATIONS participates in several documented foreign-key relationships that define its role in the Applications DBA data model.

• FND_APPLICATION — Referenced via APPLICATION_ID; supplies the product name and short name.
• FND_ORACLE_USERID — Referenced via ORACLE_ID; supplies the Oracle schema name for the product.
• FND_PRODUCT_DEPENDENCIES — References FND_PRODUCT_INSTALLATIONS through (APPLICATION_ID, ORACLE_ID) and through (REQUIRED_APPLICATION_ID, REQUIRED_ORACLE_ID), expressing prerequisite relationships between installed products.
• ALR_ACTION_SET_CHECKS — References FND_PRODUCT_INSTALLATIONS through (APPLICATION_ID, ORACLE_ID), linking Alert (ALR) action-set checks to installed products.

Together these relationships make FND_PRODUCT_INSTALLATIONS the anchor table for product registration, dependency validation, and Applications DBA diagnostics across Oracle EBS 12.1.1 and 12.2.2.