Search Results fnd_sequences




Overview
Explore in AI Chat

Overview

The FND_SEQUENCES table is a core metadata repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the central registry for all sequences that are defined and managed by the application, as opposed to sequences created directly in the database schema. This registration mechanism is fundamental to the EBS architecture, ensuring sequences are properly integrated with the application's modular structure, security model, and upgrade processes. By cataloging sequences, Oracle EBS can maintain control over their definition, usage, and dependencies across different application modules, which is critical for the integrity and supportability of the entire system in both the 12.1.1 and 12.2.2 versions.

Key Information Stored

The table stores essential metadata that uniquely identifies and describes each registered sequence. Its structure, as indicated by the primary and unique keys, emphasizes the relationship between a sequence and its owning application. The key columns include APPLICATION_ID, which links to FND_APPLICATION to identify the product module (e.g., GL, AP) that owns the sequence. SEQUENCE_ID is the primary numeric identifier, while SEQUENCE_NAME holds the actual name of the sequence object. Other columns typically include metadata such as the initial value, increment, cache size, and cycle flag, defining the sequence's behavior. The presence of the unique key on APPLICATION_ID and SEQUENCE_NAME enforces that sequence names are unique within a given application.

Common Use Cases and Queries

Primary use cases involve administration, troubleshooting, and impact analysis. Database administrators and functional consultants query this table to understand sequence dependencies before patching or upgrading, or to diagnose issues with number generation. Common reporting queries include identifying all sequences for a specific application or finding a particular sequence's definition. For example:

  • To find a sequence by name across all modules: SELECT a.application_short_name, s.sequence_name FROM applsys.fnd_sequences s, applsys.fnd_application a WHERE s.application_id = a.application_id AND s.sequence_name LIKE '%BATCH%';
  • To list sequences for the General Ledger (GL) module: SELECT sequence_name FROM applsys.fnd_sequences WHERE application_id = (SELECT application_id FROM applsys.fnd_application WHERE application_short_name = 'GL');

It is crucial to note that direct manipulation of data in this table is strongly discouraged; sequences should be managed through standard application administration interfaces or APIs.

Related Objects

As per the provided metadata, FND_SEQUENCES has defined relationships with several other key Application Object Library tables. The primary foreign key links it to FND_APPLICATION via the APPLICATION_ID column, anchoring each sequence to its product. Furthermore, the table is referenced by FND_BUILDING_BLOCK_OBJECTS through the composite foreign key on OBJECT_APPLICATION_ID and OBJECT_ID. This relationship indicates that registered sequences are treated as building block objects within the EBS architecture, allowing them to be incorporated into higher-level application constructs. This integration underscores the sequence's role as a managed application component rather than a standalone database object.