Results for “install_group_num”

50+ results




Overview
Explore in AI Chat

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

Overview

FND_ORACLE_USERID is a core reference table in the Oracle E-Business Suite environment, owned by the APPLSYS schema and delivered as part of the FND — Application Object Library product. As its description states, the table records the ORACLE accounts that contain application data, meaning it serves as the authoritative registry of Oracle database schemas registered within an EBS instance. Each row identifies one such account by Oracle username, its characteristics (such as whether it is enabled or read-only), and, in some releases, an encrypted password and a concurrent batch queue association.

Because the table is referenced widely throughout the FND and ALR (Alert) schemas, it functions as a foundational lookup that allows applications to translate an internal numeric identifier into a validated Oracle database user. From a Data Vault modeling perspective, this object is a hub: it holds the unique business keys and their associated identity, and it is referenced by a large number of links and satellites that record events and configuration for those accounts.

Key Information Stored

The table is defined in APPLSYS and contains thirteen documented columns. The most significant columns are:

  • ORACLE_ID — The surrogate primary key of the table, defined by the FND_ORACLE_USERID_PK constraint. Foreign keys throughout the EBS data model point to this column.
  • ORACLE_USERNAME — The Oracle database username. This is the business-key candidate, enforced by the unique index FND_ORACLE_USERID_UK1 (also documented as FND_ORACLE_USERID_U2 in the physical schema).
  • DESCRIPTION — Free-form text describing the purpose or application associated with the account.
  • ENABLED_FLAG — Indicates whether the registered account is active and usable.
  • READ_ONLY_FLAG — Flags accounts provisioned for read-only query access rather than data manipulation.
  • ENCRYPTED_ORACLE_PASSWORD — An encrypted representation of the account password, maintained for compatibility with the application's older connectivity model.
  • CONCURRENT_BATCH_QUEUE_ID — Associates the account with a concurrent batch queue used in parallel concurrent processing.
  • INSTALL_GROUP_NUM — Numeric group used by Rapid Install to partition accounts across the installation topology.
  • LAST_UPDATE_DATE — The date the row was last modified.
  • LAST_UPDATED_BY — The application user who last modified the row.
  • CREATION_DATE — The date the row was created.
  • CREATED_BY — The application user who created the row.
  • LAST_UPDATE_LOGIN — The login session under which the last update occurred.

Audit columns such as LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATED_BY are the standard EBS "Who" columns and support change tracking and troubleshooting.

Common Use Cases and Queries

This table is used to validate Oracle schema names during data-group and installation configuration, to join concurrent request records to the account that submitted the request, and to populate reports that list which Oracle accounts are registered in the instance.

A representative query joining the hub to concurrent requests is:

  • SELECT r.request_id, r.oracle_id, u.oracle_username FROM fnd_concurrent_requests r, fnd_oracle_userid u WHERE r.oracle_id = u.oracle_id;

To list enabled accounts, an analyst would filter on ENABLED_FLAG. Because ORACLE_ID is the primary key and ORACLE_USERNAME the unique business key, queries may join on either, but joins on ORACLE_ID are preferred for index efficiency.

Related Objects

The table is a hub referenced by many satellites and links. The following are the most significant dependents, each joining on the column shown:

Together these relationships confirm FND_ORACLE_USERID as a central hub whose ORACLE_ID is propagated across concurrent processing, alerting, data grouping, and installation metadata throughout Oracle EBS 12.1.1 and 12.2.2.