Results for “fnd_document_categories”

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

Overview

FND_DOCUMENT_CATEGORIES is a foundational reference table in the Oracle E-Business Suite Application Object Library (FND) product family, owned by the APPLSYS schema. It defines the classification framework by which documents are grouped and categorized across the EBS instance. Each row represents a single document category, scoped to a particular application, and serves as the master reference for any EBS feature that needs to tag or organize documents—attachments, contracts, sourcing documents, or service agreements—into meaningful groupings.

The table is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its structure reflects a standard FND reference entity: a surrogate primary key, a foreign key to the owning application, audit columns, descriptive attributes, and the editioning column ZD_EDITION_NAME carried in the 12.2.2 data model. Based on the extracted foreign-key topology, the object is best modeled heuristically as a hub candidate in a Data Vault design—it holds a durable, non-transactional business key (the category identity) that is referenced by multiple downstream satellites and link-like child entities. This classification is a modeling suggestion only.

Key Information Stored

The 28 documented columns resolve into a small set of functionally meaningful fields. The most significant are:

• CATEGORY_ID — the surrogate primary key (FND_DOCUMENT_CATEGORIES_PK) and the internal identifier used by allforeign keys in child tables.
• NAME — the human-readable category name. This is the primary business-key candidate, enforced by the unique index FND_DOCUMENT_CATEGORIES_U2 (NAME, ZD_EDITION_NAME) and the legacy FND_DOCUMENT_CATEGORIES_UK1 constraint.
• APPLICATION_ID — foreign key to FND_APPLICATION, scoping the category to its owning Oracle application.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window that controls the category's availability for selection.
• DEFAULT_DATATYPE_ID — identifies the default datatype associated with the category.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard FND audit/WHO columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard 15-column descriptive flexfield (DFF) block allowing customers to extend the category with site-specific attributes.
• ZD_EDITION_NAME — the editioning discriminator used in the 12.2.2 Online Patching (ADOP) architecture.

The second unique index, FND_DOCUMENT_CATEGORIES_U1 (CATEGORY_ID, ZD_EDITION_NAME), confirms that the surrogate key is edition-scoped, while U2 establishes NAME as the true business key. Note that translatable columns such as descriptions live in FND_DOCUMENT_CATEGORIES_TL rather than in this table.

Common Use Cases and Queries

Typical use is populating values lists for document classification pickers, validating category assignments, and reporting document volumes by category per application. Because the category text is translated, queries that need display names must join the TL table and pin the language.

A representative query listing active categories for an application:

• SELECT dc.category_id, dc.name
FROM fnd_document_categories dc
WHERE dc.application_id = :app_id
AND TRUNC(SYSDATE) BETWEEN NVL(dc.start_date_active, SYSDATE)
AND NVL(dc.end_date_active, SYSDATE);

To retrieve translated names:

• SELECT dc.category_id, dct.name
FROM fnd_document_categories dc,
fnd_document_categories_tl dct
WHERE dc.category_id = dct.category_id
AND dct.language = USERENV('LANG');

For document-inventory reporting, join to FND_DOCUMENTS on CATEGORY_ID to count attached documents per category, filtering on entity name and source. In the 12.2.2 model, constrain queries to the current edition by including dc.zd_edition_name = 'ORA$BASE' where appropriate.

Related Objects

The FK graph identifies the principal dependent objects:

• FND_APPLICATION — referenced by APPLICATION_ID; supplies the owning application.
• FND_DOCUMENTS — references this table via CATEGORY_ID; the primary child holding document attachment records.
• FND_DOCUMENT_CATEGORIES_TL — the translation (satellite) table, joined on CATEGORY_ID, holding language-specific names.
• FND_DOC_CATEGORY_USAGES — references CATEGORY_ID; records where each category may be used.
• OKE_DOCUMENT_FLOWDOWNS (Oracle Contracts/OKE) — references DOCUMENT_CATEGORY_ID; drives contract document category flows.

Collectively these objects confirm the hub role of FND_DOCUMENT_CATEGORIES as the central reference for document classification throughout Oracle EBS.