Results for “fnd_doc_sequence_categories”

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

Overview

The FND_DOC_SEQUENCE_CATEGORIES table resides in the APPLSYS schema and is owned by the FND — Application Object Library product. It stores document category definitions that drive the Oracle E-Business Suite document sequencing framework, the mechanism used to assign gapless, auditable sequential numbers to financial and transactional documents such as invoices, payments, journals, and receipts. Each row defines a category — identified by an APPLICATION_ID and a CODE — that legal or fiscal requirements mandate be numbered consecutively within a period.

From a Data Vault modeling perspective, the metadata classifies this table as hub-leaning. That is, it functions primarily as a hub of distinct business entities (document categories), keyed by the composite business key (APPLICATION_ID, CODE). The associated descriptive attributes and audit columns behave satellite-like, but the table's dominant role is to centralize the set of valid categories referenced elsewhere.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• APPLICATION_ID — Part of the composite primary key; identifies the owning Oracle application (e.g., Payables, Receivables, General Ledger).
• CODE — Part of the composite primary key; the short internal identifier for the category (for example, the code used by FND_DOC_SEQUENCE_ASSIGNMENTS).
• NAME — The user-facing name of the document category.
• TABLE_NAME — The underlying transactional table whose rows are numbered using this category.
• DESCRIPTION — Free-text explanation of the category's purpose.
• ZD_EDITION_NAME — Editioning column used in the 12.2 online patching architecture; participates in the unique index FND_DOC_SEQUENCE_CATEGORIES_U1.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard "Who" audit columns maintained by the framework.

The surrogate primary key is FND_DOC_SEQUENCE_CATEGORIES_PK (APPLICATION_ID, CODE). The unique index FND_DOC_SEQUENCE_CATEGORIES_U1 (APPLICATION_ID, CODE, ZD_EDITION_NAME) serves as the effective business-key candidate in the editioned 12.2 schema, preventing duplicate category definitions per application per edition.

Common Use Cases and Queries

Document sequencing configuration and troubleshooting are the primary scenarios. A common query lists all categories defined for a specific application:

• SELECT application_id, code, name, table_name FROM fnd_doc_sequence_categories WHERE application_id = :app_id;

To resolve the human-readable category attached to an assignment, join to FND_DOC_SEQUENCE_ASSIGNMENTS:

• SELECT a.application_id, a.category_code, c.name, a.set_of_books_id
• FROM fnd_doc_sequence_assignments a, fnd_doc_sequence_categories c
• WHERE a.application_id = c.application_id AND a.category_code = c.code;

Reporting use cases include auditing which categories exist per module, verifying that a category's TABLE_NAME matches the intended transaction source, and validating sequencing setup before period close. Because sequence numbering influences statutory audit trails, DBAs frequently extract these definitions when comparing environments.

Related Objects

• FND_DOC_SEQUENCE_ASSIGNMENTS — References this table via APPLICATION_ID and CATEGORY_CODE; assigns a category to a specific set of books and sequence.
• FND_DOC_SEQUENCE_CATEGORIES_PK — The primary key constraint on (APPLICATION_ID, CODE).
• FND_DOC_SEQUENCE_CATEGORIES_U1 — The editioned unique index supporting the business key.
• FND_DOC_SEQUENCES — Defines the actual sequence objects used for numbering within each assignment.
• FND_DOC_SEQUENCE_AUDIT — Records the values issued for documents under a category.

Together these objects form the document sequencing configuration chain: category definition, assignment to an entity, sequence generation, and audit capture.