Results for “attachment_function_id”

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

Overview

FND_ATTACHMENT_FUNCTIONS_VL is a valid, APPS-owned view in the Oracle E-Business Suite FND (Application Object Library) product. It is documented in ETRM for both 12.1.1 and 12.2.2. The view presents a joined, denormalized projection of the FND_ATTACHMENT_FUNCTIONS base entity, enriched with either FND_FORM or FND_FORM_FUNCTIONS context. Its core purpose is to define which Forms functions permit attachments, and under what session context, so that the Forms attachment framework can resolve an attachment block at runtime and so that administrators and integrators can report on attachment configuration.

Within Oracle EBS reporting and integration, the view is the standard read interface for attachment-function metadata. It is especially relevant to the SESSION_CONTEXT_FIELD column, which drives how the framework keys attachment records to a form instance.

Underlying Base Objects

Per ETRM metadata, the view is defined over the base object FND_ATTACHMENT_FUNCTIONS (exposed as a synonym) and the package FND_ATTACHMENT_UTIL_PKG. The view text elects from FND_ATTACHMENT_FUNCTIONS FAF and calls FND_ATTACHMENT_UTIL_PKG.GET_USER_FUNCTION_NAME(FUNCTION_TYPE, APPLICATION_ID, FUNCTION_NAME) to derive the USER_FUNCTION_NAME column. The Description further states the view combines FND_ATTACHMENT_FUNCTIONS with FND_FORM or FND_FORM_FUNCTIONS, meaning it resolves the referenced form entity and its function to produce a human-readable function name. The view exposes the base ROWID, preserving a stable row identifier for the underlying attachment-function record, which is useful for downstream updates and joins.

Key Columns

• ROW_ID — row identifier of the base attachment-function row in FND_ATTACHMENT_FUNCTIONS.
• ATTACHMENT_FUNCTION_ID — primary key of the attachment-function definition.
• FUNCTION_TYPE — discriminator indicating whether the attachment target resolves to a form or a form function.
• FUNCTION_ID / FUNCTION_NAME — the referenced function identifier and internal name.
• USER_FUNCTION_NAME — derived, display-friendly function name returned by FND_ATTACHMENT_UTIL_PKG.GET_USER_FUNCTION_NAME.
• APPLICATION_ID — the owning application, scoping the attachment definition.
• SESSION_CONTEXT_FIELD — the context field used to bind an attachment to the current form session; this is the column most relevant to the "session_context_field" search.
• ENABLED_FLAG — activates or deactivates the attachment-function definition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns.

Common Use Cases and Queries

Typical uses include auditing attachment-enabled functions, identifying which session context field ties attachments to a form, and validating configuration before enabling attachments in a custom form. Because USER_FUNCTION_NAME is derived via a package call, queries benefit from filtering on indexed base columns such as APPLICATION_ID or ENABLED_FLAG rather than on the derived column.

List enabled attachment functions for an application:

SELECT attachment_function_id, function_type, function_name,
       user_function_name, session_context_field, enabled_flag
  FROM apps.fnd_attachment_functions_vl
 WHERE application_id = :app_id
   AND enabled_flag = 'Y';

Locate attachment definitions keyed to a session context field:

SELECT attachment_function_id, function_name, user_function_name,
       session_context_field
  FROM apps.fnd_attachment_functions_vl
 WHERE session_context_field IS NOT NULL
 ORDER BY attachment_function_id;

Resolve the display name for a specific form function and inspect its audit trail:

SELECT attachment_function_id, user_function_name, session_context_field,
       created_by, creation_date, last_updated_by, last_update_date
  FROM apps.fnd_attachment_functions_vl
 WHERE function_type = :type
   AND function_name = :name;

These patterns support reconciliation of attachment metadata against deployed forms and provide the foundation for customization, diagnostics, and migration scripts.