Search Results oke_document_flowdowns

Overview

The FND_DOCUMENT_CATEGORIES table is a core Application Object Library (AOL) repository within Oracle E-Business Suite (EBS) that defines and manages document categories. It serves as a master reference table, establishing a controlled classification system for documents stored and managed across the application. This categorization is fundamental to the EBS document management architecture, enabling the logical grouping, security, and workflow routing of various document types, such as purchase orders, invoices, contracts, or custom attachments. Its role is to provide a centralized, reusable definition of document types that multiple application modules can reference, ensuring consistency in how documents are handled throughout the system.

Key Information Stored

The table's primary function is to store the unique definition of each document category. The key columns, as indicated by the provided metadata, include the surrogate primary key CATEGORY_ID and the unique business key NAME. A critical foreign key is APPLICATION_ID, which links the category to its owning application (via the FND_APPLICATION table), enforcing modular data integrity. While the provided ETRM excerpt does not list all columns, typical implementations also include columns for user-defined codes, descriptions, effective dates, and security attributes that control which responsibilities or users can access documents within a given category. The existence of a corresponding translation table, FND_DOCUMENT_CATEGORIES_TL, confirms that the NAME and potentially other descriptive attributes are translatable for multilingual implementations.

Common Use Cases and Queries

This table is central to queries and reports concerning document metadata and security. A common use case is generating a list of all available document categories for a specific application module, often for setup or administrative purposes. Developers frequently reference this table when writing custom code that interfaces with the EBS document entity model. Example SQL to retrieve active categories for a given application, joining with its translated name, would be:

• SELECT fdc.CATEGORY_ID, fdct.NAME, fdc.APPLICATION_ID FROM APPLSYS.FND_DOCUMENT_CATEGORIES fdc, APPLSYS.FND_DOCUMENT_CATEGORIES_TL fdct WHERE fdc.CATEGORY_ID = fdct.CATEGORY_ID AND fdc.APPLICATION_ID = 275; -- Example APP ID

Another critical use case involves troubleshooting or auditing document security and usages, requiring joins to the FND_DOC_CATEGORY_USAGES and FND_DOCUMENTS tables to see where a specific category is applied and which document instances belong to it.

Related Objects

As per the foreign key relationships documented in the ETRM, FND_DOCUMENT_CATEGORIES is a pivotal parent table within the AOL document management schema. Its primary child table is FND_DOCUMENTS, which stores the header information for individual document instances, each linked to a category via CATEGORY_ID. The FND_DOCUMENT_CATEGORIES_TL table holds the translated names for the categories. The FND_DOC_CATEGORY_USAGES table defines which entities (e.g., forms, functions) a category can be used with. Furthermore, its integration extends beyond core AOL, as evidenced by the foreign key from OKE_DOCUMENT_FLOWDOWNS in the Oracle Contracts module, demonstrating its enterprise-wide role in document classification. The table itself references FND_APPLICATION to identify its owning product.