Search Results fnd_doc_category_usages_n1

Overview

APPLSYS.FND_DOC_CATEGORY_USAGES is an Oracle E-Business Suite application object that stores the relationships between attachment categories and the forms or form functions on which those categories are available. In Oracle EBS, attachment categories (defined in FND_DOCUMENT_CATEGORIES) classify the documents and attachments that users can associate with business records. FND_DOC_CATEGORY_USAGES acts as the assignment bridge that determines which categories are exposed on which form or form function, and whether that exposure is active. The ENABLED_FLAG column controls this: a value of Y indicates the category is enabled for the given form/function, and any other value indicates the relationship is defined but not active. The object resides in the APPS_TS_TX_DATA tablespace with PCT Free 10 and is registered under FND design data as FND.FND_DOC_CATEGORY_USAGES.

Because the table's core purpose is to resolve a many-to-many relationship between two other entities, a Data Vault modeling exercise would classify it heuristically as a link table, with FND_DOCUMENT_CATEGORIES and FND_ATTACHMENT_FUNCTIONS acting as the two referenced hubs. This is a modeling suggestion only; in the native EBS schema the object is a conventional intersection table.

Key Information Stored

The table's surrogate primary key is DOC_CATEGORY_USAGE_ID, a NUMBER populated from the FND_DOC_CATEGORY_USAGES_PK constraint and uniquely enforced by the FND_DOC_CATEGORY_USAGES_U1 unique index. The business-key candidate is the combination of ATTACHMENT_FUNCTION_ID and CATEGORY_ID, enforced by the unique index FND_DOC_CATEGORY_USAGES_U2; this pairing prevents duplicate category-to-function assignments. The non-unique index FND_DOC_CATEGORY_USAGES_N1 supports lookups driven by CATEGORY_ID alone.

• DOC_CATEGORY_USAGE_ID — Unique identifier and primary key for each usage record.
• CATEGORY_ID — Identifier of the attachment category, sourced from the FND_DOCUMENTS_CATEGORIES_S sequence and referencing FND_DOCUMENT_CATEGORIES.
• ATTACHMENT_FUNCTION_ID — Identifier of the attachment function (form or form function) that the category is assigned to, referencing FND_ATTACHMENT_FUNCTIONS.
• ENABLED_FLAG — VARCHAR2 flag indicating whether the category is enabled for the form or form function. Y means enabled; any other value means not enabled.
• FORMAT — Stores format information associated with the usage relationship.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns capturing audit and concurrency information for the row.

In the documented 12.2.2 physical schema, eleven columns are present, including the ZD_EDITION_NAME column that is used for edition-based redefinition support, and the unique indexes U1 and U2 include ZD_EDITION_NAME in their key composition.

Common Use Cases and Queries

Administrators and developers commonly query this table to determine which attachment categories are available on a specific form, to audit category assignments across the application, or to troubleshoot why a category does not appear for end users. A frequent pattern joins CATEGORY_ID to FND_DOCUMENT_CATEGORIES and ATTACHMENT_FUNCTION_ID to FND_ATTACHMENT_FUNCTIONS to resolve descriptive names.

• List all active categories for a given attachment function:

  SELECT dcu.doc_category_usage_id,
         dcu.category_id,
         dcu.attachment_function_id,
         dcu.enabled_flag
  FROM   applsys.fnd_doc_category_usages dcu
  WHERE  dcu.attachment_function_id = :function_id
  AND    dcu.enabled_flag = 'Y';

• Identify all functions where a specific category is enabled:

  SELECT attachment_function_id
  FROM   applsys.fnd_doc_category_usages
  WHERE  category_id = :category_id
  AND    enabled_flag = 'Y';

• Audit disabled or orphaned assignments by filtering on ENABLED_FLAG and reviewing the Who columns to trace when the relationship was created or last changed.
• Reporting on category coverage across forms to support implementation and security reviews.

Related Objects

• APPLSYS.FND_DOCUMENT_CATEGORIES — Referenced by the CATEGORY_ID foreign key; holds the category definitions themselves.
• APPLSYS.FND_ATTACHMENT_FUNCTIONS — Referenced by the ATTACHMENT_FUNCTION_ID foreign key; holds the forms and form functions eligible for attachments.
• FND_DOCUMENTS_CATEGORIES_S — Sequence that supplies the CATEGORY_ID value used by this table.
• APPS.FND_DOC_CATEGORY_USAGES — The APPS synonym exposed for application queries and forms.
• FND_DOC_CATEGORY_USAGES_PK, FND_DOC_CATEGORY_USAGES_U1, FND_DOC_CATEGORY_USAGES_U2, FND_DOC_CATEGORY_USAGES_N1 — Primary key constraint and supporting unique and non-unique indexes.

The table does not reference any object other than the two foreign keys noted above, and no other database objects were documented as referencing it.