Search Results fnd_sequences_u2

Overview

APPLSYS.FND_SEQUENCES is a VALID seed-data table in the Oracle E-Business Suite Applications Object Library (FND). It stores the registration metadata for database sequences used across Oracle Applications. Each row records the sequence name, description, and the seed values that Oracle Applications applies when creating or upgrading the corresponding database sequence objects during installation, patch application, and upgrade cycles. The FND design data repository identifies this object as FND.FND_SEQUENCES, and its physical storage resides in the APPS_TS_SEED tablespace, the standard location for seed and setup data in EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. Its identity is anchored by a composite surrogate primary key, while descriptive attributes such as START_VALUE, INCREMENT_BY, MIN_VALUE, MAX_VALUE, CACHE_SIZE, CYCLE_FLAG, ORDER_FLAG, and DESCRIPTION behave as context-dependent descriptive payload. Row relationships are driven primarily by the owning application rather than by a dense transactional network, consistent with a satellite classification.

Key Information Stored

The surrogate primary key is FND_SEQUENCES_PK, defined on the columns APPLICATION_ID and SEQUENCE_ID. Two unique indexes serve as business-key candidates. FND_SEQUENCES_U1 enforces uniqueness on APPLICATION_ID, SEQUENCE_ID, and ZD_EDITION_NAME, while FND_SEQUENCES_U2 enforces uniqueness on SEQUENCE_NAME, APPLICATION_ID, and ZD_EDITION_NAME. This means FND_SEQUENCES_U2 is the index the user searched for, and it guarantees that a given sequence name is unique within an application for a given edition (ZD_EDITION_NAME is a 12.2.x editioning column).

The most significant columns include:

• APPLICATION_ID — numeric identifier of the owning application; part of both the primary key and the foreign key to FND_APPLICATION.
• SEQUENCE_ID — surrogate numeric identifier for the registered sequence.
• SEQUENCE_NAME — the VARCHAR2(30) name of the registered database sequence.
• START_VALUE — the initial value used when the sequence is created.
• INCREMENT_BY — the interval between successive generated numbers.
• MIN_VALUE and MAX_VALUE — the bounds applied to the sequence.
• CACHE_SIZE — number of values cached in memory.
• CYCLE_FLAG — whether the sequence wraps after reaching MAX_VALUE.
• ORDER_FLAG — whether values are generated in requested order in RAC environments.
• DESCRIPTION — VARCHAR2(240) free-text description of the sequence's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns used for auditing and change tracking.

Common Use Cases and Queries

The table is typically queried to inventory sequences per application, audit seed values against the actual database definitions, and support patch or upgrade diagnostics. A representative pattern filters by owning application and name:

SELECT APPLICATION_ID, SEQUENCE_ID, SEQUENCE_NAME,
       START_VALUE, INCREMENT_BY, MIN_VALUE, MAX_VALUE,
       CACHE_SIZE, CYCLE_FLAG, ORDER_FLAG, DESCRIPTION
FROM   APPLSYS.FND_SEQUENCES
WHERE  SEQUENCE_NAME = :seq_name;

A common reporting join links the owning application name to each sequence, using FND_APPLICATION.APPLICATION_ID = FND_SEQUENCES.APPLICATION_ID. Listing all sequences for a single application is another frequent operation, and change auditing leverages the Who columns. Because FND_SEQUENCES_U2 covers SEQUENCE_NAME and APPLICATION_ID, queries filtering on those columns can take advantage of that unique index.

Related Objects

• FND_APPLICATION — referenced by FND_SEQUENCES.APPLICATION_ID; supplies the application short name and basepath for joins.
• FND_BUILDING_BLOCK_OBJECTS — references this table via OBJECT_APPLICATION_ID, linking sequences to building-block metadata.
• FND_SEQUENCES_PK, FND_SEQUENCES_U1, and FND_SEQUENCES_U2 — the primary key and unique indexes that enforce identity and business-key uniqueness.
• Oracle DBA_SEQUENCES — the database data dictionary view used to reconcile registered seed values against actual sequence definitions.