Search Results fnd_doc_category_usages_pk

Overview

FND_DOC_CATEGORY_USAGES is a reference and configuration table in the APPLSYS schema of Oracle E-Business Suite, owned by the FND — Application Object Library product. It defines the relationships between document categories and the forms or form functions through which attachments in those categories may be entered, viewed, or managed. The table therefore acts as the junction that binds a document category defined in FND_DOCUMENT_CATEGORIES to a specific attachment-enabled function defined in FND_ATTACHMENT_FUNCTIONS. When a user attempts to attach a document of a given category to a form, the application consults this table to determine whether that category is permitted for the function currently being executed, and how the resulting attachment should be formatted.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link. The table carries two foreign keys — CATEGORY_ID referencing FND_DOCUMENT_CATEGORIES and ATTACHMENT_FUNCTION_ID referencing FND_ATTACHMENT_FUNCTIONS — and its uniqueness constraint is expressed across exactly those two columns, which is the classic pattern of a link table resolving a many-to-many relationship between two hubs. The remaining descriptive and audit columns behave as link-level attributes rather than as a dedicated satellite.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are outlined below.

• DOC_CATEGORY_USAGE_ID — the surrogate primary key enforced by FND_DOC_CATEGORY_USAGES_PK. No business meaning is attached to the value; it exists solely to give each relationship row a stable identifier.
• CATEGORY_ID — foreign key to FND_DOCUMENT_CATEGORIES, identifying the document category being made available.
• ATTACHMENT_FUNCTION_ID — foreign key to FND_ATTACHMENT_FUNCTIONS, identifying the form or form function on which the category may be used.
• ENABLED_FLAG — controls whether the category-to-function relationship is currently active. Disabling the flag suppresses the category from the attachment selection list for that function without deleting the row.
• FORMAT — specifies the attachment format behavior associated with the usage, such as whether the document is stored and presented as text, a URL, or a file.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard FND audit columns recording who created the row, who last modified it, and the login context of that modification.
• ZD_EDITION_NAME — the edition column that supports the editioning model used in the 12.2 online patching architecture; in a 12.1.1 environment this column is absent.

Two unique indexes are documented. FND_DOC_CATEGORY_USAGES_U1 covers DOC_CATEGORY_USAGE_ID and ZD_EDITION_NAME, reinforcing the surrogate key. FND_DOC_CATEGORY_USAGES_U2 covers ATTACHMENT_FUNCTION_ID, CATEGORY_ID, and ZD_EDITION_NAME, and is the true business-key candidate: it guarantees that a given category is linked to a given function only once within an edition. The metadata also references a constraint named FND_DOC_CATEGORY_USAGES_UK2 spanning ATTACHMENT_FUNCTION_ID and CATEGORY_ID.

Common Use Cases and Queries

Typical enquiries concern which categories are available on a particular form, which functions use a given category, and which rows have been disabled.

• Listing active categories for a function: select from FND_DOC_CATEGORY_USAGES joined to FND_DOCUMENT_CATEGORIES on CATEGORY_ID where ATTACHMENT_FUNCTION_ID equals the target function and ENABLED_FLAG = 'Y'.
• Auditing category reuse: group by CATEGORY_ID across FND_DOC_CATEGORY_USAGES to find categories mapped to many functions.
• Diagnosing missing attachment choices: confirm that a row exists for the function and category pair, that ENABLED_FLAG is 'Y', and that the parent rows in FND_DOCUMENT_CATEGORIES and FND_ATTACHMENT_FUNCTIONS are themselves valid.
• Data cleanup: identify orphaned rows whose CATEGORY_ID or ATTACHMENT_FUNCTION_ID no longer resolves to a parent record.

All queries should be written against APPLSYS and, in 12.2, should account for the edition column where uniqueness is concerned.

Related Objects

• FND_DOCUMENT_CATEGORIES — parent of CATEGORY_ID; holds the category name, description, and default format.
• FND_ATTACHMENT_FUNCTIONS — parent of ATTACHMENT_FUNCTION_ID; registers the forms and functions that support attachments.
• FND_ATTACHED_DOCUMENTS — stores the actual attachment instances created against categories permitted by this table.
• FND_DOC_CATEGORIES_TL — translation table supplying the display name of the category.
• FND_ATTACHMENT_FUNCTIONS_TL — translation table for the function descriptions.
• FND_DOC_CATEGORY_USAGES_PK / _UK2 — the constraints that enforce row identity and the business key.

Together these objects govern the entire attachment-category configuration surface within the FND foundation layer.