Search Results fnd_doc_category_usages_u2

Overview

The APPLSYS.FND_DOC_CATEGORY_USAGES table is a core repository within the Oracle E-Business Suite (EBS) document management and attachment framework, specifically in releases 12.1.1 and 12.2.2. It functions as a junction table that governs the relationships between document categories and the application forms or form functions where those categories can be utilized. Its primary role is to define and control which predefined document categories are available for attaching files or notes within specific application screens, thereby enforcing business rules and data organization for attachments across the system. The ENABLED_FLAG column provides a mechanism to activate or deactivate a specific category for a given form or function without deleting the relationship.

Key Information Stored

The table's structure is designed to manage the association metadata with standard auditing columns. The most critical columns include:

• DOC_CATEGORY_USAGE_ID: The primary key and unique identifier for each association record.
• CATEGORY_ID: A foreign key referencing FND_DOCUMENT_CATEGORIES, identifying the specific document category (e.g., 'Contract', 'Invoice Image').
• ATTACHMENT_FUNCTION_ID: A foreign key referencing FND_ATTACHMENT_FUNCTIONS, identifying the specific form or form function where the category can be used.
• ENABLED_FLAG: A VARCHAR2 flag (typically 'Y' or 'N') that determines if the category is currently enabled for the linked form/function. This allows for temporary deactivation.
• FORMAT: A column whose specific purpose is not detailed in the provided metadata but is likely related to defining a default or allowed format for attachments of this category in this context.
• Standard WHO Columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN): For tracking record creation and modifications.

Common Use Cases and Queries

This table is central to configuration and troubleshooting tasks related to the attachments interface. A common use case is diagnosing why a particular document category does not appear as an option in a specific form. Administrators would query this table to verify if a valid, enabled association exists between the category and the form's function. Another scenario involves auditing or reporting on all forms where a specific document category, such as 'Supplier Certification', is enabled for use.

A typical diagnostic query would join to the related descriptive tables:

SELECT fdcu.doc_category_usage_id,
       fdc.category_name,
       faf.user_function_name,
       fdcu.enabled_flag
FROM   applsys.fnd_doc_category_usages fdcu,
       fnd_document_categories fdc,
       fnd_attachment_functions faf
WHERE  fdcu.category_id = fdc.category_id
AND    fdcu.attachment_function_id = faf.attachment_function_id
AND    fdc.category_name = '&category_name'
AND    fdcu.enabled_flag = 'Y';

To list all category-to-function mappings, the base query from the ETRM can be extended with appropriate WHERE clauses or joins for reporting.

Related Objects

The FND_DOC_CATEGORY_USAGES table sits at the intersection of two key attachment entities, as defined by its foreign key relationships:

• FND_DOCUMENT_CATEGORIES: The relationship is established via FND_DOC_CATEGORY_USAGES.CATEGORY_ID → FND_DOCUMENT_CATEGORIES. This links the usage record to the master definition of the document category.
• FND_ATTACHMENT_FUNCTIONS: The relationship is established via FND_DOC_CATEGORY_USAGES.ATTACHMENT_FUNCTION_ID → FND_ATTACHMENT_FUNCTIONS. This links the usage record to the specific application form or function where attachments can be made.

Its primary key, DOC_CATEGORY_USAGE_ID, is enforced by the unique index FND_DOC_CATEGORY_USAGES_U1. A second unique index (FND_DOC_CATEGORY_USAGES_U2) on the combination of ATTACHMENT_FUNCTION_ID and CATEGORY_ID ensures that no duplicate associations are created for the same form and category.