Results for “fnd_attachment_functions”

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

Overview

FND_ATTACHMENT_FUNCTIONS is an Oracle E-Business Suite Applications Object Library (FND) table owned by the APPLSYS schema. It stores the registry of forms and form functions that have attachments enabled within the EBS environment. In practical terms, the table maps an EBS function (identified by FUNCTION_ID) to an attachment definition, allowing the Attachments framework to determine which application entities expose the paperclip / attachment feature and how those attachments behave.

The object is documented as VALID in the ETRM repository and contains 13 columns in the 12.2.2 physical schema. It is likely visible in both 12.1.1 and 12.2.2 environments, although the presence of ZD_EDITION_NAME reflects the Edition-Based Redefinition (EBR) architecture introduced in 12.2. In a Data Vault modeling sense, the table is classified as satellite-leaning. This is a suggestion only: the table holds descriptive and configuration attributes that qualify a parent function, rather than acting as a pure hub or link of business keys. A Data Vault designer might treat it as a satellite attached to a function hub, with the composite keys acting as the referencing driver.

Key Information Stored

The primary key is FND_ATTACHMENT_FUNCTIONS_PK, defined on the surrogate column ATTACHMENT_FUNCTION_ID. Two unique indexes act as business-key candidates: FND_ATTACHMENT_FUNCTIONS_UK1 on (APPLICATION_ID, FUNCTION_ID, FUNCTION_TYPE), and FND_ATTACHMENT_FUNCTIONS_U1 on (ATTACHMENT_FUNCTION_ID, ZD_EDITION_NAME). The most significant columns include:

• ATTACHMENT_FUNCTION_ID — surrogate primary key identifying the attachment function record.
• APPLICATION_ID — the application owning the form or concurrent program.
• FUNCTION_ID — the form function or concurrent program associated with the attachment.
• FUNCTION_TYPE — discriminates the type of function (form type versus concurrent program type).
• FUNCTION_NAME — descriptive name of the function for reporting and lookup.
• SESSION_CONTEXT_FIELD — context field used to resolve the entity key at runtime.
• ENABLED_FLAG — indicates whether the attachment definition is active.
• Standard WHO columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — EBR edition discriminator present in the 12.2 family.

Common Use Cases and Queries

Administrators and technical consultants query this table to inventory which functions have attachments enabled, to troubleshoot missing paperclip icons, and to verify attachment configuration after a clone or upgrade. A typical lookup joins to FND_FORM_FUNCTIONS to obtain the user-facing function name:

SELECT aff.attachment_function_id, fff.function_name,
       aff.function_type, aff.enabled_flag
FROM   fnd_attachment_functions aff,
       fnd_form_functions fff
WHERE  aff.function_id = fff.function_id
AND    aff.enabled_flag = 'Y';

Reporting scripts frequently filter by APPLICATION_ID or FUNCTION_TYPE to isolate forms from concurrent programs, and join to FND_ATTACHMENT_BLOCKS and FND_DOC_CATEGORY_USAGES to render the full attachment footprint for a given function. During upgrades, comparing the row count and ENABLED_FLAG values against a baseline helps confirm that custom attachments survived migration.

Related Objects

The table participates in a well-defined foreign key network. The following relationships are documented in the ETRM metadata:

• FND_FORM_FUNCTIONS — joined on FUNCTION_ID; supplies the function definition referenced by this table.
• FND_FORM — joined on APPLICATION_ID and FUNCTION_ID; identifies the form-level attachment context.
• FND_CONCURRENT_PROGRAMS — joined on APPLICATION_ID and FUNCTION_ID; applies the same mechanism to concurrent programs.
• FND_ATTACHMENT_BLOCKS — references this table via ATTACHMENT_FUNCTION_ID; defines block-level attachment behavior.
• FND_DOC_CATEGORY_USAGES — references this table via ATTACHMENT_FUNCTION_ID; links document categories to attachment functions.

Together these objects form the configuration layer that underpins the EBS Attachments framework, and FND_ATTACHMENT_FUNCTIONS acts as the central bridge between functions and the blocks and document categories that consume them.