Results for “audit_enabled_flag”

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

Overview

FND_FORM is a core Oracle Application Object Library (FND) registration table owned by the APPLSYS schema. It stores the master list of application forms registered with Oracle Application Object Library in Oracle E-Business Suite 12.1.1 and 12.2.2. Every Oracle Forms-based screen that a user can invoke — whether reached through a menu function, a responsibility, or a direct navigation path — is represented by a row in this table. Each row associates a single form with the owning application, allowing the framework to resolve form identity, ownership, and audit attributes consistently across the EBS instance.

Because the table defines the identity of each registered form and is referenced by several dependent tables (function attachments, form functions, translations, and login responsibility forms), the ETRM relationship data classifies FND_FORM as hub-leaning in a heuristic Data Vault sense. In other words, it behaves as a business hub holding the durable business key (application and form identity), with surrounding tables acting as dependent satellites or links. This classification is a modeling suggestion derived from the foreign-key topology, not a physical implementation requirement.

Key Information Stored

The table contains 10 documented columns. The most significant are:

• APPLICATION_ID — Identifies the owning application (for example, FND or another registered product). Part of the composite primary key and a foreign key to FND_APPLICATION.
• FORM_ID — The internal numeric identifier assigned to the form. Together with APPLICATION_ID it forms the surrogate primary key FND_FORM_PK.
• FORM_NAME — The internal form module name used by the runtime to locate the .fmx/.fmb file. This is a business-key candidate, captured by unique index FND_FORM_U2 (FORM_NAME, APPLICATION_ID, ZD_EDITION_NAME).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard "Who" audit columns maintained by the framework for row-level change tracking.
• AUDIT_ENABLED_FLAG — Indicates whether row-level auditing is enabled for the form registration.
• ZD_EDITION_NAME — The edition indicator used for online patching (Edition-Based Redefinition) in 12.2.x; it is part of both unique indexes and disambiguates rows across editions. In 12.1.1 this column is not populated.

The primary key FND_FORM_PK (APPLICATION_ID, FORM_ID) is the surrogate identifier, while FND_FORM_U1 (APPLICATION_ID, FORM_ID, ZD_EDITION_NAME) and FND_FORM_U2 (FORM_NAME, APPLICATION_ID, ZD_EDITION_NAME) represent the business-key candidates enforced by the database.

Common Use Cases and Queries

DBAs and developers query FND_FORM to reconcile registered forms against the file system, to audit custom form registrations, and to troubleshoot navigation or menu failures. A typical lookup joins the table to FND_APPLICATION to resolve a readable application name:

• Find a form by name: SELECT form_id, application_id, form_name FROM applsys.fnd_form WHERE form_name = :form_name;
• List all forms for an application: SELECT f.form_name, a.application_name FROM applsys.fnd_form f, applsys.fnd_application a WHERE f.application_id = a.application_id AND a.application_short_name = 'FND';
• Identify forms referenced by functions: join FND_FORM_FUNCTIONS on (APPLICATION_ID, FORM_ID) to see which menu functions invoke each form.
• Reconcile custom registrations: filter on CREATION_DATE or LAST_UPDATED_BY to isolate forms added outside standard patching cycles.

These queries support migration validation, patch-impact analysis, and access reviews where responsibility-to-form mappings (via FND_LOGIN_RESP_FORMS and FND_FORM_FUNCTIONS) must be traced.

Related Objects

FND_FORM participates in a well-defined referential network:

• FND_APPLICATION — Parent table; FND_FORM.APPLICATION_ID references FND_APPLICATION.APPLICATION_ID.
• FND_FORM_FUNCTIONS — Child table; references (APPLICATION_ID, FORM_ID), defining functions that invoke the form.
• FND_FORM_TL** — Translated/display metadata keyed by (APPLICATION_ID, FORM_ID).
• FND_ATTACHMENT_FUNCTIONS — Links attachment functions to forms via (APPLICATION_ID, FUNCTION_ID); indirectly dependent on the form registry.
• FND_LOGIN_RESP_FORMS — References (FORM_APPL_ID, FORM_ID), controlling which forms appear at login for a responsibility.