Search Results ce_arch_headers_all




Overview
Explore in AI Chat

Overview

The FND_DOCUMENT_SEQUENCES table is a core repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the central registry for all document sequences defined across the application. Document sequences are a critical control mechanism, providing a method to generate and enforce unique, auditable, and often sequential numbers for key business documents such as invoices, journal entries, purchase orders, and receipts. The table's registration function ensures that sequences are managed consistently, can be assigned to specific applications and document categories, and are subject to unified auditing and access control rules. Its existence in the APPLSYS schema underscores its foundational role in the EBS architecture, supporting financial, order management, and other transactional modules.

Key Information Stored

The table's primary identifier is the DOC_SEQUENCE_ID, a unique numeric key. The NAME column provides a unique, human-readable identifier for the sequence. While the full column list is not detailed in the provided metadata, based on its function, the table typically stores configuration data such as the associated application (APPLICATION_ID), the method of generation (e.g., automatic or manual), the initial number, and status flags (e.g., ACTIVE_FLAG). It also links to the underlying Oracle sequence object used to generate the numeric values. The primary keys (FND_DOCUMENT_SEQUENCES_PK on ID and FND_DOCUMENT_SEQUENCES_UK1 on NAME) enforce data integrity for this central reference point.

Common Use Cases and Queries

Primary use cases involve administration, troubleshooting, and auditing of document numbering. System administrators query this table to review configured sequences, diagnose gaps or errors in document numbering, and verify assignments. Common reporting queries join with related audit and assignment tables to track sequence usage. For example, to list all active document sequences and their basic definitions, a query might be: SELECT doc_sequence_id, name FROM fnd_document_sequences WHERE enabled_flag = 'Y';. To investigate assignment details, a join with FND_DOC_SEQUENCE_ASSIGNMENTS is typical: SELECT fds.name, fdsa.* FROM fnd_document_sequences fds, fnd_doc_sequence_assignments fdsa WHERE fds.doc_sequence_id = fdsa.doc_sequence_id;. Auditors rely on the related FND_DOC_SEQUENCE_AUDIT table, which is foreign-keyed to this one, to trace the complete history of number generation.

Related Objects

As evidenced by the extensive foreign key relationships, FND_DOCUMENT_SEQUENCES is a pivotal parent table referenced by numerous transactional and control tables across EBS modules. Key relationships include:

This network of foreign keys demonstrates that the DOC_SEQUENCE_ID from this table is the universal key for linking document sequence definitions to their operational use throughout the system.