Search Results fnd_sequences_uk1

Overview

FND_SEQUENCES is a core dictionary table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the metadata registry of database sequences that have been registered with Oracle Application Object Library. Rather than merely reflecting Oracle's native sequence catalog, FND_SEQUENCES records the EBS-aware attributes of each sequence — its owning application, its naming identity, and its generator behavior — so that the concurrent manager, installation utilities, and patching tools can manage them consistently across releases.

In Data Vault modeling terms, the mined relationship metadata classifies FND_SEQUENCES as satellite-leaning. This is a modeling suggestion: the table behaves as a descriptive satellite attached to the application hub (FND_APPLICATION), rather than as a transactional hub or an association link. The surrogate identifier is the composite (APPLICATION_ID, SEQUENCE_ID); the business key is expressed by the unique index FND_SEQUENCES_U1 on (APPLICATION_ID, SEQUENCE_ID, ZD_EDITION_NAME) and FND_SEQUENCES_U2 on (SEQUENCE_NAME, APPLICATION_ID, ZD_EDITION_NAME). The ZD_EDITION_NAME column supports the editioning framework introduced for online patching in EBS 12.2.x; in 12.1.1 this column is not present in the running dictionary.

Key Information Stored

• APPLICATION_ID — The registered application that owns the sequence; part of both the primary key and the foreign key to FND_APPLICATION.
• SEQUENCE_ID — The internal numeric identifier assigned by AOL; combined with APPLICATION_ID it forms the surrogate primary key FND_SEQUENCES_PK.
• SEQUENCE_NAME — The database sequence name as known to the EBS instance; together with APPLICATION_ID it is the business-key candidate enforced by FND_SEQUENCES_UK1 / FND_SEQUENCES_U2.
• START_VALUE — Initial value from which the sequence begins generating numbers.
• INCREMENT_BY — Step size applied on each NEXTVAL call.
• MIN_VALUE and MAX_VALUE — Bounds defining the valid range of generated values.
• CACHE_SIZE — Number of values pre-allocated in memory to reduce dictionary contention.
• CYCLE_FLAG — Indicates whether the sequence wraps to MIN_VALUE after reaching MAX_VALUE.
• ORDER_FLAG — Indicates whether values are generated in strict request order, relevant in Real Application Clusters.
• DESCRIPTION — Functional narrative describing the sequence's purpose.
• ZD_EDITION_NAME — Edition qualifier used by the 12.2.x online patching architecture.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture standard EBS row-level audit information.

Common Use Cases and Queries

The most frequent requirement is locating which application owns a given sequence, or auditing sequence behavior after a clone or patch. A typical pattern joins FND_SEQUENCES to FND_APPLICATION to resolve the application short name:

SELECT fs.sequence_name, fa.application_short_name, fs.start_value, fs.increment_by, fs.cache_size FROM fnd_sequences fs, fnd_application fa WHERE fs.application_id = fa.application_id ORDER BY fa.application_short_name, fs.sequence_name;

Because the LAST_UPDATE_DATE column is maintained by AOL, administrators can audit recently modified definitions following an upgrade:

SELECT sequence_name, application_id, last_update_date, last_updated_by FROM fnd_sequences WHERE last_update_date > SYSDATE - 30;

Reconciliation scripts compare FND_SEQUENCES rows against ALL_SEQUENCES to detect drift between the AOL registry and the physical database catalog — a common check after a failed installation or patch cycle. Reporting extracts frequently combine this table with FND_BUILDING_BLOCK_OBJECTS to enumerate which AOL objects are associated with a given sequence.

Related Objects

• FND_APPLICATION — Referenced via FND_SEQUENCES.APPLICATION_ID; the owning application registry.
• FND_BUILDING_BLOCK_OBJECTS — References FND_SEQUENCES through OBJECT_APPLICATION_ID and OBJECT_ID, associating AOL building-block objects with registered sequences.
• FND_SEQUENCES_PK — Primary key index on (APPLICATION_ID, SEQUENCE_ID).
• FND_SEQUENCES_UK1 / FND_SEQUENCES_U2 — Unique business-key indexes on the sequence name and application combination.
• ALL_SEQUENCES / DBA_SEQUENCES — Oracle data dictionary views used to validate registered sequences against physical definitions.
• FND_APPLICATION_TL — Provides translated application names for reporting joins.